Oninit
Talk to an expert →

Informix Error -335

-335 There is no audit trail for the specified table.

This statement requires an audit trail to work, but no current audit trail exists for the table. Either none was ever started, or it was dropped. Check that you specified the table you intended. In a recovery situation (the statement was RECOVER TABLE), check that the table has just been restored from a backup copy. If so, the table did not have an audit trail at the time that this backup was made. If an audit trail was specified later, an unknown period remains between the backup and the start of auditing during which unaudited updates might have been made.

Oninit® Troubleshooting Guidance

Reasons / Common Causes

-335 fires when a statement that requires an audit trail runs against a table that doesn't have one — either because auditing was never configured for it, or because a previously existing audit trail was dropped.

  1. The target table was never enrolled in an audit trail — auditing simply isn't configured for it.
  2. An audit trail existed previously but was dropped (via DROP AUDIT) and never re-established.
  3. Wrong table specified — the statement targets a different table than the one that actually has an active audit trail.
  4. A restored table from a backup taken before auditing was configured — per the official guidance, a table restored from an earlier backup can genuinely lack an audit trail for the period between that backup and when auditing began, even if auditing is active now.
Solutions / Resolution
  1. Verify the correct table was specified, per the official guidance, as the first check.
  2. Confirm whether an audit trail is actually configured for this table before running statements that depend on one.
  3. If auditing is required, set it up for the table using the appropriate START AUDIT configuration for the server version in use.
  4. In a recovery scenario, be aware that a restored table may have a genuine gap in audit coverage between the backup point and when auditing was (re-)established** — this may be expected, not a bug.
Examples
Confirming the correct table before troubleshooting further
-- Confirm this is really the intended table:
SELECT tabname FROM systables WHERE tabname = 'orders';
-- then check whether auditing is actually configured for it
Diagnostic Checks
  1. Double-check the table name used in the statement that triggered the error.
  2. Check whether an audit trail is currently configured for that table.
  3. If this is a restored table, check the backup's timing relative to when auditing was established — a gap may be expected rather than a misconfiguration.
Related Errors / Related Topics
  • -333 — "The audit trail file already exists with a different name." A related audit-trail configuration error, on the setup side.
  • -334 — "Cannot create audit trail." Another audit-trail setup failure, at the infrastructure level.

A restored table can legitimately lack audit coverage for the period before auditing was established on it — check backup timing before assuming a configuration bug.