EVENT: 3177 "enable logging of read-only violations"
(Doc ID 1206774.1)
Last updated on APRIL 03, 2020
Applies to:
Oracle Database - Enterprise Edition - Version 11.1.0.7 to 11.2.0.2.0 [Release 11.1 to 11.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.
Purpose
This event can be used to identify SQL within an application that cannot be run on a READ-ONLY database environment (i.e. Active Data Guard) because it requires READ-WRITE access to data (i.e. DML, DDL, sequences in a table). It can also be used to diagnose ORA-16000 'database open for read-only access' issues.
Scope
All DBAs and Support Engineers
Details
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 |
| Scope |
| Details |
| References |