Oracle 12C Error Codes, Solutions and Suggestions from ORA 19700 to ORA 20000
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.
Cause: The device name indicated is invalid.
Action: Supply a correct device name and retry the allocation.
- ORA-19702: device parameter exceeds maximum length of string
- 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.
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.
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.
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.
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.
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.
Cause: A numeric parameter to an DBMS_BACKUP_RESTORE procedure is negative or contains a fractional portion.
Action: Supply a valid numeric parameter.
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.
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.
Cause: The table name string exceeds maximum length.
Action: Retry the operation with a shorter table name.
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.
Cause: The specified format exceeds the maximum length for the piece name.
Action: Change the format to create shorter piece names.
Cause: A restricted format or undefined format was used incorrectly.
Action: Change the format specified in the additional information by removing the restricted format.
Cause: There were errors while processing the format to generate name for backup.
Action: Change the format.
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.
Cause: The specified command id exceeds the maximum length for command id.
Action: Supply a shorter command id and retry the operation.
Cause: The specified operation name exceeds the maximum length for operation name.
Action: Supply a shorter operation name and retry the operation.
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.
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.
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.
Cause: The datafile is plugged in read only. It can not recreated.
Action: Use ALTER DATABASE RENAME FILE command instead.
Cause: The snapshot SCN is before the SCN at which the referred datafile is plugged into the database.
Action: retry the query.
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.
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.
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.
Cause: The file is not the initial version of the plugged in datafile.
Action: Use the correct initial version of the plugged in datafile.
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.
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.
Cause: The number of datafiles in the export file for the referred tablespace is not the same as expected. This is most likely caused by a user editing the export file.
Action: Use the correct export file and retry the operation.
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.
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.
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.
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.
Cause: The compatibility check failed because a character set name that was provided is not valid.
Action: Correct the character set name and retry.
Cause: The specified text exceeds the maximum length for text.
Action: Supply a shorter text and retry the operation.
Cause: The specified string exceeds the maximum allowable length for the parameter
Action: Supply a shorter string for the parameter and retry the operation.
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.
Cause: The specified server and volume combination was not found and could not be unmounted.
Action: Specify the server and volume name correctly to complete the operation successfully.
Cause: The specified volume could not be unmounted because it was in use and had open files.
Action: Retry the unmount after all open files in the volume have been closed.
Cause: This message reports the name of a file involved in other messages.
Action: See associated error messages for a description of the problem.
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.
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.
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.
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.
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.
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.
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.
Cause: out of SGA memory
Action: Increase SGA and restart the instance.
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.
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.
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.
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.
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.
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.
Cause: The change tracking file does not match the one that was present when this instance was opened. In RAC, this error is most likely caused 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.
Cause: Syntax error.
Action: Use the correct syntax: ENABLE/DISABLE BLOCK CHANGE TRACKING
Cause: Syntax error.
Action: Use the correct syntax: ENABLE/DISABLE BLOCK CHANGE TRACKING
Cause: The USING clause was specified with DISABLE CHANGE TRACKING
Action: Correct the statement.
Cause: Syntax error.
Action: Use the correct syntax: ENABLE/DISABLE BLOCK CHANGE TRACKING
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.
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.
Cause: The name specified for the change tracking file is too long.
Action: Specify a shorter 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.
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.
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.
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.
Cause: Change tracking at a standby database required the Active Data Guard option.
Action: Enable the Active Data Guard option.
Cause: The PROXY option was used with a sparse file. This is not supported.
Action: Do not use the PROXY option with sparse files.
Cause: The name given for an Oracle managed files destination cannot be initialized.
Action: Check previous error messages for the reason Oracle was unable to initialize destination. Take corrective action, if possible, and retry the command or use a different name for destination.
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.
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.
Cause: Parameter DB_RECOVERY_FILE_DEST_SIZE specified was not valid.
Action: Specify a valid number within the range.
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.
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.
Cause: Duplex backup to recovery area is not supported.
Action: Remove duplex option and try again.
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.
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.
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.
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.
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.
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.
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
Cause: Logging was disabled when ARCHIVELOG mode was used.
Action: Execute ALTER DATABASE NOARCHIVELOG in mount state.
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.
Cause: An attempt to resore a preplugin file in a recovery area failed. This is not supported.
Action: Use the SET ARCHVIELOG DESTINATION RMAN command to specify an archivelog destination and retry the RESTORE or RECOVER command.
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.
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.
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.
Cause: This control file was restored by a DUPLICATE operation used only to restore and recover the data files of the new database. It is not meant to be used for mounting or opening the database, as allowing so might corrupt data files or online redo logs of the target database or both.
Action: Re-create the control file manually specifying all of the names of the data files and online redo logs. Do not forget to use NID to change the name or DBID or both of the new database.
Cause: The snapshot time which was specified when starting the recovery less than data file’s checkpoint time. The snapshot recovery is only possible with data file’s whose checkpoint time is less than snapshot time.
Action: Restore the data file’s associated for the specified snapshot time or specify the correct snapshot time associated with the data file.
Cause: An attempt was made to use SNAPSHOT TIME recovery. But, the feature was not enabled.
Action: Contact Oracle Support Services to enable snapshot time recovery and then retry the command.
Cause: An attempt to create a cross-platform backup was made but the COMPATIBLE parameter was not set to a high enough value to allow this.
Action: Do not attempt to use this functionality or raise the compatibility level.
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: Retry the backup.
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.
Cause: The database ID on the remote site did not match the ID of the target database. This is most likely caused by a wrong service name for the remote connection.
Action: Supply the correct service name and retry the command.
Cause: An error occurred while initiating backup on remote database server for network restore. Additional error messages will be issued to describe the failure.
Action: Check additional error messages.
Cause: Unable to read the file header from remote site.
Action: Make sure the data file is accessible on remote site and retry the command.
Cause: Could not read the control file header from the remote site.
Action: Make sure the database is mounted on the remote site and retry the command.
Cause: An attempt was made to perform a cross-platform operation from a backup piece created with a higher compatibility than the current COMPATIBLE parameter.
Action: Raise the compatibility level or do not attempt a cross-platform restore from this backup piece.
Cause: This error should be followed by other errors indicating the cause of the problem.
Action: See other errors actions.
Cause: This error indicates that the backup piece that was constructed from the service is corrupt.
Action: See alert log for details of the corruption. Fix the corruption and retry the command.
Cause: An OS error was received while managing the automatic auxiliary instance.
Action: Check the accompanying errors.
Cause: An error was received while managing the services of the auxiliary instance.
Action: Check the accompanying errors.
Cause: An error was received while managing the automatic auxiliary instance.
Action: Check the accompanying errors.
Cause: Could not obtain the connect string from the target database
Action: Check the accompanying errors.
Cause: The clone mounted control file could not be used to drop the database because the names of the data files and online logs were not fixed using the RMAN DUPLICATE command. This could cause the original database files to be lost.
Action: Manually drop the database.
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.
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.
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.
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.
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.
Cause: During a block recovery, the header of the datafile could not be updated.
Action: Contact Oracle Support Services.
Cause: This backup piece container identifier did not match the supplied data file container identifier.
Action: Retry the command with the correct backup piece or the correct data file.
Cause: This error should be followed by other errors indicating the cause of the problem.
Action: See other errors actions.
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.
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.
Cause: During a multisection restore or copy, the file being restored was not a file in which a multisection restore or copy was in progress.
Action: If this error occurs while running RMAN, then it was an internal error and you should contact Oracle Support Services.
Cause: While completing a multisection restore or copy, 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 Services.
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.
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.
Cause: Accompanying errors detail the problem that prevented Unused Block Optimization from being used.
Action: See accompanying errors for appropriate 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.
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.
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.
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.
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.
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.
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.
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.
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 command. To see which incarnations are available for this target database, query V$DATABASE_INCARNATION or use RMAN’s LIST INCARNATION command.
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.
Cause: The specified datafile has an invalid checkpoint.
Action: Restore the datafile from a backup.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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-19925: Internal error while cleaning memory used by V$RMAN_STATUS view
- ORA-19926: Database cannot be converted at this time
Cause: Another CONVERT DATABASE operation is already in progress.
Action: Retry CONVERT DATABASE command later.
Cause: An error occurred earlier during CONVERT DATABASE operation.
Action: Retry CONVERT DATABASE command.
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.
Cause: An error occurred during ALTER DATABASE RECOVER with the FORCE START AT option because there were no archive logs registered in the control file covering the specified start SCN or time.
Action: Register archive logs covering the specified SCN or time.
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.
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.
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.
Cause: This backup piece contained data pump dump file. Cataloging such a backup piece is not supported.
Action: Do not request to catalog data pump dump file backup piece.
Cause: An attempt was made to validate block 0 of a datafile.
Action: Do not specify block 0 for validation.
Cause: The data file was moved or rekeyed.
Action: Check the status of the data file and try this command again.
Cause: Some tablespaces that were specified for restoration were not found in the backup set directory. Message 19937 is issued for each file that was not found.
Action: See the instructions for message 19937.
Cause: The indicated tablespace could not be restored because it was not in this backup set.
Action: This message is issued when the directory from the first backup piece is read and one or more tablespaces named for restoration are not found. The restore conversation is still active, but no data has been read and you must supply the first backup piece of a backup set that contains all of the requested files or tablespaces or both.
Cause: Data Pump dump file backup requested but COMPATIBLE did not allow it.
Action: Do not request dump file backup or set COMPATIBLE to minimum value and retry backup.
Cause: Data Pump dump file backup requested but the backup conversation is not a cross-platform conversation.
Action: Start a new cross-platform backup conversation or do not include a Data Pump dump file.
Cause: Cross-platform backups or restores of whole database between different endianess was requested but it is not supported.
Action: Revise the specified platforms for conversion before retrying the command.
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.
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.
Cause: The Data Pump dump file could not be restored because it was not in this backup set.
Action: This message is issued when the directory from the first backup piece is read and the Data Pump dump file is not found in the piece. You must supply the first backup piece of a backup set that contains the requested file.
Cause: The backup piece did not belong to the platform specified in FROM PLATFORM.
Action: Retry the restore using the correct FROM PLATFORM or without specifying FROM PLATFORM at all.
Cause: This file was already specified for inclusion in this restore conversation. The restore conversation may process only a single instance of a datafile.
Action: No action required. The conversation is still active and more files can be specified.
Cause: It was not possible to determine the cross-platform transportable backup piece block size.
Action: Contact Oracle Support Services.
Cause: The block size obtained from the backup piece using the specified platform was not valid. Either the piece is corrupted or the specified platform is incorrect.
Action: Retry the restore using the correct FROM PLATFORM clause.
Cause: A cross-platform transportable restore was specified but the backup piece was not produced with the correct command.
Action: Produce a cross-platform transportable backup piece by using BACKUP … TO PLATFORM and retry the restore.
Cause: The backup piece had a different endianess than the platform specified in FROM PLATFORM.
Action: Retry the restore using the correct FROM PLATFORM or without specifying FROM PLATFORM at all.
Cause: This tablespace was already specified for inclusion in this restore conversation.
Action: No action required. The conversation is still active and more tablespaces or files or both can be specified. The restore conversation may process only a single instance of a tablespace.
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.
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.
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.
Cause: The operation failed because a non-current, non-standby control file was mounted.
Action: Make the control file current and retry.
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.
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.
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.
Cause: DIAG requested a control file operation that may lead to a deadlock
Action: Try last operation later when the control file is released
Cause: An attempt was made to use the DBNEWID utility in a pluggable database.
Action: Connect to CDB$ROOT and retry the command.
Cause: NID usage
Action: None
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.
Cause: Algorithm in initialization parameter requires a lower compatibility that is currently set.
Action: Change algorithm in initialization parameter file or lower compatibility.
Cause: Error occurred when querying the logical block size of a file.
Action: None
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.
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.
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.
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.
Cause: ALTER DATABASE RECOVER TO LOGICAL required only one instance to be left running.
Action: Shutdown all but one instance, then retry the command.
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.
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.
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.
Cause: The standby role transition operation failed because a concurrent standby role transition was already in progress.
Action: None
Cause: When attempting to open the specified dump file, an error was received.
Action: Verify that the specified dump file exists and is accessible.
Cause: When attempting to read the header of the specified dump file, an error was received.
Action: Verify that the specified dump file is complete.
Cause: The specified dump file did not contain data created by Data Pump.
Action: Verify that the specifed dump file is really a file created by Data Pump.
Cause: Some data blocks for the Data Pump dump file were corrupt in the backup set.
Action: Unless the damage to the backup set can be repaired, the Data Pump dump file cannot be restored from this backup set.
Cause: Data Pump dump file restore requested but COMPATIBLE did not allow it.
Action: Do not request dump file backup or set COMPATIBLE to minimum value and retry backup.
Cause: Data Pump dump file restore requested but the restore conversation is not a cross-platform conversation.
Action: Start a new cross-platform restore conversation or do not include a Data Pump dump file.
Cause: A cross-platform backup was requested for a backup piece that contained archived logs.
Action: Specify a datafile backup piece for cross-platform processing.
Cause: The platform ID obtained from a cross-platform backup was incorrect.
Action: Verify that the platform specified in the FROM PLATFORM clause is correct.
- ORA-19988: must specify FROM PLATFORM for cross-platform restore of backup sets with pre-12.1 compatibility
Cause: A cross-platform restore was requested from a backup piece created with pre-12.1 compatibility without providing the platform name that created it.
Action: Reissue the command including the FROM PLATFORM clause.
Cause: A cross-platform restore was requested from an encrypted backup set.
Action: Specify a non-encrypted backup set from which to perform the restore.
Cause: A cross-platform backup was requested for an encrypted backup to a different endianess from the current platform.
Action: Do not specify an encrypted backup or specify the same endian platform.
- ORA-19992: cross-platform backup of encrypted backup piece with different endianess is not supported
Cause: A cross-platform backup was requested for an encrypted backup piece with different endianess from the current platform.
Action: Specify a backup piece without encryption to the backup.
- ORA-19993: must specify FROM PLATFORM for cross-platform backup of backup pieces with compatibility set prior to 12.1
Cause: A cross-platform backup was requested for a backup piece created with compatibility prior to 12.1 without providing the platform name that created it.
Action: Reissue the command including the FROM PLATFORM clause.
Cause: A cross-platform backup was requested for a compressed backup to a different endianess from the current platform.
Action: Do not specify a compressed backup or specify the same endian platform.
Cause: A restore of the controlfile was requested from a cross-platform backup, but the backup did not have the same endianess and restore was not possible.
Action: Do not attempt to restore a controlfile from a cross-platform backup set.
Cause: A cross-platform backup was requested for a backup created with pre-10.2 compatibility.
Action: Do not attempt to perform cross-platform backup of backups created with with pre-10.2 compatibility.
Cause: A cross-platform operation was requested for a backup created with pre-10.2 compatibility.
Action: Do not attempt to perform the cross-platform operation of backups created with pre-10.2 compatibility.
Cause: This data file was already specified for inclusion in this restore conversation.
Action: No action required. The conversation is still active and more files can be specified. 19999 is used for event
- 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.
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.
Comments
Post a Comment