ORA-38792: encountered unknown flashback record from release string

ORA-38792: encountered unknown flashback record from release string

Cause: A Flashback Database logfile contains a record written by a future Oracle release and is unknown by this release.

Action: The given release of Oracle must be installed in order to use these flashback database log files.

ORA-38791: flashback did not start because file string was not in a valid incarnation

ORA-38791: flashback did not start because file string was not in a valid incarnation

Cause: Flashback could not be started because a file was checkpointed or fuzzy at a point where the file can neither be restored nor recovered to our restore target. In order for a file to be brought to the restore target, the file has to be in one of the incarnations along the ancestral path from the current incarnation to the restore incarnation.

Action: Manually restore or recover the file to a point where it is in one of the incarnations along the ancestral path from the current incarnation to the restore incarnation.

ORA-38790: BEFORE must be specified with RESETLOGS

ORA-38790: BEFORE must be specified with RESETLOGS

Cause: The FLASHBACK DATABASE command included the RESETLOGS parameter but not the BEFORE parameter.

Action: Retry the command with TO BEFORE RESETLOGS.

ORA-38788: More standby database recovery is needed

ORA-38788: More standby database recovery is needed

Cause: An attempt was made to create a restore point or a guaranteed while a physical standby database is not cleanly checkpointed.

Action: Perform more standby database recovery via managed standby database recovery. Cancel managed recovery and retry the command.

ORA-38787: Creating the first guaranteed restore point requires mount mode when flashback database is off.

ORA-38787: Creating the first guaranteed restore point requires mount mode when flashback database is off.

Cause: While flashback database is not on, an attempt was made to create the first guaranteed restore point while the database is open.

Action: Mount the database and retry.

ORA-38786: Flash recovery area is not enabled.

ORA-38786: Flash recovery area is not enabled.

Cause: An attempt was made to perform a command that requires Flash recovery area to be enabled.

Action: Set DB_RECOVERY_FILE_DEST to an appropriate location and retry.

ORA-38785: Media recovery must be enabled for guaranteed restore point.

ORA-38785: Media recovery must be enabled for guaranteed restore point.

Cause: Media recovery is not enabled. Media recovery must be enabled in order to create a guaranteed restore point.

Action: Turn on media recovery with an ALTER DATABASE ARCHIVELOG statement and then retry the command.

ORA-38784: Cannot create restore point string .

ORA-38784: Cannot create restore point string .

Cause: An attempt to create a restore point failed. See other errors on the error stack for the specific reason.

Action: Fix the problem and retry.

ORA-38783: Instance recovery required.

ORA-38783: Instance recovery required.

Cause: An attempt was made to create a restore point when the database is in mount mode but it was not shutdown cleanly before it was mounted. In order to create a restore point when the database is mounted, the database must be shutdown cleanly before it is mounted.

Action: Consider one of the following: 1. Create the restore point after opening the database. 2. Open the database, shut it down cleanly, mount the database, and retry creating the restore point.

ORA-38782: cannot flashback database to non-guaranteed restore point string

ORA-38782: cannot flashback database to non-guaranteed restore point string

Cause: An attempt was made to flashback database to a non-guaranteed restore point while flashback database is off. You can only flashback a database to guaranteed restore point when flashback database is not on.

Action: Consider picking a guaranteed restore point to flashback the database to, if there is one.

ORA-38781: cannot disable media recovery - have guaranteed restore points

ORA-38781: cannot disable media recovery - have guaranteed restore points

Cause: An attempt was made to disable media recovery while there is at least one guaranteed restore point.

Action: Drop all guaranteed restore points and then disable media recovery.

ORA-38780: Restore point string does not exist.

ORA-38780: Restore point string does not exist.

Cause: The restore point name of the DROP RESTORE POINT command does not exist.

Action: No action required.

ORA-38779: cannot create restore point - too many restore points.

ORA-38779: cannot create restore point - too many restore points.

Cause: The maximum number of restore points already have been created.

Action: Delete some existing restore point and retry the operation.

ORA-38778: Restore point string already exists.

ORA-38778: Restore point string already exists.

Cause: The restore point name of the CREATE RESTORE POINT command already exists. A restore point name must be unique.

Action: Either use a different name or delete the existing restore point with the same name.

ORA-38777: database must not be started in any other instance.

ORA-38777: database must not be started in any other instance.

Cause: A command was attempted that required the database to be mounted in this instance and not started in any other instance. Standby database recovery through a RESETLOGS and ALTER DATABASE OPEN RESETLOGS require that the database be started in only one instance if flashback database logging is enabled.

Action: Ensure that the no other instances are started. Then retry the command.

ORA-38776: cannot begin flashback generation - flash recovery area is disabled

ORA-38776: cannot begin flashback generation - flash recovery area is disabled

Cause: During a database mount, the RVWR process discovered that the flash recovery area was disabled. DB_RECOVERY_FILE_DEST must have been set null or removed from the INIT.ORA file while the database was unmounted.

Action: Flashback database requires the flash recovery area to be enabled. Either enable the flash recovery area by setting the DB_RECOVERY_FILE_DEST and DB_ RECOVERY_FILE_DEST_SIZE initialization parameters, or turn off flashback database with the ALTER DATABASE FLASHBACK OFF command.

ORA-38775: cannot disable flash recovery area - flashback database is enabled

ORA-38775: cannot disable flash recovery area - flashback database is enabled

Cause: An attempt was made to set DB_RECOVERY_FILE_DEST to null while flashback database was enabled. Flashback database requires DB_RECOVERY_ FILE_DEST to be set.

Action: Use the ALTER DATABASE FLASHBACK OFF statement to disable flashback database, then disable the flash recovery area.

ORA-38774: cannot disable media recovery - flashback database is enabled

ORA-38774: cannot disable media recovery - flashback database is enabled

Cause: An attempt was made to disable media recovery while flashback database was enabled.

Action: Use the ALTER DATABASE FLASHBACK OFF statement to disable flashback database, then disable media recovery.

ORA-38773: cannot add data file string - file already part of database

ORA-38773: cannot add data file string - file already part of database

Cause: The recovery step of FLASHBACK database encountered the creation of a datafile and could not create the file because the file name is already in use in the database. The control file file entry for the file is UNNAMEDnnnnn .

Action: Use the ALTER DATABASE CREATE DATAFILE statement to create the file with a different name.

ORA-38772: cannot add datafile string - file could not be created

ORA-38772: cannot add datafile string - file could not be created

Cause: The recovery step of FLASHBACK DATABASE encountered the creation of a datafile and could not recreate the file. The error from the creation attempt is displayed in another message. The control file file entry for the file is UNNAMEDnnnnn.

Action: Use the ALTER DATABASE CREATE DATAFILE statement to create the file.

ORA-38771: unnamed datafile(s) added to control file by flashback recovery

ORA-38771: unnamed datafile(s) added to control file by flashback recovery

Cause: The recovery step of FLASHBACK DATABASE encountered the creation of a datafile that could not be added to the control file. An entry has been added to the control file for the new datafile, but with the file name UNNAMEDnnnn, where nnnn is the file number. Related error messages provide the file names that were originally used to create the files.

Action: Rename the file in the control file, or use the ALTER ALTER DATABASE CREATE DATAFILE command to create a file suitable for recovery. If the file is not going to be recovered, then take it offline with the FOR DROP option. The recovery step of Flashback can be resumed by entering a RECOVERY command with the same SCN or timestamp as used in the FLASHBACK DATABASE command. For example, RECOVER AUTOMTAIC DATABASE UNTIL CHANGE lamp;lt;lamp;nbsp;flashback-scnlamp;gt;.

