High Availability Data Guard, Sharding and Global Data Services (MOSC)

MOSC Banner

Which is "inst 1"?

We set up a 10g DataGuard configuration with 1 primary database (say, "chicago") and 1 physical standby (say, "boston").

Log transport and apply work fine, but ever so often, alert_dsboston.log reports this:

Sun Aug 06 20:16:34 EDT 2017Errors in file /home/oracle/base/product/10.2.0/dbhome_2/rdbms/log/dsboston_arc0_16725.trc:ORA-00494: enqueue [CF] held for too long (more than 900 seconds) by 'inst 1, osid 30194'Sun Aug 06 20:17:04 EDT 2017System State dumped to trace file /home/oracle/base/product/10.2.0/dbhome_2/rdbms/log/dsboston_arc0_16725.trcKilling enqueue blocker (pid=30194) on resource CF-00000000-00000000 by terminating the processSun Aug 06 20:17:04 EDT 2017Attempt to get Control File Enqueue by ARC0 pid=16725 (mode=S, type=0, timeout=300) is being blocked by inst=1, pid=30194Please check inst 1's alert log for more information on the blocker including a possible ORA-00494 and related incident logs

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center