Oracle Database Errors or Warnings from Error ORA-38795 to ORA-38804
ORA-38795: warning: FLASHBACK succeeded but OPEN RESETLOGS would get error below
Cause: Flashback Database ended without error. However, if the ALTER DATABASE OPEN RESETLOGS command were attempted now, it would fail with the specified error. The most likely cause is that Flashback Database had to add a file back to the control file but could not restore the file’s contents.
Action: If a backup is available, restore the backup, online the file, and recover the database to the original flashback target scn or timestamp. If a backup is not available, but the redo from the file creation to the target scn or timestamp is available, then create the file using the ALTER DATABASE CREATE DATAFILE command, bring the file online, and recover the database to the original flashback target scn or timestamp.
ORA-38796: Not enough flashback database log data to undo FLASHBACK.
Cause: There was not enough flashback log data to undo the flashback so a flashback was not started.
Action: It is still possible to get to the restore target by doing a flashback until the resetlogs branch point of the restore target is reached. This can be done by executing multiple “flashback to before resetlogs” commands, or by doing a flashback to the exact time or SCN of the desired resetlogs branch point. Note that this flashback cannot be undone should an error occur. The only option is to complete the flashback.
ORA-38797: Full database recovery required after a database has been flashed back
Cause: An attempt was made to recover some datafiles or tablespaces of a database after the database had been flashed back. In order to recover control file and all datafiles correctly, full database recovery is required after a database has been flashed back.
Action: Recover the whole database instead.
ORA-38798: Cannot perform partial database recovery
Cause: See other other messages on error stack for the cause.
Action: See other other messages on error stack for the action.
ORA-38799: Cannot drop guaranteed restore point internally created for snapshot standby
Cause: An attempt is made to drop the guaranteed restore point Oracle created internally for a snapshot standby.
Action: Use the “alter database convert to physical standby” command to convert the snapshot standby to a normal physical standby. This will automatically flashback the database and drop this guaranteed restore point.
ORA-38800: Cannot start Redo Apply on the open physical standby database
Cause: An attempt was made to start Redo Apply on an open physical standby database instance.
Action: Make sure the primary database is at compatibility 11.0.0 or higher. The redo logs to be recovered on an open physical standby database must be generated at compatibility 11.0.0 or higher. If you have any redo below 11.0.0 to be applied on the standby, you must apply them on a mounted standby before restarting recovery on an open standby when the log format advances to 11.0.0 or higher. If this is a RAC standby database, make sure the ACTIVE_INSTANCE_COUNT parameter is not set.
ORA-38801: improper value for ORA_EDITION
Cause: An improper value was used for ORA_EDITION when trying to specify an edition to use at login time. The value is not understandable as an identifier, or is too long.
Action: Correct the value for ORA_EDITION and try again.
ORA-38802: edition does not exist
Cause: This error occurred because a reference was made to an edition that does not exist or that the current user does not have privileges on.
Action: Check the edition name and verify that the current user has appropriate privileges on the edition.
ORA-38803: edition is unusable
Cause: This error occurred because a reference was made to an unusable edition.
Action: Use another edition.
ORA-38804: not a legal edition name
Cause: This error occurred because an attempt was made to create an edition called ORA$BASE, DATABASE_DEFAULT, or USER_DEFAULT. These are not legal edition names. Or a value provided as an edition name is not understandable as an identifier, or is too long.
Action: Choose a different name for the edition.
Above are list of Oracle Database Errors or Warnings from Error ORA-38795 to ORA-38804 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.
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.