How to Roll Forward a Standby Database Using Recover Database From Service
(Doc ID 2850185.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.1 to 23.4 [Release 12.1 to 23]Information in this document applies to any platform.
Goal
Utilize RECOVER DATABASE FROM SERVICE to skip over a large gap in redo or a gap in redo which is unresolvable(missing logs).
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 |
| Stop Managed Recovery and Redo Transport |
| Save Existing Logfile Names |
| Refresh Standby Control File From Primary |
| Document the Current SCN for the Standby |
| Save Current RMAN Configuration Settings |
| Refresh the Standby Control File |
| Replace RMAN Configuration Settings and Remove Orphaned Online and Standby Redo Log Files |
| Catalog Standby Database Files to the Refreshed Control File |
| Restore Any Missing Files |
| Switch Database to Copy |
| Clean Up Orphaned Files |
| Clear Online Redo Logs and Standby Redo Logs |
| Roll the Standby Database Forward |
| Restart All Instances to Mount |
| Re-Enable Redo Transport |
| Determine Section Size to be Used |
| Run Recover From Service |
| Recover Until Consistent |
| Re-Enable Flashback Database |
| Restart the Standby and Managed Recovery |
| Take a New Backup (If Needed) |
| References |