Cause: Normal exit.

Cause: An UPDATE or INSERT statement attempted to insert a duplicate key. For Trusted Oracle configured in DBMS MAC mode, you may see this message if a duplicate entry exists at a different level.

Cause: The current session was requested to set a trace event by another session.

Cause: All session state objects are in use.

Cause: All licenses are in use.

Cause: All process state objects are in use.

Cause: The user session is currently used by others.

Cause: Either the session specified does not exist or the caller does not have the privilege to access it.

Cause: An attempt was made to detach the current session when it contains references to process private memory.

Cause: Trying to login more than once from different processes for ORACLE started in single-process mode.

Cause: Out of memory.

Cause: Missing or invalid session ID string for the current operation.

Cause: Attempted to use ALTER SYSTEM KILL SESSION to kill the current session.

Cause: A privileged user has killed your session and you are no longer logged on to the database.

Cause: The session ID specified in the current operation was not a user session (for example, recursive, etc.).

Cause: The user session ID no longer exists, probably because the session was logged out.

Cause: The session specified in an ALTER SYSTEM KILL SESSION command cannot be killed immediately (because it is rolling back or blocked on a network operation), but it has been marked for kill. This means it will be killed as soon as possible after its current uninterruptable operation is done.

Cause: The session migration password specified in a session creation call was invalid (probably too long).

Cause: An attempt was made to detach or clone the current session and it has an empty migration password. This is not allowed.

Cause: An attempt was made to issue a commit or rollback from a PL/SQL object (procedure, function, package) in a session that has this disabled (by 'alter session disable commit in procedure')

Cause: An attempt was made to go more than the specified number of recursive SQL levels.

Cause: An attempt was made to switch to a session in a different server group. This is not allowed.

Cause: An attempt was made to create a non-migratable session in a server group that is owned by a different user.

Cause: An unexpected error occurred while executing a periodically invoked action.

Cause: The Resource Manager SWITCH_TIME limit was exceeded.

Cause: The Resource Manager SWITCH_TIME limit was exceeded.

Cause: An attempt was made to use an invalid application service.

Cause: Execution of the inter-instance operation failed.

Cause: The user attempted to set timed_statistics to FALSE when statistics_level was not BASIC. timed_statistics is required to be TRUE to collect meaningful statistics when statistics_level is set to TYPICAL or ALL.

Cause: A privileged user terminated your session and you were no longer logged on to the database. Your session will not be replayed by Application Continuity or Transparent Application Failover (TAF).

Cause: An attempt was made to alter the sessions parameter in the root container or non-consolidated database.

Cause: An attempt was made to alter the sessions parameter to a value greater than the root container's session value.

Cause: Could not obtain the operating system resources necessary to cover an oracle enqueue. This is normally the result of an operating system user quota that is too low.

Cause: Usually due to a dead instance.

Cause: Ran out of enqueue resources.

Cause: Ran out of enqueue state objects.

Cause: Interested resource is busy.

Cause: Ran out of DML lock state objects.

Cause: An attempt was made to acquire a DDL lock that is already locked.

Cause: The number of temporary tables equals or exceeds the number of temporary table locks. Temporary tables are often created by large sorts.

Cause: DB_BLOCK_SIZE initialization parameter is wrong for the database being mounted. It does not match the value used to create the database.

Cause: The value of the DB_FILES initialization parameter was exceeded.

Cause: Transactions deadlocked one another while waiting for resources.

Cause: The shared instance being started is using DML locks, and the running instances are not, or vice-versa.

Cause: The instance was started with DML_LOCKS = 0, and the statement being executed needs a full-table lock (S, X, or SSX).

Cause: The number of log files specificied exceeded the maximum number of log files supported in this release.

Cause: An initialization parameter was set to a value that required allocating more contiguous space than can be allocated on this operating system.

Cause: The FIXED_DATE string was not in date format yyyy-mm-dd:hh24:mi:ss.

Cause: The specified SID contained an illegal character or the SID specified was too long, which cannot occur in an SPFILE setting. Illegal characters include ,#"'=() and whitespace.

Cause: The value for the initialization parameter is invalid.

Cause: The value for the initialization parameter is invalid.

Cause: A command was issued that tried to lock the table indicated in the message. Examples of commands that can lock tables are: LOCK TABLE, ALTER TABLE ... ADD (...), and so on.

Cause: An invalid debugger command was specified.

Cause: An invalid process number was specified.

Cause: An invalid process was specified.

Cause: An incorrect number of arguments was specified.

Cause: No debug process has been specified.

Cause: The specified process was not logged on to the current instance.

Cause: An attempt was made to invoke a dump that does not exist.

Cause: An attempt was made to invoke an invalid dump.

