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

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

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

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

ORA-19755: could not open change tracking file

ORA-19755: could not open change tracking file

Cause: The change tracking file could not be opened.

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

ORA-19754: error reading from change tracking file

ORA-19754: error reading from change tracking file

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

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

ORA-19753: error writing to change tracking file

ORA-19753: error writing to change tracking file

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

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

ORA-19752: block change tracking is already enabled

ORA-19752: block change tracking is already enabled

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

Action: None, this is an informative message only.

ORA-19751: could not create the change tracking file

ORA-19751: could not create the change tracking file

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

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

ORA-19750: change tracking file: string

ORA-19750: change tracking file: string

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

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

ORA-19740: text is longer than string

ORA-19740: text is longer than string

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

Action: Supply a shorter text and retry the operation.

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

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

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

Action: Correct the character set name and retry.

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

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

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

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

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

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

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

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

ORA-19734: wrong creation SCN - control file expects converted plugged-in datafile

ORA-19734: wrong creation SCN - control file expects converted plugged-in datafile

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

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

ORA-19733: COMPATIBLE parameter needs to be string or greater

ORA-19733: COMPATIBLE parameter needs to be string or greater

Cause: The COMPATIBLE initialization parameter is not high enough to allow the operation. Allowing the command would make the database incompatible with the release specified by the current COMPATIBLE parameter.

Action: Shutdown and startup with a higher compatibility setting.

ORA-19732: incorrect number of datafiles for tablespace string

ORA-19732: incorrect number of datafiles for tablespace string

Cause: d by a user editing the export file.

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

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

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

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

Action: Use the correct control file and continue recovery.

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

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

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

Action: Online the datafile and retry the operation.

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

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

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

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

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

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

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

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

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

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

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

Action: Upgrade Oracle and retry the operation.

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

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

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

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

ORA-19725: can not acquire plug-in enqueue

ORA-19725: can not acquire plug-in enqueue

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

Action: retry the operation.

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

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

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

Action: retry the query.

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

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

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

Action: Use ALTER DATABASE RENAME FILE command instead.

ORA-19722: datafile string is an incorrect version

ORA-19722: datafile string is an incorrect version

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

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

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

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

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

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

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

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

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

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

ORA-19719: length for operation name longer than string

ORA-19719: length for operation name longer than string

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

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

ORA-19718: length for command id longer than string

ORA-19718: length for command id longer than string

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

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

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

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

Cause: The procedure dbms_backup_restore.searchFiles was called with an empty pattern while the parameter omf was set to FALSE.

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

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

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

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

Action: Change the format.

ORA-19715: invalid format string for generated name

ORA-19715: invalid format string for generated name

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

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

ORA-19714: length for generated name longer than string

ORA-19714: length for generated name longer than string

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

Action: Change the format to create shorter piece names.

ORA-19713: invalid copy number: string

ORA-19713: invalid copy number: string

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

Action: Report the error and other information to support.

ORA-19712: table name exceeds maximum length of string

ORA-19712: table name exceeds maximum length of string

Cause: The table name string exceeds maximum length.

Action: Retry the operation with a shorter table name.

ORA-19711: cannot use reNormalizeAllFileNames while database is open

ORA-19711: cannot use reNormalizeAllFileNames while database is open

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

Action: Close the database before using the reNormalizeAllFileNames procedure.

ORA-19710: unsupported character set string

ORA-19710: unsupported character set string

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

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

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

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

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

Action: Supply a valid numeric parameter.

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

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

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

Action: Supply a shorter destination and retry the operation.

ORA-19707: invalid record block number - string

ORA-19707: invalid record block number - string

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

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

ORA-19706: invalid SCN

ORA-19706: invalid SCN

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

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

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

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

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

Action: Supply a shorter tag and retry the operation.

ORA-19704: file name exceeds maximum length of string

ORA-19704: file name exceeds maximum length of string

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

Action: Retry the operation with a shorter file name.

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

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

Cause: The device command string exceeds maximum length.

Action: Correct the command and retry the operation.

ORA-19701: device name exceeds maximum length of string

ORA-19701: device name exceeds maximum length of string

Cause: The device name indicated is invalid.

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

ORA-19700: device type exceeds maximum length of string

ORA-19700: device type exceeds maximum length of string

Cause: The device type indicated is invalid.

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

ORA-19699: cannot make copies with compression enabled

ORA-19699: cannot make copies with compression enabled

Cause: Datafile copies with compression are not supported.

