{"id":2274,"date":"2016-09-24T21:43:59","date_gmt":"2016-09-24T18:43:59","guid":{"rendered":"http:\/\/www.fatihacar.com\/blog\/?p=2274"},"modified":"2017-02-15T21:46:43","modified_gmt":"2017-02-15T18:46:43","slug":"oracle-12c-r2-error-codes-and-solution-suggestions-from-ora-19700-to-ora-20000","status":"publish","type":"post","link":"http:\/\/www.fatihacar.com\/blog\/oracle-12c-r2-error-codes-and-solution-suggestions-from-ora-19700-to-ora-20000\/","title":{"rendered":"Oracle 12c R2 Error Codes and Solution Suggestions from ORA-19700 to ORA-20000"},"content":{"rendered":"

Oracle 12c R2 Error Codes and Solution Suggestions from ORA-19700 to ORA-20000<\/strong><\/p>\n

\n
ORA-19700: device type exceeds maximum length of\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The device type indicated is invalid.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Supply a correct device type and retry the allocation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19701: device name exceeds maximum length of\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The device name indicated is invalid.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Supply a correct device name and retry the allocation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19702: device parameter exceeds maximum length of\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n
<\/a> ORA-19703: device command string exceeds maximum length of\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The device command string exceeds maximum length.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the command and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19704: file name exceeds maximum length of\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified file name, which was a parameter to a copy, backup, or restore operation, exceeds the maximum file name length for this operating system.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the operation with a shorter file name.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19705: tag value exceeds maximum length of\u00a0string<\/i>\u00a0characters<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0During a backup or copy operation, the user supplied a tag value too long to fit in the file header.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Supply a shorter tag and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19706: invalid SCN<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The input SCN is either not a positive integer or too large.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the input SCN and make sure it is a valid SCN.<\/span><\/span>
\n<\/p>\n

\n
<\/a> ORA-19707: invalid record block number –\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The input number is either negative or too large.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the input record block number and make sure it is a valid number clauses in the create database statement.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19708: log destination exceeds maximum length of\u00a0string<\/i>\u00a0characters<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0When starting a restore conversation, the user specified a log restore destination longer than the port-specific maximum.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Supply a shorter destination and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19709: numeric parameter must be non-negative integer<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A numeric parameter to an DBMS_BACKUP_RESTORE procedure is negative or contains a fractional portion.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Supply a valid numeric parameter.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19710: unsupported character set\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0When the target database is not mounted, RMAN sets the target database character set to the value specified in the users environment.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a valid character set in the environment. This is usually done via the NLS_LANG environment variable.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19711: cannot use RENORMALIZEALLFILENAMES while database is open<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to re-normalize all the file names in the control file while the database is open.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Close the database before using the RENORMALIZEALLFILENAMES procedure.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19712: table name exceeds maximum length of\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The table name string exceeds maximum length.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the operation with a shorter table name.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19713: invalid copy number:\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The copy number is not in a valid range or you have reached maximum limit.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Report the error and other information to support.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19714: length for generated name longer than\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified format exceeds the maximum length for the piece name.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Change the format to create shorter piece names.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19715: invalid format\u00a0string<\/i>\u00a0for generated name<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A restricted format or undefined format was used incorrectly.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Change the format specified in the additional information by removing the restricted format.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19716: error processing format\u00a0string<\/i>\u00a0to generate name for backup<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0There were errors while processing the format to generate name for backup.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Change the format.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19717: for non-OMF search the pattern must be specified<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The procedure DBMS_BACKUP_RESTORE.SEARCHFILES was called with an empty pattern while the parameter OMF was set to FALSE.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Either specify the pattern or set the parameter OMF to TRUE.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19718: length for command id longer than\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified command id exceeds the maximum length for command id.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Supply a shorter command id and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19719: length for operation name longer than\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified operation name exceeds the maximum length for operation name.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Supply a shorter operation name and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19720: Error occurred when converting an OCI number into an SCN<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This is most likely caused by an invalid SCN number that came from an external file, such as an export file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0See other errors on the error stack to look for the source of the problem.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19721: Cannot find datafile with absolute file number\u00a0string<\/i>\u00a0in tablespace\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Can not find one of the datafile that should be in the Pluggable Set.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Make sure all datafiles are specified via import command line option or parameter files.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19722: datafile\u00a0string<\/i>\u00a0is an incorrect version<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The datafile is an incorrect version. It contains either less or more changes then the desired version.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Make sure the right datafiles are transported. Make sure the datafile is copied while its tablespace is read only.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19723: Cannot recreate plugged in read-only datafile\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The datafile is plugged in read only. It can not recreated.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use ALTER DATABASE RENAME FILE command instead.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19724: snapshot too old: snapshot time is before file\u00a0string<\/i>\u00a0plug-in time<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The snapshot SCN is before the SCN at which the referred datafile is plugged into the database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0retry the query.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19725: can not acquire plug-in enqueue<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0There maybe another “ALTER DATABASE RESET COMPATIBILITY” command issued concurrently, preventing this process from acquiring the plug-in enqueue.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19726: cannot plug data [string<\/i>] at level\u00a0string<\/i>\u00a0into database running at compatibility level\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Some 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Raise the “compatible” init.ora parameter and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19727: cannot plug data [string<\/i>] at level\u00a0string<\/i>\u00a0into database running Oracle\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Some 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Upgrade Oracle and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19728: data object number conflict between table\u00a0string<\/i>\u00a0and partition\u00a0string<\/i>\u00a0in table\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use “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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19729: File\u00a0string<\/i>\u00a0is not the initial version of the plugged in datafile<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The file is not the initial version of the plugged in datafile.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use the correct initial version of the plugged in datafile.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19730: can not convert offline plugged-in datafile\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0As part of making a tablespace read-write, we need to convert datafiles that are plugged in read-only. The file must be online.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Online the datafile and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19731: cannot apply change to unverified plugged-in datafile\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Recovery 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use the correct control file and continue recovery.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19732: incorrect number of datafiles for tablespace\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use the correct export file and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19733: COMPATIBLE parameter needs to be\u00a0string<\/i>\u00a0or greater<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Shutdown and startup with a higher compatibility setting.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19734: wrong creation SCN – control file expects converted plugged-in datafile<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0When 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Either restore the converted datafile or continue recovering the datafile.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19735: wrong creation SCN – control file expects initial plugged-in datafile<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0When 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Either restore the initial version of the plugged-in datafile, or continue database recovery, which will recover the control file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19736: can not plug a tablespace into a database using a different national character set<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Oracle does not support plugging a tablespace into a database using a different national character set.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use import\/export or unload\/load to move data instead.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19738: cannot find language information for character set: ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The compatibility check failed because a character set name that was provided is not valid.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the character set name and retry.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19740: text is longer than\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified text exceeds the maximum length for text.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Supply a shorter text and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19741:\u00a0string<\/i>\u00a0exceeds maximum allowable length of\u00a0string<\/i>\u00a0for parameter ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified string exceeds the maximum allowable length for the parameter<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Supply a shorter string for the parameter and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19742: control file is not a backup control file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This parameter could not be set because the control file was not a backup control file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do not use this call for this control file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19743: could not unmount volume\u00a0string<\/i>:string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified server and volume combination was not found and could not be unmounted.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify the server and volume name correctly to complete the operation successfully.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19744: Volume\u00a0string<\/i>:string<\/i>\u00a0is currently in use and cannot be unmounted.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified volume could not be unmounted because it was in use and had open files.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the unmount after all open files in the volume have been closed.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19750: change tracking file: ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This message reports the name of a file involved in other messages.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0See associated error messages for a description of the problem.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19751: could not create the change tracking file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0It was not possible to create the change tracking file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check that there is sufficient disk space and no conflicts in file names and try to enable block change tracking again.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19752: block change tracking is already enabled<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The ALTER DATABASE ENABLE BLOCK CHANGE TRACKING command was issued, but block change tracking is already turned on for this database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0None, this is an informative message only.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19753: error writing to change tracking file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An I\/O error occurred while writing to the change tracking file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0There will be other messages on the error stack that show details of the problem.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19754: error reading from change tracking file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An I\/O error occurred while reading from the change tracking file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0There will be other messages on the error stack that show details of the problem.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19755: could not open change tracking file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The change tracking file could not be opened.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0There will be other messages on the error stack that show details of the problem.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19756: corrupt block number\u00a0string<\/i>\u00a0found in change tracking file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified block number is corrupt in the change tracking file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0There 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19757: could not resize change tracking file to\u00a0string<\/i>\u00a0blocks<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An error occurred while trying to change the size of the change tracking file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0There will be other messages on the error stack that show details of the problem.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19758: failed to enable\/disable block change tracking: out of SGA memory<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0out of SGA memory<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Increase SGA and restart the instance.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19759: block change tracking is not enabled<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A command was entered that requires block change tracking to be enabled, but block change tracking is not enabled.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0None, this is an informative message only.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19760: error starting change tracking<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Change 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Examine the trace and alert files. Correct the error if possible, otherwise disable change tracking.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19761: block size\u00a0string<\/i>\u00a0is not valid for change tracking file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0While 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If the file can be repaired, do so, otherwise disable and re-enable change tracking to re-initialize the file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19762: invalid file type\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Disable then re-enable change tracking.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19763: compatibility version\u00a0string<\/i>\u00a0is higher than maximum allowed:\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Disable then re-enable change tracking.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19764: database id\u00a0string<\/i>\u00a0does not match database id\u00a0string<\/i>\u00a0in control file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The change tracking file is not the correct one for this database. This can happen when the database ID for this database has been changed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Disable then re-enable change tracking.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19765: mount id\u00a0string<\/i>\u00a0does not match mount id\u00a0string<\/i>\u00a0in control file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0In 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19766: missing CHANGE keyword<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Syntax error.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use the correct syntax: ENABLE\/DISABLE BLOCK CHANGE TRACKING<\/span><\/span><\/p>\n

\n
<\/a> ORA-19767: missing TRACKING keyword<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Syntax error.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use the correct syntax: ENABLE\/DISABLE BLOCK CHANGE TRACKING<\/span><\/span><\/p>\n

\n
<\/a> ORA-19768: USING clause only valid with ENABLE CHANGE TRACKING<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The USING clause was specified with DISABLE CHANGE TRACKING<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the statement.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19769: missing FILE keyword<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Syntax error.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use the correct syntax: ENABLE\/DISABLE BLOCK CHANGE TRACKING<\/span><\/span><\/p>\n

\n
<\/a> ORA-19770: invalid change tracking file name<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The USING clause was specified with ALTER DATABASE ENABLE BLOCK CHANGE TRACKING, but no file name was given.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify the change tracking file name, or omit the USING clause to allow Oracle to create a default name for the change tracking file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19771: cannot rename change tracking file while database is open<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Close the database and reissue the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19772: change tracking file name exceeds limit of\u00a0string<\/i>\u00a0characters<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The name specified for the change tracking file is too long.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a shorter change tracking file name.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19773: must specify change tracking file name<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0No file name was specified with the ALTER DATABASE ENABLE CHANGE TRACKING command, and the DB_CREATE_FILE_DEST parameter was not set.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Either specify a file name, or set the DB_CREATE_FILE_DEST parameter.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19776: PROXY restore to ASM disk group “string<\/i>” is not supported.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to proxy restore a file to ASM disk group using RMAN command. This is not supported.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use a different file name and reissue RMAN command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19777: ASM file\u00a0string<\/i>\u00a0cannot be proxy backed up.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to proxy backup a ASM file. This is not supported.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use a different file name and reissue RMAN command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19779: could not obtain resilvering status for change tracking file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An error occurred while obtaining the mirror resilvering status of the change tracking file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Refer to other error messages shown for additional details of the problem.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19780: Active Data Guard option not enabled<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Change tracking at a standby database required the Active Data Guard option.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Enable the Active Data Guard option.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19781: The PROXY option is not supported on sparse file\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The PROXY option was used with a sparse file. This is not supported.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do not use the PROXY option with sparse files.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19800: Unable to initialize Oracle Managed Destination<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The name given for an Oracle managed files destination cannot be initialized.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19801: initialization parameter DB_RECOVERY_FILE_DEST is not set<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a valid destination for DB_RECOVERY_FILE_DEST in initialization parameter file or with the ALTER SYSTEM SET command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19802: cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_FILE_DEST_SIZE<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0There 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the dependency parameter definitions and retry the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19803: Parameter DB_RECOVERY_FILE_DEST_SIZE is out of range (1 –\u00a0string<\/i>)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Parameter DB_RECOVERY_FILE_DEST_SIZE specified was not valid.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a valid number within the range.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19804: cannot reclaim\u00a0string<\/i>\u00a0bytes disk space from\u00a0string<\/i>\u00a0bytes limit<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Oracle cannot reclaim disk space of specified bytes from the DB_RECOVERY_FILE_DEST_SIZE limit.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0There 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19805: RECID\u00a0string<\/i>\u00a0of\u00a0string<\/i>\u00a0was deleted to reclaim disk space<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The file described by the record in control file was deleted in order to reclaim disk space from recovery area for other operations.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Wait and try again.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19806: cannot make duplex backups in recovery area<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Duplex backup to recovery area is not supported.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Remove duplex option and try again.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19808: recovery destination parameter mismatch<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE values in all instances.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19809: limit exceeded for recovery files<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The limit for recovery files specified by the DB_RECOVERY_FILE_DEST_SIZE was exceeded.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0There 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19810: Cannot create temporary control file\u00a0string<\/i>\u00a0in DB_RECOVERY_FILE_DEST<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to create a control file for a temporary purpose in DB_RECOVERY_FILE_DEST.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the operation with a new file name.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19811: cannot have files in DB_RECOVERY_FILE_DEST with keep attributes<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Reissue RMAN command without KEEP options.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19812: cannot use\u00a0string<\/i>\u00a0without DB_RECOVERY_FILE_DEST<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0There 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Eliminate any incompatible parameter definitions.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19813: cannot have unavailable file\u00a0string<\/i>\u00a0in DB_RECOVERY_FILE_DEST<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to change a backup piece or image copy in recovery area to UNAVAILABLE.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct and resubmit the RMAN command. Do not use messages 19814; it is used for simulating crash.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19815: WARNING:\u00a0string<\/i>\u00a0of\u00a0string<\/i>\u00a0bytes is\u00a0string<\/i>%% used, and has\u00a0string<\/i>\u00a0remaining bytes available.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0DB_RECOVERY_FILE_DEST is running out of disk space.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0One 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19816: WARNING: Files may exist in\u00a0string<\/i>\u00a0that are not known to database.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0One 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use 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<\/span><\/span><\/p>\n

\n
<\/a> ORA-19820: database must be in NOARCHIVELOG mode to disable logging<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Logging was disabled when ARCHIVELOG mode was used.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Execute ALTER DATABASE NOARCHIVELOG in mount state.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19821: an intentionally corrupt log file was found<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A log file that was intentionally corrupt for testing or benchmarking purposes was found and failed the operation.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Remove such log files and retry or use the NOARCHIVELOG option if possible.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19827: Restoring preplugin files to a recovery area is not supported.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt to resore a preplugin file in a recovery area failed. This is not supported.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use the SET ARCHVIELOG DESTINATION RMAN command to specify an archivelog destination and retry the RESTORE or RECOVER command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19830: error from target database: \\nstring<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This error should be followed by other errors indicating the cause of the problem.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action required.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19831: incompatible\u00a0string<\/i>.string<\/i>.string<\/i>.string<\/i>\u00a0DBMS_BACKUP_RESTORE package:\u00a0string<\/i>.string<\/i>.string<\/i>.string<\/i>\u00a0required<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This version of database was incompatible with the the indicated DBMS_BACKUP_RESTORE package installed in the database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19836: cannot use passphrase encryption for this backup<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Passphrase encryption was attempted for a backup that contains encrypted tablespaces and uses compression.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do not use passphrase encryption for this backup. Use transparent wallet-based encryption instead.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19837: invalid blocksize\u00a0string<\/i>\u00a0in backup piece header<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The blocksize of the backup piece obtained from the header was invalid.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The backup piece is corrupted, a different backup piece should be used for restore.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19838: cannot use this control file to mount or open database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Re-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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19839: snapshot datafile checkpoint time is greater than snapshot time<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore the data file’s associated for the specified snapshot time or specify the correct snapshot time associated with the data file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19840: SNAPSHOT TIME recovery is not enabled<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to use SNAPSHOT TIME recovery. But, the feature was not enabled.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Contact Oracle Support Services to enable snapshot time recovery and then retry the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19841: Cross-platform backups require COMPATIBLE\u00a0string<\/i>\u00a0or greater<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt to create a cross-platform backup was made but the COMPATIBLE parameter was not set to a high enough value to allow this.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do not attempt to use this functionality or raise the compatibility level.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19842: The current database incarnation changed during backup<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The backup failed because the current database incarnation was changed during the backup. One of the following events caused this incarnation change: – 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the backup.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19843: Cannot obtain datafile name for datafile\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0While trying to obtain the file enqueue for the datafile the datafile name could not be obtained.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Examine the trace and alert files for possible causes. Fix underlying problem before attempting command again.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19844: database ID is from different database: ID=string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Supply the correct service name and retry the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19845: error in\u00a0string<\/i>\u00a0while communicating with remote database server<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An error occurred while initiating backup on remote database server for network restore. Additional error messages will be issued to describe the failure.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check additional error messages.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19846: cannot read header of datafile\u00a0string<\/i>\u00a0from remote site<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Unable to read the file header from remote site.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Make sure the data file is accessible on remote site and retry the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19847: cannot read header of control file from remote site<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Could not read the control file header from the remote site.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Make sure the database is mounted on the remote site and retry the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19848: cross-platform backup piece requires COMPATIBLE\u00a0string<\/i>\u00a0or greater<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to perform a cross-platform operation from a backup piece created with a higher compatibility than the current COMPATIBLE parameter.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Raise the compatibility level or do not attempt a cross-platform restore from this backup piece.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19849: error while reading backup piece from service\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This error should be followed by other errors indicating the cause of the problem.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0See other errors actions.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19850: backup piece constructed from service\u00a0string<\/i>\u00a0is corrupt<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This error indicates that the backup piece that was constructed from the service is corrupt.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0See alert log for details of the corruption. Fix the corruption and retry the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19851: OS error while managing auxiliary database\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An OS error was received while managing the automatic auxiliary instance.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the accompanying errors.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19852: error creating services for auxiliary instance\u00a0string<\/i>\u00a0(error\u00a0string<\/i>)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An error was received while managing the services of the auxiliary instance.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the accompanying errors.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19853: error preparing auxiliary instance\u00a0string<\/i>\u00a0(error\u00a0string<\/i>)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An error was received while managing the automatic auxiliary instance.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the accompanying errors.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19854: error obtaining connect string from target<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Could not obtain the connect string from the target database<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the accompanying errors.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19855: cannot use clone mounted control file to drop database<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Manually drop the database.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19860: piece validation cannot be performed more than once<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The user attempted to validate a list of backup pieces more than once. Validation may only be performed once for a given validation conversation.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do not attempt to validate the pieces more than once.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19861: additional backup pieces cannot be validated in this conversation<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Add all the backup pieces to the list before validating, or start a new validation conversation for the remaining pieces.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19862: backup pieces must be validated before accessing results<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The user tried to get validation results for backup pieces before the pieces were actually validated.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Validate the pieces before trying to access the results.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19863: device block size\u00a0string<\/i>\u00a0is larger than max allowed:\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The user specified a device BLKSIZE that is larger than the device BLKSIZE specified during compressed backup.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Change the device BLKSIZE to be smaller than the maximum allowed.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19864:\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n
<\/a> ORA-19865: Backup piece\u00a0string<\/i>\u00a0has no data<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0No data was returned for the specified backup piece.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0This 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19866: error writing file header for datafile\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0During a block recovery, the header of the datafile could not be updated.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Contact Oracle Support Services.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19867: backup piece\u00a0string<\/i>\u00a0is from a different container identifier\u00a0string<\/i>; data file\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This backup piece container identifier did not match the supplied data file container identifier.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the command with the correct backup piece or the correct data file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19870: error while restoring backup piece\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This error should be followed by other errors indicating the cause of the problem.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0See other errors actions.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19872: Unexpected end of file at block\u00a0string<\/i>\u00a0while decompressing backup piece\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0While reading a compressed backup piece, RMAN received an end-of-file without finding the end-of-compression stream.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0This is most likely caused by a corrupted backup piece. Consider using a different backup piece for restore.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19873: cannot apply this backup section to file\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0RMAN 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If this error occurs while running RMAN, then it is an internal error and you should contact Oracle support.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19874: cannot finish multisection restore or copy to file\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0During a multisection restore or copy, the file being restored was not a file in which a multisection restore or copy was in progress.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If this error occurs while running RMAN, then it was an internal error and you should contact Oracle Support Services.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19875: multisection restore or copy not complete for file\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0While completing a multisection restore or copy, it was found that all required sections for this file were not correctly applied.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If this error occurs while running RMAN, then it is an internal error and you should contact Oracle Support Services.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19880: Corrupted space header for datafile\u00a0string<\/i>, block\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0When reading the space header block to use Unused Block Optimization for the backup of the datafile, the space header block had corrupted information.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19881: Corrupted space bitmap for datafile\u00a0string<\/i>, block\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0When reading a space bitmap block to use Unused Block Optimization for the backup of the datafile, the space bitmap block had corrupted information.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0The 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19882: datafile\u00a0string<\/i>\u00a0checkpoint\u00a0string<\/i>\u00a0is ahead of space bitmap datafile\u00a0string<\/i>\u00a0checkpoint\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0When 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Examine the trace and alert files for possible causes. Fix underlying problem to use Unused Block Optimization for datafile’s backup.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19883: Unused Block Optimization stopped for data file\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Accompanying errors detail the problem that prevented Unused Block Optimization from being used.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0See accompanying errors for appropriate action.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19884: datafile\u00a0string<\/i>\u00a0is unable to use Unused Block Optimization because tablespace has been dropped<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0When attempting to find information about datafile that holds bitmaps of migrated tablespace, the tablespace was found to have been dropped.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0None. This is an informational message.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19899: missing incarnation information<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Media recovery stopped because information of one or more ancestor incarnations of recovery target incarnation was not available.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Register logs from the missing incarnations and retry recovery.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19900: RESETLOGS must be specified after recovery to new incarnation<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Recovery was done to an incarnation after changing the destination incarnation using RMAN’s RESET DATABASE command.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Open the database with the RESETLOGS option.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19901: database needs more recovery to create new incarnation<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Recovery was done to an incarnation after changing the destination incarnation using RMAN’s RESET DATABASE command, but one or more of the recovered datafiles still belongs to the parent incarnation. This usually happens when recovery is ended before any logs from the desired incarnation have been applied.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Continue recovery.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19902: incarnation key\u00a0string<\/i>\u00a0not found<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified incarnation was not found in the control file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Resubmit request with known incarnation key. To see which incarnations are available for this target database, query V$DATABASE_INCARNATION or use RMAN’s LIST INCARNATION command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19903: test recovery not allowed when recovering to new incarnation<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Either a new incarnation was set using RMAN’s RESET DATABASE command for a control file that was CURRENT, or the control file is from a prior incarnation. As recovery to a new incarnation requires changing the control file, test recovery is not allowed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Perform actual recovery or RESET DATABASE to incarnation that was last opened using the control file to do test recovery.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19904: test recovery not allowed for datafile\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified datafile has been restored from a backup that was taken before the last RESETLOGS. Recovering this datafile will require a file header update that is incompatible with test recovery.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Perform actual recovery.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19905: log_archive_format must contain %string<\/i>, %string<\/i>\u00a0and %%r<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0log_archive_format is missing a mandatory format element. Starting with Oracle 10i, archived log file names must contain each of the elements %s(sequence), %t(thread), and %r(RESETLOGS ID) to ensure that all archived log file names are unique.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Add the missing format elements to log_archive_format.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19906: recovery target incarnation changed during recovery<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0While a media recovery was active, a new incarnation was detected by the server due to inspection or cataloging of archived logs or backup files.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If you want recovery to use the new incarnation, restart recovery. This is the most common action on a standby database when RESETLOGS is done in primary. If you do not want recovery to use the new incarnation, change the recovery destination using RMAN’s RESET DATABASE TO INCARNATION <incarnation#> command. To see which incarnations are available for this target database, query V$DATABASE_INCARNATION or use RMAN’s LIST INCARNATION command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19907: recovery time or SCN does not belong to recovered incarnation<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A point-in-time recovery to an SCN or time stamp prior to the last RESETLOGS was requested.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Either change the specified recovery time\/SCN, or change the recovery destination using RMAN’s RESET DATABASE command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19908: datafile\u00a0string<\/i>\u00a0has invalid checkpoint<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified datafile has an invalid checkpoint.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore the datafile from a backup.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19909: datafile\u00a0string<\/i>\u00a0belongs to an orphan incarnation<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Either the specified datafile was restored from a backup that was taken during a period of time that has already been discarded by a RESETLOGS operation, or Oracle cannot identify which database incarnation the file belongs to. The alert log contains more information.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore a backup of this file that belongs to either the current or a prior incarnation of the database. If you are using RMAN to restore, RMAN will automatically select a correct backup.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19910: can not change recovery target incarnation in control file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The RESET DATABASE TO INCARNATION command was used while the database is open. This is not allowed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Close the database then re-issue the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19911: datafile\u00a0string<\/i>\u00a0contains future changes at the incarnation boundary<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The file did not hit end backup marker redo during recovery at the incarnation boundary, hence may contain changes discarded by new incarnation.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use older backup of the file and then re-issue the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19912: cannot recover to target incarnation\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The control file is not in the recovery path of the target incarnation, and does not contain enough information as to how to recover to the target incarnation.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Restore the latest control file from the target incarnation and retry.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19913: unable to decrypt backup<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A backup piece could not be decrypted. This message is accompanied with another message that indicates the name of the encrypted backup that could not be restored. The reason could be either that an invalid password was entered, or that, when using transparent decryption, the database external security device is not open.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If password-based restore was enabled for this backup, then supply the correct password using the RMAN SET DECRYPTION command. If transparent restore was enabled for this backup, then ensure that the database external security device is open.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19914: unable to encrypt backup<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0RMAN could not create an encrypted backup. This message will be accompanied by other messages that give more details about why the encrypted backup could not be created. The most common reason for this message is that you are trying to create a backup that can be transparently decrypted, and the database external security device is not open.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If the external security device is not open, then open it. If the external security device is not configured, then the only type of encrypted backup that you can create is a password-based backup.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19915: unable to encrypt pre-10.2 files<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An RMAN encrypted backup was requested, but this backup includes one or more archived logs that were generated by an older release of Oracle. These archived logs cannot be encrypted.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Back up the older logs without encryption. Logs created with Oracle release 10.2 and greater can be encrypted.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19919: encrypted backups to tertiary storage require Oracle Secure Backup<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0RMAN was configured to create encrypted backups, but the channel is neither a DISK channel nor an Oracle Secure Backup channel.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Allocate a DISK channel or an Oracle Secure Backup channel to use backup encryption.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19920: RMAN does not support PKI-based master key for encryption.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to use Oracle public key infrastructure (PKI) based master key algorithm. RMAN only supports Advanced Encryption Standard (AES) based encryption.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Use AES based encryption.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19921: maximum number of\u00a0string<\/i>\u00a0rows exceeded<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The maximum number of rows in the V$RMAN_STATUS or V$RMAN_OUTPUT table has been exceeded.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Close some of existing and unused RMAN connections and sessions.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19922: there is no parent row with id\u00a0string<\/i>\u00a0and level\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0RMAN tried to add a new V$RMAN_STATUS row, but the parent row did not exist.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0This is an internal error. Contact Oracle Support.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19923: the session for row with id\u00a0string<\/i>\u00a0is not active<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0RMAN tried to update an V$RMAN_STATUS row but the process which owns this row died.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0This is an internal error. Contact Oracle Support.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19924: there are no row with id\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0RMAN tried to update an V$RMAN_STATUS row, but the row don’t exist.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0This is an internal error. Contact Oracle Support.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19925: Internal error while cleaning memory used by V$RMAN_STATUS view<\/b><\/span><\/span><\/span><\/dt>\n
<\/a> ORA-19926: Database cannot be converted at this time<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Another CONVERT DATABASE operation is already in progress.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry CONVERT DATABASE command later.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19927: CONVERT DATABASE operation cannot proceed<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An error occurred earlier during CONVERT DATABASE operation.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry CONVERT DATABASE command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19928: CONVERT of data files with undo segments between different endian is not supported.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Conversion of data files with undo segments was not supported between endianess. The only time that data files with undo segments can be converted is between the same endianess as part of convert database. Convert database between different endian is not supported.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do not attempt to convert data files with undo segments between different endian.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19929: no archive log registered<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Register archive logs covering the specified SCN or time.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19930: file\u00a0string<\/i>\u00a0has invalid checkpoint SCN\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0When opening the file to be placed in a copy or backup set, to be inspected, the file header was not recognized as a valid header because it contained a invalid checkpoint SCN. The indicated file cannot be processed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Ensure that the correct files are being specified for the catalog or backup operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19931: file\u00a0string<\/i>\u00a0has invalid creation SCN\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0When opening the file to be placed in a copy or backup set, to be inspected, the file header was not recognized as a valid header because it contained a invalid creation SCN. The indicated file cannot be processed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Ensure that the correct files are being specified for the catalog or backup operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19932: control file is not clone, standby or backup<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The operation failed because the control file was not mounted as clone, standby or backup.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Mount the database as clone, standby or backup and retry.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19933: catalog backup piece\u00a0string<\/i>\u00a0of data pump dump file is not supported<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This backup piece contained data pump dump file. Cataloging such a backup piece is not supported.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do not request to catalog data pump dump file backup piece.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19934: cannot validate block 0<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to validate block 0 of a datafile.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do not specify block 0 for validation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19935: During backing up, the data file\u00a0string<\/i>\u00a0is moved or rekeyed to\u00a0string<\/i>.<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The data file was moved or rekeyed.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Check the status of the data file and try this command again.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19936: some tablespaces were not found in backup set<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Some 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0See the instructions for message 19937.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19937: tablespace\u00a0string<\/i>\u00a0was not found in backup set<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The indicated tablespace could not be restored because it was not in this backup set.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0This 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19938: Data Pump dump file backup requires COMPATIBLE\u00a0string<\/i>\u00a0or greater<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Data Pump dump file backup requested but COMPATIBLE did not allow it.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do not request dump file backup or set COMPATIBLE to minimum value and retry backup.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19939: Data Pump dump file can only be included in a cross-platform backup<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Data Pump dump file backup requested but the backup conversation is not a cross-platform conversation.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Start a new cross-platform backup conversation or do not include a Data Pump dump file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19940: cannot use cross-platform backups to convert whole database to different endianess<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Cross-platform backups or restores of whole database between different endianess was requested but it is not supported.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Revise the specified platforms for conversion before retrying the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19941: invalid blocksize in cross-platform datafile\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Blocksize in header of datafile copy being converted at target was invalid. Either datafile has not been made read\/write with compatibility 10.0 or greater at source database or datafile copy is corrupted.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Make a new datafile copy taken after tablespace has been made read\/write with compatibility 10.0 at source database and retry conversion.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19942: datafile copy\u00a0string<\/i>\u00a0not created with compatibility 10.0 or greater<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified datafile copy to be converted at the target was not produced after making the tablespace in read\/write mode with compatibility 10.0 or greater at the source database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Make a new datafile copy taken after tablespace has been made read\/write with compatibility 10.0 at source database and retry conversion.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19943: Data Pump dump file not found in backup set<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The Data Pump dump file could not be restored because it was not in this backup set.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0This 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19944: Specified platform: ‘string<\/i>‘ does not match piece header platform: ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The backup piece did not belong to the platform specified in FROM PLATFORM.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the restore using the correct FROM PLATFORM or without specifying FROM PLATFORM at all.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19945: file\u00a0string<\/i>\u00a0already included to be restored to\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This file was already specified for inclusion in this restore conversation. The restore conversation may process only a single instance of a datafile.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action required. The conversation is still active and more files can be specified.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19946: Cannot determine block size of backup piece ‘string<\/i>‘ (string<\/i>)<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0It was not possible to determine the cross-platform transportable backup piece block size.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Contact Oracle Support Services.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19947: Invalid block size\u00a0string<\/i>\u00a0in backup piece ‘string<\/i>‘ from specified platform ‘string<\/i>‘<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the restore using the correct FROM PLATFORM clause.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19948: Backup piece does not contain a cross-platform datafile backup, reason=string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A cross-platform transportable restore was specified but the backup piece was not produced with the correct command.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Produce a cross-platform transportable backup piece by using BACKUP … TO PLATFORM and retry the restore.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19949: Specified platform: ‘string<\/i>‘ has different endianess than piece ‘string<\/i>‘, cannot read<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The backup piece had a different endianess than the platform specified in FROM PLATFORM.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry the restore using the correct FROM PLATFORM or without specifying FROM PLATFORM at all.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19950: tablespace\u00a0string<\/i>\u00a0already included to be restored<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This tablespace was already specified for inclusion in this restore conversation.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No 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.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19951: cannot modify control file until DBNEWID is completed<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An operation requiring to modify the control file was attempted, but a NID change is in progress.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Wait until NID completes before attempting the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19952: database should be mounted exclusively<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database was started in parallel mode. To change the DBID, the database must be mounted exclusively.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Shut down the database and start it in exclusive mode.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19953: database should not be open<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The database was open. To change the DBID, the database must be mounted exclusively.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Shut down the database and mount it in exclusive mode.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19954: control file is not current<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The operation failed because a non-current, non-standby control file was mounted.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Make the control file current and retry.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19955: only one open thread is allowed to change the DBID<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The operation failed because there were active threads in the database. The most likely cause is that the database crashed the last time it was shut down.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Ensure that all threads are closed before retrying the operation. Start and open the database to perform crash recovery, then shut down with the NORMAL or IMMEDIATE options to close it cleanly. Finally, try running the utility again.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19956: database should have no offline immediate datafiles<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The operation failed because the database had one or more datafiles that were in OFFLINE IMMEDIATE mode.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Drop the datafiles or recover them and bring them online.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19957: database should have no datafiles in unknown state<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The operation failed because the database had one or more datafiles that were in an unknown state.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Drop the datafiles or recover them and bring them online.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19958: potential deadlock involving DIAG process<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0DIAG requested a control file operation that may lead to a deadlock<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Try last operation later when the control file is released<\/span><\/span><\/p>\n

\n
<\/a> ORA-19959: DBNEWID utility only allowed in CDB$ROOT<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0An attempt was made to use the DBNEWID utility in a pluggable database.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Connect to CDB$ROOT and retry the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19960: Internal use only<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0NID usage<\/span><\/span><\/p>\n

Action:<\/b>\u00a0None<\/span><\/span><\/p>\n

\n
<\/a> ORA-19961: compression algorithm\u00a0string<\/i>\u00a0requires advanced compression option to be enabled<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Requested compression algorithm in initialization parameter or by RMAN configuration requires that the advanced compression option be enabled and it was not.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Change initialization parameter advanced_compression_option_usable to true or change RMAN configurations and retry the operation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19962: compression algorithm\u00a0string<\/i>\u00a0is not valid with release\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Algorithm in initialization parameter requires a lower compatibility that is currently set.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Change algorithm in initialization parameter file or lower compatibility.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19963: error getting logical block size of file\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Error occurred when querying the logical block size of a file.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0None<\/span><\/span><\/p>\n

\n
<\/a> ORA-19965: ALTER DATABASE RECOVER STANDBY TABLESPACE has been deprecated<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The STANDBY TABLESPACE clause of the ALTER DATABASE RECOVER statement (partial_database_recovery clause) has been deprecated.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If you want to recover the standby database to a consistent point, but no further, use the statement ALTER DATABASE RECOVER MANAGED STANDBY DATABASE UNTIL CONSISTENT.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19966: ALTER DATABASE RECOVER STANDBY DATAFILE has been deprecated<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The STANDBY DATAFILE clause of the ALTER DATABASE RECOVER statement (partial_database_recovery clause) has been deprecated.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0If you want to recover the standby database to a consistent point, but no further, use the statement ALTER DATABASE RECOVER MANAGED STANDBY DATABASE UNTIL CONSISTENT.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19970: multi-instance standby role transition in progress<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0ALTER DATABASE MOUNT failed because a multi-instance standby role transition was in progress.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Retry after the multi-instance standby role transition finishes.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19971: event 10875 or 10879 is set<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Event 10875 or event 10879 was set which prevented the operation from completing with multiple instances running in Oracle RAC.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Shutdown all but one instance, then retry the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19972: ALTER DATABASE RECOVER TO LOGICAL requires one instance left<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0ALTER DATABASE RECOVER TO LOGICAL required only one instance to be left running.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Shutdown all but one instance, then retry the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19973: flashback database is not enabled<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Physical standby transition to snapshot standby required only one instance left running if flashback database logging was not enabled.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Shutdown all but one instance, then retry the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19974: database name has changed<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Physical standby role transition required only one instance left running if database name was changed and flashback database logging was enabled.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Shutdown all but one instance, then retry the command.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19975: database must not be started in any other instance<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The physical standby role transition command failed because a certain condition required the database to be mounted in this instance and not started in any other instance.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0See associated error message for detailed explanation.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19976: a concurrent standby role transition in progress<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The standby role transition operation failed because a concurrent standby role transition was already in progress.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0None<\/span><\/span><\/p>\n

\n
<\/a> ORA-19980: cannot open Data Pump dump file\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0When attempting to open the specified dump file, an error was received.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify that the specified dump file exists and is accessible.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19981: cannot read header of Data Pump dump file\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0When attempting to read the header of the specified dump file, an error was received.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify that the specified dump file is complete.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19982: file\u00a0string<\/i>\u00a0is not a Data Pump dump file<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The specified dump file did not contain data created by Data Pump.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify that the specifed dump file is really a file created by Data Pump.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19983: Data Pump dump file could not be verified<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Some data blocks for the Data Pump dump file were corrupt in the backup set.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Unless the damage to the backup set can be repaired, the Data Pump dump file cannot be restored from this backup set.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19984: Data Pump dump file restore requires COMPATIBLE\u00a0string<\/i>\u00a0or greater<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Data Pump dump file restore requested but COMPATIBLE did not allow it.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do not request dump file backup or set COMPATIBLE to minimum value and retry backup.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19985: Data Pump dump file can only be requested in a cross-platform restore<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0Data Pump dump file restore requested but the restore conversation is not a cross-platform conversation.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Start a new cross-platform restore conversation or do not include a Data Pump dump file.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19986: archived log backup piece found for cross-platform backup<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A cross-platform backup was requested for a backup piece that contained archived logs.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a datafile backup piece for cross-platform processing.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19987: unknown platform ID\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The platform ID obtained from a cross-platform backup was incorrect.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Verify that the platform specified in the FROM PLATFORM clause is correct.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19988: must specify FROM PLATFORM for cross-platform restore of backup sets with pre-12.1 compatibility<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A cross-platform restore was requested from a backup piece created with pre-12.1 compatibility without providing the platform name that created it.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Reissue the command including the FROM PLATFORM clause.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19990: restore from cross-platform encrypted backup is not supported<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A cross-platform restore was requested from an encrypted backup set.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a non-encrypted backup set from which to perform the restore.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19991: cross-platform backup of encrypted backups to different endianess is not supported<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A cross-platform backup was requested for an encrypted backup to a different endianess from the current platform.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do not specify an encrypted backup or specify the same endian platform.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19992: cross-platform backup of encrypted backup piece with different endianess is not supported<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A cross-platform backup was requested for an encrypted backup piece with different endianess from the current platform.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Specify a backup piece without encryption to the backup.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19993: must specify FROM PLATFORM for cross-platform backup of backup pieces with compatibility set prior to 12.1<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A cross-platform backup was requested for a backup piece created with compatibility prior to 12.1 without providing the platform name that created it.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Reissue the command including the FROM PLATFORM clause.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19994: cross-platform backup of compressed backups to different endianess is not supported<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A cross-platform backup was requested for a compressed backup to a different endianess from the current platform.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do not specify a compressed backup or specify the same endian platform.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19995: controlfile cannot be restored from a cross-platform backup with different endianess<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A 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.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do not attempt to restore a controlfile from a cross-platform backup set.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19996: cross-platform backup of backup pieces with pre-10.2 compatibility is not supported<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A cross-platform backup was requested for a backup created with pre-10.2 compatibility.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do not attempt to perform cross-platform backup of backups created with with pre-10.2 compatibility.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19997: backup pieces prior to 10.2 cannot be operated for cross-platform<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0A cross-platform operation was requested for a backup created with pre-10.2 compatibility.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Do not attempt to perform the cross-platform operation of backups created with pre-10.2 compatibility.<\/span><\/span><\/p>\n

\n
<\/a> ORA-19998: data file\u00a0string<\/i>\u00a0already included to be plugged<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0This data file was already specified for inclusion in this restore conversation.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0No action required. The conversation is still active and more files can be specified. 19999 is used for event<\/span><\/span><\/p>\n

\n
ORA-19999: skip_row procedure was called<\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The skip_row procedure was called which raises this error<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Skip_row should only be called within a trigger or a procedure called by a trigger.<\/span><\/span><\/p>\n

\n
<\/a> ORA-20000:\u00a0string<\/i><\/b><\/span><\/span><\/span><\/dt>\n<\/dl>\n

Cause:<\/b>\u00a0The stored procedure ‘raise_application_error’ was called which causes this error to be generated.<\/span><\/span><\/p>\n

Action:<\/b>\u00a0Correct the problem as described in the error message or contact the application administrator or DBA for more information.<\/span><\/span><\/p>\n

\n
<\/dd>\n<\/dl>\n","protected":false},"excerpt":{"rendered":"

Oracle 12c R2 Error Codes and Solution Suggestions from ORA-19700 to ORA-20000 ORA-19700: device type exceeds maximum length of\u00a0string Cause:\u00a0The device type indicated is invalid. Action:\u00a0Supply a correct device type and retry the allocation. ORA-19701: device name exceeds maximum length of\u00a0string Cause:\u00a0The device name indicated is invalid. Action:\u00a0Supply a correct device name and retry the…<\/p>\n","protected":false},"author":37,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":true,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[53],"tags":[54],"class_list":["post-2274","post","type-post","status-publish","format-standard","hentry","category-oracle-errors-and-solutions","tag-oracle-error-solutions"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p39NFI-AG","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2274","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/users\/37"}],"replies":[{"embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/comments?post=2274"}],"version-history":[{"count":3,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2274\/revisions"}],"predecessor-version":[{"id":2277,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/2274\/revisions\/2277"}],"wp:attachment":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/media?parent=2274"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/categories?post=2274"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/tags?post=2274"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}