Informix Error Messages and Error Codes From Error 170 to 178

Informix Error Code -171 ISAM error: ISAM file format change detected.
A program that uses a particular locking method or index-node size has attempted to access an ISAM file that was created using a different locking method or index-node size.
If you are migrating files from a platform that uses another index-node size, you must run the bcheck or secheck utility with the -s option against all of the ISAM files (.dat and .idx) to resize the index nodes.
For INFORMIX-SE, if you are migrating applications between platforms that use different locking methods, you must set the environment variable RESETLOCK to convert ISAM files as you access them. You can access all files for a given database by running UPDATE STATISTICS in that database, if time permits.

For C-ISAM applications, if you are migrating applications between platforms that use different locking methods, you must set the environment variable RESETLOCK to convert C-ISAM files as you access them.

Informix Error Code -172 ISAM error: Unexpected internal error.
You encountered an unanticipated internal event. Consult the online.log to see if the diagnostics preserved any additional information regarding this event. If the error recurs, refer to your Administrator’s Guide to acquire additional diagnostics. Contact Informix Technical Support with the diagnostic information.
Informix Error Code -173 ISAM error: An error has occurred during logical log back up.
This generic message indicates that the logical-log backup has failed. The SQL API also contains useful error text that is associated with this error.
Informix Error Code -174 ISAM error: An error has occurred during archive back up.

This generic message indicates that the archive backup has failed. The SQL API also contains useful error text that is associated with this error.
Informix Error Code -175 ISAM error: An error has occurred during physical restore.
This generic message indicates that the physical restore has failed. The SQL API also contains useful error text that is associated with this error.
Informix Error Code -176 ISAM error: An error has occurred during logical restore.
This generic error indicates that the logical restore has failed. The SQL API also contains useful error text that is associated with this error.
Informix Error Code -178 ISAM error: Database is locked; pending change to logging mode.
A request has been made to change the logging status of a database. Until a level-0 archive is done for all the storage spaces that the database uses, access to the database is blocked.

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 *