ORA-00123: idle public server terminating
Cause: Too many idle servers were waiting on the common queue.
Action: This error is used internally, no action is required.
Category Archives: ORA Database Error Messages
ORA-00122: cannot initialize network configuration
ORA-00122: cannot initialize network configuration
Cause: ORACLE could not initialize SQL*Net version 2.
Action: Check the error stack for detailed information.
ORA-00121: SHARED_SERVERS specified without DISPATCHERS
ORA-00121: SHARED_SERVERS specified without DISPATCHERS
Cause: A definition for SHARED_SERVERS was specified in the initialization parameter file, but no definition for DISPATCHERS was specified. Without a value for DISPATCHERS, shared servers will never be used.
Action: Add a definition for DISPATCHERS in the initialization parameter file (or remove the definition for SHARED_SERVERS, if shared servers are not being used).
ORA-00120: dispatching mechanism not enabled or installed
ORA-00120: dispatching mechanism not enabled or installed
Cause: Either the dispatching mechanism was not enabled or the Oracle executable image was not installed with the dispatching mechanism.
Action: Refer to the >Oracle9i Database Administrator’s Guide and your operating system-specific documentation for procedures for starting and configuring the dispatcher process.
ORA-00119: invalid specification for system parameter string
ORA-00119: invalid specification for system parameter string
Cause: The syntax for the specified parameter is incorrect.
Action: Refer to the Oracle Reference Manual for the correct syntax.
ORA-00118: Only one of PROTOCOL, ADDRESS or DESCRIPTION may be specified
ORA-00118: Only one of PROTOCOL, ADDRESS or DESCRIPTION may be specified
Cause: More than one of PROTOCOL, ADDRESS or DESCRIPTION was specified.
Action: Use only one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION to specify the listening address for dispatchers.
ORA-00117: PROTOCOL, ADDRESS or DESCRIPTION must be specified
ORA-00117: PROTOCOL, ADDRESS or DESCRIPTION must be specified
Cause: PROTOCOL, ADDRESS or DESCRIPTION was not specified.
Action: Use one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION to specify the listening address for dispatchers.
ORA-00116: SERVICE_NAMES name is too long
ORA-00116: SERVICE_NAMES name is too long
Cause: A service name specified in the SERVICE_NAMES system parameter is too long.
Action: Use a shorter name in the SERVICE_NAMES value (<= 255 chars).
ORA-00115: connection refused; dispatcher connection table is full
ORA-00115: connection refused; dispatcher connection table is full
Cause: A connection request was refused by a dispatcher because the dispatcher cannot support any more connections.
Action: Connect to a different dispatcher, or use a dedicated server.
ORA-00114: missing value for system parameter SERVICE_NAMES
ORA-00114: missing value for system parameter SERVICE_NAMES
Cause: No value was specified for the SERVICE_NAMES system parameter, nor for the DB_NAME parameter.
Action: Add an SERVICE_NAMES or DB_NAME definition to the INIT.ORA file. By default, SERVICE_NAMES is the value of DB_NAME unless SERVICE_NAMES is explicitly specified.