In this blog post, let’s learn about the error message “013 Permission denied.” in Hydra and the description of the error. Error Message 013 Permission denied. Error Details An operating-system error code with the meaning shown was unexpectedly returned to the database server. This error code usually follows an attempt to execute a file that is not a program or shell script; it might reflect…

In this blog post, let’s learn about the error message “317 Must have the same number of selected columns in each UNION element.” in Hydra and the description of the error. Error Message 317 Must have the same number of selected columns in each UNION element. Error Details All rows that are produced in a union must have the same format, so each SELECT statement…

In this blog post, let’s learn about the error message “213 Statement interrupted by user.” in Hydra and the description of the error. Error Message 213 Statement interrupted by user. Error Details Other statements might be partially complete before the error is detected. Roll back the current transaction and then investigate the cause of the error. Use the oncheck utility (secheck with INFORMIX-SE or tbcheck…

In this blog post, let’s learn about the error message “393” in Hydra and the description of the error. Error Message 393 Error Details The named view cannot be dropped as it does not exist. To see names of existing views, query systables as follows: SELECT tabname FROM systables WHERE tabtype = ‘V’ The where clause contains an outer cartesian product. This query requests an…

In this blog post, let’s learn about the error message “397” in Hydra and the description of the error. Error Message 397 Error Details This query refers to a table named syslog. A row in the systables catalog has syslog in the tabname column, but it is only a convenient place to store the pathname to the transaction-log file. Under INFORMIX-SE, a table named syslog…

In this blog post, let’s learn about the error message “285 Invalid cursor received by sqlexec.” in Hydra and the description of the error. Error Message 285 Invalid cursor received by sqlexec. Error Details Inspect the current statement, and examine the punctuation of comments and quoted strings. You can use curly braces to insert comments into SQL statements, but the braces must balance. Or you…

In this blog post, let’s learn about the error message “282 Found a quote for which there is no matching quote.” in Hydra and the description of the error. Error Message 282 Found a quote for which there is no matching quote. Error Details A character literal in this statement exceeds the maximum length. Check the punctuation and length of all quoted strings in the…

In this blog post, let’s learn about the error message “299 Cannot grant permission to self.” in Hydra and the description of the error. Error Message 299 Cannot grant permission to self. Error Details The database server cannot locate the referenced constraint in the sysconstraints system catalog table, and the referenced constraint was not created in the same ALTER TABLE statement as the referencing constraint….

In this blog post, let’s learn about the error message “254 Too many or too few host variables given.” in Hydra and the description of the error. Error Message 254 Too many or too few host variables given. Error Details The database server cannot access system information associated with the table. Check the accompanying ISAM error code for more information. Unless the ISAM error code…

In this blog post, let’s learn about the error message “079 No record locks available.” in Hydra and the description of the error. Error Message 079 No record locks available. Error Details An operating-system error code with the meaning shown was unexpectedly returned to the database server. This implementation of the Informix database server probably uses kernel locking, the use of the operating-system facilities to…

In this blog post, let’s learn about the error message “212 Cannot add index.” in Hydra and the description of the error. Error Message 212 Cannot add index. Error Details The database server refers to the tables of the system catalog while it processes most statements. When it cannot read one of these important tables, a serious error results. Check the accompanying ISAM error code…

In this blog post, let’s learn about the error message “144 ISAM error: key value locked.” in Hydra and the description of the error. Error Message 144 ISAM error: key value locked. Error Details An internal error (probably obsolete) occurred. If the error recurs, please note all circumstances and contact Informix Technical Support.