The article explains the workaround/solution when graceful switchover fails when unified auditing is enabled
Problem Details
Problem Statement
GS failed when unified auditing enabled
Applicable Error Code
Completed: alter database open
2020-04-12T21:30:45.419623+05:30
Unified Audit record write to audit trail table failed due to ORA-25153. Writing the record to OS spillover file.
...
Errors in file /u01/app/oracle/diag/rdbms/dev/DEV/trace/DEV_ora_94816.trc (incident=4543434):
ORA-00600: internal error code, arguments: [17090], [], [], [], [], [], [], [], [], [], [], []
Affected Versions
Independent of Dbvisit Versions
Affected Platforms
Platform
Description
We see the below error in the standby alert log and dbvisit trace files when Unified auditing is enabled.
Completed: alter database open
2020-04-12T21:30:45.419623+05:30
Unified Audit record write to audit trail table failed due to ORA-25153. Writing the record to OS spillover file.
...
Errors in file /u01/app/oracle/diag/rdbms/dev/DEV/trace/DEV_ora_94816.trc (incident=4543434):
ORA-00600: internal error code, arguments: [17090], [], [], [], [], [], [], [], [], [], [], []
Solution
Dbvisit is working on a permanent solution for this issue. The current workaround for this is to disable the unified auditing based on below Oracle support note.
How to Disable Oracle Database Auditing (Doc ID 1528170.1)
Update 30.12.2021, IMPORTANT NOTE
The fix for this issue has been introduced in 9.0.16 and 10.0 Dbvisit Standby version. In rare cases, you can see this error even on newest Dbvisit Standby versions while actually having Unified Auditing disabled:
SQL> SELECT VALUE FROM V$OPTION WHERE PARAMETER = 'Unified Auditing';
FALSE
If this is your case, you have to specifically enable Unified Auditing like as described here:
How To Enable The New Unified Auditing In 12c ? (Doc ID 1567006.1)
You have to recreate standby database before attempting next switchover. There will be permanent fix for this behavior in 10.2 release.
Comments