Cause: An attempt was made to dump a variable by name on a system that does not support this feature.

Cause: An attempt was made to dump a variable that does not exist.

Cause: An attempt was made to dump an invalid global area.

Cause: An attempt was made to read/write an invalid memory address range.

Cause: An invalid length was specified for the POKE command.

Cause: Even though there may be SGA corruptions, the SGA was mapped.

Cause: An attempt was made to dump an invalid global area.

Cause: An invalid attempt was made to dump the current call heap.

Cause: An invalid attempt was made to dump the user call heap.

Cause: Cluster database command issued for non cluster database ORADEBUG command.

Cause: Debug command issued on shared server.

Cause: An invalid instance number was specified in a cluster database ORADEBUG command.

Cause: Could not allocate memory needed to execute cluster database oradebug.

Cause: The value of LARGE_POOL_SIZE is below the minimum size.

Cause: The value of LARGE_POOL_SIZE is less than the value of LARGE_POOL_MIN_ALLOC.

Cause: The parameter value is not in a valid range.

Cause: The parameter value is not an integer.

Cause: The value for the initialization parameter is invalid.

Cause: Usage of Oracle's SQL extensions.

Cause: An attempt was made to create or mount the database when the instance was started without a parameter file.

Cause: Even though no parameter file was specified, the instance was started with all default values.

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

Cause: The syntax for the DISPATCHERS parameter is incorrect.

Cause: The network specified in DISPATCHERS does not have the functionality required by the dispatchers.

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

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.

Cause: Too many dispatcher configurations have been specified. No more can be added.

Cause: An attempt was made to startup/shutdown database when connected to a shared server via a dispatcher.

Cause: Most likely due to the fact that ORACLE listener has not been started.

Cause: Most likely due to the fact that the network protocol used by the the dispatcher does not support aynchronous operations.

Cause: The value specified for the attribute was incorrect.

Cause: The value specified for the attribute was incorrect.

Cause: The specified attribute was not recognized.

Cause: The attribute was specified with no value.

Cause: A protocol name specified in the DISPATCHERS system parameter is too long.

Cause: No value was specified for the SERVICE_NAMES system parameter, nor for the DB_NAME parameter.

Cause: A connection request was refused by a dispatcher because the dispatcher cannot support any more connections.

Cause: A service name specified in the SERVICE_NAMES system parameter is too long.

Cause: PROTOCOL, ADDRESS or DESCRIPTION was not specified.

Cause: More than one of PROTOCOL, ADDRESS or DESCRIPTION was specified.

Cause: The syntax for the specified parameter is incorrect.

Cause: 'shared_servers' cannot be set to a non-zero value in a non-ROOT pluggable database (PDB).

Cause: ORACLE could not initialize SQL*Net version 2.

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

Cause: The PRESENTATION in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported.

Cause: The DUPLICITY in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported.

Cause: There is currently no dispatcher running with the specified name.

Cause: Wrong syntax for ALTER SYSTEM SHUTDOWN

Cause: An error was encountered while validating the listener address.

Cause: The listener address specification is not valid.

Cause: The specified protocol does not support async notification.

Cause: Listener address has syntax error or cannot be resolved.

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

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

Cause: The indicated mandatory attribute was not specified.

Cause: The syntax for the nth LISTENER_NETWORKS specification was invalid.

Cause: The syntax for the LISTENER_NETWORKS specification with the indicated NAME was invalid.

Cause: All of the specified addresses or aliases for the attribute were invalid.

Cause: The indicated attribute was specified more than once.

Cause: An internal network name has been specified.

Cause: All of the specified addresses or aliases for the parameter were invalid.

Cause: FORWARD_LISTENER was used with LOCAL_LISTENER for the same network.

Cause: The remote HTTP/HTTPS port could not be registered without the local HTTP/HTTPS port.

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

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

Cause: The current session is not the same as the session that was passed into a upixado() call.

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

Cause: The transaction monitor returned TMJOIN on an AX_REG call but the transaction was locally suspended.

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.

Cause: An external global transaction ID with a length either too large or 0 was passed in in a distributed transaction.

Cause: An external transaction branch ID with a length either too large or 0 was passed in.

Cause: An external database name with too large a length field was passed in.

Cause: An internal database name with a too large length field was passed in.

Cause: A request was made by the application to start a distributed autonomous transaction when the application was in a migratable distributed transaction.

Cause: A request was made by the application to start a migratable distributed autonomous transaction with remote operation.

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.

Cause: It was not possible to create the control file.

Cause: The control file was created by incompatible software.

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

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.

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

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

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

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.

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

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

Cause: Cannot open the control file.

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

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

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

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

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