ORA-38770: FLASHBACK DATABASE failed during recovery.

ORA-38770: FLASHBACK DATABASE failed during recovery.

Cause: A FLASHBACK DATABASE command successfully restored the database but failed during the recovery step. Look in the alert log for more information about the failure.

Action: Fix the error and then recover the database to the same SCN or timestamp used in the FLASHBACK DATABASE command.

ORA-38769: FLASHBACK DATABASE failed after modifying data.

ORA-38769: FLASHBACK DATABASE failed after modifying data.

Cause: A FLASHBACK DATABASE command failed after modifying the the database. Look in the alert log for more information about the failure.

Action: Recover the database to return it to its previous state, or fix the cause of the error and retry the Flashback.

ORA-38768: resizing datafile string failed

ORA-38768: resizing datafile string failed

Cause: An operating system error occurred when Flashback Database tried to shrink (resize) a datafile. Flashback shrinks a file in order to undo the effects of a file expand, for example, an autoextension of the file.

Action: Recover the database to return it to its previous state, or fix the cause of the operating system error and retry the Flashback. If that is not possible, then the file can be taken offline and the Flashback command retried. The file will have to be restored from a backup and rolled forward.

ORA-38767: flashback retention target parameter mismatch

ORA-38767: flashback retention target parameter mismatch

Cause: The value of parameters DB_FLASHBACK_RETENTION_TARGET must be same in all instances. All databases must have same flashback retention target parameters.

Action: Check DB_FLASHBACK_RETENTION_TARGET values in all instances.

ORA-38766: cannot flashback data file string; file resized smaller

ORA-38766: cannot flashback data file string; file resized smaller

Cause: An attempt to do FLASHBACK DATABASE found that the file was shrunk during the time to flash back.

Action: The file cannot be flashed back. The file must be taken offline or the tablespace dropped before continuing with the FLASHBACK DATABASE command.

ORA-38765: Flashed back database cannot be opened read-only.

ORA-38765: Flashed back database cannot be opened read-only.

Cause: A complete recovery was performed after a database flashback but the database was not opened for read-write access, or a FLASHBACK DATABASE command failed.

Action: If a complete recovery was performed after a database flashback, open the database for read-write access. If a FLASHBACK DATABASE command failed, fix what caused the command to fail and retry the command, or recover and open the database for read-write access.

ORA-38764: flashback not started; datafile string enabled threads are different

ORA-38764: flashback not started; datafile string enabled threads are different

Cause: A FLASHBACK DATABASE command did not start. The datafile was restored from a backup taken when the enabled threads were different than at the time of the flashback.

Action: The flashback cannot be performed. Perform a restore and an incomplete recovery instead.

ORA-38763: flashback not started; enabled threads have changed

ORA-38763: flashback not started; enabled threads have changed

Cause: A FLASHBACK DATABASE command did not start. The set of enabled threads changed during the time to flash back.

Action: The flashback cannot be performed. Perform a restore and an incomplete recovery instead.

ORA-38762: thread string redo log with scn string could not be found

ORA-38762: thread string redo log with scn string could not be found

Cause: A redo log needed for the recovery portion of FLASHBACK could not be found. The FLASHBACK operation failed.

Action: Restore the log and retry the FLASHBACK command.

ORA-38761: redo log sequence string in thread string, incarnation string could not be accessed

ORA-38761: redo log sequence string in thread string, incarnation string could not be accessed

Cause: A redo log needed for the recovery portion of FLASHBACK could not be read or opened. The FLASHBACK operation failed.

Action: Restore the log and retry the FLASHBACK command.

ORA-38760: This database instance failed to turn on flashback database

ORA-38760: This database instance failed to turn on flashback database

Cause: Database flashback is on but this instance failed to start generating flashback data. Look in alert log for more specific errors.

Action: Correct the error or turn off database flashback.

ORA-38759: Database must be mounted by only one instance and not open.

