Hello,
In our standby server (SB server) there is a brapply process , which applies archived logs to Standby Server
brarchive -u system/systempwd -c -f -d disk -m 30 -sd
Logs applying happens every 30min time.
(From PRD to SB Server logs are shipping.)
Suddenly, log apply process (brapply) fails.
When check the archPRD.log, we have examined that until log#78 , it applies successfully.
But , from log#78 onwards , its not applying
(Log#79, Log#80, Log#81, ..... arrives to SB server from Primary. But NOT applying)
While examining, we have noted that log#79 is corrupted.
(May be log#79...or may be log#80 even)
So, now... it requires to do the recovery process.
Kindly let me know how to do this?
Needs to recover the corrupted log file(s) , and then needs to start the brapply process again.
Here SB server uses oracle 10gR2.
DB is in MOUNT state
What will be the impact on the SB Server , if i issue this command;
SQL> ALTER DATABASE RECOVER STANDBY DATABASE UNTIL CANCEL;
Specify log: {=suggested | filename | AUTO | CANCEL}
CANCEL
Will that recover the corrupted log files? (log#79 or log#80)
How this recovery process happens?
(Is it one by one (79,80,81...etc) or.... recovery all together ?)
Is it automatically discovers the corrupted log file(s) or do we need to inform that recover this and that log files?
Is both the commands are same?
#recover database until cancel;
and
#alter database recover standby database until cancel;
Kindly help me to clarify my issue.
regards,
Zerandib
.