Oracle Audio Technologies B31003-01 User Manual
Page 22
Resolving Specific Errors
3-8 Oracle Application Server Adapter for IMS/TM User’s Guide
C010: Anonymous server logins are not allowed.
Cause:
Internal error.
Action:
Contact Oracle Support Services.
C011: Client has already timed out.
Cause:
A server process was started on behalf of a client and the client has timed
out before the server completed its startup.
Action:
Increase the Connect timeout value for the server workspace in the WS
Info. section of the daemon configuration.
C012: Invalid username/password.
Cause:
Invalid username/password supplied when logging on to the daemon.
Action:
See the daemon log file for the reason that the username/password were
not accepted.
Action:
Edit the user profile in Oracle Studio to specify a valid username and
password for the IBM OS/390 or z/OS platform.
Action:
Make sure the daemon is started from an APF-authorized account that is
allowed to check for system usernames and passwords.
C014: Client connection limit reached - try later.
Cause:
The maximum number of server processes for the workspace has been
reached, and none of the active servers could accept the client connection.
Action:
Increase the value of the Number of sub-tasks in the WS Server
section of the daemon configuration.
Action:
Try running the command later.
C015: Failed to start server process.
Cause:
The Oracle Connect daemon failed to start a server process or the started
server failed upon starting up.
Action:
See the daemon and server logs for the reason the server did not start. For
example, you might receive an message with a reason specified in the log file
similar to the following: [C015] Failed to start NAVIGATOR server
process: No server account name defined for anonymous client;
code: -1601: SQL code: 0
Action:
If you use impersonation, check the user profile on the client. Also see
C069.
See Also:
See Also:
"Setting Up Run-time User Access to the IBM OS/390
See Also: