Oracle 11g Error Codes and Solution Suggestions from ORA-19700 to ORA-19900

Oracle 11g Error Codes and Solution Suggestions from ORA-19700 to ORA-19900

ORA-19700: device type exceeds maximum length of string

Cause: The device type indicated is invalid.

Action: Supply a correct device type and retry the allocation.

ORA-19701: device name exceeds maximum length of string

Cause: The device name indicated is invalid.

Action: Supply a correct device name and retry the allocation.

ORA-19703: device command string exceeds maximum length of string

Cause: The device command string exceeds maximum length.

Action: Correct the command and retry the operation.

ORA-19704: file name exceeds maximum length of string

Cause: The specified file name, which was a parameter to a copy, backup, or restore operation, exceeds the maximum file name length for this operating system.

Action: Retry the operation with a shorter file name.

ORA-19705: tag value exceeds maximum length of string characters

Cause: During a backup or copy operation, the user supplied a tag value too long to fit in the file header.

Action: Supply a shorter tag and retry the operation.

ORA-19706: invalid SCN

Cause: The input SCN is either not a positive integer or too large.

Action: Check the input SCN and make sure it is a valid SCN.

ORA-19707: invalid record block number – string

Cause: The input number is either negative or too large.

Action: Check the input record block number and make sure it is a valid number clauses in the create database statement.

ORA-19708: log destination exceeds maximum length of string characters

Cause: When starting a restore conversation, the user specified a log restore destination longer than the port-specific maximum.

Action: Supply a shorter destination and retry the operation.

ORA-19709: numeric parameter must be non-negative integer

Cause: A numeric parameter to an DBMS_BACKUP_RESTORE procedure is negative or contains a fractional portion.

Action: Supply a valid numeric parameter.

ORA-19710: unsupported character set string

Cause: When the target database is not mounted, RMAN sets the target database character set to the value specified in the users environment.

Action: Specify a valid character set in the environment. This is usually done via the NLS_LANG environment variable.

ORA-19711: cannot use RENORMALIZEALLFILENAMES while database is open

Cause: An attempt was made to re-normalize all the file names in the control file while the database is open.

Action: Close the database before using the RENORMALIZEALLFILENAMES procedure.

ORA-19712: table name exceeds maximum length of string

Cause: The table name string exceeds maximum length.

Action: Retry the operation with a shorter table name.

ORA-19713: invalid copy number: string

Cause: The copy number is not in a valid range or you have reached maximum limit.

Action: Report the error and other information to support.

ORA-19714: length for generated name longer than string

Cause: The specified format exceeds the maximum length for the piece name.

Action: Change the format to create shorter piece names.

ORA-19715: invalid format string for generated name

Cause: A restricted format or undefined format was used incorrectly.

Action: Change the format specified in the additional information by removing the restricted format.

ORA-19716: error processing format string to generate name for backup

Cause: There were errors while processing the format to generate name for backup.

Action: Change the format.

ORA-19717: for non-OMF search the pattern must be specified

Cause: The procedure DBMS_BACKUP_RESTORE.SEARCHFILES was called with an empty pattern while the parameter OMF was set to FALSE.

Action: Either specify the pattern or set the parameter OMF to TRUE.

ORA-19718: length for command id longer than string

Cause: The specified command id exceeds the maximum length for command id.

Action: Supply a shorter command id and retry the operation.

ORA-19719: length for operation name longer than string

Cause: The specified operation name exceeds the maximum length for operation name.

Action: Supply a shorter operation name and retry the operation.

ORA-19720: Error occurred when converting an OCI number into an SCN

Cause: This is most likely caused by an invalid SCN number that came from an external file, such as an export file.

Action: See other errors on the error stack to look for the source of the problem.

ORA-19721: Cannot find datafile with absolute file number string in tablespace string

Cause: Can not find one of the datafile that should be in the Pluggable Set.

Action: Make sure all datafiles are specified via import command line option or parameter files.

ORA-19722: datafile string is an incorrect version

Cause: The datafile is an incorrect version. It contains either less or more changes then the desired version.

Action: Make sure the right datafiles are transported. Make sure the datafile is copied while its tablespace is read only.

ORA-19723: Cannot recreate plugged in read-only datafile string

Cause: The datafile is plugged in read only. It can not recreated.

Action: Use ALTER DATABASE RENAME FILE command instead.

ORA-19724: snapshot too old: snapshot time is before file string plug-in time

Cause: The snapshot SCN is before the SCN at which the referred datafile is plugged into the database.

Action: retry the query.

ORA-19725: can not acquire plug-in enqueue

Cause: There maybe another “ALTER DATABASE RESET COMPATIBILITY” command issued concurrently, preventing this process from acquiring the plug-in enqueue.

Action: retry the operation.

ORA-19726: cannot plug data [string] at level string into database running at compatibility level string

Cause: Some of the data in the pluggable set requires a compatibility level higher than what is currently allowed by the database. The string in square bracket is the name of the compatibility type associated with the data.

Action: Raise the “compatible” init.ora parameter and retry the operation.

ORA-19727: cannot plug data [string] at level string into database running Oracle string

Cause: Some of the data in the pluggable set requires a compatibility level higher than the release level of the Oracle executable. The string in square bracket is the name of the compatibility type associated with the data.

Action: Upgrade Oracle and retry the operation.

ORA-19728: data object number conflict between table string and partition string in table string

Cause: The non-partitioned table has the same data object number as one of the partitions in the partitioned table. One can not exchange the table with the partition in this case.

Action: Use “alter table move partition” command to move the offending partition, so that the partition will get a new data object number. Retry the operation then.

ORA-19729: File string is not the initial version of the plugged in datafile

Cause: The file is not the initial version of the plugged in datafile.

Action: Use the correct initial version of the plugged in datafile.

ORA-19730: can not convert offline plugged-in datafile string

Cause: As part of making a tablespace read-write, we need to convert datafiles that are plugged in read-only. The file must be online.

Action: Online the datafile and retry the operation.

ORA-19731: cannot apply change to unverified plugged-in datafile string

Cause: Recovery was not able to verify the referred datafile according to information in the control file. Before encountering this change vector for this file, somehow recovery did not encounter the file conversion redo that is supposed to verify the file. This may happen due to corrupted or incorrect control file used for media recovery.

Action: Use the correct control file and continue recovery.

ORA-19732: incorrect number of datafiles for tablespace string

Cause: d by a user editing the export file.

Action: Use the correct export file and retry the operation.

ORA-19733: 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-19734: wrong creation SCN – control file expects converted plugged-in datafile

Cause: When a tablespace is plugged into a database, the tablespace is initially read-only. Oracle converts the header of the plugged-in datafiles (assign them a new creation SCN) when the tablespace is first made read-write. This error occurs when the creation SCN in the file header is different from the creation SCN in the control file, possibly because this is the initial version of plugged-in datafile.

Action: Either restore the converted datafile or continue recovering the datafile.

ORA-19735: wrong creation SCN – control file expects initial plugged-in datafile

Cause: When a tablespace is plugged into a database, the tablespace is initially read-only. Oracle converts the header of the plugged-in datafiles (assign them a new creation SCN) when the tablespace is first made read-write. This error occurs when the creation SCN in the file header is different from the creation SCN in the control file, possibly because this is the converted datafile.

Action: Either restore the initial version of the plugged-in datafile, or continue database recovery, which will recover the control file.

ORA-19736: can not plug a tablespace into a database using a different national character set

Cause: Oracle does not support plugging a tablespace into a database using a different national character set.

Action: Use import/export or unload/load to move data instead.

ORA-19738: cannot find language information for character set: ‘string‘

Cause: The compatibility check failed because a character set name that was provided is not valid.

Action: Correct the character set name and retry.

ORA-19740: text is longer than string

Cause: The specified text exceeds the maximum length for text.

Action: Supply a shorter text and retry the operation.

ORA-19741: string exceeds maximum allowable length of string for parameter ‘string‘

Cause: The specified string exceeds the maximum allowable length for the parameter

Action: Supply a shorter string for the parameter and retry the operation.

ORA-19742: control file is not a backup control file

Cause: This parameter could not be set because the control file was not a backup control file.

Action: Do not use this call for this control file.

ORA-19750: change tracking file: ‘string‘

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

Action: See associated error messages for a description of the problem.

ORA-19751: could not create the change tracking file

Cause: It was not possible to create the change tracking file.

Action: Check that there is sufficient disk space and no conflicts in file names and try to enable block change tracking again.

ORA-19752: block change tracking is already enabled

Cause: The ALTER DATABASE ENABLE BLOCK CHANGE TRACKING command was issued, but block change tracking is already turned on for this database.

Action: None, this is an informative message only.

ORA-19753: error writing to change tracking file

Cause: An I/O error occurred while writing to the change tracking file.

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

ORA-19754: error reading from change tracking file

Cause: An I/O error occurred while reading from the change tracking file.

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

ORA-19755: could not open change tracking file

Cause: The change tracking file could not be opened.

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

ORA-19756: corrupt block number string found in change tracking file

Cause: The specified block number is corrupt in the change tracking file.

Action: There will be other messages on the error stack that show details of the problem. There will also be a trace file that contains a complete dump of the corrupt block.

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.

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

Cause: out of SGA memory

Action: Increase SGA and restart the instance.

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-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-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-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-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-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-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-19766: missing CHANGE keyword

Cause: Syntax error.

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

ORA-19767: missing TRACKING keyword

Cause: Syntax error.

Action: Use the correct syntax: ENABLE/DISABLE BLOCK 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-19769: missing FILE keyword

Cause: Syntax error.

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

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-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-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-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-19776: PROXY restore to ASM disk group “string” is not supported.

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

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

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-19779: could not obtain resilvering status for change tracking file

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

Action: Refer to other error messages shown for additional details of the problem.

ORA-19780: Active Data Guard option not enabled

Cause: Change tracking at a standby database required the Active Data Guard option.

Action: Enable the Active Data Guard option.

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-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 archived log file creation was attempted. 2) STANDBY_ARCHIVE_DEST parameter was specified using a LOCATION attribute whose value was DB_RECOVERY_FILE_DEST and an archived log 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-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-19803: Parameter DB_RECOVERY_FILE_DEST_SIZE is out of range (1 – string)

Cause: Parameter DB_RECOVERY_FILE_DEST_SIZE specified was not valid.

Action: Specify a valid number within the range.

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 archived log deletion policy. 4) Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE. 5) Delete files from recovery area using RMAN.

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 recovery area for other operations.

Action: Wait and try again.

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-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-19809: limit exceeded for recovery files

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

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 archived log deletion policy. 4) Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE. 5) Delete files from recovery area using RMAN.

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-19811: cannot have files in DB_RECOVERY_FILE_DEST with keep attributes

Cause: An attempt was made to 1) Create a backup piece 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-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-19813: cannot have unavailable file string in DB_RECOVERY_FILE_DEST

Cause: An attempt was made to change a backup piece 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-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 archived log deletion policy.

5. Delete files from recovery area using RMAN.

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 reclamation before backup Do not use messages 19819; it is used to disable clearing file name

ORA-19820: database must be in NOARCHIVELOG mode to disable logging

Cause: Logging was disabled when ARCHIVELOG mode was used.

Action: Execute ALTER DATABASE NOARCHIVELOG in mount state.

ORA-19821: an intentionally corrupt log file was found

Cause: A log file that was intentionally corrupt for testing or benchmarking purposes was found and failed the operation.

Action: Remove such log files and retry or use the NOARCHIVELOG option if possible.

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-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-19836: cannot use passphrase encryption for this backup

Cause: Passphrase encryption was attempted for a backup that contains encrypted tablespaces and uses compression.

Action: Do not use passphrase encryption for this backup. Use transparent wallet-based encryption instead.

ORA-19837: invalid blocksize string in backup piece header

Cause: The blocksize of the backup piece obtained from the header was invalid.

Action: The backup piece is corrupted, a different backup piece should be used for restore.

ORA-19838: Cannot use this control file to open database

Cause: This control file was restored by a DUPLICATE operation used only to restore and recover the datafiles of the new database. It is not meant to be used for opening the database, as allowing so might corrupt datafiles or online redo logs of the target database or both.

Action: Re-create control file manually specifying all names of datafiles and online redo logs. Do not forget to use NID to change the name or DBID or both of the new database.

ORA-19843: Cannot obtain datafile name for datafile string

Cause: While trying to obtain the file enqueue for the datafile the datafile name could not be obtained.

Action: Examine the trace and alert files for possible causes. Fix underlying problem before attempting command again.

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-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-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-19854: error obtaining connect string from target

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

Action: Check the accompanying errors.

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-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-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-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-19865: Backup piece string has no data

Cause: No data was returned for the specified backup piece.

Action: This normally indicates a problem with the media management software which is linked with Oracle to provide backup and restore services. Contact the media management software vendor.

ORA-19866: error writing file header for datafile string

Cause: During a block recovery, the header of the datafile could not be updated.

Action: Contact Oracle Support Services.

ORA-19870: error while restoring backup piece string

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

Action: See other errors actions.

ORA-19872: Unexpected end of file at block string while decompressing backup piece string

Cause: While reading a compressed backup piece, RMAN received an end-of-file without finding the end-of-compression stream.

Action: This is most likely caused by a corrupted backup piece. Consider using a different backup piece for restore.

ORA-19873: cannot apply this backup section to file string

Cause: RMAN cannot restore a multi-section backup to the indicated file, because this section is not a backup of this file, or the file was not prepared correctly for this restore.

Action: If this error occurs while running RMAN, then it is an internal error and you should contact Oracle support.

ORA-19874: cannot finish multi-section restore to file string

Cause: During a multi-section restore, the file being restored is not a file in which a multi-section restore is in progress.

Action: If this error occurs while running RMAN, then it is an internal error and you should contact Oracle support.

ORA-19875: multi-section restore not complete for file string

Cause: While completing a multi-section restore, it was found that all required sections for this file were not correctly applied.

Action: If this error occurs while running RMAN, then it is an internal error and you should contact Oracle support.

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

Cause: When reading the space header block to use Unused Block Optimization for the backup of the datafile, the space header block had corrupted information.

Action: The corrupt space header must be fixed before Unused Block Optimization can be used for this file. Note that you should fix the corruption in any case because it will affect the availability of the data in the file, beyond just taking backups.

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

Cause: When reading a space bitmap block to use Unused Block Optimization for the backup of the datafile, the space bitmap block had corrupted information.

Action: The corrupt space bitmap must be fixed before Unused Block Optimization can be used for this file. Note that you should fix the corruption in any case because it will affect the availability of the data in the file, beyond just taking backups.

ORA-19882: datafile string checkpoint string is ahead of space bitmap datafile string checkpoint string

Cause: When checkpointing the datafile containing the space bitmaps for the datafile being backed up in order to use Unused Block Optimization, the checkpoint of the datafile containing the space bitmaps did not advance.

Action: Examine the trace and alert files for possible causes. Fix underlying problem to use Unused Block Optimization for datafile’s backup.

ORA-19883: Unused Block Optimization stopped for datafile string

Cause: Accompanying errors detail the problem that prevented Unused Block Optimization from being used.

Action: See accompanying errors for appropiate action.

ORA-19884: datafile string is unable to use Unused Block Optimization because tablespace has been dropped

Cause: When attempting to find information about datafile that holds bitmaps of migrated tablespace, the tablespace was found to have been dropped.

Action: None. This is an informational message.

ORA-19899: missing incarnation information

Cause: Media recovery stopped because information of one or more ancestor incarnations of recovery target incarnation was not available.

Action: Register logs from the missing incarnations and retry recovery.

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.

45 total views, no views today

Follow