Action: If the function dbms_backup_restore.backuppieceCreate is called outside RMAN, then the incompatible values are being passed for the parameters docompress and imagcp. If this message occurs during an RMAN job, then this is an internal error in RMAN, and you should contact Oracle support.

ORA-19698: %s is from different database: id=string, db_name=string

ORA-19698: %s is from different database: id=string, db_name=string

Cause: Catalog failed becasuse the database id in file header does not match the one in control file.

Action: Supply the correct file belonging to this database.

ORA-19697: standby control file not found in backup set

ORA-19697: standby control file not found in backup set

Cause: The standby control file could not be restored because it is not in this backup set.

Action: This message is issued when the directory from the first backup piece is read and one or more files named for restoration were not found in the piece. You must supply the first backup piece of a backup set that contains the requested file.

ORA-19696: control file not found in backup set

ORA-19696: control file not found in backup set

Cause: The control file could not be restored because it is not in this backup set.

Action: This message is issued when the directory from the first backup piece is read and one or more files named for restoration were not found in the piece. You must supply the first backup piece of a backup set that contains the requested file.

ORA-19695: fixed table x$krbmsft has not been populated

ORA-19695: fixed table x$krbmsft has not been populated

Cause: This is an internal error. The fixed table x$krbmaft was not populated using the function dbms_backup_restore.searchFiles.

Action: Internal error - contact Oracle Customer Support.

ORA-19694: some changed blocks were not found in the change tracking file

ORA-19694: some changed blocks were not found in the change tracking file

Cause: A backup or copy found that some changed blocks had not been recorded in the change tracking file. The details of which files and blocks are affected will be in an Oracle trace file.

Action: This indicates that there is a problem with the change tracking feature. Disable change tracking and re-start the backup.

ORA-19693: backup piece string already included

ORA-19693: backup piece string already included

Cause: This backup piece was already specified for inclusion in the restore conversation. A restore conversation may process only a single instance of a backup piece.

Action: Remove the specified duplicate backup piece in restore steps and restart the conversation.

ORA-19692: missing creation stamp on piece string

ORA-19692: missing creation stamp on piece string

Cause: The backuppiece doesn t have information about creation stamp.

Action: Supply another backuppiece which is created by oracle 9i or later version.

ORA-19691: %s is from different database: id=string, name=string

ORA-19691: %s is from different database: id=string, name=string

Cause: The database name or database id in backuppiece header does not match the one in control file.

Action: Supply the correct backuppiece belonging to this database.

ORA-19690: backup piece release string incompatible with Oracle release string

ORA-19690: backup piece release string incompatible with Oracle release string

Cause: The backup piece was created by incompatible software.

Action: Either restart with a compatible software release or create another backup using the current release.

ORA-19689: cannot have more than one %F in control file autobackup format(string) for string

ORA-19689: cannot have more than one %F in control file autobackup format(string) for string

Cause: control file autobackup format contains more than one %F for the device.

Action: Change control file format using RMAN command CONGIGURE CONTROLFILE BACKUP FORMAT FOR DEVICE TYPE lamp;lt;lamp;nbsp;typelamp;gt; TO lamp;lt;lamp;nbsp;formatlamp;gt;.

ORA-19688: control file autobackup format(string) for string does not have %F

ORA-19688: control file autobackup format(string) for string does not have %F

Cause: control file autobackup format must contain %F for the device.

Action: Change control file format using RMAN command CONGIGURE CONTROLFILE BACKUP FORMAT FOR DEVICE TYPE lamp;lt;lamp;nbsp;typelamp;gt; TO lamp;lt;lamp;nbsp;formatlamp;gt;.

ORA-19687: SPFILE not found in backup set

ORA-19687: SPFILE not found in backup set

Cause: The SPFILE could not be restored, because it is not in this backup set.

Action: This message is issued when the directory from the first backup piece is read and one or more files named for restoration were not found in the piece. You must supply the first backup piece of a backup set that contains the requested file.

ORA-19686: SPFILE not restored due to string

ORA-19686: SPFILE not restored due to string

Cause: The indicated file could not be restored, because some of its data blocks were not found in the backup piece.

Action: Unless the damage to the backup set can be repaired, the SPFILE cannot be restored from this backup set.

ORA-19685: SPFILE could not be verified

ORA-19685: SPFILE could not be verified

Cause: Some data blocks for the SPFILE were corrupt in the backup set.

Action: Unless the damage to the backup set can be repaired, the SPFILE cannot be restored from this backup set.