Informix Error -35213: No cursor declaration for procedure name.

Reasons / Common Causes

-35213 fires when an SQL statement requires a cursor id that was never declared — per the official guidance, via a DECLARE CURSOR statement.

1. A misspelled cursor id, per the official guidance — the first named possibility.
2. A missing DECLARE CURSOR statement for the cursor actually used, per the official guidance.

Solutions / Resolution

1. Check for misspellings in the cursor id, per the official guidance, as the first step.
2. Add a DECLARE CURSOR statement for this cursor, per the official guidance, if one is genuinely missing.

Examples

N/A

No specific triggering statement is documented beyond a cursor id used without a matching DECLARE CURSOR.

Diagnostic Checks

1. Search the module for a DECLARE CURSOR matching the cursor id named in the error.
2. Check for a misspelled cursor id between the declaration and the usage site.

Related Errors / Related Topics

• -35201 — "Cursor name must be an identifier." Another cursor-declaration error.
• -35203 — "Cursor cursor name already defined." The opposite problem: the same cursor id declared more than once.
• -35214 — "Cursor cursor name used with OPEN in more than one procedure." A related cursor-usage restriction.
• -35220 — "No OPEN procedure for cursor name." A related cursor-usage error, about a declared-but-unopened cursor rather than an undeclared one.

A cursor id was used without ever being declared — check for a misspelling first, then add the missing DECLARE CURSOR statement.