Cause: The control file created by release 8.0.2 was missing some record types. These record types are automatically added by resizing the control file during mount. The resize has failed.

Cause: The control file was missing some new record types supported by this release. These record types are automatically added by resizing the contol file during mount. The resize has failed.

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.

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

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.

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

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

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 ALTER DATABASE CONVERT command is issued.

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

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.

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

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

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

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

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

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

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

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

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.

Cause: Concurrent update activity on a control file caused a process to read inconsistent information from the control file without a lock.

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

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

Cause: The filename 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.

Cause: The specified process waited the maximum allowed time for the control file enqueue.

Cause: The current process did not release the control file enqueue within the maximum allowed time.

Cause: Either the control file was recently created by using CREATE CONTROLFILE, an incomplete recovery was done, or some previous operations require the control file to be re-checked against the data dictionary.

Cause: Failed to create a new filename record entry in the control file because the maximum allowed filename records have been allocated and are in use.

Cause: Failed to expand control file filename section. See alert log for more details.

Cause: Failed to create a control file backup because concurrent control file backup operation was in progress.

Cause: Failed to create a control file backup because some process signaled an error during backup creation. This is likely caused by the backup target (i.e., RMAN snapshot controlfile) being on a local file system so it could not be accessed by other instances. It can also be caused by other I/O errors to the backup target. Any process of any instance that starts a read/write control file transaction must have access to the backup control file during backup creation.

Cause: An attempt to create a control file backup failed because some process signaled an I/O error when accessing the backup target.

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

Cause: The destination specified by the LOG_ARCHIVE_DUPLEX_DEST parameter is the same as the destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command.

Cause: A log must be used for redo generation before it can be archived. The specified redo log was not been used since it was introduced to the database. However it is possible that instance death during a log switch left the log empty.

Cause: The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command was too long.

Cause: The specified archive log location is invalid in the archive command or the LOG_ARCHIVE_DEST initialization parameter.

Cause: An error occurred during archiving.

Cause: The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command could not be translated.

Cause: The archiver process received an error while trying to archive a redo log. If the problem is not resolved soon, the database will stop executing transactions. The most likely cause of this message is that the destination device is out of space to store the redo log file. Another possible cause is that a destination marked as MANDATORY has failed.

Cause: The database is in NOARCHIVELOG mode and a command to manually archive a log did not specify the log explicitly by sequence number, group number or filename.

Cause: An attempt was made to archive the current log of an open thread. This is not allowed because the redo log file may still be in use for the generation of redo entries.

Cause: The log sequence number supplied to the archival command does not match any of the online logs for the thread. The log might have been reused for another sequence number, it might have been dropped, the sequence number might be greater than the current log sequence number, or the thread might not have any logs.

Cause: The log is either being archived by another process or an administrative command is modifying the log. Operations that modify the log include clearing, adding a member, dropping a member, renaming a member, and dropping the log.

Cause: The log cannot be cleared or manually archived because it is the current log of a closed thread, and it is not possible to switch logs so another log is current. All other logs for the thread need to be archived, or cleared, and cannot be reused.

Cause: An attempt was made to manually archive the unarchived logs in this thread but no logs needed archiving.

Cause: An attempt was made to perform media recovery on files that do not // need any type of recovery.

Cause: The database either crashed or was shutdown with the ABORT option. Media recovery cannot be enabled because the online logs may not be sufficient to recover the current datafiles.

Cause: During media recovery, the name of an archived redo log file was requested, but no name was entered.

Cause: During media recovery, the name of an archived redo log file was entered, but no name was requested.

Cause: The given redo log file does not exist.

Cause: The given redo log file is not part of the given thread

Cause: An error was encountered when either creating or opening the destination file for archiving.

Cause: An attempt was made to archive the unarchived redo log files manually, but there are no files that need to be archived.

Cause: An I/O error occurred while archiving a redo log file.

Cause: A media recovery session encountered a table that was loaded by the direct loader without logging any redo information. Some or all of the blocks in this table are now marked as corrupt.

Cause: An illegal option was specified for a recovery command.

Cause: An attempt was made to start a second media recovery operation in the same session.

Cause: The CHANGE keyword was specified on the command line, but no change number was given.

Cause: Only CANCEL, CHANGE, CONSISTENT and TIME can be used with the UNTIL keyword.

Cause: The specified redo log file is no longer needed for the current recovery.

Cause: The requested log is required to proceed with recovery.

Cause: This message helps to locate the redo log file with the specified change number requested by other messages.

Cause: An attempt was made to use a dispatcher process for media recovery. Memory requirements disallow this recovery method.

Cause: The given UPI call is no longer supported.

Cause: An error during recovery was determined to be fatal enough to end the current recovery session.

