Informix Error Messages and Error Codes From Error 139 to 143
Informix Error Code 139 ISAM error: logfile table overflow.
The database server administrator sees this error. The database server is configured to handle a certain number of logical logs. The limit has been reached, so a log could not be added. Increase the LOGSMAX parameter of the TBCONFIG or ONCONFIG file and initialize shared memory.
Informix Error Code -140 ISAM error: global section disallowing access.
This error occurs only in the VMS operating system. An internal error has occurred while initializing shared memory. If the error recurs, please note all circumstances and contact Informix Technical Support.
Informix Error Code -141 ISAM error: tblspace table overflow.
The database server is configured to handle a certain number of open tblspaces (which correspond approximately to tables). This limit has been reached, so a table that is used in this statement could not be opened. In the short term, roll back the current transaction and then re-execute it when fewer concurrent operations are going on. To prevent recurrence, the database server administrator should configure the system to handle more open tblspaces. The TBLSPACES parameter of the TBCONFIG or ONCONFIG file sets the limit. The ovrtable count in the ON-Monitor or ON-Monitor Profile display reflects the number of times this error occurs.
Informix Error Code -142 ISAM error: overflow of tblspace page.
An internal error (probably obsolete) occurred. If the error recurs, please note all circumstances and contact Informix Technical Support.
Informix Error Code -143 ISAM error: deadlock detected.
The database server has detected an impending deadlock between your request and other, concurrent user requests. Each user request is waiting for a resource (a row or disk page) that is held by another request in the chain; if your requested operation went forward, the chain would be closed and all requests would be deadlocked. In the short term, treat this error the same as -107 (record is locked). Roll back the current transaction, and re-execute it after a delay. To prevent recurrence, review the design of the applications that use the same tables and execute concurrently. Various design strategies can minimize the probability of deadlock.
When INFORMIX-STAR is active, and your application is using tables in both this system and another system, deadlock detection is no longer deterministic but probabilistic, based on the duration of a delay waiting for resources in another system. The database server administrator can set the length of the delay after which deadlock is assumed.
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.
Information about Informix Error Codes or Status Codes or Exit Codes and Error Messages on Windows, Linux Operating Systems.