Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> find the nologging action in standby database efficiently

find the nologging action in standby database efficiently

From: zhu chao <zhuchao_at_gmail.com>
Date: Mon, 10 Oct 2005 15:44:12 +0800
Message-ID: <962cf44b0510100044i5fd9294ey76b37e6a9f672e19@mail.gmail.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

--

Regards
Zhu Chao
www.cnoug.org <http://www.cnoug.org>

--

http://www.freelists.org/webpage/oracle-l Received on Mon Oct 10 2005 - 02:46:18 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US