Informix Error -33013: END DECLARE SECTION with no BEGIN.
Cause and resolution
END DECLARE SECTION with no BEGIN.
The preprocessor has found this EXEC SQL END DECLARE SECTION statement but has not seen a preceding EXEC SQL BEGIN DECLARE SECTION. Possibly it was omitted or not recognized due to another error. Check that each BEGIN DECLARE is paired with an END DECLARE.
Oninit® Troubleshooting Guidance
Reasons / Common Causes
-33013 fires when the preprocessor finds EXEC SQL END DECLARE SECTION without a
preceding EXEC SQL BEGIN DECLARE SECTION — per the official guidance, this can happen
because the BEGIN was omitted, or wasn't recognized due to another error.
- A missing
EXEC SQL BEGIN DECLARE SECTION, per the official guidance — the direct cause. - A
BEGIN DECLARE SECTIONnot recognized because of another error, per the official guidance — an indirect cause.
Solutions / Resolution
- Confirm every
BEGIN DECLARE SECTIONis paired with anEND DECLARE SECTION, per the official guidance, and add or fix the missingBEGIN.
Examples
N/A
No specific triggering statement is documented beyond an unpaired END DECLARE SECTION.
Diagnostic Checks
- Check for a matching
BEGIN DECLARE SECTIONabove the flaggedEND DECLARE SECTION, and fix any preceding error that might have caused it to go unrecognized.
Related Errors / Related Topics
No closely related error codes are cross-referenced for -33013 in this set yet.
END DECLARE SECTION appeared without a matching BEGIN DECLARE SECTION — check the
pairing, and fix any preceding error that could have hidden the BEGIN.