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.


ORA-00201 controlfile version string incompatible with ORACLE version string

Cause: The control file was created by incompatible software.

Action: Either restart with a compatible software release or use CREATE CONTROLFILE to create a new control file that is compatible with this release.


ORA-00202 controlfile: 'string'

Cause: This message reports the name file involved in other messages.

Action: See associated error messages for a description of the problem.


ORA-00203 using the wrong controlfiles

Cause: The mount ID in the control file is not the same as the mount ID in the control file used by the first instance to mount this database. The control files are for the same database but they are not the same files. Most likely one instance is using a backup control file.

Action: Check that the correct control files were specified.


ORA-00204 error in reading (block string, # blocks string) of controlfile

Cause: A disk I/O failure was detected on reading the control file.

Action: Check that the disk is online. If it is not, bring it online and shut down and restart Oracle. If it is online, then look for operating system reasons for Oracle's inability to read the disk or control file. See the Oracle9i Database Administrator's Guide for information on recovering from the loss of a control file. See also your operating system-specific Oracle documentation.


ORA-00205 error in identifying controlfile, check alert log for more info

Cause: The system could not find a control file of the specified name and size.

Action: One of the following:

Check that the proper control file name is referenced in the CONTROL_FILES initialization parameter in the initialization parameter file and try again.
When using mirrored control files, that is, more than one control file is referenced in the initialization parameter file, remove the control file name listed in the message from the initialization parameter file and restart the instance. If the message does not recur, remove the problem control file from the initialization parameter file and create another copy of the control file with a new file name in the initialization parameter file.

ORA-00206 error in writing (block string, # blocks string) of controlfile

Cause: A disk I/O failure was detected on writing to the control file.

Action: Check that the disk is online. If it is not, bring it online and shut down and restart Oracle. If it is online, then look for operating system reasons for Oracle's inability to write to the disk or control file. See the Oracle9i Database Administrator's Guide for information on recovering from the loss of a control file. See also your operating system-specific Oracle documentation.


ORA-00207 controlfiles are not for the same database

Cause: The database ID in the control file is not the same as the database ID in the control file used by the first instance to mount this database. Most likely one of the mounts used the wrong control file or there are two databases with the same name.

Action: Check that the control file is for the correct database and is not an old version. When using multiplexed control files, that is, more than one control file is referenced in the initialization parameter file, remove the control file name listed in the message from the initialization parameter file and restart the instance. If the message does not recur, remove the problem control file from the initialization parameter file and create another copy of the control file using a new file name in the initialization parameter file.


ORA-00208 number of controlfile names exceeds limit of string

Cause: An attempt was made to use more control files than Oracle supports.

Action: Shut down Oracle. Reduce the number of control files specified in the CONTROL_FILES parameter in the initialization parameter file, and restart Oracle. Delete unused files.


ORA-00209 control file blocksize mismatch, check alert log for more info

Cause: The block size in the control file header does not match the size specified in the DB_BLOCK_SIZE parameter.

Action: Reduce the block size to the amount specified in the message and try again.


ORA-00210 cannot open the specified controlfile

Cause: Cannot open the control file.

Action: Check to make sure the control file exists and is not locked by some other program.


ORA-00211 controlfile does not match previous controlfiles

Cause: A control file was specified that belongs to another database.

Action: Find and install the correct control file.


ORA-00212 block size string below minimum required size of string bytes

Cause: The block size specified was too small. Space for the system overhead is required.

Action: Specify a larger block size and retry the operation.


ORA-00213 cannot reuse controlfile; old file size string, string required

Cause: To reuse a control file, it must be the same size as the one previously used.

Action: Either do not specify REUSE, or specify a matching combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses in the CREATE DATABASE or CREATE CONTROLFILE statement.


ORA-00214 controlfile 'string' version string inconsistent with file 'string' version string

Cause: An inconsistent set of control files, datafiles, and redo log files was used.

Action: Use a consistent set of control files, datafiles, and redo log files. That is, all the files must be for the same database and from the same time period.


ORA-00215 must be at least one controlfile

Cause: No control file is specified or the control file specified does not exist.

Action: Specify at least one valid control file and retry the operation.


ORA-00216 controlfile could not be resized for migration from 8.0.2

Cause: Control files created by release 8.0.2 were missing some records. These records are automatically added by resizing the control file when attempting to run a later release. The resize failed.

Action: Look in the alert log for the reason that the resize failed. If it can be fixed by giving the control file more space, then do that. Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file.


ORA-00217 controlfile could not be resized for migration from 9.0.1

Cause: Controlfiles created by release 9.0.1 were missing some records. These records are automatically added by resizing the controlfile when attempting to run a later release. The resize failed.

Action: Look in the alert log for the reason the resize failed. If it can be fixed by giving the controlfile more space, then do that. Otherwise, use the CREATE CONTROLFILE script dumpped to the trace file to create a new controlfile.


ORA-00218 block size string of controlfile does not match DB_BLOCK_SIZE (string)

Cause: The block size as stored in the control file header is different from the value of the initialization parameter DB_BLOCK_SIZE. This might be due to an incorrect setting of DB_BLOCK_SIZE, or else might indicate that the control file has either been corrupted or belongs to a different database.

Action: Restore a good copy of the control file.


ORA-00219 required controlfile size string exceeds maximum allowable size string

Cause: An invocation of CREATE DATABASE, CREATE CONTROLFILE, cfileCalcSizeList, or cfileCalcSizeArray was executed specifying a combination of parameters that would require the control file size in blocks to exceed the maximum allowable value.

Action: In the case of CREATE DATABASE or CREATE CONTROLFILE, use a different combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses. In the case of cfileCalcSizeList() or cfileCalcSizeArray(), use a different combination of record type counts.


ORA-00220 controlfile not mounted by first instance, check alert log for more info

Cause: The specified control file has a different mount ID than the other control files that are being mounted. This means that the first instance to mount the database did not use this control file.

Action: Find and install the correct control file.


ORA-00221 error on write to controlfile

Cause: An error occurred when writing to one or more of the control files.

Action: See accompanying messages.


ORA-00222 operation would reuse name of a currently mounted controlfile

Cause: The file name supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of the specified currently mounted control file.

Action: Retry the operation with a different file name.


ORA-00223 convert file is invalid or incorrect version

Cause: An Oracle7 to Oracle8 convert file contains invalid data or was created with an different version of the migration utility. This error can also be caused by incorrect ORACLE_HOME environment variable when the ALTER DATABASE CONVERT command is issued.

Action: Use a correct version of the convert file or regenerate it with the migration utility. Make sure that the migration utility is the same version as the Oracle8 RDBMS executable and that the ORACLE_HOME environment variable is properly set.


ORA-00224 controlfile resize attempted with illegal record type (string)

Cause: An attempt was made to expand or shrink the control file by calling cfileResizeSection using an invalid value for the RECORD_TYPE parameter.

Action: Use a value for the RECORD_TYPE parameter that specifies a valid record type other than type 0 (valid range is 1 to 16).


ORA-00225 expected size string of controlfile differs from actual size string

Cause: The expected size of the control file as stored in its header was different than the actual operating system file size. This usually indicates that the control file was corrupted.

Action: Restore a good copy of the control file.


ORA-00226 operation disallowed while alternate controlfile open

Cause: The attempted operation could not be executed at this time because this process had an alternate control file open for fixed table access.

Action: Retry the operation after calling cfileUseCurrent.


ORA-00227 corrupt block detected in controlfile: (block string, # blocks string)

Cause: A block header corruption or checksum error was detected on reading the control file.

Action: Use the CREATE CONTROLFILE or RECOVER DATABASE USING BACKUP CONTROLFILE command.


ORA-00228 length of alternate controlfile name exceeds maximum of string

Cause: The specified file name, which was supplied as a parameter to cfileSetSnapshotName or cfileUseCopy, exceeds the maximum file name length for this operating system.

Action: Retry the operation with a shorter file name.


ORA-00229 operation disallowed: already hold snapshot controlfile enqueue

Cause: The attempted operation cannot be executed at this time because this process currently holds the snapshot control file enqueue.

Action: Retry the operation after calling cfileUseCurrent to release the snapshot control file enqueue.


ORA-00230 operation disallowed: snapshot controlfile enqueue unavailable

Cause: The attempted operation cannot be executed at this time because another process currently holds the snapshot control file enqueue.

Action: Retry the operation after the concurrent operation that is holding the snapshot control file enqueue terminates.


ORA-00231 snapshot controlfile has not been named

Cause: During an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot, it was detected that no file name for the snapshot control file had previously been specified.

Action: Specify a name for the snapshot control file by calling cfileSetSnapshotName.


ORA-00232 snapshot controlfile is nonexistent, corrupt, or unreadable

Cause: The snapshot control file was found to be non-existent, corrupt, or unreadable during an invocation of cfileUseSnapshot.

Action: Call cfileMakeAndUseSnapshot again (or for the first time).


ORA-00233 copy controlfile is corrupt or unreadable

Cause: The specified copy control file was found to be corrupt or unreadable during an invocation of cfileUseCopy.

Action: Before retrying cfileUseCopy, use the ALTER DATABASE BACKUP CONTROLFILE command and specify the same file name that was specified for cfileUseCopy.


ORA-00234 error in identifying or opening snapshot or copy controlfile

Cause: A snapshot or copy control file of the specified name could not be found or opened during an invocation of cfileUseSnapshot, cfileMakeAndUseSnapshot, or cfileUseCopy.

Action: Re-create the snapshot or copy control file using cfileMakeAndUseSnapshot or ALTER DATABASE BACKUP CONTROLFILE, respectively.


ORA-00235 controlfile fixed table inconsistent due to concurrent update

Cause: Concurrent update activity on a control file caused a query on a control file fixed table to read inconsistent information.

Action: Retry the operation.


ORA-00236 snapshot operation disallowed: mounted controlfile is a backup

Cause: Attempting to invoke cfileSetSnapshotName, cfileMakeAndUseSnapshot, or cfileUseSnapshot when the currently mounted control file is a backup control file.

Action: Mount a current control file and retry the operation.


ORA-00237 snapshot operation disallowed: controlfile newly created

Cause: An attempt to invoke cfileMakeAndUseSnapshot with a currently mounted control file that was newly created with CREATE CONTROLFILE was made.

Action: Mount a current control file and retry the operation.


ORA-00238 operation would reuse a filename that is part of the database

Cause: The file name supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of a file that is currently part of the database.

Action: Retry the operation with a different file name.


ORA-00250 archiver not started

Cause: An attempt was made to stop automatic archiving, but the archiver process was not running.

Action: No action is required.