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…

In this blog post, let’s learn about the error message “235 Character column size is too big.” in Hydra and the description of the error. Error Message 235 Character column size is too big. Error Details Another user has locked a row that this statement selects. If you executed the statement interactively, you can do one of two things. You can wait a short time…

In this blog post, let’s learn about the error message “045 Operation not supported on socket.” in Hydra and the description of the error. Error Message 045 Operation not supported on socket. 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 circumstance, and contact Informix Technical Support.

In this blog post, let’s learn about the error message “328 Column column-name already exists in table.” in Hydra and the description of the error. Error Message 328 Column column-name already exists in table. Error Details This statement tries to add the column shown, but one with that name already exists. Check the spelling of the name; if it is as you intended, then the…

In this blog post, let’s learn about the error message “376 Log file already exists.” in Hydra and the description of the error. Error Message 376 Log file already exists. Error Details The transaction log file you specify in the WITH LOG IN clause must not already exist. The database server must start a log file fresh; it has no means of appending log data…