Below are the list of Oracle ORA message from ORA-00101 to ORA-00200. You can find the cause and actions from each of the message accordingly.
| ORA MESSAGE | CAUSE / ACTION |
|---|---|
| ORA-00101 invalid specification for system parameter DISPATCHERS | Cause: The syntax for the DISPATCHERS initialization parameter is incorrect. Action: Enter the DISPATCHERS initialization parameter into the initialization parameter file with the correct syntax and then shut down and restart the instance. |
| 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 your Oracle 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 the Net8 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 automatically start new servers to break the deadlock until the number of servers reaches the value specified in MAX_SHARED_SERVERS. |
| ORA-00105 dispatching mechanism not configured for network protocol string | Cause: An attempt was made to alter the dispatcher's configuration for a network protocol that was not specified in the initialization parameter file. Action: Do one of the following: - Include the network protocol in the definition for the DISPATCHERS initialization parameter and restart the system. - Use the ALTER SYSTEM SET DISPATCHERS statement with a network protocol that exists in the initialization parameter file. |
| ORA-00106 cannot startup/shutdown database when connected to a dispatcher | Cause: An attempt was made to start or shut down an instance while connected to a shared server via a dispatcher. Action: Reconnect 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 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. |
| ORA-00108 failed to set up dispatcher to accept connection asynchronously | Cause: The network protocol used by the dispatcher does not support asynchronous operations. Action: Contact Oracle Support Services. |
| ORA-00111 not all servers started because number of servers is limited to string | Cause: An attempt was made to start more servers than the maximum number specified by the system parameter MAX_SHARED_SERVERS. Action: Increase the value of the MAX_SHARED_SERVERS initialization parameter as needed or re-issue the ALTER SYSTEM SET SHARED_SERVERS statement with an appropriate number of servers. |
| ORA-00112 only created up to string (maximum specified) dispatchers | Cause: An attempt was made to start more dispatchers than the maximum number specified by the system parameter MAX_DISPATCHERS. Action: Increase the value of the MAX_DISPATCHERS initialization parameter as needed. |
| ORA-00113 protocol name string is too long | Cause: A protocol name specified in the DISPATCHERS initialization 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 initialization parameter nor for the DB_NAME parameter. Action: Add an SERVICE_NAMES or DB_NAME definition to the initialization parameter 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: The service name specified in the SERVICE_NAMES initialization parameter is too long. Action: Use a shorter name for the SERVICE_NAMES value (less than or equal to 255 characters). |
| ORA-00117 value out of range for system parameter SHARED_SERVERS | Cause: The specified value of the SHARED_SERVERS initialization parameter is incorrect. Action: SHARED_SERVERS must be greater than or equal to 0 and less than or equal to the value of MAX_SHARED_SERVERS. |
| ORA-00118 value out of range for system parameter DISPATCHERS | Cause: The value of the DISPATCHERS parameter is incorrect. Action: The sum of all DISPATCHERS values must be greater than or equal to 0 and less than or equal to the value of MAX_DISPATCHERS. |
| ORA-00119 invalid specification for system parameter string | Cause: The syntax for the specified parameter is incorrect. Action: Refer to the Oracle9i Database Reference for the correct syntax. |
| 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-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-00122 cannot initialize network configuration | Cause: Oracle could not initialize Net8. Action: See accompanying messages. |
| 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-00124 DISPATCHERS specified without MAX_SHARED_SERVERS | Cause: A definition for DISPATCHERS was specified in the initialization parameter file but MAX_SHARED_SERVERS was specified as zero. Action: Specify MAX_SHARED_SERVERS to be greater than zero. |
| 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 the error or contact Oracle Support Services. |
| 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. |
| ORA-00131 network protocol does not support registration 'string' | Cause: The specified protocol does not support async notification. Action: Refer to the manual for information on supported network protocols. |
| ORA-00132 syntax error or unresolved network name 'string' | Cause: Listener address has syntax error or cannot be resolved. Action: If a network name is specified check that it corresponds to an entry in TNSNAMES.ORA or other address repository as configured for your system. Make sure that the entry is syntactically correct. |
| ORA-00150 duplicate transaction ID | Cause: An attempt was made to start a new transaction with an ID already in use by an existing transaction. Action: Check your application. |
| ORA-00151 invalid transaction ID | Cause: The specified transaction ID does not correspond to an existing valid transaction. Action: Check your application. |
| ORA-00152 current session does not match requested session | Cause: The current session is not the same as the session that was passed into a UPIXADO() call. Action: Check your application. |
| ORA-00153 internal error in XA library | Cause: The XA library could not access thread-specific pointers. Action: Contact Oracle Support Services. |
| ORA-00154 protocol error in transaction monitor | Cause: The transaction monitor returned TMJOIN on an AX_REG call but the transaction was locally suspended. Action: Contact the transaction monitor customer support. |
| ORA-00155 cannot perform work outside of global transaction | Cause: The application tried to perform some work on either an Oracle 7.3 server or an Oracle8 server with local transactions disabled while outside of a global transaction. Action: Check if the application is connected to an Oracle 7.3 server. The Transaction monitor must not return a NULL XID on an AX_REG call when the resource manager is Oracle 7.3. If the application is connected to an Oracle8 server either set nolocal=f in the xa_open string or start a global transaction prior to attempting the work. |
| ORA-00160 global transaction length string is greater than maximum (string) | Cause: An external global transaction ID with a too large length field was passed in. Action: Report the problem to your external transaction coordinator vendor. |
| ORA-00161 transaction branch length string is illegal (maximum allowed string) | Cause: An external transaction branch ID with a length either too large or 0 was passed in. Action: Report the problem to your external transaction coordinator vendor. |
| ORA-00162 external dbid length string is greater than maximum (string) | Cause: An external database name with too large a length field was passed in. Action: Report the problem to your external transaction coordinator vendor. |
| ORA-00163 internal database name length string is greater than maximum (string) | Cause: An internal database name with a too large length field was passed in. Action: Report the problem to your external transaction coordinator vendor. |
| ORA-00164 distributed autonomous transaction disallowed within migratable distributed transaction | Cause: A request was made by the application to start a distributed autonomous transaction when the application was in a migratable distributed transaction. Action: Roll back or commit the current distributed transaction first. |
| ORA-00165 migratable distributed autonomous transaction with remote operation is not allowed | Cause: A request was made by the application to start a migratable distributed autonomous transaction with remote operation. |
| ORA-00200 controlfile could not be created | Cause: It was not possible to create the control file. Action: Check that there is sufficient disk space and no conflicts in file names and try to create the control file again. |
