find the nologging action in standby database efficiently

From: Zhu Chao <zhuchao_at_gmail.com>
Date: 10 Oct 2005 00:38:10 -0700
Message-ID: <1128929890.667247.189420@g43g2000cwa.googlegroups.com>

hi, all.

When you manage a lot of databases with standby, it become quite critical to find out those database which undergo nologging operation in primary, but datafiles not refreshed to standby.

v$datafile. UNRECOVERABLE_CHANGE# is dependent on controlfile, so even datafiles copied to standby after nologging operation, standby v$datafile still not consistent with primary.

DBV is able to detect the nologging action, but when there are a lot of database and size huge, it become in-practical to dbv those databases one by one.

FORCELOGGING in database is pro-active method but it only imply to 9i, and can only prevent future out of sync.

So, here is the question: how to efficiently find out the datafiles in standby need refresh because of nologging action in primary?

Thanks Received on Mon Oct 10 2005 - 02:38:10 CDT