ORA-38759: Database must be mounted by only one instance and not open.

Cause: An attempt to turn on or off Flashback Database logging was made when the database was open or mounted by more than one instance.

Action: Mount the database in only one instance and retry the command.

ORA-38758: cannot flashback data file string; restored since last recovery

ORA-38758: cannot flashback data file string; restored since last recovery

Cause: An attempt to do FLASHBACK DATABASE found that the file was restored since the last standby recovery. The file cannot be flashed back.

Action: The file must be taken offline before continuing with the FLASHBACK DATABASE command.

ORA-38757: Database must be mounted and not open to FLASHBACK.

ORA-38757: Database must be mounted and not open to FLASHBACK.

Cause: An attempt to Flashback a database was made when the database was not mounted or was already open.

Action: Mount the database and retry the FLASHBACK command.

ORA-38756: Flashback is already turned off for this tablespace.

ORA-38756: Flashback is already turned off for this tablespace.

Cause: An attempt was made to turn off flashback database logging for a tablespace that already has flashback off.

Action: No action required.

ORA-38755: Flashback is already turned on for this tablespace.

ORA-38755: Flashback is already turned on for this tablespace.

Cause: An attempt was made to turn on flashback database logging for a tablespace that already has flashback turned on.

Action: No action required.

ORA-38754: FLASHBACK DATABASE not started; required redo log is not available

ORA-38754: FLASHBACK DATABASE not started; required redo log is not available

Cause: A FLASHBACK DATABASE command did not start. A redo log needed for the recovery part of FLASHBACK DATABASE could not be found or accessed.

Action: See trace files for details of the problem.

ORA-38753: Cannot flashback data file string; no flashback log data.

ORA-38753: Cannot flashback data file string; no flashback log data.

Cause: An attempt to perform a FLASHBACK DATABASE failed because the file does not have enough flashback log data to cover the time to flash back. Either the file did not have flashback generation enabled for it, or had flashback generation turned off for it some time during the time span of the flashback.

Action: The file cannot be flashed back. The file must be taken offline or the tablespace dropped before continuing with the FLASHBACK DATABASE command.

ORA-38752: file string does not exist

ORA-38752: file string does not exist

Cause: During an RMAN FLASHBACK DATABASE conversation, a file was listed which was not part of the database. The RMAN conversation was aborted.

Action: Retry the conversation with the appropriate file numbers.

ORA-38750: FLASHBACK DATABASE may not be performed using a dispatcher.

ORA-38750: FLASHBACK DATABASE may not be performed using a dispatcher.

Cause: An attempt was made to use a dispatcher process for FLASHBACK DATABASE. Memory requirements disallow this recovery method.

Action: Connect to the instance via a dedicated server process to perform FLASHBACK DATABASE.

ORA-38749: A media recovery has been started.

ORA-38749: A media recovery has been started.

Cause: An attempt was made to start a FLASHBACK DATABASE in the same session as a media recovery.

Action: Complete or cancel the first media recovery session.

ORA-38748: cannot flashback data file string - file is in use or recovery

ORA-38748: cannot flashback data file string - file is in use or recovery

Cause: An attempt to do FLASHBACK DATABASE found that the file was not available for recovery. Either it was online and the database was open in some instance, or another process was currently doing media recovery or flashback on the file.

Action: Do not do FLASHBACK DATABASE.

