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

MOSC Banner

Standby : LGWR terminating the instance due to error 4021

edited Nov 3, 2016 9:09AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 9 commentsAnswered

Dear all,

we have a physical standby DB 11.2.0.4, opened for read only, recover process is running. The sync between Primary and Standby DB is using the current logfile. The DG configuration is maximum performance.

Today we faced a problem that the LGWR terminated the instance of the standby db abnormally.

AlertLog:

Archived Log entry 14378 added for thread 1 sequence 14395 ID 0x433c8309 dest 2:

Tue Oct 25 12:56:05 2016

Errors in file /autdbkddm/oracfg2/KDDM/ddump/diag/rdbms/kddm/KDDM/trace/KDDM_lgwr_10419.trc:

ORA-04021: timeout occurred while waiting to lock object

LGWR (ospid: 10419): terminating the instance due to error 4021

Tue Oct 25 12:56:05 2016

opiodr aborting process unknown ospid (16261) as a result of ORA-1092

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

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center