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

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

\n
ORA-19700: device type exceeds maximum length of\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The device type indicated is invalid.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Supply a correct device type and retry the allocation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19701: device name exceeds maximum length of\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The device name indicated is invalid.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Supply a correct device name and retry the allocation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19703: device command string exceeds maximum length of\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The device command string exceeds maximum length.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Correct the command and retry the operation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19704: file name exceeds maximum length of\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0Retry the operation with a shorter file name.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19705: tag value exceeds maximum length of\u00a0string<\/i>\u00a0characters<\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0Supply a shorter tag and retry the operation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19706: invalid SCN<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The input SCN is either not a positive integer or too large.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the input SCN and make sure it is a valid SCN.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19707: invalid record block number –\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The input number is either negative or too large.<\/span><\/span><\/span><\/dd>\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><\/span><\/dd>\n
<\/a><\/a>ORA-19708: log destination exceeds maximum length of\u00a0string<\/i>\u00a0characters<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0When starting a restore conversation, the user specified a log restore destination longer than the port-specific maximum.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Supply a shorter destination and retry the operation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19709: numeric parameter must be non-negative integer<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0A numeric parameter to an DBMS_BACKUP_RESTORE procedure is negative or contains a fractional portion.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Supply a valid numeric parameter.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19710: unsupported character set\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0Specify a valid character set in the environment. This is usually done via the NLS_LANG environment variable.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19711: cannot use RENORMALIZEALLFILENAMES while database is open<\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0Close the database before using the RENORMALIZEALLFILENAMES procedure.<\/span><\/span><\/span><\/dd>\n

<\/p>\n

