The Primary Db Freezed With Waited Too Long For A Row Cache Enqueue Lock
(Doc ID 790278.1)
Last updated on APRIL 03, 2020
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 to 10.2.0.4 [Release 10.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Oracle Server Enterprise Edition - Version: 10.2.0.1 to 10.2.0.4
***Checked for relevance on 22-Mar-2011***
***Checked for relevance on 06-Aug-2014***
-- Problem Statement:
On 10.2.0.3.0 in Production: Data Guard with Broker configuration:
When attempting to restart the standby in read only,
the following error occurs:
ERROR: WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
ORA-12170: TNS:Connect timeout occurred
PING[ARC6]: Error 3113 when pinging standby
ARC6: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (1089)
-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. Restart the standby in read only or shutdown the standby using sqlplus while it is configured with Broker.
2. Errors started to appear on primary.
3. Primary hang.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document