Informix Error Messages and Error Codes From Error 250 to 256

Informix Error Code -250 Cannot read record from file for update.
The database server cannot get a row of a table prior to update. Check the accompanying ISAM error code for more information. Possibly another user has locked the row or the table, or possibly a more serious problem exists.
Informix Error Code -251 ORDER BY or GROUP BY column number is too big.
The ORDER BY or GROUP BY clause uses column-sequence numbers, and at least one of them is larger than the count of columns in the select list. Check that you entered the clause correctly and that you did not omit an item from the select list.
Informix Error Code -252 Cannot get system information for table.
The database server cannot access system information associated with the table. Check the accompanying ISAM error code for more information. Unless the ISAM error code or an operating-system message points to another cause, run the oncheck utility to verify file integrity.

Informix Error Code -253 Identifier too long – maximum length is 18.
A name in the statement exceeds the maximum length. Check the length of the names and whether a typographical error caused two names to run together.
Informix Error Code -254 Too many or too few host variables given.
The number of host variables that you named in the INTO clause of this statement does not match the number of “?” place holders that you wrote into the statement. Locate the text of the statement (in a PREPARE or DECLARE statement), and verify the number of place holders. Then review the list in the INTO clause to see which item is incorrect.

Informix Error Code -255 Not in transaction.
The database server cannot execute this COMMIT WORK or ROLLBACK WORK statement because no BEGIN WORK was executed to start a transaction. Because no transaction was started, you cannot end one. Any database modifications that were made are now permanent; they cannot be rolled back but do not need to be committed. Review the sequence of SQL statements to see where the transaction should have started.
This error can occur when you open a cursor for update and have not started a transaction yet.
Informix Error Code -256 Transaction not available.
You cannot begin a transaction in this database because it does not have a transaction log. In order to support transactions, you must start a transaction log. Refer to your Administrator’s Guide for information on how to start a transaction log.

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.

When it comes to troubleshooting, the more you know the better troubleshooter you are (in my option). Sometimes knowing more actually gets in the way. We repeatedly get calls where customers couldn’t connect to AlwaysOn Listener on Azure because of the misconfiguration of the subnet mask for the listener IP. They receive this error “A...

We just released SQL Nexus 5.5.0.1 on codeplex. In addition to numerous ‘rules’ that catch issues that can potentially impact your SQL Server performance, we added quite a few reports. Some of the reports are displayed below. The following three were born out of troubleshooting experience. “Top 20 Active CPU Intensive Queries”: When troubleshooting CPU...

A user called in for help because he wasn’t able to drop a user from a database. The error message is below Msg 15136, Level 16, State 1, Line 2The database principal is set as the execution context of one or more procedures, functions, or event notifications and cannot be dropped. From the error, the...

There are multiple levels of throttling with Azure. You can get throttled at disk level, storage account level or VM/host level. These types of throttling can manifest into something that may not be that obvious. Recently we received a call from customer who was backing up databases from Azure VM to Azure blob storage. The...

Lately, we had a customer who contacted us for a performance issue where their server performed much worse in SQL Server 2016 following upgrade. To show us as an example, he even captured a video. In the video, he showed that the session that was compiling the query had multiple threads waiting on LATCH_EX of...

With so many users new to Azure, Sometimes an issue appears more complex than it really is. If you back up your databases to Azure blob storage but your company uses proxy servers for internet access, you will need to configure backuptoURL.exe.config per SQL Server Backup to URL Best Practices and Troubleshooting. We...

If you created an SQL Server VM via azure portal, there will be a section called “SQL Server Configuration” which was introduced via blog “Introducing a simplified configuration experience for SQL Server in Azure Virtual Machines”. Here is a screenshot of that setting. It allows you to configure various things like auto backup, patching or...

If you need to open up your SQL Server on an Azure VM to public internet access, you need to look no further than this document Connect to a SQL Server Virtual Machine on Azure (Resource Manager). It has very detailed step-by-step instructions. On a very high level, here are steps In your VM, create...

Recently we got a customer who called in and wanted to know why he received NULL for query_plan when querying sys.dm_exec_query_plan. This customer referenced a blog from https://dzone.com/articles/dmexecqueryplan-returning-null. In that scenario, you will get NULL for query_plan if there are any statements involving temp tables that have not been executed for the first time. For...