How to analyze and resolve ORA-16146?
(Doc ID 1073217.1)
Last updated on JANUARY 30, 2022
Applies to:
Oracle Database Cloud Exadata Service - Version N/A and laterOracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 10.1.0.2 and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.
Purpose
Step by Step document to analyze and resolve
ORA-16146: standby destination control file enqueue unavailable.
ORA-16146 errors indicate that we timed out in an attempt to obtain a control file transaction lock on a standby. This can happen on a very busy standby host/primary host, and does not itself indicate a problem. As long as there are no other side-effects this error can be ignored.
Please go through the steps below:
Troubleshooting Steps
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
| Purpose |
| Troubleshooting Steps |
| 1. Analyze the circumstances of the ORA-16146 |
| 2. Does the ORA-16146 refer to the standby or primary database? |
| 3. Please verify the Data Guard configuration on primary and standby database: |
| 4. Have you applied the recommended patches? |
| 5. Are the databases located on SUN-platforms? |
| 6. If we need to analyze the issue further, please enable following events: |
| 7. New behavior in 11.2 |
| References |