Informix Error Messages and Error Codes From Error 130 to 135
Informix Error Code -130 ISAM error: no such dbspace.
This code indicates one of two problems. The most likely problem is that this operation specifies a dbspace by name (for example, in the IN clause of a CREATE TABLE statement or in the DBSPACETEMP environment variable setting), but that name has not been defined. You can run the tbstat or onstat utility with the -d option to see the names of defined dbspaces. Ask the database server administrator about creating a new dbspace.
If the operation does not explicitly name a dbspace, or if the name is correct, the problem might be more serious. The error might reflect corruption of reserved pages in the root dbspace. Use the tbcheck or oncheck utility with the -cr option to check for this condition.
Informix Error Code -131 ISAM error: no free disk space.
Not enough contiguous free disk space is available to complete the current operation. For C-ISAM programs, if transaction logging is in use, roll back the current transaction. Make some disk space available, and run the program again. For SQL products, roll back the current transaction, if possible. Contact the system administrator about acquiring more disk space for databases.
-132 ISAM error: rowsize too big.
The limit on a single row is the disk page size that the database server supports. Define the table differently, so that each row is shorter. Consider splitting the table into two or more tables or using more compact data types.
Informix Error Code -133 ISAM error: audit trail exists.
The ISAM processor has been asked to operate on a file in a way that is incompatible with an audit trail, yet an audit trail exists for the file. For C-ISAM programs, you cannot call iscluster while an audit trail exists. First call isaudit with the AUDSTOP mode. For SQL products, you cannot create a clustered index on a table while it has an audit trail. First use the DROP AUDIT statement to drop the audit trail.
Informix Error Code -134 ISAM error: no more locks.
The ISAM processor needs to lock a row or an index page, but no locks are available. The number of locks that an operation requires depends primarily on the number of rows that a single transaction modifies. You can reduce the number of locks that an operation needs by doing less in each transaction or by locking entire tables instead of locking rows. Depending on the implementation that you are using, the number of locks that is available is configured in one of three places: the operating-system kernel, the shared-memory segment, or the database server. Consult your database server administrator about making more locks available.
Informix Error Code -135 ISAM error: tblspace does not exist.
This error might indicate corruption of control information in the root dbspace, a serious problem that might require restoring the system from archive. In the short term, roll back the current transaction, and terminate the application. Then the database server administrator should run the tbcheck, oncheck, or onutil utility.
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.