Cause: An error during recovery was determined to be minor enough to allow the current recovery session to continue.

Cause: TIME was not followed by a string constant for the time.

Cause: None of the members of a redo log file group are available, or the available members do not contain complete data.

Cause: The given change number does not appear in any of the online redo logs for the given thread.

Cause: During media recovery, a new log is not required but the continuation command is necessary to do a checkpoint and report errors.

Cause: This message reports the next redo log filename that is needed, according to the initialization parameters LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT. This message assumes that LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT are the same now as when the required redo log file was archived.

Cause: While attempting to archive to a redo log file, the server encountered an unexpected operating system error.

Cause: A recovery command was specified incorrectly. The PARALLEL option must be followed by a numeric argument that specifies the degree of parallelism.

Cause: A parallel recovery was requested when the parallel recovery option is not installed.

Cause: The redo log file and control file are out of sync because a non-current controle file was specified when the instance was started.

Cause: An invalid format specifier was found in the LOG_ARCHIVE_FORMAT initialization parameter. The only characters permitted following the % symbol are s, S, t, and T.

Cause: An invalid file number was specified.

Cause: The RECOVER DATAFILE LIST command specified more datafiles than are allowed by the DB_FILES initialization parameter. This error occurs when doing recovery with Recovery Manager, and the instance has been started with a DB_FILES parameter specifying fewer datafiles than recovery manager needs to recover to satisfy the user's RECOVER command.

Cause: The RECOVER DATAFILE START command was issued, but no RECOVER DATAFILE LIST commands had been issued. This only happens when doing recovery with Recovery Manager, and is an internal error in Recovery Manager, because Recovery Manager should always issue RECOVER DATAFILE LIST before RECOVER DATAFILE START.

Cause: A non-zero integer value is required when the following keyword attributes are specified: TIMEOUT, EXPIRE, DELAY, NEXT

Cause: The control file does not contain an entry for this file, so block media recovery cannot be done.

Cause: The specified block size of the redo log is greater than the maximum block size for the operating system.

Cause: The creation of the redo log file failed

Cause: The maximum number of redo log files has been exceeded.

Cause: A redo log containing Parallel Redo has been detected. The current Oracle release cannot process this format of redo.

Cause: An instance tried to start by using a value of the initialization parameter INSTANCE_NUMBER that is already in use.

Cause: The database ID in the redo log file does not match the database ID in the control file. This redo log file is not from the current database.

Cause: Starting this instance would exceed the maximum number of instances allowed for this database. This message occurs only with STARTUP shared and multiple instances.

Cause: The initialization parameter INSTANCE_NUMBER specified a number that was out of range.

Cause: The system cannot access a required archived redo log file.

Cause: The system cannot access the archived redo log because it belongs to another database.

Cause: The archived log was out of sequence, probably because it was corrupt or the wrong redo log file name was specified during recovery.

Cause: An I/O error occurred when attempting to read the log file header from the specified archived redo log file.

Cause: This message reports the filename for details of another message.

Cause: The online log cannot be opened. May not be able to find file.

Cause: The online log is corrupted or is an old version.

Cause: The online log is corrupted or is an old version.

Cause: The online log is corrupted or is an old version.

Cause: This is not an archived log file.

Cause: On header read the file size indicated in the control file did not match the file size contained in the log file.

Cause: Check of log file header at database open found that an online log has log reset data that is different from the control file. The log is probably an incorrectly restored backup.

Cause: The file is not available.

Cause: Cannot write to the log file.

Cause: Check of log file header at database open found that an online log appears to be an incorrectly restored backup.

Cause: Attempt to open thread failed because it is necessary to switch redo generation to another online log, but all the other logs need to be archived before they can be used.

Cause: the translated name for a log file is too long.

Cause: The archived log is corrupted or for another thread. Can not use the log for applying redo.

Cause: The archived log supplied for recovery was generated after the log that is needed. Can not yet use the log for applying redo.

Cause: A log file has shrunk in size. This is likely to have been caused by operator or operating system error.

Cause: The archived log supplied for recovery was generated before the log that is needed. Can not use the log for applying redo.

Cause: The archived log is not the correct log. An earlier log is needed.

Cause: The archived log is not the correct log. A later log is needed.

Cause: The log was written by incompatible version of Oracle.

Cause: The log is smaller than the space allocated in it. May be the result of a shutdown abort while it was being written by the archiver.

Cause: An IO error occurred while reading the log described in the accompanying error.

Cause: Reporting filename for details of another error

Cause: Reporting filename for details of another error

Cause: The log file size as specified in create database is too small.

Cause: An attempt to add a log found neither an existing file nor a size for creating the file.

