Informix Error Messages and Error Codes From Error 771 to 780

SQLServerF1

Informix Error Code -771 Bad table lock id specified.
If you cannot find a direct cause for this internal error, please note all circumstances and contact Informix Technical Support.
Informix Error Code -772 Record/key doesn’t qualify for any table/index fragment.
This error can occur during a record insert or update. The most likely cause is an incorrect fragmentation specification that did not specify a REMAINDER. The easiest correction is to add a REMAINDER fragment to your SQL statement. However, the best correction is probably to reexamine the original fragmentation specification, figure out what is wrong, and fix it with an ALTER FRAGMENT statement.

Informix Error Code -773 Expression required for new fragment.
When you add a fragment to an expression-based fragmentation strategy, you must specify an expression for the new fragment. Restate your SQL statement to include a fragment expression.
Informix Error Code -774 Cannot specify fragment expressions with a round-robin fragmentation.
If table fragmentation is based on a round-robin strategy, you cannot specify a fragment expression during an ALTER FRAGMENT operation.
Informix Error Code -775 Dbspace dbspacename not used by table/index.
The dbspace that is specified during an ALTER FRAGMENT operation is incorrect because that dbspace contains no fragment. Specify a dbspace that has a fragment.
Informix Error Code -776 Alter fragment error: unable to move rows to new fragmentation scheme.
During an ALTER FRAGMENT operation, the rows could not be moved to another fragmentation strategy. See the accompanying ISAM error for more information on why the ALTER FRAGMENT operation failed.

Informix Error Code -777 Internal – function not valid on fragmented table.
If you cannot find a direct cause for this internal error, please note all circumstances and contact Informix Technical Support.
Informix Error Code -778 Unable to alter fragmentation scheme on index.
During an ALTER FRAGMENT operation, the fragmentation strategy for the index could not be altered. See the accompanying ISAM error for more information on why the ALTER FRAGMENT operation failed.
Informix Error Code -779 Duplicate table name in the alter fragment specification.
You cannot attach the same table multiple times. Check that your alter fragment specification attaches the same table only once.
Informix Error Code -780 Table/index is not fragmented.
You cannot perform the ALTER FRAGMENT operation because the table or index is not fragmented. Fragment the table or index, or do not perform the fragmentation operation.

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 *