<\/a><\/a>ORA-19712: table name exceeds maximum length of\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The table name string exceeds maximum length.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Retry the operation with a shorter table name.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19713: invalid copy number:\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The copy number is not in a valid range or you have reached maximum limit.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Report the error and other information to support.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19714: length for generated name longer than\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The specified format exceeds the maximum length for the piece name.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Change the format to create shorter piece names.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19715: invalid format\u00a0string<\/i>\u00a0for generated name<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0A restricted format or undefined format was used incorrectly.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Change the format specified in the additional information by removing the restricted format.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19716: error processing format\u00a0string<\/i>\u00a0to generate name for backup<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0There were errors while processing the format to generate name for backup.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Change the format.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19717: for non-OMF search the pattern must be specified<\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0Either specify the pattern or set the parameter OMF to TRUE.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19718: length for command id longer than\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The specified command id exceeds the maximum length for command id.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Supply a shorter command id and retry the operation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19719: length for operation name longer than\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The specified operation name exceeds the maximum length for operation name.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Supply a shorter operation name and retry the operation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19720: Error occurred when converting an OCI number into an SCN<\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0See other errors on the error stack to look for the source of the problem.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19721: Cannot find datafile with absolute file number\u00a0string<\/i>\u00a0in tablespace\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Can not find one of the datafile that should be in the Pluggable Set.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Make sure all datafiles are specified via import command line option or parameter files.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19722: datafile\u00a0string<\/i>\u00a0is an incorrect version<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The datafile is an incorrect version. It contains either less or more changes then the desired version.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Make sure the right datafiles are transported. Make sure the datafile is copied while its tablespace is read only.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19723: Cannot recreate plugged in read-only datafile\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The datafile is plugged in read only. It can not recreated.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Use ALTER DATABASE RENAME FILE command instead.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19724: snapshot too old: snapshot time is before file\u00a0string<\/i>\u00a0plug-in time<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The snapshot SCN is before the SCN at which the referred datafile is plugged into the database.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0retry the query.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19725: can not acquire plug-in enqueue<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0There maybe another “ALTER DATABASE RESET COMPATIBILITY” command issued concurrently, preventing this process from acquiring the plug-in enqueue.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0retry the operation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19726: cannot plug data [string<\/i>] at level\u00a0string<\/i>\u00a0into database running at compatibility level\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0Raise the “compatible” init.ora parameter and retry the operation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19727: cannot plug data [string<\/i>] at level\u00a0string<\/i>\u00a0into database running Oracle\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0Upgrade Oracle and retry the operation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19728: data object number conflict between table\u00a0string<\/i>\u00a0and partition\u00a0string<\/i>\u00a0in table\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\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><\/span><\/dd>\n
<\/a><\/a>ORA-19729: File\u00a0string<\/i>\u00a0is not the initial version of the plugged in datafile<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The file is not the initial version of the plugged in datafile.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Use the correct initial version of the plugged in datafile.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19730: can not convert offline plugged-in datafile\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0Online the datafile and retry the operation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19731: cannot apply change to unverified plugged-in datafile\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0Use the correct control file and continue recovery.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19732: incorrect number of datafiles for tablespace\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0d by a user editing the export file.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Use the correct export file and retry the operation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19733: COMPATIBLE parameter needs to be\u00a0string<\/i>\u00a0or greater<\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0Shutdown and startup with a higher compatibility setting.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19734: wrong creation SCN – control file expects converted plugged-in datafile<\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0Either restore the converted datafile or continue recovering the datafile.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19735: wrong creation SCN – control file expects initial plugged-in datafile<\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\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><\/span><\/dd>\n
<\/a><\/a>ORA-19736: can not plug a tablespace into a database using a different national character set<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Oracle does not support plugging a tablespace into a database using a different national character set.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Use import\/export or unload\/load to move data instead.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19738: cannot find language information for character set: ‘string<\/i>‘<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The compatibility check failed because a character set name that was provided is not valid.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Correct the character set name and retry.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19740: text is longer than\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The specified text exceeds the maximum length for text.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Supply a shorter text and retry the operation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19741:\u00a0string<\/i>\u00a0exceeds maximum allowable length of\u00a0string<\/i>\u00a0for parameter ‘string<\/i>‘<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The specified string exceeds the maximum allowable length for the parameter<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Supply a shorter string for the parameter and retry the operation.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19742: control file is not a backup control file<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0This parameter could not be set because the control file was not a backup control file.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Do not use this call for this control file.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19750: change tracking file: ‘string<\/i>‘<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0This message reports the name of a file involved in other messages.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0See associated error messages for a description of the problem.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19751: could not create the change tracking file<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0It was not possible to create the change tracking file.<\/span><\/span><\/span><\/dd>\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><\/span><\/dd>\n
<\/a><\/a>ORA-19752: block change tracking is already enabled<\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0None, this is an informative message only.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19753: error writing to change tracking file<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An I\/O error occurred while writing to the change tracking file.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0There will be other messages on the error stack that show details of the problem.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19754: error reading from change tracking file<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An I\/O error occurred while reading from the change tracking file.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0There will be other messages on the error stack that show details of the problem.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19755: could not open change tracking file<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The change tracking file could not be opened.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0There will be other messages on the error stack that show details of the problem.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19756: corrupt block number\u00a0string<\/i>\u00a0found in change tracking file<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The specified block number is corrupt in the change tracking file.<\/span><\/span><\/span><\/dd>\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><\/span><\/dd>\n
<\/a><\/a>ORA-19757: could not resize change tracking file to\u00a0string<\/i>\u00a0blocks<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An error occurred while trying to change the size of the change tracking file.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0There will be other messages on the error stack that show details of the problem.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19758: failed to enable\/disable block change tracking: out of SGA memory<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0out of SGA memory<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Increase SGA and restart the instance.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19759: block change tracking is not enabled<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0A command was entered that requires block change tracking to be enabled, but block change tracking is not enabled.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0None, this is an informative message only.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19760: error starting change tracking<\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0Examine the trace and alert files. Correct the error if possible, otherwise disable change tracking.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19761: block size\u00a0string<\/i>\u00a0is not valid for change tracking file<\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\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><\/span><\/dd>\n
<\/a><\/a>ORA-19762: invalid file type\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0Disable then re-enable change tracking.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19763: compatibility version\u00a0string<\/i>\u00a0is higher than maximum allowed:\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0Disable then re-enable change tracking.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19764: database id\u00a0string<\/i>\u00a0does not match database id\u00a0string<\/i>\u00a0in control file<\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0Disable then re-enable change tracking.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19765: mount id\u00a0string<\/i>\u00a0does not match mount id\u00a0string<\/i>\u00a0in control file<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0d by having a change tracking file that cannot be consistently updated by all instances.<\/span><\/span><\/span><\/dd>\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><\/span><\/dd>\n
<\/a><\/a>ORA-19766: missing CHANGE keyword<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Syntax error.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Use the correct syntax: ENABLE\/DISABLE BLOCK CHANGE TRACKING<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19767: missing TRACKING keyword<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Syntax error.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Use the correct syntax: ENABLE\/DISABLE BLOCK CHANGE TRACKING<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19768: USING clause only valid with ENABLE CHANGE TRACKING<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The USING clause was specified with DISABLE CHANGE TRACKING<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Correct the statement.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19769: missing FILE keyword<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Syntax error.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Use the correct syntax: ENABLE\/DISABLE BLOCK CHANGE TRACKING<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19770: invalid change tracking file name<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The USING clause was specified with ALTER DATABASE ENABLE BLOCK CHANGE TRACKING, but no file name was given.<\/span><\/span><\/span><\/dd>\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><\/span><\/dd>\n
<\/a><\/a>ORA-19771: cannot rename change tracking file while database is open<\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0Close the database and reissue the command.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19772: change tracking file name exceeds limit of\u00a0string<\/i>\u00a0characters<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The name specified for the change tracking file is too long.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Specify a shorter change tracking file name.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19773: must specify change tracking file name<\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0Either specify a file name, or set the DB_CREATE_FILE_DEST parameter.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19776: PROXY restore to ASM disk group “string<\/i>” is not supported.<\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0Use a different file name and reissue RMAN command.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19777: ASM file\u00a0string<\/i>\u00a0cannot be proxy backed up.<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to proxy backup a ASM file. This is not supported.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Use a different file name and reissue RMAN command.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19779: could not obtain resilvering status for change tracking file<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An error occurred while obtaining the mirror resilvering status of the change tracking file.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Refer to other error messages shown for additional details of the problem.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19780: Active Data Guard option not enabled<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Change tracking at a standby database required the Active Data Guard option.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Enable the Active Data Guard option.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19800: Unable to initialize Oracle Managed Destination<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The name given for an Oracle managed files destination cannot be initialized.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0, if possible, and retry the command or use a different name for destination.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19801: initialization parameter DB_RECOVERY_FILE_DEST is not set<\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\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><\/span><\/dd>\n
<\/a><\/a>ORA-19802: cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_FILE_DEST_SIZE<\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0Correct the dependency parameter definitions and retry the command.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19803: Parameter DB_RECOVERY_FILE_DEST_SIZE is out of range (1 –\u00a0string<\/i>)<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Parameter DB_RECOVERY_FILE_DEST_SIZE specified was not valid.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Specify a valid number within the range.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19804: cannot reclaim\u00a0string<\/i>\u00a0bytes disk space from\u00a0string<\/i>\u00a0limit<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Oracle cannot reclaim disk space of specified bytes from the DB_RECOVERY_FILE_DEST_SIZE limit.<\/span><\/span><\/span><\/dd>\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><\/span><\/dd>\n
<\/a><\/a>ORA-19805: RECID\u00a0string<\/i>\u00a0of\u00a0string<\/i>\u00a0was deleted to reclaim disk space<\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0Wait and try again.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19806: cannot make duplex backups in recovery area<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Duplex backup to recovery area is not supported.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Remove duplex option and try again.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19808: recovery destination parameter mismatch<\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0Check DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE values in all instances.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19809: limit exceeded for recovery files<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The limit for recovery files specified by the DB_RECOVERY_FILE_DEST_SIZE was exceeded.<\/span><\/span><\/span><\/dd>\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><\/span><\/dd>\n
<\/a><\/a>ORA-19810: Cannot create temporary control file\u00a0string<\/i>\u00a0in DB_RECOVERY_FILE_DEST<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to create a control file for a temporary purpose in DB_RECOVERY_FILE_DEST.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Retry the operation with a new file name.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19811: cannot have files in DB_RECOVERY_FILE_DEST with keep attributes<\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0Reissue RMAN command without KEEP options.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19812: cannot use\u00a0string<\/i>\u00a0without DB_RECOVERY_FILE_DEST<\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0Eliminate any incompatible parameter definitions.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19813: cannot have unavailable file\u00a0string<\/i>\u00a0in DB_RECOVERY_FILE_DEST<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An attempt was made to change a backup piece or image copy in recovery area to UNAVAILABLE.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Correct and resubmit the RMAN command. Do not use messages 19814; it is used for simulating crash.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19815: WARNING:\u00a0string<\/i>\u00a0of\u00a0string<\/i>\u00a0bytes is\u00a0string<\/i>% used, and has\u00a0string<\/i>\u00a0remaining bytes available.<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0DB_RECOVERY_FILE_DEST is running out of disk space.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0One of the following:<\/span><\/span><\/span><\/dd>\n
1. Add disk space and increase DB_RECOVERY_FILE_DEST_SIZE.<\/span><\/span><\/span><\/dd>\n
2. Backup files to tertiary device using RMAN.<\/span><\/span><\/span><\/dd>\n
3. Consider changing RMAN retention policy.<\/span><\/span><\/span><\/dd>\n
4. Consider changing RMAN archived log deletion policy.<\/span><\/span><\/span><\/dd>\n
5. Delete files from recovery area using RMAN.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19816: WARNING: Files may exist in\u00a0string<\/i>\u00a0that are not known to database.<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0One of the following events caused this:<\/span><\/span><\/span><\/dd>\n
1. A database crash happened during file creation.<\/span><\/span><\/span><\/dd>\n
2. A backup control file was restored.<\/span><\/span><\/span><\/dd>\n
3. The control file was re-created.<\/span><\/span><\/span><\/dd>\n
4. DB_RECOVERY_FILE_DEST has previously been enabled and then disabled.<\/span><\/span><\/span><\/dd>\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><\/span><\/dd>\n
<\/a><\/a>ORA-19820: database must be in NOARCHIVELOG mode to disable logging<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Logging was disabled when ARCHIVELOG mode was used.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Execute ALTER DATABASE NOARCHIVELOG in mount state.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19821: an intentionally corrupt log file was found<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0A log file that was intentionally corrupt for testing or benchmarking purposes was found and failed the operation.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Remove such log files and retry or use the NOARCHIVELOG option if possible.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19830: error from target database:\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0This error should be followed by other errors indicating the cause of the problem.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0No action required.<\/span><\/span><\/span><\/dd>\n
<\/a><\/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<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0This version of database was incompatible with the the indicated DBMS_BACKUP_RESTORE package installed in the database.<\/span><\/span><\/span><\/dd>\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><\/span><\/dd>\n
<\/a><\/a>ORA-19836: cannot use passphrase encryption for this backup<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Passphrase encryption was attempted for a backup that contains encrypted tablespaces and uses compression.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Do not use passphrase encryption for this backup. Use transparent wallet-based encryption instead.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19837: invalid blocksize\u00a0string<\/i>\u00a0in backup piece header<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The blocksize of the backup piece obtained from the header was invalid.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0The backup piece is corrupted, a different backup piece should be used for restore.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19838: Cannot use this control file to open database<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0This control file was restored by a DUPLICATE operation used only to restore and recover the datafiles of the new database. It is not meant to be used for opening the database, as allowing so might corrupt datafiles or online redo logs of the target database or both.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Re-create control file manually specifying all names of datafiles and online redo logs. Do not forget to use NID to change the name or DBID or both of the new database.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19843: Cannot obtain datafile name for datafile\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0While trying to obtain the file enqueue for the datafile the datafile name could not be obtained.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Examine the trace and alert files for possible causes. Fix underlying problem before attempting command again.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19851: OS error while managing auxiliary database\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An OS error was received while managing the automatic auxiliary instance.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the accompanying errors.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19852: error creating services for auxiliary instance\u00a0string<\/i>\u00a0(error\u00a0string<\/i>)<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An error was received while managing the services of the auxiliary instance.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the accompanying errors.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19853: error preparing auxiliary instance\u00a0string<\/i>\u00a0(error\u00a0string<\/i>)<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0An error was received while managing the automatic auxiliary instance.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the accompanying errors.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19854: error obtaining connect string from target<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Could not obtain the connect string from the target database<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Check the accompanying errors.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19860: piece validation cannot be performed more than once<\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0Do not attempt to validate the pieces more than once.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19861: additional backup pieces cannot be validated in this conversation<\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\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><\/span><\/dd>\n
<\/a><\/a>ORA-19862: backup pieces must be validated before accessing results<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The user tried to get validation results for backup pieces before the pieces were actually validated.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Validate the pieces before trying to access the results.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19863: device block size\u00a0string<\/i>\u00a0is larger than max allowed:\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0The user specified a device BLKSIZE that is larger than the device BLKSIZE specified during compressed backup.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Change the device BLKSIZE to be smaller than the maximum allowed.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19865: Backup piece\u00a0string<\/i>\u00a0has no data<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0No data was returned for the specified backup piece.<\/span><\/span><\/span><\/dd>\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><\/span><\/dd>\n
<\/a><\/a>ORA-19866: error writing file header for datafile\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0During a block recovery, the header of the datafile could not be updated.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Contact Oracle Support Services.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19870: error while restoring backup piece\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0This error should be followed by other errors indicating the cause of the problem.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0See other errors actions.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19872: Unexpected end of file at block\u00a0string<\/i>\u00a0while decompressing backup piece\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0While reading a compressed backup piece, RMAN received an end-of-file without finding the end-of-compression stream.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0This is most likely caused by a corrupted backup piece. Consider using a different backup piece for restore.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19873: cannot apply this backup section to file\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0If this error occurs while running RMAN, then it is an internal error and you should contact Oracle support.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19874: cannot finish multi-section restore to file\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0During a multi-section restore, the file being restored is not a file in which a multi-section restore is in progress.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0If this error occurs while running RMAN, then it is an internal error and you should contact Oracle support.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19875: multi-section restore not complete for file\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0While completing a multi-section restore, it was found that all required sections for this file were not correctly applied.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0If this error occurs while running RMAN, then it is an internal error and you should contact Oracle support.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19880: Corrupted space header for datafile\u00a0string<\/i>, block\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\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><\/span><\/dd>\n
<\/a><\/a>ORA-19881: Corrupted space bitmap for datafile\u00a0string<\/i>, block\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\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><\/span><\/dd>\n
<\/a><\/a>ORA-19882: datafile\u00a0string<\/i>\u00a0checkpoint\u00a0string<\/i>\u00a0is ahead of space bitmap datafile\u00a0string<\/i>\u00a0checkpoint\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\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><\/span><\/dd>\n
<\/a><\/a>ORA-19883: Unused Block Optimization stopped for datafile\u00a0string<\/i><\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Accompanying errors detail the problem that prevented Unused Block Optimization from being used.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0See accompanying errors for appropiate action.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19884: datafile\u00a0string<\/i>\u00a0is unable to use Unused Block Optimization because tablespace has been dropped<\/span><\/b><\/span><\/span><\/dt>\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><\/span><\/dd>\n
Action:<\/b>\u00a0None. This is an informational message.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19899: missing incarnation information<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Media recovery stopped because information of one or more ancestor incarnations of recovery target incarnation was not available.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Register logs from the missing incarnations and retry recovery.<\/span><\/span><\/span><\/dd>\n
<\/a><\/a>ORA-19900: RESETLOGS must be specified after recovery to new incarnation<\/span><\/b><\/span><\/span><\/dt>\n
Cause:<\/b>\u00a0Recovery was done to an incarnation after changing the destination incarnation using RMAN’s RESET DATABASE command.<\/span><\/span><\/span><\/dd>\n
Action:<\/b>\u00a0Open the database with the RESETLOGS option.<\/span><\/span><\/span><\/dd>\n
<\/dd>\n<\/dl>\n","protected":false},"excerpt":{"rendered":"

Oracle 11g Error Codes and Solution Suggestions from ORA-19700 to ORA-19900 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 allocation….<\/p>\n","protected":false},"author":37,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[53],"tags":[14,32,54],"class_list":["post-1974","post","type-post","status-publish","format-standard","hentry","category-oracle-errors-and-solutions","tag-database-administration","tag-oracle-administration","tag-oracle-error-solutions"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p39NFI-vQ","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1974","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=1974"}],"version-history":[{"count":1,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1974\/revisions"}],"predecessor-version":[{"id":1975,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/posts\/1974\/revisions\/1975"}],"wp:attachment":[{"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/media?parent=1974"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/categories?post=1974"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.fatihacar.com\/blog\/wp-json\/wp\/v2\/tags?post=1974"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}