Cause: The control file change sequence number in the log file is greater than the number in the control file. This implies that the wrong control file is being used. Note that repeatedly causing this error can make it stop happening without correcting the real problem. Every attempt to open the database will advance the control file change sequence number until it is great enough.

Cause: The archived log is not the correct log. It is a copy of a log file that has never been used for redo generation, or was an online log being prepared to be the current log.

Cause: An IO error occurred on the named online log.

Cause: The internal information in an online log file does not match the control file.

Cause: Recovery was given a log that does not belong to current incarnation or one of the parent incarnation. There should be another log that contains the correct redo.

Cause: An I/O failure occurred when attempting to re-create an online as part of either ALTER DATABASE OPEN RESETLOGS or ALTER DATABASE CLEAR LOGFILE command.

Cause: An IO error has occurred while writing the log

Cause: A log file member was no longer complete.

Cause: On header read the blocksize indicated in the control file did not match the blocksize contained in the log file.

Cause: A failure occurred during a critical portion of the log code during single process operation. This error does not occur during normal multi-process operation.

Cause: The operating system was unable to determine the blocksize for the given filename.

Cause: The command cannot be done because the log has not been archived, and media recovery has been enabled.

Cause: The time specified in a recover-until statement must be after January 1st 1988.

Cause: Attempting to enable a thread with all logs needing to be archived, and media recovery has been enabled. There is no log that can be made the new current log for the thread.

Cause: Some type of redo log corruption has been discovered. This error describes the location of the corruption. Accompanying errors describe the type of corruption.

Cause: The block header on the redo block indicated by the accompanying error, is not reasonable.

Cause: A change number found in the redo log is lower than a previously encountered change number. The log is corrupted in some way. The corruption may be at the earlier change or at this one.

Cause: A change record in the redo log contains lengths that do not add up to a consistent value. The log is corrupted in some way.

Cause: An add logfile or add logfile member command would result in a log with too many members. The number of members is set when the database is created.

Cause: A create or alter statement specified too many members in a parenthesised file list.

Cause: An add logfile member or drop logfile request specified a logfile group number that does not exist.

Cause: A filename was given to drop logfile member that is not a part of the database, or which is a data file.

Cause: An attempt has been made to remove the last member of a log file group.

Cause: A request to drop a logfile member was denied because it would remove data required to form a complete logfile.

Cause: The log given to recovery is a backup of the online version from the time it was the current log. The archived version of the log would not be marked as end of thread. This error can also be caused by failing to list the current log of an enabled thread in a CREATE CONTROLFILE command.

Cause: An i/o error occurred when attempting to write the header to a log member that is being added to an existing group.

Cause: The specified log failed to pass checks to ensure it corresponds to the log that was just applied. This is probably the result of using a log that was generated against a cold backup image of the database.

Cause: The file header for the redo log contains a checksum that does not match the value calculated from the file header as read from disk. This means the file header is corrupted

Cause: The file header for the redo log contains a checksum that does not match the value calculated from the file header as read from disk. This means the file header is corrupted

Cause: The redo block indicated by the accompanying error, is not vaild. It has a checksum that does not match the block contents.

Cause: Attempt to open thread failed because it is necessary to switch redo generation to another online log, but all the other logs are being cleared or need to be archived before they can be used.

Cause: Error code used internally by software. Should never be reported

Cause: The SHARED_POOL_SIZE initialization parameter was too small.

Cause: attempting to modify the contents of a file that cannot be modified. The file is most likely part of a read only tablespace but may be in the process of going offline, or the database may be in the process of closing.

Cause: The online log was written by incompatible version of Oracle. Can occur when the log file was created by either a new or older version of Oracle.

Cause: invalid value for db_block_size parameter

Cause: attempting to read from a file that is not readable. Most likely the file is offline.

Cause: Backups are occurring too frequently on this file. Each time a new backup is started for a file, any writes which have been previously issued (but not completed) have to be re-issued. If hot backups are started very, very frequently, it is possible that some writes will be re-issued repeatedly and never complete.

Cause: Either the number of buffers or the number of lru latches is too small to satisfy the specified buffer pool configuration.

Cause: All buffers in the specified buffer pool for the specified block size are in use and no free buffers are available.

Cause: User specified the parameter db_nk_cache_size (where n is one of 2,4,8,16,32), while the standard block size for this database is equal to n Kbytes. This is illegal.

Cause: User specified one or more of { db_cache_size , db_recycle_cache_size, db_keep_cache_size, db_nk_cache_size (where n is one of 2,4,8,16,32), db_cache_advice } AND one or more of { db_block_buffers, buffer_pool_keep , buffer_pool_recycle }. This is illegal.

Cause: User specified a value for db_nk_cache_size where n is one of {2, 4, 8, 16, 32}, but nk is not a valid block size for this platform.

