Oracle Database Errors or Warnings from Error ORA-38765 to ORA-38774

SQLServerF1

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-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-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-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-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-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-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 <flashback-scn>.
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-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-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.

Above are list of Oracle Database Errors or Warnings from Error ORA-38765 to ORA-38774 received while performing certain operation against Oracle Database or related products.

What are atOracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database. Each Oracle Dabase Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *