Oracle Database Discussions

We turned on Oracle auditing of sessions a few weeks ago. Generally it work well.

However, I noticed today a few instances of
ORA-02002: Error while writing to audit trail

It happened for only one Oracle account (different os users) over a period of about 4 minutes (6.53-6.57pm).

In between the errors, for the same account, there were also errors:
ORA-28000: The account is locked
ORA-01017: Invalid username/password

Anyway, researching the error seems to suggest 2 work arounds.

1) Turn off auditing. Yes, it will stop doing it but I won't have an audit. Silly suggestion. I didn't turn auditing on because I was bored!

2) Do not allow more than 50,000 rows on AUD$. I need the audit to retain 60days!

Others have suggested SYSTEM tablespace may have become full. I cannot confirm this since it's at 85% now which is "normal" for us.

Any ideas, please?