Cause: User attempted to reduce db_cache_size to zero, or attempted to to reduce db_nK_cache_size to zero while there were still online tablespaces with blocksize nK. Note that since the SYSTEM tablespace cannot be taken offline, it is always illegal to set db_cache_size to zero.

Cause: The system could not allocate sufficient memory to grow the cache to the specified size.

Cause: The instance contained buffers that had non-durable changes and depended on redo in another thread that was lost because of that thread crash. No data are lost because changes to such buffers cannot be commited while they are non-durable.

Cause: An attempt to switch to a new online log for the redo thread failed because no reusable log could be found. This log is being cleared and will be useable when the clearing completes. The command that began the clearing may have terminated without completing the clearing.

Cause: An attempt to switch the current log of a single thread is not allowed because the compatiblity requirements force a new log format version number. When changing log formats, all threads must switch to the new format at the same time.

Cause: An operation encountered this online log in the middle of being cleared. The command that began the clearing may have terminated without completing the clearing.

Cause: Log cannot be cleared because the redo in it is needed to recover offline datafiles. It has not been archived so there is no other copy available. If the log is cleared the tablespaces containing the files will have to be dropped.

Cause: It has been detected that an online log that is being archived has been reused

Cause: A clone database open forces logfile renaming to avoid overwriting the primary logfiles

Cause: The indicated error caused two-pass instance or crash recovery to fail. Recovery was retried with an alternate (slower) method to avoid the error.

Cause: The foreground process doing instance recovery died.

Cause: Global enqueue service reconfiguration occurred during instance/crash recovery.

Cause: A change vector in the redo log failed validation checks.

Cause: The release level given for the specified init parameter is invalid.

Cause: The value specified cannot be supported by this release of the software.

Cause: Changes have been made to the database that require a newer software release or that violate the compatibility parameters.

Cause: Another instance has set the compatible or compatible no recovery parameters differently than this instance.

Cause: The file used for converting the database from V7 to V8 could not be found.

Cause: Reporting a type associated with another error.

Cause: The COMPATIBLE initialization parameter is not high enough to allow the operation. Allowing the command would make the database incompatible with the release specified by the current COMPATIBLE parameter.

Cause: Another instance executing software at a different point release already has the database mounted.

Cause: Reporting the parameter that resulted in the compatibility error.

Cause: This is due to migrating from an older release of Oracle with tablespaces created using AUTO SEGMENT SPACE MANAGEMENT. To open the database, the COMPATIBLE parameter needs to be set to the specified value.

Cause: The required number of sessions for the PROCESSES parameter was greater than the maximum supported value.

Cause: ORACLE feature is not licensed.

Cause: The specified option is not installed.

Cause: The specified feature is not enabled.

Cause: An attempt was made to start more than one Oracle Database Express Edition (XE) instance.

Cause: The specified process did not start.

Cause: Usually due to a bad (or non-existent) background process image.

Cause: The specified process did not start after the specified time.

Cause: The background process specified started up AFTER the RDBMS was already running.

Cause: One of the background processes died unexpectedly.

Cause: One of the background processes completed normally (i.e. exited). The background process thinks that somebody asked it to exit.

Cause: A foreground process needing service from a background process has discovered the process died.

Cause: The specified process did not start.

Cause: The foreground process for the new connection did not start.

Cause: The foreground process for the new connection did not start.

Cause: The background process that was being messaged was dead or its incarnation was invalid.

Cause: An attempt to spawn a background process that was already running failed.

Cause: The state of the background process was not cleaned up.

Cause: Prespawn was not enabled.

Cause: The process pool was not found.

Cause: The process pool was already started.

Cause: The process pool was not started.

Cause: Invalid configuration values were specified for the process pool.

Cause: Managed Global Area(MGA) namespace was already opened.

Cause: Managed Global Area(MGA) namespace shared handle was not valid.

Cause: Managed Global Area(MGA) namespace private handle was not valid.

Cause: Processes were still attached to Managed Global Area(MGA) namespace.

Cause: Segments were still attached to Managed Global Area(MGA) namespace.

Cause: Managed Global Area(MGA) segment information was not valid.

Cause: There was already an attachement to the Managed Global Area(MGA) handle.

Cause: There was no attachement to the Managed Global Area(MGA) handle.

Cause: The checkpoint process died

Cause: The log writer process died

Cause: The database writer process died

Cause: The process cleanup process died

Cause: The archive process died

Cause: The system cleanup process died

Cause: The system tracing process died

Cause: The distributed transaction (two-phase commit) recovery process died.

Cause: A materialized view refresh process died

Cause: SMON was unable to service the requests due to error in cleanup of resources

