How to verify real-time redo streaming in Data Guard 9i
I wanted a 100% verifiable way to prove they were indeed streaming and not just accumulating on the primary.
DUMP LOGFILE 'xxx' did not seem to bear the fruit I wanted and it turns my 100MB log into a 170MB file.
Its difficult to verify because the standby database is never open so you cannot simply query the tables unless you cancel recovery and open read-only.
After mere seconds I checked my standby log for a very distinctive record and its there....
ÜÔü$ ä@KL ***595959<<<<>>>>595959*** ÜÔü$ äÜÔü$ ä
..amidst the binary control info is
***595959<<<<>>>>595959*** my inserted record on the standby
This was what I have been looking for and I did not need to stop nor open up the standby.
I will take one more look at dump logfile but I think my 'os level copy of current standby redo log' followed by a search for distinctive row data is simple, absolute and allows the standby to remain in recovery mode.
I guess its prudent to scan the lqwr trace files for errors but not as clear cut an answer if you ask me, plus I may not have tracing on in production.
I think logminor is worth a look, perhaps it can perform the test quickly and save me redo log copy.
Anybody know the best way? One that can be automated from a web servlet call?
off to learn about log minor.....
...back from log minor already - yeach, looks like you have to open the database and run sql pl/sql. I thought it was an external utility that read the log file.
Sticking with 'cp log log2' grep for distinctive record - call it good.