Oracle Error Messages: 01/04/12

Wednesday, 4 January 2012

ORA-00210: cannot open the specified control file

ORA-00210: cannot open the specified control file

Cause: Cannot open the control file.

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

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

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: Look at the alert log for more information.

ORA-00208: number of control file names exceeds limit of string

ORA-00208: number of control file 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 usused files.

ORA-00207: control files are not for the same database

ORA-00207: control files 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.

ORA-00206: error in writing (block string, # blocks string) of control file

ORA-00206: error in writing (block string, # blocks string) of control file

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

Action: Check if the disk is online, if it is not, bring it online and try a warm start again. If it is online, then you need to recover the disk.

ORA-00205: error in identifying control file, check alert log for more info

ORA-00205: error in identifying control file, check alert log for more info

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

Action: Check that ALL control files are online and that they are the same files that the system created at cold start time.

ORA-00204: error in reading (block string, # blocks string) of control file

ORA-00204: error in reading (block string, # blocks string) of control file

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

Action: Check if the disk is online, if it is not, bring it online and try a warm start again. If it is online, then you need to recover the disk.

ORA-00203: using the wrong control files

ORA-00203: using the wrong control files

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-00202: control file: string

ORA-00202: control file: string

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

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

ORA-00201: control file version string incompatible with ORACLE version string

ORA-00201: control file 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-00200: control file could not be created

ORA-00200: control file 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 filenames and try to create the control file again.

ORA-00166: remote or local nesting level is too deep

ORA-00166: remote or local nesting level is too deep

Cause: Too many remote table operations required a reverse trip back to the local site, for example to execute a local function on a remote table.

Action: Rearrange the query or co-locate the functions with the tables.

ORA-00165: migratable distributed autonomous transaction with remote operation is not allowed

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.

Action: none

ORA-00164: distributed autonomous transaction disallowed within migratable distributed transaction

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-00163: internal database name length string is greater than maximum (string)

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-00162: external dbid length string is greater than maximum (string)

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-00161: transaction branch length string is illegal (maximum allowed string)

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-00160: global transaction length string is greater than maximum (string)

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-00155: cannot perform work outside of global transaction

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-00154: protocol error in transaction monitor

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-00153: internal error in XA library

ORA-00153: internal error in XA library

Cause: The XA library could not access thread-specific pointers.

Action: Contact customer support.

ORA-00152: current session does not match requested session

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-00151: invalid transaction ID

ORA-00151: invalid transaction ID

Cause: The specified transaction ID does not correspond to an existing valid transaction.

Action: Check your application.

ORA-00150: duplicate transaction ID

ORA-00150: duplicate transaction ID

Cause: Attempted to start a new transaction with an ID already in use by an existing transaction.

Action: Check your application.

ORA-00134: invalid DISPATCHERS specification #string

ORA-00134: invalid DISPATCHERS specification #string

Cause: The syntax for the n-th DISPATCHERS specification was incorrect.

Action: Refer to the Oracle Reference Manual for the correct syntax.

ORA-00133: value of string is too long

ORA-00133: value of string is too long

Cause: The value specified for the attribute was too long.

Action: Use shorter names and keywords or remove unneeded blanks.

ORA-00132: syntax error or unresolved network name string

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-00131: network protocol does not support registration string

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-00130: invalid listener address string

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-00129: listener address validation failed string

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-00128: this command requires a dispatcher name

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-00127: dispatcher string does not exist

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-00126: connection refused; invalid duplicity

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-00125: connection refused; invalid presentation

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-00123: idle public server terminating

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-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-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 (lamp;lt;lamp;nbsp;= 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.

ORA-00113: protocol name string is too long

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-00112: value of string is null

ORA-00112: value of string is null

Cause: The attribute was specified with no value.

Action: Specify a non-null value.

ORA-00111: invalid attribute string

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-00110: invalid value string for attribute string, must be between string and string

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-00109: invalid value for attribute string: string

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-00108: failed to set up dispatcher to accept connection asynchronously

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-00107: failed to connect to ORACLE listener process

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-00106: cannot startup or shutdown database when connected to a dispatcher

ORA-00106: cannot startup or shutdown database when connected to a dispatcher

Cause: An attempt was made to startup or 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-00105: too many dispatcher configurations

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-00104: deadlock detected; all public servers blocked waiting for resources

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-00103: invalid network protocol; reserved for use by 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-00102: network protocol string cannot be used by dispatchers

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.