Informix Error Messages and Error Codes From Error 9704 to 9709

Informix Error Code -9704 For SPL routine, parameter must be named.
The name of the parameter in a CREATE FUNCTION or CREATE PROCEDURE statement is optional only for external routines. Specify the parameter name.

Informix Error Code -9705 These modifiers are invalid for SPL routines: CLASS, CLIENT, HANDLESNULLS, INTERNAL, ITERATOR, PERCALL_COST, SELFUNC and STACK.
Do not specify these modifiers for SPL routines.
Informix Error Code -9706 END PROCEDURE/FUNCTION does not match with CREATE PROCEDURE/FUNCTION.
If you are using a CREATE PROCEDURE statement, the end clause must contain END PROCEDURE. If you are using a CREATE FUNCTION statement, the end clause must contain END FUNCTION. Do not mix and match PROCEDURE and FUNCTION keywords.

Informix Error Code -9707 Modifiers COMMUTATOR and NEGATOR are not allowed in procedure.
Because procedures do not return values, these modifiers are not allowed in a CREATE PROCEDURE statement. Use a CREATE FUNCTION statement or do not specify these modifiers.
Informix Error Code -9708 SELFUNC modifier can only be used in EXTERNAL FUNCTION.
Do not specify SELFUNC modifier to a SPL routine or an external procedure.
Informix Error Code -9709 More than one distinct type of the parameter type have cast to argument type.
This situation occurs if more than one distinct type of the source type of the parameter has casts from the argument type. For example, assume the routine routine_name(paramtype) exists. Both paramdist1 and paramdist2 are distinct types of paramdist1. The routine is invoked as routine_name(argtype). Casts also exist from argtype to paramdist1 and argtype to paramdist2. Because distinct types inherit all the routines defined on the source types, paramdist2 and paramdist1 inherit the routine routine_name. Thus the routine resolution cannot resolve the routine, and this error results.

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.

With codeplex shutting down, we have moved SQL Nexus to github with a new release (6.0). Now both Pssdiag/SQLDiag manager and SQL Nexus are on github. Where to get it As you navigate to SQL Nexus, you can download code and released binary files. If you choose to download binary files, you can go to...

SQL Server : large RAM and DB Checkpointing Hi everyone, This post’s purpose is to establish a summary of the specific behaviors with relation to DB Checkpoint that may happen within SQL Server when running with a large quantity of allocated memory and when applicable, how to best address them. SQL Server 2016 improves...

Recently we got an inquiry from a customer who received the following message in errorlog and wanted to know why. [INFO] HkDatabaseTryAcquireUserMemory(): Database ID: [7]. Out of user memory quota: requested = 131200; available = 74641; quota = 34359738368; operation = 1. This is my first time to see this error. As usual, I relied...

Recently I assisted on a customer issue where customer wasn’t able to alter a memory optimized table with the following error Msg 41317, Level 16, State 3, Procedure ddl, Line 4 [Batch Start Line 35]A user transaction that accesses memory optimized tables or natively compiled modules cannot access more than one user database or databases...

In a previous blog, I talked about memory optimized table consumes memory until end of the batch. In this blog, I want to make you aware of cardinality estimate of memory optimized table as we have had customers who called in for clarifications. By default memory optimized table variable behaves the same way as...

I worked on an interesting issue today where a user couldn’t restore a backup. Here is what this customer did: backed up a database from an on-premises server (2008 R2) copied the file to an Azure VM tried to restore the backup on the Azure VM (2008 R2 with exact same build#) But he got...

Recently, I looked an In-Memory OLTP issue with Principal Software Engineer Bob Dorr who is still my office neighbor. After restoring a database that had just one memory optimized table, we dropped the table. Even without any memory optimized tables,number of checkpoint files keep going up every time we issue a checkpoint. For a while,...

In this blog Added per-operator level performance stats for Query Processing, Senior PM in QP talks about extending operator level performance stats. They include stats related to reads, CPU and elapse time. These are very helpful to track down query performance issues. We worked on recent case where we put ActualElapsedms in a good...

In blog “Importance of choosing correct bucket count of hash indexes on a memory optimized table”, I talked about encountering performance issues with incorrect sized bucket count. I was actually investigating an out of memory issues with the following error. Msg 701, Level 17, State 103, Line 11There is insufficient system memory in resource pool...

I was working with a customer to troubleshoot memory optimized table issues. In this scenario, our customer uses a memory optimized table variable. He put 1 million rows of data into the table variable and then process it. Based on what he said, I tried to come up with a repro to see if...