How to effectively use Block recovery with datafilecopy Option in Primary and Standby configuration when corruption is on Primary
(Doc ID 1466097.1)
Last updated on DECEMBER 30, 2021
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterOracle Database Exadata Express Cloud 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 Backup Service - Version N/A and later
Information in this document applies to any platform.
Goal
- This Article is intended for users who have a Primary and Standby configuration and corruption has been reported on couple of blocks in a datafile.
- This document explains how to use datafile copy option in block recovery to do block recovery there by effectively saving time in applying lots of archivelogs .
- This document is intended for users where Downtime is not available and datafile restore/ recovery is not a option since file would have to be taken offline.
- A valid level0 or full backups are available but were taken few days/weeks backup and there are lots of archivelog that need to be applied for block recovery from these backups which might take days.
- Backups are on tape.
- Corruption are reported Only on Primary or Standby database but not on both and not on same data blocks.
- Both Primary and standby are in Sync or gap is less.
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 |
| References |