We have a standby database that pulls archive logs from the primary and applies them to the standby. When these logs arrive at the standby they are often corrupted. I know I'm being lazy here, but does anyone have a script that will check whether the archive redo logs are OK.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
check for corrupt archive redo logs
- Thread starter GERPAT
- Start date
Not quite the answer you asked for BUT . . . I had this prob: In a "asynchronous" job I zipped the logs (primarily to reduce network load), copied them to standby and the unzip detected the corruption. What I think (pretty sure) was happening was that the zip was taking place as the log was still being written. My solution was to MOVE the logs to a different directory first. The move fails with a sharing violation if it is still being written - the log gets moved, zipped & copied in the next cycle.
(There is an init.ora param which will PUSH the logs to a remote location - presumably this will be synchronised correctly, but the logs will not be zipped.)
(There is an init.ora param which will PUSH the logs to a remote location - presumably this will be synchronised correctly, but the logs will not be zipped.)
- Thread starter
- #3
- Status
Similar threads
- Locked
- Question