How to quickly check that Database is consistent after incomplete recovery (Point in Time Recovery) before OPEN RESETLOGS
(Doc ID 1354256.1)
Last updated on JULY 07, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 9.0.1.0 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Goal
What is the LEAST amount of recovery that has to be done before a database restored from a backup can be opened?
After performing a RESTORE / RECOVER, we need to perform a quick validation to ensure database is consistent and ready for OPEN RESETLOGS.
This proactive check helps to prevent several issues which may appear during or after OPEN RESETLOGS.
Through out this note we assume that you are restoring from a valid backup.
There can be more scenarios than discussed here. Please consult Oracle Support when in doubt.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| Check 1: Checkpoint Time and Fuzziness |
| Check 2: Datafile Status |
| Check 3: Absolute Fuzzy |
| Check 4: Archive Logs Required |
Check 5: Post OPEN RESETLOGS Activities |
| References |