Oracle Application Server 10.1.3.4 User Manual page 99

Action: Check the network connection by trying to ping the host computer or run
FTP or Telnet to or from it.
C045: Failed to create a service thread
Cause: The server failed to create a thread to service a client request.
Action: A system or process quota limit has been exceeded. Either increase the
quota or lower the Clients per server limit field value in the WS Info.
section of the daemon configuration.
"General"
See Also:
C047: %s out of memory
Cause: Not enough memory was available to Oracle Connect to complete a
requested operation.
Action: Terminate unnecessary processes running on the server.
Action: Add more memory to the system.
Action: Allow the process to use more memory.
Action: Limit the number of processes the daemon may start. If the demand for
servers exceeds the number of available servers, clients get a message telling them
the maximum number of servers has been reached and asking them to try again
later.
C066: Communication error with the server%s
Cause: Connection to the Oracle Connect daemon or server failed, or an
established session with a server has failed.
Action: Check the remote computer definition in the oc4j-ra-xml file.
Action: Check that the daemon is up on the IBM z/OS platform. Use the Status
option in the Runtime Manager perspective.
Action: In case of a network problem, check the network connection by trying to
ping the host computer or run ftp or telnet to or from it.
C067: Unexpected error occurred in server function %s
Cause: One of the server functions has exited with an exception (such as an
abend, or an Invalid Instruction).
Action: Contact Oracle Support Services.
C068: Fail to login daemon
Cause: The daemon is not running on the server computer.
Action: Use the Status in Oracle Studio Runtime Manager perspective to check
whether a daemon is running on the server
Action: Have the system administrator reinstall Oracle Connect on the server.
C069: Fail to get server
Cause: The Oracle Connect daemon on the server computer could not start a
server process to serve the client. A separate message provides more detail on why
the server process could not start.
Action: There are many possible causes of this error. If the cause is not clear from
the related message, see the Oracle Connect daemon log file on the server
on page C-7.
Troubleshooting OracleAS Adapter for IMS/DB 7-13
Resolving Specific Errors