ORA-46268: Conflicting operation on audit table(s)
Solution:
Close the offending session, establish a new session, then try again.
Steps to reproduce.
Re-connected to the database, ran without issue.
Full error:
Error report -
ORA-46268: Conflicting operation on audit table(s)
ORA-06512: at "SYS.DBMS_AUDIT_MGMT", line 61
ORA-06512: at "SYS.DBMS_AUDIT_MGMT", line 774
ORA-06512: at line 2
46268. 00000 - "Conflicting operation on audit table(s)"
*Cause: Audit tables were being operated by more than one DBMS_AUDIT_MGMT
API from different sessions. The simultaneous execution of the
following API with one another and with itself can cause the
conflict: INIT_CLEANUP, DEINIT_CLEANUP, SET_AUDIT_TRAIL_LOCATION
and MOVE_DBAUDIT_TABLES.
*Action: Wait until the execution of one of the API's completes and try
executing the API again.
Could not find anything on MOS (or any English forums/blogs) about this error outside of the below description.
Related note:
The init cleanup also moves the audit log from system to sysaux - unless you specify a different tablespace using set_audit_trail_location.
See:
http://oraclesqltips.blogspot.com.au/2013/09/ora-46267-insufficient-space-in-sysaux.html
Version: 11.2.0.1.0
Close the offending session, establish a new session, then try again.
Steps to reproduce.
- Ran dbms_audit_mgmt.init_cleanup through SQL Developer.
- Control+C out of statement.
- Attempt to run init_cleanup again.
No amount of waiting got around the error.
There was clearly nothing running.Re-connected to the database, ran without issue.
Full error:
Error report -
ORA-46268: Conflicting operation on audit table(s)
ORA-06512: at "SYS.DBMS_AUDIT_MGMT", line 61
ORA-06512: at "SYS.DBMS_AUDIT_MGMT", line 774
ORA-06512: at line 2
46268. 00000 - "Conflicting operation on audit table(s)"
*Cause: Audit tables were being operated by more than one DBMS_AUDIT_MGMT
API from different sessions. The simultaneous execution of the
following API with one another and with itself can cause the
conflict: INIT_CLEANUP, DEINIT_CLEANUP, SET_AUDIT_TRAIL_LOCATION
and MOVE_DBAUDIT_TABLES.
*Action: Wait until the execution of one of the API's completes and try
executing the API again.
Could not find anything on MOS (or any English forums/blogs) about this error outside of the below description.
Related note:
The init cleanup also moves the audit log from system to sysaux - unless you specify a different tablespace using set_audit_trail_location.
See:
http://oraclesqltips.blogspot.com.au/2013/09/ora-46267-insufficient-space-in-sysaux.html
Version: 11.2.0.1.0
Comments
Post a Comment