Informix Error Messages and Error Codes From Error 367 to 371

SQLServerF1

Informix Error Code -372 Cannot alter table with audit trail on.
Once an audit trail has been started for a table, the table should not be altered. If you must alter the table, do the following. Copy the table to a backup medium. Use DROP AUDIT to remove the audit trail. Delete the audit-trail file. Alter the table. Again, copy the table to a backup medium. Finally, use CREATE AUDIT to start a new audit trail. The first backup is needed to restore the table if a failure occurs while the table is being altered (a lengthy, disk-intensive procedure if the table is large). The second backup is required because, if the table has to be recovered later, the new audit trail must be applied against a backup that has the same layout of columns.
Informix Error Code -373 DBPATH too long.
While the database server was trying to locate a database using the DBPATH environment variable, it constructed a full-path string that exceeds its limit of 80 characters. A limit exists on the length of one complete database directory pathname, from the starting slash or backslash through the .dbs suffix. You will have to locate your databases higher up in the directory hierarchy in order to use them. (The message text is misleading; there is no specific limit on the total length of the contents of DBPATH.)

Informix Error Code -374 Can only use column number in ORDER BY clause with UNION.
This query has both a UNION and an ORDER BY clause. In a union query, where several select statements exist and the names of the selected columns in each are not necessarily the same, you cannot use column names in the ORDER BY clause. Instead you must use column position numbers, where 1 stands for the first selected column, 2 for the second, and so on. Rewrite the query to use only numbers in the ORDER BY clause.
Informix Error Code -375 Cannot create log file for transaction.
While the database server was trying to execute a START statement, it got an unexpected error in trying to create the transaction-log file. Check the accompanying ISAM error code for more detailed information on the cause. Typical causes include a shortage of disk space, file permission problems, or a limit on the number of open files.

Informix Error Code -376 Log file already exists.
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 to an old log file. An existing log file contains recovery information that may be crucial, so it will not simply empty an existing file. To make a full backup, lock the database, copy all of the database directory to a backup medium, erase the log file (it is no longer needed), and use the START DATABASE statement. To make a partial backup, lock the database, copy the log file to a backup medium and store it with the full backup, erase or rename the log file, and use the START DATABASE statement.
Informix Error Code -377 Must terminate transaction before closing database.
This statement (DATABASE, CREATE DATABASE, or CLOSE DATABASE) cannot be executed until the current transaction has been finished. Use either COMMIT WORK or ROLLBACK WORK. Then the database can be closed.

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 *