Informix Error -332
-332 Cannot access audit trail name information.
An error occurred while reading the audit-trail file. Re-execute the latest statement; if the error recurs, the audit-trail file is corrupt. In that case you will need to drop and restart the audit.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-332 is a database-server auditing infrastructure error: the server can't read information from the audit-trail file, most often a transient I/O condition, but sometimes a sign the audit-trail file itself has become corrupted.
- A transient I/O condition while reading the audit-trail file — often resolves simply by retrying.
- A corrupted audit-trail file, if the error persists across retries.
- Filesystem or disk-level problems affecting the location where the audit trail is stored,
similar in kind to the system-catalog access failures (
-311/-312).
Solutions / Resolution
- Re-execute the statement that triggered the error, per the official guidance — many occurrences are transient.
- If the error persists after retrying, treat the audit-trail file as corrupted: drop it and
restart auditing (via the appropriate
onaudit/audit-configuration tooling for the server version in use). - Check underlying disk/filesystem health for the location where the audit trail is stored, if corruption is confirmed.
Examples
Retrying after a transient failure
-- The statement that produced -332:
SELECT * FROM orders;
-- retry once:
SELECT * FROM orders;
Dropping and restarting a corrupted audit trail
onaudit -d
-- drop the existing (corrupted) audit trail configuration,
-- then reconfigure and restart auditing as appropriate
-- for the server version in use
Diagnostic Checks
- Retry the failing statement once or twice to rule out a transient condition.
- Check the online log for related I/O errors around the same timestamp.
- Check disk health for the filesystem backing the audit-trail location if retries consistently fail.
Related Errors / Related Topics
- -311 — "Cannot open system catalog table-name." A related infrastructure-level access failure, though against the system catalog rather than the audit trail specifically.
Retry first — most occurrences are transient — and only treat the audit-trail file as corrupted if the error persists across repeated attempts.