Informix Error Messages and Error Codes From Error 33065 to 33070

SQLServerF1

Informix Error Code -33065 Cursor/statement id name is too long when prefixed by module name.
This message is a warning only. When you use the -local preprocessing option, cursor names and statement names are prefixed with a unique tag generated from the module name. (On UNIX systems, the inode number of the source program is used as the unique tag.) The combined length of the cursor or statement name and the unique tag should not exceed 18 characters, but in the case of name, it does. As a result, if the same name is used in a different source module, the two names might not be distinct as the -local option requests.

Informix Error Code -33066 Cursor/statement ids id1 and id2 are not unique in first 18 characters when prefixed by module name.
When you use the -local preprocessing option, cursor names and statement IDs are prefixed with a unique tag that is generated from the module name. (On UNIX systems, the inode number of the source program is used as the unique tag.) In this case, id1 and id2 are at least 14 characters long, and their first 13 characters do not differ. As a result, they are the same when the tag is added and the result is trimmed to 18 characters. Change the two names to avoid name collision and try again.

Informix Error Code -33067 ELIF without IFDEF.
An IFDEF or IFNDEF statement does not precede this ELIF statement. Review the source lines that precede this point. The preceding statement was omitted, or it might not have been recognized due to an earlier error.
Informix Error Code -33068 ELIF after ELSE.
The ESQL preprocessor ELSE statement indicates the last part of an IFDEF or IFNDEF statement; another ELIF part might not follow. Review the contents of this IFDEF or IFNDEF statement and put its parts in order.
Informix Error Code -33070 Stack overflow occurred during statement parse.
This message, which indicates that the parser stack has overflowed, rarely occurs. It might occur, for example, if your embedded-language statement (SELECT, INSERT, UPDATE, DELETE, and so on) contains an extremely large or complicated clause (WHERE, MATCHES, LIKE, and so on) that the parser is trying to process. In that case, break up the clause and try again.

Above are list of Informix Error Messages and Errors Codes or Status Codes or Exit Codes along with Error and Warning messages received while performing certain operation against Informix applications or related products.

What are Informix Error Messages?
All Informix messages returned by the Informix server are assigned an error code.

In general, each Informix error contains the following information:
• The Informix Error Code or Informix Error status
• The message text. This text is usually returned with the Error code. Some messages employ word substitution, where the word substituted represents the system-replacement of a term more specific to the occurrence.
• An explanation of how the error may have occurred.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Informix Error Codes or Status Codes or Exit Codes and Error Messages on Windows, Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *