Oracle 11g Error Codes and Solution Suggestions from ORA-19900 to ORA-20000
- ORA-19900: RESETLOGS must be specified after recovery to new incarnation
- Cause: Recovery was done to an incarnation after changing the destination incarnation using RMAN’s RESET DATABASE command.
- Action: Open the database with the RESETLOGS option.
- ORA-19901: database needs more recovery to create new incarnation
- Cause: Recovery was done to an incarnation after changing the destination incarnation using RMAN’s RESET DATABASE command, but one or more of the recovered datafiles still belongs to the parent incarnation. This usually happens when recovery is ended before any logs from the desired incarnation have been applied.
- Action: Continue recovery.
- ORA-19902: incarnation key string not found
- Cause: The specified incarnation was not found in the control file.
- Action: Resubmit request with known incarnation key. To see which incarnations are available for this target database, query V$DATABASE_INCARNATION or use RMAN’s LIST INCARNATION command.
- ORA-19903: test recovery not allowed when recovering to new incarnation
- Cause: Either a new incarnation was set using RMAN’s RESET DATABASE command for a control file that was CURRENT, or the control file is from a prior incarnation. As recovery to a new incarnation requires changing the control file, test recovery is not allowed.
- Action: Perform actual recovery or RESET DATABASE to incarnation that was last opened using the control file to do test recovery.
- ORA-19904: test recovery not allowed for datafile string
- Cause: The specified datafile has been restored from a backup that was taken before the last RESETLOGS. Recovering this datafile will require a file header update that is incompatible with test recovery.
- Action: Perform actual recovery.
- ORA-19905: log_archive_format must contain %s, %t and %r
- Cause: log_archive_format is missing a mandatory format element. Starting with Oracle 10i, archived log file names must contain each of the elements %s(sequence), %t(thread), and %r(RESETLOGS ID) to ensure that all archived log file names are unique.
- Action: Add the missing format elements to log_archive_format.
- ORA-19906: recovery target incarnation changed during recovery
- Cause: While a media recovery was active, a new incarnation was detected by the server due to inspection or cataloging of archived logs or backup files.
- Action: If you want recovery to use the new incarnation, restart recovery. This is the most common action on a standby database when RESETLOGS is done in primary. If you do not want recovery to use the new incarnation, change the recovery destination using RMAN’s RESET DATABASE TO INCARNATION <incarnation#> command. To see which incarnations are available for this target database, query V$DATABASE_INCARNATION or use RMAN’s LIST INCARNATION command.
- ORA-19907: recovery time or SCN does not belong to recovered incarnation
- Cause: A point-in-time recovery to an SCN or time stamp prior to the last RESETLOGS was requested.
- Action: Either change the specified recovery time/SCN, or change the recovery destination using RMAN’s RESET DATABASE command.
- ORA-19908: datafile string has invalid checkpoint
- Cause: The specified datafile has an invalid checkpoint.
- Action: Restore the datafile from a backup.
- ORA-19909: datafile string belongs to an orphan incarnation
- Cause: Either the specified datafile was restored from a backup that was taken during a period of time that has already been discarded by a RESETLOGS operation, or Oracle cannot identify which database incarnation the file belongs to. The alert log contains more information.
- Action: Restore a backup of this file that belongs to either the current or a prior incarnation of the database. If you are using RMAN to restore, RMAN will automatically select a correct backup.
- ORA-19910: can not change recovery target incarnation in control file
- Cause: The RESET DATABASE TO INCARNATION command was used while the database is open. This is not allowed.
- Action: Close the database then re-issue the command.
- ORA-19911: datafile string contains future changes at the incarnation boundary
- Cause: The file did not hit end backup marker redo during recovery at the incarnation boundary, hence may contain changes discarded by new incarnation.
- Action: Use older backup of the file and then re-issue the command.
- ORA-19912: cannot recover to target incarnation string
- Cause: The control file is not in the recovery path of the target incarnation, and does not contain enough information as to how to recover to the target incarnation.
- Action: Restore the latest control file from the target incarnation and retry.
- ORA-19913: unable to decrypt backup
- Cause: A backup piece could not be decrypted. This message is accompanied with another message that indicates the name of the encrypted backup that could not be restored. The reason could be either that an invalid password was entered, or that, when using transparent decryption, the database external security device is not open.
- Action: If password-based restore was enabled for this backup, then supply the correct password using the RMAN SET DECRYPTION command. If transparent restore was enabled for this backup, then ensure that the database external security device is open.
- ORA-19914: unable to encrypt backup
- Cause: RMAN could not create an encrypted backup. This message will be accompanied by other messages that give more details about why the encrypted backup could not be created. The most common reason for this message is that you are trying to create a backup that can be transparently decrypted, and the database external security device is not open.
- Action: If the external security device is not open, then open it. If the external security device is not configured, then the only type of encrypted backup that you can create is a password-based backup.
- ORA-19915: unable to encrypt pre-10.2 files
- Cause: An RMAN encrypted backup was requested, but this backup includes one or more archived logs that were generated by an older release of Oracle. These archived logs cannot be encrypted.
- Action: Back up the older logs without encryption. Logs created with Oracle release 10.2 and greater can be encrypted.
- ORA-19916: string
- Cause: An error occurred when processing user request.
- Action: Do not use message 19917; it is used internally for testing purpose. Do not use message 19918; it is an internal event used by encryption.
- ORA-19919: encrypted backups to tertiary storage require Oracle Secure Backup
- Cause: RMAN was configured to create encrypted backups, but the channel is neither a DISK channel nor an Oracle Secure Backup channel.
- Action: Allocate a DISK channel or an Oracle Secure Backup channel to use backup encryption.
- ORA-19920: RMAN does not support PKI-based master key for encryption.
- Cause: An attempt was made to use Oracle public key infrastructure (PKI) based master key algorithm. RMAN only supports Advanced Encryption Standard (AES) based encryption.
- Action: Use AES based encryption.
- ORA-19921: maximum number of string rows exceeded
- Cause: The maximum number of rows in the V$RMAN_STATUS or V$RMAN_OUTPUT table has been exceeded.
- Action: Close some of existing and unused RMAN connections and sessions.
- ORA-19922: there is no parent row with id string and level string
- Cause: RMAN tried to add a new V$RMAN_STATUS row, but the parent row did not exist.
- Action: This is an internal error. Contact Oracle Support.
- ORA-19923: the session for row with id string is not active
- Cause: RMAN tried to update an V$RMAN_STATUS row but the process which owns this row died.
- Action: This is an internal error. Contact Oracle Support.
- ORA-19924: there are no row with id string
- Cause: RMAN tried to update an V$RMAN_STATUS row, but the row don’t exist.
- Action: This is an internal error. Contact Oracle Support.
- ORA-19926: Database cannot be converted at this time
- Cause: Another CONVERT DATABASE operation is already in progress.
- Action: Retry CONVERT DATABASE command later.
- ORA-19927: CONVERT DATABASE operation cannot proceed
- Cause: An error occurred earlier during CONVERT DATABASE operation.
- Action: Retry CONVERT DATABASE command.
- ORA-19928: CONVERT of data files with undo segments between different endian is not supported.
- Cause: Conversion of data files with undo segments was not supported between endianess. The only time that data files with undo segments can be converted is between the same endianess as part of convert database. Convert database between different endian is not supported.
- Action: Do not attempt to convert data files with undo segments between different endian.
- ORA-19930: file string has invalid checkpoint SCN string
- Cause: When opening the file to be placed in a copy or backup set, to be inspected, the file header was not recognized as a valid header because it contained a invalid checkpoint SCN. The indicated file cannot be processed.
- Action: Ensure that the correct files are being specified for the catalog or backup operation.
- ORA-19931: file string has invalid creation SCN string
- Cause: When opening the file to be placed in a copy or backup set, to be inspected, the file header was not recognized as a valid header because it contained a invalid creation SCN. The indicated file cannot be processed.
- Action: Ensure that the correct files are being specified for the catalog or backup operation.
- ORA-19932: control file is not clone, standby or backup
- Cause: The operation failed because the control file was not mounted as clone, standby or backup.
- Action: Mount the database as clone, standby or backup and retry.
- ORA-19941: invalid blocksize in cross platform datafile string
- Cause: Blocksize in header of datafile copy being converted at target was invalid. Either datafile has not been made read/write with compatibility 10.0 or greater at source database or datafile copy is corrupted.
- Action: Make a new datafile copy taken after tablespace has been made read/write with compatibility 10.0 at source database and retry conversion.
- ORA-19942: datafile copy string not created with compatibility 10.0 or greater
- Cause: The specified datafile copy to be converted at the target was not produced after making the tablespace in read/write mode with compatibility 10.0 or greater at the source database.
- Action: Make a new datafile copy taken after tablespace has been made read/write with compatibility 10.0 at source database and retry conversion.
- ORA-19943: The current database incarnation changed during backup
- Cause: The backup failed because the current database incarnation was changed during the backup. One of the following events caused this incarnation change:
- – The database was opened using ALTER DATABASE OPEN RESETLOGS statement.
- – RMAN command RESET DATABASE TO INCARNATION was issued.
- – If this happened on physical standby database, then redo apply has applied redo data from a new database incarnation.
- Action: Re-try the backup.
- ORA-19951: cannot modify control file until DBNEWID is completed
- Cause: An operation requiring to modify the control file was attempted, but a NID change is in progress.
- Action: Wait until NID completes before attempting the operation.
- ORA-19952: database should be mounted exclusively
- Cause: The database was started in parallel mode. To change the DBID, the database must be mounted exclusively.
- Action: Shut down the database and start it in exclusive mode.
- ORA-19953: database should not be open
- Cause: The database was open. To change the DBID, the database must be mounted exclusively.
- Action: Shut down the database and mount it in exclusive mode.
- ORA-19954: control file is not current
- Cause: The operation failed because a non-current, non-standby control file was mounted.
- Action: Make the control file current and retry.
- ORA-19955: only one open thread is allowed to change the DBID
- Cause: The operation failed because there were active threads in the database. The most likely cause is that the database crashed the last time it was shut down.
- Action: Ensure that all threads are closed before retrying the operation. Start and open the database to perform crash recovery, then shut down with the NORMAL or IMMEDIATE options to close it cleanly. Finally, try running the utility again.
- ORA-19956: database should have no offline immediate datafiles
- Cause: The operation failed because the database had one or more datafiles that were in OFFLINE IMMEDIATE mode.
- Action: Drop the datafiles or recover them and bring them online.
- ORA-19957: database should have no datafiles in unknown state
- Cause: The operation failed because the database had one or more datafiles that were in an unknown state.
- Action: Drop the datafiles or recover them and bring them online.
- ORA-19958: potential deadlock involving DIAG process
- Cause: DIAG requested a control file operation that may lead to a deadlock
- Action: Try last operation later when the control file is released
- ORA-19960: Internal use only
- Cause: NID usage
- Action: None
- ORA-19961: compression algorithm string requires advanced compression option to be enabled
- Cause: Requested compression algorithm in initialization parameter or by RMAN configuration requires that the advanced compression option be enabled and it was not.
- Action: Change initialization parameter advanced_compression_option_usable to true or change RMAN configurations and retry the operation.
- ORA-19962: compression algorithm string is not valid with release string
- Cause: Algorithm in initialization parameter requires a lower compatibility that is currently set.
- Action: Change algorithm in initialization parameter file or lower compatibility.
- ORA-19963: error getting logical block size of file string
- Cause: Error occurred when querying the logical block size of a file.
- Action: None
- ORA-19965: ALTER DATABASE RECOVER STANDBY TABLESPACE has been deprecated
- Cause: The STANDBY TABLESPACE clause of the ALTER DATABASE RECOVER statement (partial_database_recovery clause) has been deprecated.
- Action: If you want to recover the standby database to a consistent point, but no further, use the statement ALTER DATABASE RECOVER MANAGED STANDBY DATABASE UNTIL CONSISTENT.
- ORA-19966: ALTER DATABASE RECOVER STANDBY DATAFILE has been deprecated
- Cause: The STANDBY DATAFILE clause of the ALTER DATABASE RECOVER statement (partial_database_recovery clause) has been deprecated.
- Action: If you want to recover the standby database to a consistent point, but no further, use the statement ALTER DATABASE RECOVER MANAGED STANDBY DATABASE UNTIL CONSISTENT.
- ORA-19970: multi-instance standby role transition in progress
- Cause: ALTER DATABASE MOUNT failed because a multi-instance standby role transition was in progress.
- Action: Retry after the multi-instance standby role transition finishes.
- ORA-19971: event 10875 or 10879 is set
- Cause: Event 10875 or event 10879 was set which prevented the operation from completing with multiple instances running in Oracle RAC.
- Action: Shutdown all but one instance, then retry the command.
- ORA-19972: ALTER DATABASE RECOVER TO LOGICAL requires one instance left
- Cause: ALTER DATABASE RECOVER TO LOGICAL required only one instance to be left running.
- Action: Shutdown all but one instance, then retry the command.
- ORA-19973: flashback database is not enabled
- Cause: Physical standby transition to snapshot standby required only one instance left running if flashback database logging was not enabled.
- Action: Shutdown all but one instance, then retry the command.
- ORA-19974: database name has changed
- Cause: Physical standby role transition required only one instance left running if database name was changed and flashback database logging was enabled.
- Action: Shutdown all but one instance, then retry the command.
- ORA-19975: database must not be started in any other instance
- Cause: The physical standby role transition command failed because a certain condition required the database to be mounted in this instance and not started in any other instance.
- Action: See associated error message for detailed explanation.
- ORA-19976: a concurrent standby role transition in progress
- Cause: The standby role transition operation failed because a concurrent standby role transition was already in progress.
- Action: None
- ORA-19999: skip_row procedure was called
- Cause: The skip_row procedure was called which raises this error
- Action: Skip_row should only be called within a trigger or a procedure called by a trigger.
- ORA-20000: string
- Cause: The stored procedure ‘raise_application_error’ was called which causes this error to be generated.
- Action: Correct the problem as described in the error message or contact the application administrator or DBA for more information.