I recently created a standby for one of our production databases. Got it
in Managed Recovery mode, no problem. A couple of days later, the
standby 's Alert log started showing "Recovery is repairing media corrupt
block X of file Y " errors for the 25 datafiles of our main application 's
(3rd Party COTS Student Info. package that doesn 't work on 9i) tablespace.
No errors for the datafiles for System, RBS, Users, etc.
I checked and there are absolutely no tables or indexes in that tablespace
with LOGGING = NO. In fact, the only tables in the entire database with
LOGGING = NO are Global Temporary Tables.
I suspected the COTS app. of issuing "Alter Table...NoLogging " commands
and slapped an After Alter database trigger on the primary. So far it has
only caught the "Alter Tablespace Begin/End Backup " commands for our
nightly hot backup - nothing else.
The Unrecoverable_Change# in v$Datafile continues to increment
periodically in the primary for those 25 datafiles, leading me to believe
that the NOLOGGING operations are continuing there. However, I 'm at a
loss to discover the source.
Am I an idiot? What am I missing?
I 've created a TAR, but wanted to run this by the vast experience of this
list for advice.
Thanks.
Jack C. Applewhite - Database Administrator
Austin (Texas) Independent School District
512.414.9715 (wk)
512.935.5929 (pager)
May have come a long way, but we got a long way to go.
-- B.W. Stevenson
