ORA-00101: invalid specification for system parameter DISPATCHERS
Cause: The syntax for the DISPATCHERS parameter is incorrect.
Action: Refer to the manual for correct syntax.
ORA-00102: network protocol string cannot be used by dispatchers
Cause: The network specified in DISPATCHERS does not have the functionality required by the dispatchers.
Action: Refer to the manual on network protocols supported by the dispatchers.
ORA-00103: invalid network protocol; reserved for use by dispatchers
Cause: The network specified in the SQL*Net connect string is reserved for use by the dispatchers.
Action: Specify other network protocols in the connection string.
ORA-00104: deadlock detected; all public servers blocked waiting for resources
Cause: All available public servers are servicing requests that require resources locked by a client which is unable to get a public server to release the resources.
Action: Increase the limit for the system parameter MAX_SHARED_SERVERS as the system will automaticaly start up new servers to break the deadlock until the number of servers reaches the value specified in MAX_SHARED_SERVERS.
ORA-00105: too many dispatcher configurations
Cause: Too many dispatcher configurations have been specified. No more can be added.
Action: Consolidate the dispatcher configurations if possible.
ORA-00106: cannot startup/shutdown database when connected to a dispatcher
Cause: An attempt was made to startup/shutdown database when connected to a shared server via a dispatcher.
Action: Re-connect as user INTERNAL without going through the dispatcher. For most cases, this can be done by connect to INTERNAL without specifying a network connect string.
ORA-00107: failed to connect to ORACLE listener process
Cause: Most likely due to the fact that ORACLE listener has not been started.
Action: Start ORACLE listener if it has not been started. Or else contact your ORACLE representative.
ORA-00108: failed to set up dispatcher to accept connection asynchronously
Cause: Most likely due to the fact that the network protocol used by the the dispatcher does not support aynchronous operations.
Action: Contact your ORACLE representative.
ORA-00109: invalid value for attribute string: string
Cause: The value specified for the attribute was incorrect.
Action: Refer to the manual for the proper values.
ORA-00110: invalid value string for attribute string, must be between string and string
Cause: The value specified for the attribute was incorrect.
Action: Specify a value within the range allowed.
ORA-00111: invalid attribute string
Cause: The specified attribute was not recognized.
Action: Refer to the manual for the proper keyword to use to specify a dispatcher attribute.
ORA-00112: value of string is null
Cause: The attribute was specified with no value.
Action: Specify a non-null value.
ORA-00113: protocol name string is too long
Cause: A protocol name specified in the DISPATCHERS system parameter is too long.
Action: Use a valid protocol name for the DISPATCHERS value.
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.
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-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-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-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-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-00122: cannot initialize network configuration
Cause: ORACLE could not initialize SQL*Net version 2.
Action: Check the error stack for detailed information.
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.
ORA-00125: connection refused; invalid presentation
Cause: The PRESENTATION in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported.
Action: Correct the PRESENTATION specified in the TNS address.
ORA-00126: connection refused; invalid duplicity
Cause: The DUPLICITY in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported.
Action: Correct the DUPLICITY specified in the TNS address.
ORA-00127: dispatcher string does not exist
Cause: There is currently no dispatcher running with the specified name.
Action: Retry with a name of the form “D###” denoting an existing dispatcher process.
ORA-00128: this command requires a dispatcher name
Cause: Wrong syntax for ALTER SYSTEM SHUTDOWN
Action: Use correct syntax: ALTER SYSTEM SHUTDOWN [ IMMEDIATE ] ‘dispatcher name’
ORA-00129: listener address validation failed ‘string’
Cause: An error was encountered while validating the listener address.
Action: Resolve error or contact your ORACLE representative.
ORA-00130: invalid listener address ‘string’
Cause: The listener address specification is not valid.
Action: Make sure that all fields in the listener address (protocol, port, host, key, …) are correct.
1,285 views last month, 1 views today