Informix Error -1313: SQL statement error number number.

Reasons / Common Causes

-1313 is a wrapper message: the current statement called on the database server, which detected an error and returned an error code that's embedded in this message's text — per the official guidance, that embedded number should be looked up separately, alongside any other accompanying error messages.

1. A database-server-detected error whose specific cause is identified by the embedded error number, per the official guidance — -1313 itself is generic; the embedded number carries the actual diagnostic detail.

Solutions / Resolution

1. Look up the embedded error number in the error-code reference, per the official guidance, and address it as its own specific condition.
2. Also look for other error messages, per the official guidance, since -1313 may accompany additional diagnostic detail.

Examples

Reading the embedded error number

SQL statement error -206.
-- -1313 wraps -206 here: "The specified table (table) is not in the database" —
-- look up and resolve -206 specifically

Diagnostic Checks

1. Extract the embedded error number from the -1313 message text, and look it up as its own specific error.
2. Check for other accompanying error messages for additional context.

Related Errors / Related Topics

• -1312 — "FORMS statement error number number." A related wrapper-error message, for a forms-processing error rather than a general SQL-statement error.
• -1315 — "4GL run-time error number number." A related wrapper-error message, for a general 4GL runtime error.
• -1316 — "ISAM error number number." A related wrapper-error message, specifically for an ISAM-level error, often accompanying -1313.

A generic SQL-statement-error wrapper — look up the embedded error number for the actual diagnostic detail.