ORA-19912: cannot recover to target incarnation string

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-19911: datafile string contains future changes at the incarnation boundary

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-19910: can not change recovery target incarnation in control file

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-19909: datafile string belongs to an orphan incarnation

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-19908: datafile string has invalid checkpoint

ORA-19908: datafile string has invalid checkpoint

Cause: The specified datafile has an invalid checkpoint.

Action: Restore the datafile from a backup.

ORA-19907: recovery time or SCN does not belong to recovered incarnation

ORA-19907: recovery time or SCN does not belong to recovered incarnation

Cause: A point-in-time recovery to an SCN or timestamp prior to the last resetlogs was requested.

Action: Either change the specified recovery time or scn, or change the recovery destination using RMAN s RESET DATABASE command.

ORA-19906: recovery target incarnation changed during recovery

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 lamp;lt;lamp;nbsp;incarnation#lamp;gt; command. To see which incarnations are available for this target database, query V$DATABASE_INCARNATION or use RMAN s LIST INCARNATION command.

ORA-19905: log_archive_format must contain %%s, %%t and %%r

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-19904: test recovery not allowed for datafile string

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-19903: test recovery not allowed when recovering to new incarnation

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-19902: incarnation key string not found

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-19901: database needs more recovery to create new incarnation

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-19900: RESETLOGS must be specified after recovery to new incarnation

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-19881: Corrupted space bitmap for datafile string, block string backup aborted

ORA-19881: Corrupted space bitmap for datafile string, block string backup aborted

Cause: When reading a space bitmap block to optimize the backup of the datafile, the space bitmap block was corrupted.

Action: Fix corruption before attempting backup again.

ORA-19880: Corrupted space header for datafile string, block string backup aborted

ORA-19880: Corrupted space header for datafile string, block string backup aborted

Cause: When reading the space header block to optimize the backup of the datafile, the space header block was corrupted.

Action: Fix corruption before attempting backup again.

ORA-19870: error reading backup piece string

ORA-19870: error reading backup piece string

Cause: This error should be followed by other errors indicating the cause of the problem.

Action: See other errors actions. Do not use message 19871; it is used by RMAN client for testing previous resync time when using backup or standby control file.

ORA-19863: device block size string is larger than max allowed: string

ORA-19863: device block size string is larger than max allowed: string

Cause: The user specified a device BLKSIZE that is larger than the device BLKSIZE specified during compressed backup.

Action: Change the device BLKSIZE to be smaller than the maximum allowed.

ORA-19862: backup pieces must be validated before accessing results

ORA-19862: backup pieces must be validated before accessing results

Cause: The user tried to get validation results for backup pieces before the pieces were actually validated.

Action: Validate the pieces before trying to access the results.

ORA-19861: additional backup pieces cannot be validated in this conversation

ORA-19861: additional backup pieces cannot be validated in this conversation

Cause: The user tried to add new pieces to the list of files being validated after the validation had already been performed. In a validation conversation, the list can only be validated once.

Action: Add all the backup pieces to the list before validating, or start a new validation conversation for the remaining pieces.

ORA-19860: piece validation cannot be performed more than once

ORA-19860: piece validation cannot be performed more than once

Cause: The user attempted to validate a list of backup pieces more than once. Validation may only be performed once for a given validation conversation.

Action: Do not attempt to validate the pieces more than once.

ORA-19854: error obtaining connect string from target

ORA-19854: error obtaining connect string from target

Cause: Could not obtain the connect string from the target database

Action: Check the accompanying errors.

ORA-19853: error preparing auxiliary instance string (error string)

ORA-19853: error preparing auxiliary instance string (error string)

Cause: An error was received while managing the automatic auxiliary instance.

Action: Check the accompanying errors.

ORA-19852: error creating services for auxiliary instance string (error string)

ORA-19852: error creating services for auxiliary instance string (error string)

Cause: An error was received while managing the services of the auxiliary instance.

Action: Check the accompanying errors.

ORA-19851: OS error while managing auxiliary database string

ORA-19851: OS error while managing auxiliary database string

Cause: An OS error was received while managing the automatic auxiliary instance.

Action: Check the accompanying errors.

ORA-19831: incompatible string.string.string.string DBMS_BACKUP_RESTORE package: string.string.string.string required

ORA-19831: incompatible string.string.string.string DBMS_BACKUP_RESTORE package: string.string.string.string required

Cause: This version of database was incompatible with the the indicated dbms_ backup_restore package installed in the database.

Action: If the database has been upgraded from an earlier version, ensure that the catxxxx.sql script has been run successfully. Re-install dbmsbkrs.sql and prvtbkrs.plb if necessary.

ORA-19830: error from target database: string

ORA-19830: error from target database: string

Cause: This error should be followed by other errors indicating the cause of the problem.

Action: No action required.

ORA-19816: WARNING: Files may exist in string that are not known to database.

ORA-19816: WARNING: Files may exist in string that are not known to database.

Cause: One of the following events caused this: 1. A database crash happened during file creation. 2. A backup control file was restored. 3. The control file was re-created. 4. DB_RECOVERY_FILE_DEST has previously been enabled and then disabled.

Action: Use RMAN command CATALOG RECOVERY AREA to re-catalog any such files. If the file header is corrupted, then delete those files using an OS utility. Do not use messages 19817; it is used for simulating lock failure Do not use messages 19818; it is used for space reclaimation before backup

ORA-19815: WARNING: string of string bytes is string%% used, and has string remaining bytes available.

ORA-19815: WARNING: string of string bytes is string%% used, and has string remaining bytes available.

Cause: DB_RECOVERY_FILE_DEST is running out of disk space.

Action: One of the following: 1. Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE. 2. Backup files to tertiary device using RMAN. 3. Consider changing RMAN retention policy. 4. Consider changing RMAN archivelog deletion policy. 5. Delete files from recovery area using RMAN.

ORA-19813: cannot have unavailable file string in DB_RECOVERY_FILE_DEST

ORA-19813: cannot have unavailable file string in DB_RECOVERY_FILE_DEST

Cause: An attempt was made to change backuppiece or image copy in recovery area to UNAVAILABLE.

Action: Correct and resubmit the RMAN command. Do not use messages 19814; it is used for simulating crash.

ORA-19812: cannot use string without DB_RECOVERY_FILE_DEST

ORA-19812: cannot use string without DB_RECOVERY_FILE_DEST

Cause: There are three possible cause for this error: 1) The indicated parameter was in use when no DB_RECOVERY_FILE_DEST parameter was encountered while fetching the initialization parameter. 2) An attempt was made to set indicated the parameter with the ALTER SYSTEM command when no DB_ RECOVERY_FILE_DEST was in use. 3) An attempt was made to clear DB_ RECOVERY_FILE_DEST with the ALTER SYSTEM command when the indicated parameter was in use.

Action: Eliminate any incompatible parameter definitions.

ORA-19811: cannot have files in DB_RECOVERY_FILE_DEST with keep attributes

ORA-19811: cannot have files in DB_RECOVERY_FILE_DEST with keep attributes

Cause: An attempt was made to 1) Create backuppiece or image copy in the recovery area with KEEP option. 2) Update the KEEP attributes of an existing backup piece or image copy in the recovery area.

Action: Reissue RMAN command without KEEP options.

ORA-19810: Cannot create temporary control file string in DB_RECOVERY_FILE_ DEST

ORA-19810: Cannot create temporary control file string in DB_RECOVERY_FILE_ DEST

Cause: An attempt was made to create a control file for a temporary purpose in DB_RECOVERY_FILE_DEST.

Action: Retry the operation with a new file name.

ORA-19809: limit exceeded for recovery files

ORA-19809: limit exceeded for recovery files

Cause: The limit for recovery files specified by the DB_RECOVERY_FILE_DEST_ SIZE was exceeded.

Action: The error is accompanied by 19804. See message 19804 for further details.

ORA-19808: recovery destination parameter mismatch

ORA-19808: recovery destination parameter mismatch

Cause: The value of parameters DB_RECOVERY_FILE_DEST and DB_ RECOVERY_FILE_DEST_SIZE must be same in all instances. instance. All databases must have same recovery destination parameters.

Action: Check DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_ SIZE values in all instances.

ORA-19806: cannot make duplex backups in recovery area

ORA-19806: cannot make duplex backups in recovery area

Cause: Duplex backup to recovery area is not supported.

Action: Remove duplex option and try again.

ORA-19805: recid string of string was deleted to reclaim disk space

ORA-19805: recid string of string was deleted to reclaim disk space

Cause: The file described by the record in control file was deleted in order to reclaim disk space from flash recovery area for other operations.

Action: Wait and try again.

ORA-19804: cannot reclaim string bytes disk space from string limit

ORA-19804: cannot reclaim string bytes disk space from string limit

Cause: Oracle cannot reclaim disk space of specified bytes from the DB_ RECOVERY_FILE_DEST_SIZE limit.

Action: There are five possible solutions: 1) Take frequent backup of recovery area using RMAN. 2) Consider changing RMAN retention policy. 3) Consider changing RMAN archivelog deletion policy. 4) Add disk space and increase DB_ RECOVERY_FILE_DEST_SIZE. 5) Delete files from recovery area using RMAN.

ORA-19803: Parameter DB_RECOVERY_FILE_DEST_SIZE is out of range (1 - string)

ORA-19803: Parameter DB_RECOVERY_FILE_DEST_SIZE is out of range (1 - string)

Cause: Parameter DB_RECOVERY_FILE_DEST_SIZE specfied was not valid.

Action: Specify a valid number within the range.

ORA-19802: cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_ FILE_DEST_SIZE

ORA-19802: cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_ FILE_DEST_SIZE

Cause: There are two possible cause for this error: 1) The DB_RECOVERY_FILE_ DEST parameter was in use when no DB_RECOVERY_FILE_DEST_SIZE parameter was encountered while fetching initialization parameter. 2) An attempt was made to set DB_RECOVERY_FILE_DEST with the ALTER SYSTEM command when no DB_RECOVERY_FILE_DEST_SIZE was in use.

Action: Correct the dependency parameter definitions and retry the command.

ORA-19801: initialization parameter DB_RECOVERY_FILE_DEST is not set

ORA-19801: initialization parameter DB_RECOVERY_FILE_DEST is not set

Cause: An attempt was made to create a file in DB_RECOVERY_FILE_DEST when DB_RECOVERY_FILE_DEST was not set. There are number of possible causes of this error, including: 1) A LOG_ARCHIVE_DEST_n parameter was specified using a LOCATION attribute whose value was DB_RECOVERY_FILE_ DEST and an archivelog file creation was attempted. 2) STANDBY_ARCHIVE_ DEST parameter was specified using a LOCATION attribute whose value was DB_ RECOVERY_FILE_DEST and an archivelog file creation was attempted.

Action: Specify a valid destination for DB_RECOVERY_FILE_DEST in initialization parameter file or with the ALTER SYSTEM SET command.

ORA-19800: Unable to initialize Oracle Managed Destination

ORA-19800: Unable to initialize Oracle Managed Destination

Cause: The name given for an Oracle managed files destination cannot be initialized.

Action: , if possible, and retry the command or use a different name for destination.

ORA-19777: ASM file string cannot be proxy backed up.

ORA-19777: ASM file string cannot be proxy backed up.

Cause: An attempt was made to proxy backup a ASM file. This is not supported.

Action: Use a different file name and reissue RMAN command.

ORA-19776: PROXY restore to ASM diskgroup string is not supported.

ORA-19776: PROXY restore to ASM diskgroup string is not supported.

Cause: An attempt was made to proxy restore a file to ASM diskgroup using RMAN command. This is not supported.

Action: Use a different file name and reissue RMAN command.

ORA-19773: must specify change tracking file name

ORA-19773: must specify change tracking file name

Cause: No file name was specified with the ALTER DATABASE ENABLE CHANGE TRACKING command, and the DB_CREATE_FILE_DEST parameter was not set.

Action: Either specify a file name, or set the DB_CREATE_FILE_DEST parameter.

ORA-19772: change tracking file name exceeds limit of string characters

ORA-19772: change tracking file name exceeds limit of string characters

Cause: The name specified for the change tracking file is too long.

Action: Specify a shorter change tracking file name.

ORA-19771: cannot rename change tracking file while database is open

ORA-19771: cannot rename change tracking file while database is open

Cause: The ALTER DATABASE RENAME FILE command was used to rename the change tracking file, and the database is open by one or more instances. The database must be mounted, and not open, to rename the change tracking file.

Action: Close the database and reissue the command.

ORA-19770: invalid change tracking file name

ORA-19770: invalid change tracking file name

Cause: The USING clause was specified with ALTER DATABASE ENABLE BLOCK CHANGE TRACKING, but no file name was given.

Action: Specify the change tracking file name, or omit the USING clause to allow Oracle to create a default name for the change tracking file.

ORA-19769: missing FILE keyword

ORA-19769: missing FILE keyword

Cause: Syntax error.

Action: Use the correct syntax: ENABLE or DISABLE BLOCK CHANGE TRACKING

ORA-19768: USING clause only valid with ENABLE CHANGE TRACKING

ORA-19768: USING clause only valid with ENABLE CHANGE TRACKING

Cause: The USING clause was specified with DISABLE CHANGE TRACKING

Action: Correct the statement.

ORA-19767: missing TRACKING keyword

ORA-19767: missing TRACKING keyword

Cause: Syntax error.

Action: Use the correct syntax: ENABLE or DISABLE BLOCK CHANGE TRACKING

ORA-19766: missing CHANGE keyword

ORA-19766: missing CHANGE keyword

Cause: Syntax error.

Action: Use the correct syntax: ENABLE or DISABLE BLOCK CHANGE TRACKING

ORA-19765: mount id string does not match mount id string in control file

ORA-19765: mount id string does not match mount id string in control file

Cause: d by having a change tracking file that cannot be consistently updated by all instances.

Action: In RAC, ensure that the name specified for the change tracking file truly represents the same disk location for all nodes in the cluster. Disable then re-enable change tracking.

ORA-19764: database id string does not match database id string in control file

ORA-19764: database id string does not match database id string in control file

Cause: The change tracking file is not the correct one for this database. This can happen when the database ID for this database has been changed.

Action: Disable then re-enable change tracking.

ORA-19763: compatibility version string is higher than maximum allowed: string

ORA-19763: compatibility version string is higher than maximum allowed: string

Cause: The compatibility version in the change tracking file is greater than what can be used by the current release of Oracle. This can happen when you upgrade, use change tracking with a new release, then downgrade.

Action: Disable then re-enable change tracking.

ORA-19762: invalid file type string

ORA-19762: invalid file type string

Cause: An invalid file type was found in the change tracking file. Some other file was put in place of the change tracking file, or the file is corrupt.

Action: Disable then re-enable change tracking.

ORA-19761: block size string is not valid for change tracking file

ORA-19761: block size string is not valid for change tracking file

Cause: While opening the specified change tracking file, it was found that the file header did not contain a valid logical block size. This probably means that the file is corrupt.

Action: If the file can be repaired, do so, otherwise disable and re-enable change tracking to re-initialize the file.

ORA-19760: error starting change tracking

ORA-19760: error starting change tracking

Cause: Change tracking is enabled, but a problem was encountered while enabling the change tracking subsystem in this instance. The alert log and the trace file from the CTWR process will contain more information about the error.

Action: Examine the trace and alert files. Correct the error if possible, otherwise disable change tracking.

ORA-19759: block change tracking is not enabled

ORA-19759: block change tracking is not enabled

Cause: A command was entered that requires block change tracking to be enabled, but block change tracking is not enabled.

Action: None, this is an informative message only.

ORA-19758: failed to enable or disable block change tracking: out of SGA memory

ORA-19758: failed to enable or disable block change tracking: out of SGA memory

Cause: out of SGA memory

Action: Increase SGA and restart the instance.

ORA-19757: could not resize change tracking file to string blocks

ORA-19757: could not resize change tracking file to string blocks

Cause: An error occurred while trying to change the size of the change tracking file.

Action: There will be other messages on the error stack that show details of the problem.