In this blog post, let’s learn about the error message “058 Can’t send after socket shutdown.” in Hydra and the description of the error. Error Message 058 Can’t send after socket shutdown. Error Details An operating-system error code with the meaning shown was unexpectedly returned to the database server. If the error recurs, please note all circumstances and contact Informix Technical Support.

In this blog post, let’s learn about the error message “182 ISAM error: Duplicate optical BLOBSpace name.” in Hydra and the description of the error. Error Message 182 ISAM error: Duplicate optical BLOBSpace name. Error Details A user-defined routine (UDR) failed to execute properly. Typically, this occurs when the UDR raises an error. For more specific information, see the message log.

In this blog post, let’s learn about the error message “201 A syntax error has occurred.” in Hydra and the description of the error. Error Message 201 A syntax error has occurred. Error Details An SQL identifier exceeded the maximum number of characters. In Informix Dynamic Server 9.2x or 9.3, the maximum length for identifiers in SQL statements is 128 characters. In other Informix database…

In this blog post, let’s learn about the error message “007 Arg list too long.” in Hydra and the description of the error. Error Message 007 Arg list too long. Error Details An operating-system error code with the meaning shown was unexpectedly returned to the database server. Look for other operating-system error messages that might give more information. If the error recurs, please refer to…

In this blog post, let’s learn about the error message “036 Operation now in progress.” in Hydra and the description of the error. Error Message 036 Operation now in progress. Error Details An operating-system error code with the meaning shown was unexpectedly returned to the database server. If the error recurs, please note all circumstances and contact Informix Technical Support.

In this blog post, let’s learn about the error message “377 Must terminate transaction before closing database.” in Hydra and the description of the error. Error Message 377 Must terminate transaction before closing database. Error Details This statement (DATABASE, CREATE DATABASE, or CLOSE DATABASE) cannot be executed until the current transaction is finished. Use either COMMIT WORK or ROLLBACK WORK and then close the database….

In this blog post, let’s learn about the error message “303 Expression mixes columns with aggregates.” in Hydra and the description of the error. Error Message 303 Expression mixes columns with aggregates. Error Details This SELECT statement uses an aggregate function in its WHERE clause. This action is not allowed. The WHERE clause must be applied row by row as a table is scanned, but…

In this blog post, let’s learn about the error message “028 No space left on device.” in Hydra and the description of the error. Error Message 028 No space left on device. Error Details An operating-system error code with the meaning shown was unexpectedly returned to the database server. Either a database table or an ASCII output file has probably filled the available disk space….

In this blog post, let’s learn about the error message “330 Cannot create database.” in Hydra and the description of the error. Error Message 330 Cannot create database. Error Details Possibly you tried to create a database with the same name as one that already exists; if so, choose a different name. Otherwise, check the accompanying ISAM error code for more detailed information on the…

In this blog post, let’s learn about the error message “301 The total size of the GROUP BY columns is too big.” in Hydra and the description of the error. Error Message 301 The total size of the GROUP BY columns is too big. Error Details The database server limits the total number of bytes in the combined columns that the GROUP BY clause lists….

In this blog post, let’s learn about the error message “239 Could not insert new row – duplicate value in a UNIQUE INDEX column.” in Hydra and the description of the error. Error Message 239 Could not insert new row – duplicate value in a UNIQUE INDEX column. Error Details The database server cannot execute a BEGIN WORK statement. Check the accompanying ISAM error code…

In this blog post, let’s learn about the error message “207 Cannot update cursor declared on more than one table.” in Hydra and the description of the error. Error Message 207 Cannot update cursor declared on more than one table. Error Details The database server cannot find a table or view specified in the statement. The table or view might have been renamed or dropped…

In this blog post, let’s learn about the error message “192 ISAM error: Can not drop first chunk.” in Hydra and the description of the error. Error Message 192 ISAM error: Can not drop first chunk. Error Details The dbspace is full. If you are adding a logical log through onparams, there is not enough space in the dbspace for a log of the size…

In this blog post, let’s learn about the error message “171 ISAM error: ISAM file format change detected.” in Hydra and the description of the error. Error Message 171 ISAM error: ISAM file format change detected. Error Details You attempted to add a log to a storage space for TEXT or BYTE data. You can add logs only to dbspaces.

In this blog post, let’s learn about the error message “014 Bad address.” in Hydra and the description of the error. Error Message 014 Bad address. Error Details An operating-system error code with the meaning shown was unexpectedly returned to the database server. Look for other operating-system error messages that might give more information. If the error recurs, please note all circumstances and contact Informix…

In this blog post, let’s learn about the error message “255 Not in transaction.” in Hydra and the description of the error. Error Message 255 Not in transaction. Error Details An SQL identifier exceeded the maximum number of characters. In Informix Dynamic Server 9.2x or 9.3, the maximum length for identifiers in SQL statements is 128 characters. In other Informix database servers, the maximum length…

In this blog post, let’s learn about the error message “380 Cannot erase log file.” in Hydra and the description of the error. Error Message 380 Cannot erase log file. Error Details The database server, while trying to initialize a transaction log file, received an unexpected error. Check the accompanying ISAM error code for more detailed information on the cause. Typical causes include hardware errors…

In this blog post, let’s learn about the error message “295 Referenced and referencing tables have to be in the same database.” in Hydra and the description of the error. Error Message 295 Referenced and referencing tables have to be in the same database. Error Details The test for a null value can be applied only to a column name (not to a subscripted character…

In this blog post, let’s learn about the error message “117 ISAM error: bad custom collating sequence.” in Hydra and the description of the error. Error Message 117 ISAM error: bad custom collating sequence. Error Details The ISAM processor needed to allocate memory for data storage but was unable to do so. A problem may exist in the operating system; look for operating-system error messages…

In this blog post, let’s learn about the error message “313 Not owner of table.” in Hydra and the description of the error. Error Message 313 Not owner of table. Error Details This statement tries to do something, such as dropping a table, that only the owner of the table or a user who has Database Administrator privileges can do. Check that the statement names…