00101-00149: Multi-threaded Server

This section lists message generated by the multi-threaded server.

Cause:	An application made reference to unknown or inaccessible data.

Action:	Handle this condition within the application or make appropriate modifications to the application code.

Note	If the application uses Oracle-mode SQL instead of ANSI-mode SQL, ORA-01403. will be generated instead of ORA-00100.

ORA-00101 invalid specification for initialization parameter MTS_DISPATCHERS

Cause:	The syntax for the MTS_DISPATCHERS parameter is incorrect.

Action:	Enter the MTS_DISPATCHERS parameter into the initialization parameter file with the correct syntax and then shut down and restart the instance.

ORA-00102 network protocol str cannot be used by the dispatchers

Cause:	The network specified in MTS_DISPATCHERS initialization parameter does not have the functionality required by the dispatchers.

Action:	Refer to your Oracle7 operating system-specific documentation for network protocols supported by the dispatchers.

ORA-00103 invalid network protocol; reserved for use by dispatchers

Cause:	The network specified in SQL*Net CONNECT string is reserved for use by the dispatchers.

Action:	Specify other network protocols in the CONNECT string.

ORA-00104 deadlock detected; all public servers blocked waiting for resource

Cause:	This message occurs when a client locks a resource and the maximum number of shared servers are taken by other clients who are requesting a locked resource. The original client is unable to get a shared server and cannot release the lock on the resource.

Action:	The system automatically starts up new servers to break the deadlock until the number of servers reaches the value specified in MTS_MAX_SERVERS. If this problem occurs frequently, ensure more shared servers will be available at the next restart of the instance by increasing the value of the initialization parameter MTS_SERVERS or MTS_MAX_SERVERS.

ORA-00105 dispatching mechanism not configured to support network protocol

Cause:	The ALTER SYSTEM SET MTS_DISPATCHERS command was used to alter a set of dispatchers for a network protocol that is not specified in the initialization parameter file.

Action:	Do either of the following:

• Include the network protocol in the MTS_DISPATCHERS initialization parameter and restart the system.

• Use the ALTER SYSTEM SET MTS_DISPATCHERS command with a network protocol that exists in the initialization parameter file.

Cause:	An attempt was made to start up or shut down an instance while connected to a shared server process via a dispatcher.

Action:	Reconnect to the database using a dedicated server.

ORA-00107 failed to connect to network listener process

Cause:	Usually caused by the fact that the network listener process has not been started.

Action:	Check for the following:

• The network configuration file is not set up correctly.

• The client side address is not specified correctly.

• The listener initialization parameter file is not set up correctly.

Cause:	The network protocol used by the dispatcher does not support asynchronous operations.

Action:	Contact customer support.

ORA-00111 Warning: maximum number of servers is only num; adding num servers

Cause:	An attempt was made to start more shared server processes than the number allowed by the initialization parameter MTS_MAX_SERVERS. The actual number of shared servers started is specified in the message.

Action:	If more shared server processes are required, increase the initialization parameter MTS_MAX_SERVERS and restart the instance.

ORA-00112 only created up to num maximum specified dispatchers

Cause:	An attempt was made to start up more dispatchers than the maximum number specified by the initialization parameter MTS_MAX_DISPATCHERS.

Action:	If more dispatchers are required, increase MTS_MAX_DISPATCHERS, restart the instance, and add dispatchers using the ALTER SYSTEM MTS_DISPATCHERS command.

ORA-00113 protocol name string is too long

Cause:	A protocol name specified in the MTS_DISPATCHERS initialization parameter is too long.

Action:	Use a valid protocol name for the MTS_DISPATCHERS initialization parameter.

ORA-00114 missing value for initialization parameter MTS_SERVICE

Cause:	There is no value for the MTS_SERVICE initialization parameter, nor for the DB_NAME parameter.

Action:	Add an MTS_SERVICE or DB_NAME definition to the initialization parameter file. By default, MTS_SERVICE is the value of DB_NAME unless MTS_SERVICE 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 MTS_SERVICE name is too long

Cause:	The service name specified in the MTS_SERVICE initialization parameter is too long.

Action:	Use a shorter name for the MTS_SERVICE value (maximum is 255 characters).

ORA-00117 value out of range for the MTS_SERVERS system parameter

Cause:	The value of the MTS_SERVERS parameter is incorrect.

Action:	The MTS_SERVERS parameter must be from 0 to MTS_MAX_SERVERS.

ORA-00118 value out of range for MTS_DISPATCHERS system parameter

Cause:	The value of the MTS_DISPATCHERS parameter is incorrect.

Action:	The sum of all MTS_DISPATCHERS values must be from 0 to MTS_MAX_DISPATCHERS.

ORA-00119 invalid specification for system parameter MTS_LISTENER_ADDRESS

Cause:	The syntax for the MTS_LISTENER_ADDRESS is incorrect.

Action:	Refer to the Oracle7 Server Administrator's Guide for the correct syntax.

ORA-00120 dispatching mechanism not enabled or installed

Cause:	Either the dispatching mechanism is not enabled or the Oracle executable image is not installed with the dispatching mechanism.

Action:	Refer to the Oracle7 Server Administrator's Guide and your Oracle7 operating system-specific documentation for procedures for starting and configuring the dispatcher processes.

ORA-00121 MTS_SERVERS specified without MTS_DISPATCHERS

Cause:	A definition for MTS_SERVERS was specified in the INIT.ORA file, but no definition for MTS_DISPATCHERS was specified. If no value is specified for MTS_DISPATCHERS, shared servers will not be used.

Action:	Add a definition for MTS_DISPATCHERS in the INIT.ORA file. If you do not intend to use shared servers, remove the MTS_SERVERS definition.

ORA-00122 cannot initialize network configuration

Cause:	Oracle could not initialize SQL*Net Version 2.

Action:	See accompanying messages.

ORA-00123 idle public server terminating

Cause:	Too many idle servers were waiting on the common queue.

Action:	This is used internally, no action required.

ORA-00124 MTS_DISPATCHERS specified without MTS_MAX_SERVERS

Cause:	A definition for MTS_DISPATCHERS was specified in the INIT.ORA file, but MTS_MAX_SERVERS was specified as zero.

Action:	Specify MTS_MAX_SERVERS to be greater than zero.