Cause: The RVWR process died

Cause: A system lock process died

Cause: The global enqueue service monitor process died

Cause: A global enqueue service daemon process died

Cause: One of the background processes did not exit normally at or near the time of shutdown.

Cause: A global cache service process died

Cause: A global diagnostic process died

Cause: An ASM background process died.

Cause: The change tracking process died

Cause: The ASM rebalance coordinator process died.

Cause: An ASM rebalance worker process died.

Cause: The process spawner died

Cause: The RAC Management Process died

Cause: A global transaction background process died.

Cause: The ASM disk group monitor process died

Cause: The specified process did not release the enqueue within the maximum allowed time.

Cause: The generic background processing process died.

Cause: The LM heartbeat monitor process died.

Cause: The Cell automation manager process terminated with error.

Cause: The Cell automation worker actions process terminated with error.

Cause: The Cell automation manager process repeatedly failed to initialize.

Cause: The listener registration process died.

Cause: The cleanup process died.

Cause: The manager process died.

Cause: A cleanup slave died.

Cause: The service monitor background process died.

Cause: The generic background processing process 1 died.

Cause: The generic background processing process 2 terminated.

Cause: The message bridge background process was terminated.

Cause: The given Managed Global Area (MGA) index was not of the heap type.

Cause: The cluster flash cache process died.

Cause: A kill request was attempted on an operating system process that had multiple threads but the process was not marked as one that could be killed as a group.

Cause: Cannot start process in a requested processor group when the NUMA feature is disabled.

Cause: The process could not be started in the requested processor group.

Cause: User specified too many ^c handlers

Cause: A prior error occurred on one of the instances in the cluster. Typically errors are caused by shared pool resource contention.

Cause: This is the generic internal error number for Oracle program exceptions. It indicates that a process has encountered a low-level, unexpected condition. The first argument is the internal message number. This argument and the database version number are critical in identifying the root cause and the potential impact to your system.

Cause: The process monitor (PMON) database process ran into a lock conflict while trying to recover the processes.

Cause: An address violation was encountered.

Cause: An Oracle server session was in an unrecoverable state.

Cause: An error occurred while processing a recursive SQL statement (a statement applying to internal dictionary tables).

Cause: A call to deferred upi functions was made in non deferred mode

Cause: An internal error or memory exception occurred while Oracle was applying redo to a data block.

Cause: Internal error reserved for testing.

Cause: Oracle process could not answer incoming connection

Cause: A quarantine limit was reached and the instance was aborted.

Cause: This is the generic PDB-specific internal error number for Oracle program exceptions. It indicates that a process encountered a low-level, unexpected condition within a PDB. The PDB was closed (abort). The first argument in the message is the internal message. This argument and the database version number are critical in identifying the root cause and the potential impact to your system.

Cause: Internal inconsistency that will not crash a process

Cause: Attempt to alter or drop a database object (table, cluster, or index) which are needed for warmstarting the database.

Cause: The reading version of the boostrap is incompatible with the current bootstrap version.

Cause: There are not enough row cache enqueues.

Cause: Failure in processing bootstrap data - see accompanying error.

Cause: A previous attempt to start an instance was terminated.

Cause: An attempt to change the block0 format of the specified file failed because the file is read-only or offline.

Cause: An attempt to rename a tablespace failed because the new name is the same as the old name.

Cause: An attempt to rename a tablespace failed because the new name is invalid.

Cause: An attempt to rename the system tablespace failed.

Cause: ALTER DATABASE RESET COMPATIBILITY command has been de-supported since Oracle 10i.

Cause: An attempt to import a tablespace failed because the tablespace contains changes that require a newer software release or that violate the compatibility parameters.

Cause: Reporting name of the feature for details of another error.

Cause: Oracle detected that the initialization parameter COMPATIBLE was not explicitly specified, and the compatibility of the database is lower than the default value of the COMPATIBLE parameter. In order to use the new compatible setting, the intialization parameter must be explicitly set by the user.

Cause: ALTER DATABASE CONVERT command has been de-supported since Oracle 10i.

Cause: A deprecated ALTER DATABASE SET STANDBY was specified.

Cause: The user specified datafile size exceeded maximum file size.

Cause: The user specified logfile size exceeded maximum logfile size.

Cause: Either a write issued by Oracle was lost by the underlying operating system or storage system or an Oracle internal error occurred.

Cause: The instance has already mounted and dismounted the database, which is only allowed once in its lifetime.

Cause: An error occurred while obtaining the mirror resilvering status of a file.

Cause: A data block write to storage was lost during normal database operation on the primary database.

Cause: A data block write to storage was lost during normal redo database operation on the standby database or during recovery on a primary database.

Cause: An error caused a data block mismatch with a log record.

Cause: A data block write to storage was lost during normal redo database operation on the standby database or during recovery on a primary database.

Cause: An internal error occurred.

Cause: The standby database was going through a role transition and the new primary database was not reopened in the configured timeout duration after switchover.

Cause: An error occurred while trying to remove lost write tracking.

Cause: An error occurred while trying to suspend lost write tracking.

Cause: Memory allocation failed.

Cause: An error occurred while trying to add lost write tracking; could not lookup the target data file or there was insufficient space in the shadow tablespace.

Cause: The session, which started a transaction on the standby database and stayed alive after a role transition, attempted to do an update.

Cause: An improper system configuration or setting resulted in failure. This failure is not fatal to the instance at the moment, however, this might result in an unexpected behavior during query execution.

Cause: The specified value of sga_max_size is too small for the SGA to accommodate all of the necessary SGA components such as the log buffer, buffer pools, shared pool, etc.

Cause: The specified value of sga_target is too small for the SGA to accommodate all of the necessary SGA components such as the log buffer, buffer pools, shared pool, etc.

Cause: The Memory Management process died.

Cause: The specified value of sga_target is greater than sga_max_size.

Cause: Could not set SGA_TARGET or MEMORY_TARGET due to current parameter settings.

Cause: SGA_TARGET or MEMORY_TARGET set with DB_BLOCK_BUFFERS set.

Cause: SGA_TARGET or MEMORY_TARGET set for an ASM instance.

Cause: Attempted to shrink the SGA to the specified value but did not succeed because the SGA components could not be shrunk as they were already at their minimum sizes.

Cause: Unable to set shared_pool_reserved_size to specified value if SGA_TARGET set, either because the specified value is too small, or because it is too large for the current internal size of shared pool. More details can be found in the alert log.

Cause: The user attempted to set statistics_level to BASIC with auto-tune SGA enabled which cannot be done because auto-tune SGA cannot work with statistics_level set to BASIC.

Cause: A database feature which needs STREAMS SGA was being used, however, the streams_pool_size parameter was not defined and the value of db_cache_size was too small to permit an automatic transfer of SGA to the streams pool from the buffer cache.

Cause: The specified value of MEMORY_TARGET was greater than MEMORY_MAX_TARGET.

Cause: The specified value of MEMORY_TARGET was less than the sum of the specified values for SGA_TARGET and PGA_AGGREGATE_TARGET.

Cause: The specified value of SGA_TARGET was not compatible with current settings of PGA_AGGREGATE_TARGET and MEMORY_TARGET/MEMORY_MAX_TARGET.

Cause: The specified value of PGA_AGGREGATE_TARGET was not compatible with current settings of SGA_TARGET and MEMORY_TARGET/MEMORY_MAX_TARGET.

Cause: MEMORY_TARGET parameter was not supported on this system as shmfs was disabled.

Cause: DB_BLOCK_BUFFERS was incompatible with SGA_TARGET and MEMORY_TARGET.

Cause: The parameter was larger than MEMORY_MAX_TARGET.

Cause: The parameter was larger than MEMORY_TARGET.

Cause: The MEMORY_TARGET parameter was not supported on this operating system or /dev/shm was not sized correctly on Linux.

Cause: Attempted to shrink MEMORY_TARGET to the specified value but did not succeed because the PGA and SGA components could not be shrunk.

Cause: MEMORY_TARGET/MEMORY_MAX_TARGET was set to a non-zero value and LOCK_SGA was also set

Cause: STATISTICS_LEVEL of BASIC was incompatible with SGA_TARGET and MEMORY_TARGET.

Cause: SGA_TARGET value was more than MEMORY_MAX_TARGET value.

Cause: PGA_AGGREGATE_TARGET value was more than MEMORY_MAX_TARGET value.

Cause: SGA_MAX_SIZE value was more than MEMORY_TARGET value.

Cause: The ASM rolling migration monitor process died.

Cause: SGA_MAX_SIZE value was more than MEMORY_MAX_TARGET value.

Cause: The ASM IOServer Fence monitor process died.

Cause: PGA_AGGREGATE_TARGET value was too high for the current system global area (SGA) size and amount of physical memory available.

Cause: PGA_AGGREGATE_TARGET value was greater than 50 percent the current value of PGA_AGGREGATE_LIMIT.

Cause: The current operation could not be performed on the same session.

Cause: The SQL ID specified was invalid or did not exist.

Cause: The instance ID specified was invalid.

Cause: The dedicated connection broker could not be enabled or disabled.

Cause: The syntax for the nth CONNECTION_BROKERS specification was invalid.

Cause: Multiple CONNECTION_BROKER specifications contained the same TYPE.