-
ORA-00001: unique constraint (string.string) violated
-
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.
-
Action: Either remove the unique restriction or do not insert the key.
-
ORA-00023: session references process private memory; cannot detach session
-
Cause: An attempt was made to detach the current session when it contains references to process private memory.
-
Action: A session may contain references to process memory (PGA) if it has an open network connection, a very large context area, or operating system privileges. To allow the detach, it may be necessary to close the session's database links and/or cursors. Detaching a session with operating system privileges is always disallowed.
-
ORA-00031: session marked for kill
-
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.
-
Action: No action is required for the session to be killed, but further executions of the ALTER SYSTEM KILL SESSION command on this session may cause the session to be killed sooner.
-
ORA-00034: cannot string in current PL/SQL session
-
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')
-
Action: Enable commits from PL/SQL in this session, or do not attempt to use commit or rollback in PL/SQL when they are disabled in the current session.
-
ORA-00038: Cannot create session: server group belongs to another user
-
Cause: An attempt was made to create a non-migratable session in a server group that is owned by a different user.
-
Action: A server group is owned by the first user who logs into a server in the server group in non-migratable mode. All subsequent non-migratable mode logins must be made by the user who owns the server group. To have a different user login in non-migratable mode, the ownership of the server group will have to be changed. This can be done by logging off all current sessions and detaching from all existing servers in the server group and then having the new user login to become the new owner.
-
ORA-00044: timed_statistics must be TRUE when statistics_level is not BASIC
-
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.
-
Action: Either set timed_statistics to TRUE or set statistics_level to BASIC.
-
ORA-00050: operating system error occurred while obtaining an enqueue
-
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.
-
Action: Look up the operating system error in your system documentation and perform the needed action.
-
ORA-00057: maximum number of temporary table locks exceeded
-
Cause: The number of temporary tables equals or exceeds the number of temporary table locks. Temporary tables are often created by large sorts.
-
Action: Increase the value of the TEMPORARY_TABLE_LOCKS initialization parameter and warm start.
-
ORA-00058: DB_BLOCK_SIZE must be string to mount this database (not string)
-
Cause: DB_BLOCK_SIZE initialization parameter is wrong for the database being mounted. It does not match the value used to create the database.
-
Action: Fix the value of the DB_BLOCK_SIZE parameter or mount a database that matches the value.
-
ORA-00069: cannot acquire lock -- table locks disabled for string
-
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.
-
Action: Use the ALTER TABLE ... ENABLE TABLE LOCK command, and retry the command.
-
ORA-00080: invalid global area specified by level string
-
Cause: An attempt was made to dump an invalid global area.
-
Action: Use level 1 for the PGA, 2 for the SGA, and 3 for the UGA. Use <extra + level> to dump global area <level> as well as <extra> bytes for every pointer; <extra> must be a multiple of 4.
-
ORA-00100: no data found
-
Cause: An application made reference to unknown or inaccessible data.
-
Action: Handle this condition within the application or make appropriate modifications to the application code. NOTE: If the application uses Oracle-mode SQL instead of ANSI-mode SQL, ORA-01403 will be generated instead of ORA-00100.
-
ORA-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-00106: cannot startup/shutdown database when connected to a dispatcher
-
Cause: An attempt was made to startup/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-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-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-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-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-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-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-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-00213: cannot reuse control file; 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: control file 'string' version string inconsistent with file 'string' version string
-
Cause: An inconsistent set of control files, datafiles/logfiles, and redo files was used.
-
Action: Use a consistant set of control files, datafiles/logfiles, and redo log files. That is, all the files must be for the same database and from the same time period.
-
ORA-00216: control file could not be resized for migration from 8.0.2
-
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.
-
Action: Look in the alert log for the reason that the resize has failed. If indicated in the alert log, give the control file more space. Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file.
-
ORA-00217: control file could not be resized for new record types
-
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.
-
Action: Look in the alert log for the reason that the resize has failed. If indicated in the alert log, give the control file more space. Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file.
-
ORA-00218: block size string of control file 'string' 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. If the control file is known to be clean set the DB_BLOCK_SIZE to match control file headers block size value.
-
ORA-00219: required control file size (string logical blocks) exceeds maximum allowable size (string logical blocks)
-
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.
-
Action: In the case of CREATE DATABASE or CREATE CONTROLFILE, use a different combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses.
-
ORA-00220: control file 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-00222: operation would reuse name of a currently mounted control file
-
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.
-
Action: Retry the operation with a different filename.
-
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 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: control file 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-16).
-
ORA-00225: expected size string of control file 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-00229: operation disallowed: already hold snapshot control file 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 control file 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 control file has not been named
-
Cause: During an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot it was detected that no filename for the snapshot control file had previously been specified.
-
Action: Specify a name for the snapshot control file by calling cfileSetSnapshotName.
-
ORA-00233: copy control file 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 filename that was specified for cfileUseCopy.
-
ORA-00234: error in identifying or opening snapshot or copy control file
-
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-00238: operation would reuse a filename that is part of the database
-
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.
-
Action: Retry the operation with a different filename.
-
ORA-00241: operation disallowed: control file inconsistent with data dictionary
-
Cause: The control file was either recently created via CREATE CONTROLFILE or an incomplete recovery has been done. Thus, the datafiles in the control file and the ones in the data dictionary may not match.
-
Action: Open the database, then retry the operation.
-
ORA-00242: maximum allowed filename records used up in control file
-
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.
-
Action: Free up controlfile filename section entries by dropping unwanted tablespaces/datafiles/redofiles.
-
ORA-00251: LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as string string
-
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.
-
Action: Specify a different destination for parameter LOG_ARCHIVE_DUPLEX_DEST, or specify a different destination with the ALTER SYSTEM command.
-
ORA-00252: log string of thread string is empty, cannot archive
-
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.
-
Action: Empty logs do not need to be archived. Do not attempt to archive the redo log file.
-
ORA-00255: error archiving log string of thread string, sequence # string
-
Cause: An error occurred during archiving.
-
Action: Check the accompanying message stack for more detailed information. If the online log is corrupted, then the log can be cleared using the UNARCHIVED option. This will make any existing backups useless for recovery to any time after the log was created, but will allow the database to generate redo.
-
ORA-00256: cannot translate archive destination string string
-
Cause: The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command could not be translated.
-
Action: Check the accompanying message stack for more detailed information. Then, retry the ALTER SYSTEM command using a different string.
-
ORA-00257: archiver error. Connect internal only, until freed.
-
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 the destination device is out of space to store the redo log file.
-
Action: Check archiver trace file for a detailed description of the problem. Also verify that the device specified in the initialization parameter ARCHIVE_LOG_DEST is set up properly for archiving.
-
ORA-00258: manual archiving in NOARCHIVELOG mode must identify log
-
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.
-
Action: Specify log by filename, by group number or by thread and sequence number.
-
ORA-00259: log string of open instance string (thread string) is the current log, cannot archive
-
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.
-
Action: Force a log switch in the instance where the thread is open. If no instances are open, open the database so that instance recovery can recover the thread.
-
ORA-00260: cannot find online log sequence string for thread string
-
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.
-
Action: Check the ARCHIVE statement, then specify a valid log sequence number. Specify a valid log sequence number.
-
ORA-00261: log string of thread string is being archived or modified
-
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.
-
Action: Wait for the current operation to complete and try again.
-
ORA-00262: current log string of closed thread string cannot switch
-
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.
-
Action: Archive another log in the same thread first, or complete the clearing. See attached errors for the reason the switch cannot be completed.
-
ORA-00264: no recovery required
-
Cause: An attempt was made to perform media recovery on files that do not // need any type of recovery.
-
Action: Do not attempt to perform media recovery on the selected files. Check to see that the filenames were entered properly. If not, retry the command with the proper filenames.
-
ORA-00265: instance recovery required, cannot set ARCHIVELOG mode
-
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.
-
Action: Open the database and then enter the SHUTDOWN command with the NORMAL or IMMEDIATE option.
-
ORA-00269: specified log file is part of thread string not string
-
Cause: The given redo log file is not part of the given thread
-
Action: Check that the thread of the redo log file matches the thread on the command line. If not, use a redo log file from the appropriate thread. Retry the command after correcting the error.
-
ORA-00272: error writing archive log string
-
Cause: An I/O error occurred while archiving a redo log file.
-
Action: Check that the output device is still available and correct any device errors that may have occurred. Also, make certain that sufficient space for archiving is available on the output device.
-
ORA-00273: media recovery of direct load data that was not logged
-
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.
-
Action: The table must be dropped or truncated so that the corrupted blocks can be reused. If a more recent backup of the file is available, try to recover this file to eliminate this error.
-
ORA-00278: log file 'string' no longer needed for this recovery
-
Cause: The specified redo log file is no longer needed for the current recovery.
-
Action: No action required. The archived redo log file may be removed from its current location to conserve disk space, if needed. However, the redo log file may still be required for another recovery session in the future.
-
ORA-00280: change string for thread string is in sequence #string
-
Cause: This message helps to locate the redo log file with the specified change number requested by other messages.
-
Action: Use the information provided in this message to specify the required archived redo log files for other errors.
-
ORA-00286: no members available, or no member contains valid data
-
Cause: None of the members of a redo log file group are available, or the available members do not contain complete data.
-
Action: If a member is temporarily offline, attempt to make it available. Make sure that the correct filenames are being used, especially if the redo log file is being accessed from a remote location.
-
ORA-00289: suggestion : string
-
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.
-
Action: Consider using this filename for the next log needed for recovery.
-
ORA-00290: operating system archival error occurred. See error below
-
Cause: While attempting to archive to a redo log file, the server encountered an unexpected operating system error.
-
Action: Correct the operating system error given in the messages and retry the operation. See also your operating system-specific Oracle documentation.
-
ORA-00291: numeric value required for PARALLEL option
-
Cause: A recovery command was specified incorrectly. The PARALLEL option must be followed by a numeric argument that specifies the degree of parallelism.
-
Action: Re-enter the command with a numeric argument specifying the degree of parallelism desired.
-
ORA-00293: control file out of sync with redo log
-
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.
-
Action: Retry the RECOVER command using the current control file, or retry the RECOVER command using the USING BACKUP CONTROLFILE clause.
-
ORA-00296: maximum number of files (string) exceeded for RECOVER DATAFILE LIST
-
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.
-
Action: Re-start the instance with a higher value for DB_FILES.
-
ORA-00297: must specify RECOVER DATAFILE LIST before RECOVER DATAFILE START
-
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.
-
Action: Contact customer support
-
ORA-00301: error in adding log file 'string' - file cannot be created
-
Cause: The creation of the redo log file failed
-
Action: Check: 1) there is enough storage space on the device 2) the name of the file is valid 3) the device is online 4) an IO error occurred Also, it is possible REUSE was specified on the command line and a file of the incorrect size exists. Either do not specify REUSE or use a file of the correct size.
-
ORA-00304: requested INSTANCE_NUMBER is busy
-
Cause: An instance tried to start by using a value of the initialization parameter INSTANCE_NUMBER that is already in use.
-
Action: Either a) specify another INSTANCE_NUMBER, b) shut down the running instance with this number c) wait for instance recovery to complete on the instance with this number.
-
ORA-00306: limit of string instances in this 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.
-
Action: You cannot start more than the lower of a) port-specific limit as to the number of instances b) the number of instances specified at create-database time
-
ORA-00307: requested INSTANCE_NUMBER out of range, maximum is string
-
Cause: The initialization parameter INSTANCE_NUMBER specified a number that was out of range.
-
Action: Change INSTANCE_NUMBER to a valid range and restart the instance. The minimum value is one and the maximum value is the lower of the operating system-specific maximum or the MAXINSTANCES option specified in the CREATE DATABASE statement. See also your operating system-specific Oracle documentation.
-
ORA-00308: cannot open archived log 'string'
-
Cause: The system cannot access a required archived redo log file.
-
Action: Check that the off line log exists, the storage device is online, and the archived file is in the correct location. Then attempt to continue recovery or restart the recovery session.
-
ORA-00323: Current log of thread string not useable and all others need archiving
-
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.
-
Action: Archive the logs for the thread then retry open.
-
ORA-00327: log string of thread string, physical size string less than needed string
-
Cause: A log file has shrunk in size. This is likely to have been caused by operator or operating system error.
-
Action: Restore the log file from backup. If backup is not available, drop this log and re-create. If the database was shut down cleanly, no further action should be required; otherwise incomplete recovery may be required.
-
ORA-00332: archived log is too small - may be incompletely archived
-
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.
-
Action: Get a complete version of this log and use it for recovery. There should either be an online version of it or a copy that was successfully archived.
-
ORA-00338: log string of thread string is more recent than control 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.
-
Action: Use the current control file or do backup control file recovery to make the control file current. Be sure to follow all restrictions on doing a backup control file recovery.
-
ORA-00350: log string of instance string (thread string) needs to be archived
-
Cause: The command cannot be done because the log has not been archived, and media recovery has been enabled.
-
Action: Archive the log or disable media recovery. If the command supports an UNARCHIVED option then it can be used. However this may result in making backups unuseable, and forcing the drop of some offline files.
-
ORA-00352: all logs for thread string need to be archived - cannot enable
-
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.
-
Action: Archive a log for the thread or disable media recovery.
-
ORA-00353: log corruption near block string change string time string
-
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.
-
Action: Do recovery with a good version of the log or do incomplete recovery up to the indicated change or time.
-
ORA-00354: corrupt redo log block header
-
Cause: The block header on the redo block indicated by the accompanying error, is not reasonable.
-
Action: Do recovery with a good version of the log or do time based recovery up to the indicated time. If this happens when archiving, archiving of the problem log can be skipped by clearing the log with the UNARCHIVED option. This must be followed by a backup of every datafile to insure recoverability of the database.
-
ORA-00355: change numbers out of order
-
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.
-
Action: Do recovery with a good version of the log or do time based recovery up to the indicated time.
-
ORA-00363: log is not the archived version
-
Cause: d by failing to list the current log of an enabled thread in a CREATE CONTROLFILE command.
-
Action: Find the archived version of the log and supply its name. If this is media recovery immediately following a CREATE CONTROLFILE, be sure the current log for this thread was included.
-
ORA-00365: the specified log is not the correct next log
-
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.
-
Action: Find the log that was generated by this copy of the database and give that filename to recovery.
-
ORA-00366: log string of thread string, checksum error in the file header
-
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
-
Action: Find and install correct version of log or reset logs.
-
ORA-00369: Current log of thread string not useable and other log being cleared
-
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.
-
Action: If the ALTER DATABASE CLEAR LOGFILE command is still active then wait for it to complete. Otherwise reissue the CLEAR command. If there are other online logs for the thread, that are not being cleared, then archive the logs.
-
ORA-00372: file string cannot be modified at this time
-
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.
-
Action: check the status of the file and its tablespace
-
ORA-00373: online log version string incompatible with ORACLE version string
-
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.
-
Action: Recover the database with the compatible software, shut it down cleanly, then restart with current software.
-
ORA-00377: Frequent backups of file string causing write operation to stall
-
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.
-
Action: Increase the interval between begin hot-backup commands for this file.
-
ORA-00380: cannot specify db_stringk_cache_size since stringK is the standard block size
-
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.
-
Action: Specify the standard block size cache using db_cache_size (DEFAULT pool) (and db_recycle_cache_size, db_keep_cache_size if additional buffer pools are required). Do NOT use the corresponding db_nk_cache_size parameter for the standard block size.
-
ORA-00381: cannot use both new and old parameters for buffer cache size specification
-
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.
-
Action: Use EITHER the old (pre-Oracle_8.2) parameters OR the new ones. Don't specify both. If old size parameters are specified in the parameter file, you may want to replace them with new parameters since the new parameters can be modified dynamically and allow you to configure additional caches for additional block sizes. Cache advisory can only be enabled with the new cache parameters.
-
ORA-00382: string not a valid block size, valid range [string..string]
-
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.
-
Action: Remove corresponding parameter from the "init.ora" file and restart the instance.
-
ORA-00383: DEFAULT cache for blocksize string cannot be reduced to zero
-
Cause: User attempted to reduce db_cache_size to zero, or attempted to to reduce db_<n>K_cache_size to zero while there were still online tablespaces with blocksize <n>K. Note that since the SYSTEM tablespace cannot be taken offline, it is always illegal to set db_cache_size to zero.
-
Action: Offline any tablespaces with the corresponding blocksize and then perform the operation again.
-
ORA-00385: cannot enable Very Large Memory with new buffer cache parameters
-
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) } AND use_indirect_data_buffers is set to TRUE. This is illegal.
-
Action: Very Large Memory can only be enabled with the old (pre-Oracle_8.2) parameters.
-
ORA-00390: log string of thread string is being cleared, cannot become current log
-
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.
-
Action: If the clear command is still executing then wait for its completion. If it terminated then reissue the clear command, or drop the log.
-
ORA-00391: All threads must switch to new log format at the same time
-
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.
-
Action: Open the database to cause the coordinated log switch. If that is not possible then return to the same software version and compatibility setting last used to open the database.
-
ORA-00392: log string of thread string is being cleared, operation not allowed
-
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.
-
Action: If the clear command is still executing then wait for its completion. If it terminated then reissue the clear command, or drop the log.
-
ORA-00393: log string of thread string is needed for recovery of offline datafiles
-
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.
-
Action: Archive the log then repeat the clear command. If archiving is not possible, and dropping the tablespaces is acceptible, then add the clause UNRECOVERABLE DATAFILE at the end of the clear command.
-
ORA-00396: error string required fallback to single-pass recovery
-
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.
-
Action: Correct the cause of the indicated error (also recorded) so that future instance or crash recovery can succeed with the two-pass algorithm. This usually requires making more main memory available to the recovery process.
-
ORA-00402: database changes by release string cannot be used by release string
-
Cause: Changes have been made to the database that require a newer software release or that violate the compatibility parameters.
-
Action: Use a version of the software that can understand the changes or relax the compatibility requirements in the init file.
-
ORA-00406: COMPATIBLE parameter needs to be string or greater
-
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.
-
Action: Shutdown and startup with a higher compatibility setting.
-
ORA-00409: COMPATIBLE needs to be string or higher to use AUTO SEGMENT SPACE MANAGEMENT
-
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.
-
Action: Shutdown and startup with the specified compatibility setting.
-
ORA-00569: Failed to acquire global enqueue.
-
Cause: A prior error occurred on one of the instances in the cluster. Typically errors are caused by shared pool resource contention.
-
Action: Check for and resolve prior errors on all instances in the cluster. If there is shared pool resource contention, increase the SHARED_POOL_SIZE, DML_LOCKS, PROCESSES, TRANSACTIONS, CLUSTER_DATABASE_INSTANCES and PARALLEL_MAX_SERVERS initialization parameters.
-
ORA-00600: internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string], [string], [string], [string], [string]
-
Cause: This is the generic internal error number for Oracle program exceptions. This indicated that a process encountered an exceptional condition.
-
Action: Report as a bug - the first argument is the internal error number.
-
ORA-00604: error occurred at recursive SQL level string
-
Cause: An error occurred while processing a recursive SQL statement (a statement applying to internal dictionary tables).
-
Action: If the situation described in the next error on the stack can be corrected, do so; otherwise contact Oracle Support.
-
ORA-00721: changes by release string cannot be used by release string
-
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.
-
Action: Use a version of the software that can understand the changes or relax the compatibility requirements in the initialization parameter file.
-
ORA-00723: Initialization parameter COMPATIBLE must be explicitly set
-
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.
-
Action: Explicitly set the value of COMPATIBLE parameter either in PFILE or SPFILE, whichever is used.
-
ORA-00752: recovery detected a lost write of a data block
-
Cause: A write of a data block to storage was lost during normal database operation on the primary database.
-
Action: Shutdown the primary database and activate the physical standby database to failover. See the Data Guard Concepts and Administration guide for details.
-
ORA-00820: Specified value of sga_max_size is too small, needs to be at least stringM
-
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.
-
Action: Set sga_max_size to the recommended value or reduce the values of any SGA component size parameters you have specified.
-
ORA-00821: Specified value of sga_target stringM is too small, needs to be at least stringM
-
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.
-
Action: Set sga_target to the recommended value or reduce the values of any SGA component size parameters you have specified.
-
ORA-00827: could not shrink sga_target to specified value
-
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.
-
Action: Do not set sga_target to a value below the current value without first shrinking the individual SGA components.
-
ORA-00828: specified value of shared_pool_reserved_size inconsistent with internal settings
-
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.
-
Action: If possible, do not set shared_pool_reserved_size without setting shared_pool_size if SGA_TARGET set. Examine the alert log for information about current internal size of shared pool, and valid range of values for shared_pool_reserved_size.
-
ORA-00830: cannot set statistics_level to BASIC with auto-tune SGA enabled
-
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.
-
Action: Disable auto-tune SGA and try setting the statistics_level to BASIC again.
-
ORA-00832: no streams pool created and cannot automatically create one
-
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.
-
Action: Please set the parameter streams_pool_size or set SGA_TARGET.
-
ORA-00839: SGA_TARGET cannot be modified to the specified value
-
Cause: The specified value of SGA_TARGET was not compatible with current settings of PGA_AGGREGATE_TARGET and MEMORY_TARGET/MEMORY_MAX_TARGET.
-
Action: Set SGA_TARGET to be no more than the difference of MEMORY_TARGET/MEMORY_MAX_TARGET and PGA_AGGREGATE_TARGET. Also ensure that the current PGA memory used for non-auto workareas is low.
-
ORA-00840: PGA_AGGREGATE_TARGET cannot be modified to the specified value
-
Cause: The specified value of PGA_AGGREGATE_TARGET was not compatible with current settings of SGA_TARGET and MEMORY_TARGET/MEMORY_MAX_TARGET.
-
Action: Set PGA_AGGREGATE_TARGET to be no more than the difference of MEMORY_TARGET/MEMORY_MAX_TARGET and SGA_TARGET.
-
ORA-00845: MEMORY_TARGET not supported on this system
-
Cause: The MEMORY_TARGET parameter was not supported on this operating system or /dev/shm was not sized correctly on Linux.
-
Action: Refer to documentation for a list of supported operating systems. Or, size /dev/shm to be at least the SGA_MAX_SIZE on each Oracle instance running on the system.
-
ORA-00846: could not shrink MEMORY_TARGET to specified value
-
Cause: Attempted to shrink MEMORY_TARGET to the specified value but did not succeed because the PGA and SGA components could not be shrunk.
-
Action: Do not set MEMORY_TARGET to a value below the current value without first shrinking the individual memory components.