{"id":1976,"date":"2016-05-14T14:41:48","date_gmt":"2016-05-14T11:41:48","guid":{"rendered":"http:\/\/www.fatihacar.com\/blog\/?p=1976"},"modified":"2016-10-26T14:49:42","modified_gmt":"2016-10-26T11:49:42","slug":"oracle-11g-error-codes-and-solution-suggestions-from-ora-19900-to-ora-20000","status":"publish","type":"post","link":"http:\/\/www.fatihacar.com\/blog\/oracle-11g-error-codes-and-solution-suggestions-from-ora-19900-to-ora-20000\/","title":{"rendered":"Oracle 11g Error Codes and Solution Suggestions from ORA-19900 to ORA-20000"},"content":{"rendered":"

Oracle 11g Error Codes and Solution Suggestions from ORA-19900 to ORA-20000<\/strong><\/p>\n

\n
ORA-19900: RESETLOGS must be specified after recovery to new incarnation<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Recovery was done to an incarnation after changing the destination incarnation using RMAN’s RESET DATABASE command.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Open the database with the RESETLOGS option.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19901: database needs more recovery to create new incarnation<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Recovery 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Continue recovery.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19902: incarnation key\u00a0string<\/i>\u00a0not found<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The specified incarnation was not found in the control file.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Resubmit 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.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19903: test recovery not allowed when recovering to new incarnation<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Either 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Perform actual recovery or RESET DATABASE to incarnation that was last opened using the control file to do test recovery.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19904: test recovery not allowed for datafile\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Perform actual recovery.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19905: log_archive_format must contain %s, %t and %r<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0log_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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Add the missing format elements to log_archive_format.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19906: recovery target incarnation changed during recovery<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0While a media recovery was active, a new incarnation was detected by the server due to inspection or cataloging of archived logs or backup files.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0If 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.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19907: recovery time or SCN does not belong to recovered incarnation<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0A point-in-time recovery to an SCN or time stamp prior to the last RESETLOGS was requested.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Either change the specified recovery time\/SCN, or change the recovery destination using RMAN’s RESET DATABASE command.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19908: datafile\u00a0string<\/i>\u00a0has invalid checkpoint<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The specified datafile has an invalid checkpoint.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Restore the datafile from a backup.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19909: datafile\u00a0string<\/i>\u00a0belongs to an orphan incarnation<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Either 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Restore 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.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19910: can not change recovery target incarnation in control file<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The RESET DATABASE TO INCARNATION command was used while the database is open. This is not allowed.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Close the database then re-issue the command.<\/span><\/span><\/span><\/dd>\n

<\/p>\n

<\/a><\/a>ORA-19911: datafile\u00a0string<\/i>\u00a0contains future changes at the incarnation boundary<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The file did not hit end backup marker redo during recovery at the incarnation boundary, hence may contain changes discarded by new incarnation.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Use older backup of the file and then re-issue the command.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19912: cannot recover to target incarnation\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Restore the latest control file from the target incarnation and retry.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19913: unable to decrypt backup<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0A 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0If 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.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19914: unable to encrypt backup<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0RMAN 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0If 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.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19915: unable to encrypt pre-10.2 files<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Back up the older logs without encryption. Logs created with Oracle release 10.2 and greater can be encrypted.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19916:\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An error occurred when processing user request.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Do not use message 19917; it is used internally for testing purpose. Do not use message 19918; it is an internal event used by encryption.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19919: encrypted backups to tertiary storage require Oracle Secure Backup<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0RMAN was configured to create encrypted backups, but the channel is neither a DISK channel nor an Oracle Secure Backup channel.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Allocate a DISK channel or an Oracle Secure Backup channel to use backup encryption.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19920: RMAN does not support PKI-based master key for encryption.<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to use Oracle public key infrastructure (PKI) based master key algorithm. RMAN only supports Advanced Encryption Standard (AES) based encryption.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Use AES based encryption.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19921: maximum number of\u00a0string<\/i>\u00a0rows exceeded<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The maximum number of rows in the V$RMAN_STATUS or V$RMAN_OUTPUT table has been exceeded.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Close some of existing and unused RMAN connections and sessions.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19922: there is no parent row with id\u00a0string<\/i>\u00a0and level\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0RMAN tried to add a new V$RMAN_STATUS row, but the parent row did not exist.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0This is an internal error. Contact Oracle Support.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19923: the session for row with id\u00a0string<\/i>\u00a0is not active<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0RMAN tried to update an V$RMAN_STATUS row but the process which owns this row died.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0This is an internal error. Contact Oracle Support.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19924: there are no row with id\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0RMAN tried to update an V$RMAN_STATUS row, but the row don’t exist.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0This is an internal error. Contact Oracle Support.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19926: Database cannot be converted at this time<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Another CONVERT DATABASE operation is already in progress.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Retry CONVERT DATABASE command later.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19927: CONVERT DATABASE operation cannot proceed<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An error occurred earlier during CONVERT DATABASE operation.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Retry CONVERT DATABASE command.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19928: CONVERT of data files with undo segments between different endian is not supported.<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Conversion 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Do not attempt to convert data files with undo segments between different endian.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19930: file\u00a0string<\/i>\u00a0has invalid checkpoint SCN\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0When 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Ensure that the correct files are being specified for the catalog or backup operation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19931: file\u00a0string<\/i>\u00a0has invalid creation SCN\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0When 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Ensure that the correct files are being specified for the catalog or backup operation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19932: control file is not clone, standby or backup<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The operation failed because the control file was not mounted as clone, standby or backup.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Mount the database as clone, standby or backup and retry.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19941: invalid blocksize in cross platform datafile\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Blocksize 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Make a new datafile copy taken after tablespace has been made read\/write with compatibility 10.0 at source database and retry conversion.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19942: datafile copy\u00a0string<\/i>\u00a0not created with compatibility 10.0 or greater<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Make a new datafile copy taken after tablespace has been made read\/write with compatibility 10.0 at source database and retry conversion.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19943: The current database incarnation changed during backup<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The backup failed because the current database incarnation was changed during the backup. One of the following events caused this incarnation change:<\/span><\/span><\/span><\/dd>\n
– The database was opened using ALTER DATABASE OPEN RESETLOGS statement.<\/span><\/span><\/span><\/dd>\n
– RMAN command RESET DATABASE TO INCARNATION was issued.<\/span><\/span><\/span><\/dd>\n
– If this happened on physical standby database, then redo apply has applied redo data from a new database incarnation.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Re-try the backup.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19951: cannot modify control file until DBNEWID is completed<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An operation requiring to modify the control file was attempted, but a NID change is in progress.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Wait until NID completes before attempting the operation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19952: database should be mounted exclusively<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The database was started in parallel mode. To change the DBID, the database must be mounted exclusively.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Shut down the database and start it in exclusive mode.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19953: database should not be open<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The database was open. To change the DBID, the database must be mounted exclusively.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Shut down the database and mount it in exclusive mode.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19954: control file is not current<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The operation failed because a non-current, non-standby control file was mounted.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Make the control file current and retry.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19955: only one open thread is allowed to change the DBID<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Ensure 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.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19956: database should have no offline immediate datafiles<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The operation failed because the database had one or more datafiles that were in OFFLINE IMMEDIATE mode.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Drop the datafiles or recover them and bring them online.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19957: database should have no datafiles in unknown state<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The operation failed because the database had one or more datafiles that were in an unknown state.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Drop the datafiles or recover them and bring them online.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19958: potential deadlock involving DIAG process<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0DIAG requested a control file operation that may lead to a deadlock<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Try last operation later when the control file is released<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19960: Internal use only<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0NID usage<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0None<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19961: compression algorithm\u00a0string<\/i>\u00a0requires advanced compression option to be enabled<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Requested compression algorithm in initialization parameter or by RMAN configuration requires that the advanced compression option be enabled and it was not.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Change initialization parameter advanced_compression_option_usable to true or change RMAN configurations and retry the operation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19962: compression algorithm\u00a0string<\/i>\u00a0is not valid with release\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Algorithm in initialization parameter requires a lower compatibility that is currently set.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Change algorithm in initialization parameter file or lower compatibility.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19963: error getting logical block size of file\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Error occurred when querying the logical block size of a file.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0None<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19965: ALTER DATABASE RECOVER STANDBY TABLESPACE has been deprecated<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The STANDBY TABLESPACE clause of the ALTER DATABASE RECOVER statement (partial_database_recovery clause) has been deprecated.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0If 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.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19966: ALTER DATABASE RECOVER STANDBY DATAFILE has been deprecated<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The STANDBY DATAFILE clause of the ALTER DATABASE RECOVER statement (partial_database_recovery clause) has been deprecated.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0If 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.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19970: multi-instance standby role transition in progress<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0ALTER DATABASE MOUNT failed because a multi-instance standby role transition was in progress.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Retry after the multi-instance standby role transition finishes.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19971: event 10875 or 10879 is set<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Event 10875 or event 10879 was set which prevented the operation from completing with multiple instances running in Oracle RAC.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Shutdown all but one instance, then retry the command.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19972: ALTER DATABASE RECOVER TO LOGICAL requires one instance left<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0ALTER DATABASE RECOVER TO LOGICAL required only one instance to be left running.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Shutdown all but one instance, then retry the command.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19973: flashback database is not enabled<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Physical standby transition to snapshot standby required only one instance left running if flashback database logging was not enabled.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Shutdown all but one instance, then retry the command.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19974: database name has changed<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Physical standby role transition required only one instance left running if database name was changed and flashback database logging was enabled.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Shutdown all but one instance, then retry the command.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19975: database must not be started in any other instance<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The 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.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0See associated error message for detailed explanation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19976: a concurrent standby role transition in progress<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The standby role transition operation failed because a concurrent standby role transition was already in progress.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0None<\/span><\/span><\/span><\/dd>\n
ORA-19999: skip_row procedure was called<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The skip_row procedure was called which raises this error<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Skip_row should only be called within a trigger or a procedure called by a trigger.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-20000:\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The stored procedure ‘raise_application_error’ was called which causes this error to be generated.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Correct the problem as described in the error message or contact the application administrator or DBA for more information.<\/span><\/span><\/span><\/dd>\n
<\/dd>\n<\/dl>\n","protected":false},"excerpt":{"rendered":"

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:\u00a0Recovery was done to an incarnation after changing the destination incarnation using RMAN’s RESET DATABASE command. Action:\u00a0Open the database with the RESETLOGS option. ORA-19901: database needs more recovery to create new incarnation Cause:\u00a0Recovery was…<\/p>\n","protected":false},"author":37,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[53],"tags":[14,32,54],"class_list":["post-1976","post","type-post","status-publish","format-standard","hentry","category-oracle-errors-and-solutions","tag-database-administration","tag-oracle-administration","tag-oracle-error-solutions"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p39NFI-vS","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1976","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/users\/37"}],"replies":[{"embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/comments?post=1976"}],"version-history":[{"count":1,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1976\/revisions"}],"predecessor-version":[{"id":1977,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1976\/revisions\/1977"}],"wp:attachment":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/media?parent=1976"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/categories?post=1976"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/tags?post=1976"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}