ORA-38747: corrupt before image (file# string, block# string)

ORA-38747: corrupt before image (file# string, block# string)

Cause: A corrupt data block before image was encountered during a FLASHBACK DATABASE command.

Action: The flashback log data is probably corrupt. If so, a restore and an incomplete recovery must be performed instead.

ORA-38746: error occurred while restoring data block (file# string, block# string)

ORA-38746: error occurred while restoring data block (file# string, block# string)

Cause: An error occurred during a FLASHBACK DATABASE command. See other errors on error stack.

Action: Investigate why the error occurred. It may be that the flashback database log data is corrupt. If so, a restore and an incomplete recovery must be performed instead.

ORA-38744: file string is not the same file seen at start of flashback

ORA-38744: file string is not the same file seen at start of flashback

Cause: A different copy of the file was accessed the last time FLASHBACK DATABASE looked at the file header. A backup of the file was restored or the meaning of the file name changed during FLASHBACK DATABASE.

Action: Ensure the correct file is available, then retry FLASHBACK DATABASE.

ORA-38743: Time or SCN is in the future of the database.

ORA-38743: Time or SCN is in the future of the database.

Cause: The Time or SCN provided in a FLASHBACK DATABASE command was in the future of the database.

Action: Retry the command with a correct Time or SCN or RECOVER the database.

ORA-38742: Flashback log file has incorrect log reset status.

ORA-38742: Flashback log file has incorrect log reset status.

Cause: The flashback database log file header had log reset data that was different than the control file. The log was probably an incorrectly restored backup. Flashback database logs cannot be backed up.

Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.

ORA-38741: Formatted blocks value string is not valid.

ORA-38741: Formatted blocks value string is not valid.

Cause: The formatted blocks value in the flashback database log file was greater than the file size. The flashback database log file was corrupt.

Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.

ORA-38740: Usable blocks value string is not valid.

ORA-38740: Usable blocks value string is not valid.

Cause: A flashback database log file header contained a usable blocks value greater than the file size. The flashback database log file file is corrupt.

Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.

ORA-38739: Flashback log file is more recent than control file.

ORA-38739: Flashback log file is more recent than control file.

Cause: The control file change sequence number in the flashback database log file was greater than the number in the control file. This implies that the wrong control file was being used. Note that repeatedly causing this error can make it stop happening without correcting the real problem. Every attempt to open the database will advance the control file change sequence number until it is great enough.

Action: FLASHBACK DATABASE can only be used with the current control file. If it is not available, then a restore and an incomplete recovery must be performed instead.

ORA-38738: Flashback log file is not current copy.

ORA-38738: Flashback log file is not current copy.

Cause: A check of flashback database log file header at database open found that the flashback database log appeared to be an incorrectly restored backup. Flashback database log files cannot be backed up and restored.

Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.

ORA-38737: Expected sequence number string doesn t match string

ORA-38737: Expected sequence number string doesn t match string

Cause: The flashback database log is corrupted or is an old version.

Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.

ORA-38736: Wrong thread number string in flashback log file header.

ORA-38736: Wrong thread number string in flashback log file header.

Cause: The thread number in the flashback database log file did not match the control file.

Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.

ORA-38735: Wrong log number string in flashback log file header.

ORA-38735: Wrong log number string in flashback log file header.

Cause: The log file number in the flashback database log file did not match the control file.

Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.

ORA-38734: Flashback log is inconsistent; belongs to another database.

ORA-38734: Flashback log is inconsistent; belongs to another database.

Cause: The database ID in the flashback database log file did not match the database ID in the control file.

Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.

ORA-38733: Physical size string less than needed string.

ORA-38733: Physical size string less than needed string.

Cause: A flashback database log file shrank in size. This was likely to have been caused by operator or operating system error.

Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.

ORA-38732: Expected file size string does not match string.

ORA-38732: Expected file size string does not match string.

Cause: The file size indicated in the control file did not match the file size contained in the flashback log file header. The flashback database log file was corrupt.

Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.

ORA-38731: Expected version string does not match string in log header.

ORA-38731: Expected version string does not match string in log header.

Cause: The version of the flashback database log file header was corrupt.

Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.

ORA-38730: Invalid SCN or TIMESTAMP expression.

ORA-38730: Invalid SCN or TIMESTAMP expression.

Cause: The expression supplied in a FLASHBACK DATABASE command was invalid.

Action: Retry the command using a valid number or time stamp expression.