Jayesh Pande

Testing A Physical Standby Database In Oracle 10 g If you don’t want to deal with missteps, I recommend that you test your standby database to facilitate the failover or switchover process. This procedure is very useful when you have physical standby databases for testing and other purposes that require read-write access to the standby database. Also, it improves your checklist in the event of an error or disaster. By using Snapshot standby databases, redo data is not applied until you convert the snapshot standby database back into a physical standby database, and after all local updates to the snapshot standby database are discarded. Requirements The following requirements need to be met in order to create a snapshot standby. The Data Guard environment (a primary and a physical standby) needs to be Oracle 10.2.0.1 version or higher.The Primary and Standby databases need to be in archivelog mode (this is a default requirement for Data Guard).Force logging should be set to...

RAC Wait Event A) Block-Oriented Waits ----------------------- 1. gc current block 2-way 2. gc current block 3-way 3. gc cr block 2-way 4. gc cr block 3-way B) Message-Oriented Wais ------------------------- 1. gc current grant 2-way 2. gc current grant 3-way 3. gc cr grant 2-way 4. gc cr grant 3-way (Normally this wait event is not possible, but "_cr_grant_local_role" --> turn 3-way CR grants off, make it automatic, or turn it on) C) Contention-Oriented Waits ---------------------------- 1. gc current block busy (cluster cache contention) 2. gc cr block busy 3. gc current buffer busy (local cache contention) D) Load-Oriented Waits ---------------------- 1. gc current block congested 2. gc cr block congested 3. gc current grant congested 4. gc cr grant congested Now let's come to the discription part --------------------------------------- A) Block-Oriented Waits ======================== 1. gc current block 2-way (write/write with 2 nodes) ------------------------...