00001 - 00600 Generic Oracle WebServer Configuration Messages

Cause:	The file may not exist or may not be readable to the signalling program.

Action:	Verify the file's existence in the file-system. Check file and directory permissions and ownership, as well as the ownership of the signalling process.

OWS--00002 component: error reading file name

Cause:	Usually an operating system error. If the problem had been file permissions or non-existence, error 1 would have been signalled.

Action:	Check your operating system log for errors.

OWS--00003 component: error writing file name

Cause:	Usually an operating system error. If the problem had been file permissions or non-existence, error 1 would have been signalled.

Action:	Check your operating system log for errors.

OWS--00010 component: file format error when reading name

Cause:	The signalling program expected a specific file format which it did not find.

Action:	Analyze the file for incorrect formatting.

OWS--00011 Installation not completed. Root.sh must be run

Cause:	The signalling program checked if root.sh completed successfully.

Action:	Run root.sh as indicated by your installation guide.

OWS--00020 component out of memory when requesting number bytes

Cause:	The operating system was not able to supply the requested amount of memory.

Action:	Reduce the number of running programs on the machine and retry the operation.

OWS--00600 component internal error, arguments [arg1][arg2][arg3][arg4][arg5]

Cause:	This is the generic internal error number for Oracle WebServer program exceptions. This indicates that a process has encountered an exceptional condition.

Action:	Report as a bug. The first argument is the internal error number