So, I got contacted by a client in emergency because no more sessions were being opened on database with error ORA-02002. Even worse, everything stopped working and started raising this error.
So , checking on this trace generated for error here is what I found:
ORA-02002: error while writing to audit trail ORA-00604: error occurred at recursive SQL level 1 ORA-01653: unable to extend table SYS.AUD$ by 8 in tablespace AUDIT_TBS
Seems client has moved the AUD$ to another tablespace to avoid filling SYSTEM, just like described in this post. The tablespace got full, however, due bad monitoring, it got full.
As the auditing facility was unable to write to the AUDIT_TRAIL table, SQL statements that were currently being audited also failed.
What to do?
- Turn off auditing for the database
- Restart database
- Add space to tablespace
- Re-enable auditing, if required.
To avoid application back and forth, I did it in restrict mode, until get all fixed.
To avoid this sort of issue:
- Be sure you are monitoring properly the new tablespace.
- Place the audit tablespace on a reliable disk location and perhaps mirrored for protection.
Hope it helps,