900 Message number -900 not found.

901 Message number -901 not found.

902 Message number -902 not found.

903 Licensed INFORMIX-SQL server not accessible.

This statement refers to another host computer system, and that system is active and accessible. However, the sqlexecd network daemon has not been started on it, so no database services can be gotten from it. Contact the DBA of the other system. Check that the INFORMIX-STAR or INFORMIX-NET software is correctly installed.

904 Authorization file not on licensed INFORMIX-SQL server.

This message indicates that the installation of the Informix networking software was not completed correctly. Review the installation steps on the workstation and on the network server(s) to make sure that it was completed without error.

905 Cannot locate sqlexec service /tcp service in /etc/services.

The INFORMIX-STAR or INFORMIX-NET software has not been properly installed on this system. In particular, entries in the system-configuration file /etc/services (UNIX) or \etc\services (DOS) have not been made. Contact the person who installs your Informix software.

906 Cannot locate database server (check DBPATH).

A server name that your DBPATH environment variable specifies is invalid. This message appears in Version 6.0 and later.
Check that each database server name in your DBPATH setting is valid and is not too long. In Dynamic Server 200, the maximum length for database server names is 128 characters. In other Informix database servers, the maximum length for server names is 18 characters.
Cannot locate remote system (check DBPATH).
INFORMIX-NET is searching for the database that is requested in the current statement. It is using the entries in the DBPATH environment variable and is trying one that, by use of //sitename, specifies a directory on another computer system. That system cannot be accessed.
Review the setting of the DBPATH environment variable. Check that any other systems it specifies have INFORMIX-STAR or INFORMIX-NET installed and active. This message appears prior to Version 6.0.

907 Cannot create socket on current database server.

INFORMIX-STAR or INFORMIX-NET is trying to access another computer system but is unable to create a connection. Contact your system administrator, and ask for a check that TCP/IP is correctly installed and functioning.

908 Attempt to connect to database server (servername) failed.

The program or application is trying to access another database server but has failed. Note the server name in the current statement.
The desired database server is unavailable, or the network is down or is congested. Ask your DBA and system administrator to verify that the server and network are operational. If the network is congested, use the environment variables INFORMIXCONTIME and INFORMIXCONRETRY to tune connection timing. For information on setting these environment variables, see the Informix Guide to SQL: Reference.
This message appears in Version 6.0 and later versions.

909 Invalid database name format.

This statement seems to refer to a database from another database server, but the database name, site name, server name, or punctuation is incorrect. Review the statement, and check that all identifiers start with a letter (or underscore, for Version 6.0 and later) and contain only letters, digits, and underscores, and that the reference is in the form dbname@sitename or //sitename/dbname (before Version 6.0) or dbname@servername or //servername/dbname (Version 6.0 and later). If you are using INFORMIX-OnLine for NetWare, check that you provided the remote database name in one of the forms that is explained in the product manual.

910 Cannot create an Informix Dynamic Server database from an INFORMIX-SE client.

This CREATE DATABASE statement cannot be carried out because the database server on your workstation and the one on the other computer system are different products: one is INFORMIX-SE and the other is another Informix database server. You can manipulate databases in this configuration, but you cannot create one.
To create a database, either start the same product in both locations, or run this statement locally on the other computer system.
Cannot create a Dynamic Server or INFORMIX-OnLine database from an INFORMIX-SE client.
This CREATE DATABASE statement cannot be carried out because the database server on your workstation and the one on the other computer system are different products: one is INFORMIX-SE and the other is another Informix database server. You can manipulate databases in this configuration, but you cannot create one. To create a database, either start the same product in both locations, or run this statement locally on the other computer system. The SQLEXEC environment variable (for database servers before Version 6.0) determines which database server your application uses.

911 System error – Cannot read from pipe.

This internal error reflects a failure in communication between your application and the INFORMIX-STAR or INFORMIX-NET software. Look for operating-system error messages that might give more information. Restart the application. If the problem recurs, please note all circumstances and contact Informix Technical Support.

912 Network error – Could not write to database server.

A network failure occurred. Look for operating-system error messages that might give more information. Restart the application. If the problem recurs, contact your system administrator, and ask for network diagnostics to be run.

913 Network error – Could not read from database server.

A network failure occurred. Look for operating-system error messages that might give more information. Restart the application. If the problem recurs, contact your system administrator, and ask for network diagnostics to be run.

914 System error – Cannot write to pipe.

This internal error reflects a failure in communication between your application and the INFORMIX-STAR or INFORMIX-NET software. Look for operating-system error messages that might give more information. Restart the application. If the problem recurs, please note all circumstances and contact Informix Technical Support.

915 Cannot create an INFORMIX-SE database from an Informix Dynamic Server client.

This CREATE DATABASE statement cannot be carried out because the database server on your workstation and the one in the other computer system are different products: one is INFORMIX-SE and the other is another Informix database server. You can manipulate databases in this configuration, but you cannot create one.
To create a database, either start the same product in both locations, or run this statement locally on the other computer system.

916 NFS mount table error.

The database server that you tried to access or a path that was specified in your DBPATH environment variable is located on an NFS-mounted file system. However, the database server or client application encountered an error accessing the NFS-mounted table file /etc/mtab (or, on some operating systems, /etc/mnttab). This condition probably occurred because your account does not have read permission for the file. Contact your system administrator, and have the file made readable to public.
This message appears with Version 6.0 and later.
Cannot open /etc/mtab.
The database server needs to check the system configuration file /etc/mtab to verify the location of a file system. However, it got an error when it tried to read that file, probably because your account does not have read permission for it. Contact your system administrator, and have the file made readable to public.
This message appears prior to Version 6.0.

917 Must close current database before using a new database.

This statement (DATABASE or CREATE DATABASE) requires you to open a different database. However, the current database is located on another computer system, so you must explicitly close it with the CLOSE DATABASE statement. (When you work with databases located on the same computer as your application program, the database server will close the current database for you automatically.) If a program receives this error, review the program logic, and check that it executes a CLOSE DATABASE statement before a CREATE DATABASE statement. This solution will work in all situations, networked or local.

918 Unexpected data received from another database server.

This internal error reflects a failure in communication between your application and the INFORMIX-STAR or INFORMIX-NET software at another site. Restart your application. If the problem recurs, ask your system administrator to run network diagnostics. If the error recurs, please note all circumstances and contact Informix Technical Support.

919 System error. Wrong number of arguments to database server process.

This internal error reflects a failure in communication between your application, INFORMIX-STAR or INFORMIX-NET software, and the database server on the other computer system. Check that all three of these software components are at compatible software levels. (For versions prior to Version 6.0, see the appropriate INFORMIX-NET/INFORMIX-STAR Installation and Configuration Guide for a compatibility chart). Recompile and relink your application program if necessary. If the problem recurs, please note all circumstances and contact Informix Technical Support.

920 Message number -920 not found.

921 System error. Illegal or wrong number of arguments to sqlexec server.

This internal error reflects a failure in communications between your application and the database server on the other computer system. Check that all software components are at compatible software levels. Recompile and relink your application program if necessary. If the problem recurs, please note all circumstances and contact Informix Technical Support.
For a Windows NT system, check your Client Installation and Configuration Guide for information about using Setnet32 to set the environment variables that affect client-server communications.
For versions prior to Version 6.0, see the appropriate INFORMIX-NET/INFORMIX-STAR Installation and Configuration Guide for a compatibility chart.

922 Cannot get name of current working directory.

A problem exists with the current working directory on this system or on another computer system that your application is using. Possibly your account does not have read access to the directory, or possibly the file system that contains it is improperly mounted. Exit your application, and retry. If the problem persists, see your system administrator for assistance.

923 INFORMIX is not licensed to access the current database server only.

This version of the Informix product is not licensed for network use. Locate the version of the software that is licensed for use with INFORMIX-STAR or INFORMIX-NET, and reset your INFORMIXDIR environment variable and the SQLEXEC environment variable (for database servers prior to Version 6.0) to point to it.

924 INFORMIX is not licensed to access the specified database server.

If you have installed an INFORMIX-NET NET station package only on your client computer, you cannot access locally resident databases. If the database that you are attempting to access is not locally resident, enter the command again and specify a site name with the database name, or set your DBPATH environment variable to indicate searches only in specific sites. If you want to use your Informix product to access both local and remote databases, please contact your Informix representative for details on purchasing the appropriate Informix product.

925 The protocol type should be tcp.

The protocol type that is shown in the $INFORMIXDIR/etc/sqlhosts file (or in \INFORMIX\etc\sqlhosts on INFORMIX-OnLine for NetWare) should be tcp.

926 The database server is not licensed for distributed data access.

This statement refers to a database in a different database server (for example, by qualifying the name of a table with dbname@sitename:table). However, this version is not licensed for such use. With this version, you can refer only to tables in databases that are all on the same database server.
Contact your Informix representative about upgrading this database server to full INFORMIX-STAR status. If you believe that you have INFORMIX-STAR installed, check the contents of the INFORMIXDIR environment variable. If you are using INFORMIX-OnLine for NetWare, you cannot access tables or databases on remote systems unless you have INFORMIX-NET PC.
INFORMIX-OnLine is not licensed for distributed data access.
This statement refers to a database in a different database server (for example, by qualifying the name of a table with dbname@sitename:table). However, this version is not licensed for such use. With this version, you can refer only to tables in databases that are all on the same database server. Contact your Informix representative about upgrading this database server to full INFORMIX-STAR status. If you believe that you have INFORMIX-STAR installed, check the contents of the INFORMIXDIR environment variable. If you are using INFORMIX-OnLine for NetWare, you cannot access tables or databases on remote systems unless you have INFORMIX-NET PC.

927 Exceeded limit on maximum number of servers you can reference.

This statement contains references to more sites than the database server can handle. Through Version 4.1, the limit on different site names that can appear in one statement is 32 (later versions might allow more). Review the statement, and check that only necessary sites are named. If so, revise the operation to use fewer sites (for example, by selecting some data into a local, temporary table).

928 The database server is not licensed for distributed data access.

This statement refers to a database on a different computer system (for example, by qualifying the name of a table with dbname@sitename:table). However, the database server that is active at the indicated site is not licensed for such use. This situation indicates an error in the setup of the remote computer system: it was configured for network access, but the wrong database server was started. Contact the network administrator, and ask for a check of the environment variables when starting the sqlexecd daemon. If you are using INFORMIX-OnLine for NetWare, you tried to access a table on an database server that is not licensed for remote access; you can access only other INFORMIX-NET PC systems.

929 Message number -929 not found.

930 Cannot connect to database server servername.

The application is trying to access another computer system but failed. Note the server name in the current statement. Ask your network administrator and DBA to check that the network is operational and that the particular database server is active. This message appears with Version 6.0 and later.
Cannot connect to remote host sitename.
INFORMIX-STAR or INFORMIX-NET is trying to access another computer system but has failed. Note the site name in the current statement. Contact your network administrator, and ask for a check that the network is operational and that the particular site is active. This message appears in database servers prior to Version 6.0.

931 Cannot locate servicename service/tcp service in /etc/services.

The service servicename is not listed in the network configuration file /etc/services (UNIX) or \etc\services (DOS). Check the $INFORMIXDIR/etc/sqlhosts file, and check that the service name for the desired server is correct. If so, contact your network administrator to find out why the service is not known. If you are using INFORMIX-OnLine for NetWare, check the \etc\services file on the client for the required entries.

932 Error on network connection, function system call failed.

This internal error reflects a failure in communication between your application and the network software (INFORMIX-STAR, INFORMIX-NET, INFORMIX-NET for Windows, and so on) at another site. Restart your application. Look for operating-system messages that might give more information.
If you are using INFORMIX-NET for Windows, a Windows Sockets problem might exist; check your Windows Sockets 1.1 documentation for more information. Check the sqlerrm field of the sqlca structure for the particular Windows Sockets message.
In the ASCL context, this error might also indicate problems in your informix.ini file. Verify that the SERVICE, HOST, and PASSWD entries are correct.
If the problem recurs, ask your network administrator to run network diagnostics. If the error recurs, please note all circumstances and contact Informix Technical Support.

933 Unknown network type specified in DBNETTYPE.

The DBNETTYPE environment variable is used on certain machines to distinguish which network protocol to use when two protocols are available. The value that is currently set in it is not supported. Display the variable, and check that it is set correctly. Prior to Version 6.0, refer to the INFORMIX-NET/INFORMIX-STAR Installation and Configuration Guide for the correct setting. If you are using INFORMIX-OnLine for NetWare, set DBNETTYPE to starlan, tcp/ip, or some other supported network.

934 Connection to remote site no longer valid.

This statement uses data from another computer system, but the connection has been lost. Roll back the transaction, and try again after you reestablish the connection.

935 Cannot obtain IPX address for service name servicename.

You are trying to connect to a database server with the indicated service name via the IPX/SPX network protocol on a system with portable INFORMIX-OnLine for NetWare. The client application, INFORMIX-NET or INFORMIX-STAR, is not able to determine the IPX address that is associated with the specified service name. Possibly the service name is misspelled in your sqlhosts file; the sqlexecd daemon or the database server is not running; or the portable INFORMIX-OnLine for NetWare software is not operating properly. Verify the service name in your sqlhosts file. Ask your DBA or system administrator to verify that the sqlexecd daemon, the database server, and the portable INFORMIX-OnLine for NetWare software are operational.

936 Error on remote connection connection-name.

An attempted connection to a remote host failed. Check the name of the connection that is specified in your particular connection statement (CONNECT, DATABASE, and so on) to make sure that you correctly specified the name or path of the connection. Check for incorrect spelling. Check for the wrong connection name.

937 User Defined Routine error.

mi_db_error_raise() has been called from within a user-defined routine and set a fatal error. For an explanation, look at the SQLSTATE that the user-defined routine set.

938 VALUES clause may not have expressions if a cursor is declared on an INSERT.

The INSERT statement to be associated with the INSERT cursor includes a VALUES clause that has one or more expressions.
Change the application so that expressions are not used in the VALUES clause.

939 Message number -939 not found.

940 Check Option is not supported in Union Views.

You tried to define a union view with a check options. Redefine the union view without the check options clause.

941 String processing error while evaluating function (function_name).

An error occurred during evaluation of the case conversion function on the input string. This error could be due to an invalid character (single- or multi-byte) in the string. You need to execute the query again after verifying that the characters in the input string are valid.

942 Transaction commit failed – transaction will be rolled back.

This error can occur at transaction-commit time if an error is raised when a DataBlade routine calls a UDR-registered end-of-transaction (MI_EVENT_END_XACT) callback. You have registered a callback for the MI_EVENT_END_XACT (or MI_Xact_State_Change) event in the context of a server routine. When the end-of-transaction (MI_EVENT_END_XACT) event occurred to commit the transaction, an error was raised.
Within a DataBlade routine, you can use the mi_error_desc_next() function to obtain the next error, which should explain the cause of the failure. Currently, the end-of-transaction (MI_EVENT_END_XACT) event occurs only within the context of a DataBlade server routine. It does not occur within the context of a DataBlade client application.

943 Found a non-terminated comment (“/” with no matching “/”).

DB-Access does not currently support comments without terminators. You might see this message when you run .sql scripts through DB-Access.

944 Cannot use “first” in this context.

This statement uses FIRST N inside a subquery. This action is not supported.
Review the use of FIRST N and check that it is applied only to the outer main query SELECT clause.

945 Invalid parameter given to dbinfo(version).

The arguments to dbinfo() are invalid or NULL. The first argument was the string constant version.
Check that the second argument is also a quoted string constant that corresponds to one of the following values:major,minor,level,os,server-type, or full.
Invalid parameter given to dbinfo(version).
You entered a value for a version that this command does not support.

946 Source string for UPPER, LOWER, and INITCAP must be of string type.

The source string passed as input to a case conversion function must have a character data type.

947 Declaration of an SPL variable named null conflicts with SQL NULL value.

Users may not define an SPL routine variable whose spelling is null. This is an error because allowing such definition would restrict the global scope of the NULL constant.

948 Cannot rename constraint index.

User tried to rename a system-generated constraint index.
You do not need to take any action because you are not allowed to rename a system-generated constraint index.

949 Unable to alter fragmentation scheme when indexes disabled.

An attempt has been made to alter the fragmentation scheme on a table that has disabled indexes. This is not allowed. The action is aborted.

950 Message number -950 not found.

951 User username is not known on the database server.

The database server that you tried to access does not accept either your user ID, the login name that is specified for the desired server host in your ~/.netrc file, or the user name that is specified in the USER clause of a CONNECT statement. If you are explicitly specifying your user name in the ~/.netrc file or in a CONNECT statement, check that the name is correct. If you do not have a valid user ID on the server computer, see your system administrator. This message appears with Version 6.0 and later.
User is not known on remote host.
This statement refers to a database on another computer system, but the other system does not accept your account name. You must have a valid login identity on any computer system you access. See your network administrator about getting a login ID. This message appears prior to Version 6.0.

952 User’s password is not correct for the database server.

The password that is specified for the server computer in your ~/.netrc file or in the USER clause of a CONNECT statement is incorrect. The database server does not accept (or cannot find) your account password. Check that your password is specified correctly, and try again. This message appears with Version 6.0 and later.
User ()’s password is not correct for the database server.
The password that is specified for the server computer in your ~/.netrc file or in the USER clause of a CONNECT statement is incorrect. The database server does not accept (or cannot find) your account password. Check that your password is specified correctly, and try again. This message appears with Version 6.0 and later.

953 Network server could not exec sqlexec program.

The network server was unable to start the database server thread. The most common cause for this error is a failure to define the INFORMIXDIR environment variable, by root, at the time the database server process was started. Contact your network administrator, and ask that the database server process on the remote system be restarted with a valid path to the Informix software. This message appears with Version 6.0 and later.
Remote host could not exec sqlexec program.
The network daemon, sqlexecd, on the other computer system was unable to start the database server process. The most common cause of this error is a failure to define the INFORMIXDIR and SQLEXEC environment variables, by root, at the time the daemon was started. Contact your network administrator, and ask that the daemon on the remote system be restarted with a valid path to the Informix software. This message appears prior to Version 6.0.

954 Client is not known to remote host.

The computer on which your application is running is not known to the computer you are trying to access. Contact your network administrator, and ask that your computer be made known. The usual way of making a computer known is through the configuration file /etc/hosts.equiv on the other system. Refer to the INFORMIX-NET/INFORMIX-STAR Installation and Configuration Guide. This message appears prior to Version 6.0.
Client is not known to database server.
The computer on which your application is running is not known to the database server that you are trying to access. Contact your network administrator, and ask that your computer be made known, most likely through the configuration file /etc/hosts on the other system. This message appears with Version 6.0 and later.

955 Remote host could not receive data from client.

This internal error reflects a failure in communication between your application and the INFORMIX-STAR or INFORMIX-NET software at another site. Restart your application. Look for operating-system messages that might give more information. If the problem recurs, ask your network administrator to run network diagnostics. If the error recurs, please note all circumstances and contact Informix Technical Support. This message appears prior to Version 6.0.
Database server could not receive data from client.
This internal error reflects a failure in communication between your client application and the database server software at another site. Restart your application. Look for operating-system messages that might give more information. If the problem recurs, ask your DBA to run network diagnostics. If the error recurs, please note all circumstances and contact Informix Technical Support. This message appears beginning with Version 6.0.

956 Client client-name is not in /etc/hosts.equiv on the remote host.

This operation cannot be completed because the specified remote computer does not recognize the name of the client computer (the local host, whose name the hostname command returns). Client names are normally recorded in the configuration file /etc/hosts.equiv. The rhosts file on the remote computer might also need modification. For more information on these files and the relation between them, try man rhosts on a UNIX system. See the remote host administrator to ensure that the client host name is specified in /etc/hosts.equiv file for the remote host. This message appears in versions prior to Version 6.0.
Client client-name or user is not trusted by the database server.
The desired database server does not consider the client computer or your user ID trusted. Ask the system administrator to include the client computer as a trusted host and/or your user id as a trusted user in the /etc/hosts.equiv file on the server computer or in the .rhosts file in your home directory on the server computer. See the UNIX manual pages on HOSTS.EQUIV(5) for more information.
Alternatively, you can explicitly specify your user name and password in the USER clause of a CONNECT statement or in the .netrc file in your home directory on the client computer. See the Informix Guide to SQL: Syntax for information on the CONNECT statement, and the UNIX manual pages regarding NETRC(5) for information on the .netrc file. This message appears with Version 6.0 and later.

957 Cannot create/access database on NFS mount.

Please note the specifics of your system when this internal error occurred, and contact Informix Technical Support.

958 Temp table already exists in session.

This statement tries to create a table with the name that is shown, but a temporary table with that name already exists. Only one temporary table with a given name can exist in a session.
Check the spelling of the name. If the name is spelled as you intended, check that a temporary table with the given name does not exist in the session. To review the names of temporary tables, query the systabnames table as follows:
SELECT dbsname, tabname FROM sysmaster:systabnames WHERE tabname =
If the name exists, review this name by querying the systables table in:
SELECT tabname FROM :systables WHERE tabname =
If the name does not exist in systables (” No rows found “), this table is a temporary table.

959 The current transaction has been rolled back due to an internal error.

A server thread associated with your session has been suspended, most likely because of a serious internal error. Evidence about the problem has been gathered and written to an Assertion Failure file, and your online log should contain more information. Please contact Informix Technical Support and provide them with your Assertion Failure file.
Before suspending the session thread, the server attempted to roll back all work performed by the current transaction. Your connection to the server may also have been broken, depending on the type of thread that was suspended. At a minimum you will have to begin a new transaction.

960 Message number -960 not found.

This error reflects problems you may have with file odbc.ini. It means that either the contents of the file is damaged or invalid, or the user does not have the permissions to read this file and write into it. It should be fixed, if the user is granted these rights.

961 Message number -961 not found.

962 Unable to connect to the ODBC Data Source.

If you get -962 error on MySQL on Lunix you should check your dirver ‘libmydobc’.
By default should be in:
/usr/local/lib/mysql/libmysqlclient.so
Check your odbc.ini file, should be:
Basic Configuration
[ODBC Data Sources]
cms = MySQL cms database
[cms]
Description = CMS sample database under MySQL
Driver = /usr/lib/odbc/libmyodbc.so
Database = cms
Servername = localhost
UserName =
Password =
Port = 3306
Protocol = 6.4

963 Message number -963 not found.

964 Message number -964 not found.

965 Message number -965 not found.

966 Message number -966 not found.

967 Message number -967 not found.

968 Message number -968 not found.

969 Message number -969 not found.

970 Message number -970 not found.

971 Integrity violations detected.

The user has attempted to change the object mode of a disabled constraint or disabled unique index to the enabled or filtering mode, but the SET statement fails because the table contains data that violates the constraint or the unique-index requirement. If a violations table has been started for the table that contains the inconsistent data, this message is returned to the user. The message is returned whether or not the SET statement included the WITH ERROR option.
Similarly, when an INSERT, DELETE, or UPDATE statement causes some records to be added to the violations table because the statement violates a filtering-mode object, this message is returned to the user if the following two conditions are true:

The SET statement or CREATE statement that specified the filtering-object mode for the object included the WITH ERROR option.
No other errors have been encountered during the execution of the INSERT, DELETE, or UPDATE statement.

972 Unable to alter table table-name.

The in-place alter table operation cannot be performed. Please see the accompanying ISAM error for more information.

973 Cannot insert from the violations table to the target table.

The user issued a statement that attempts to insert rows from the violations table into the target table. For example, the user enters the following statement:
INSERT INTO mytable SELECT * FROM mytable_vio
If the target table has some filtering-mode objects, this error is returned to the user. The user can recover in any of the following ways:

Set the object mode of the filtering objects to some other mode.
Stop the violations table.
Insert rows from the violations table into a temporary table, and then insert rows from the temporary table into the target table.

974 Cannot drop not null constraint on the serial column.

The user issued a statement to drop a NOT NULL constraint on a column that has a SERIAL data type. Such constraints can be disabled, but they cannot be dropped before the column is dropped.

975 Invalid object and object mode combination.

The user tried to create a new object in an object mode that does not apply to that object type, or the user set the object mode of an existing object to a mode that does not apply to that type of object. For example, if the user tries to create a trigger in the filtering mode or set an existing trigger to the filtering mode, the user receives this error.

976 Table must be fragmented by expression to grant fragment authority.

The user attempted to grant fragment-level privileges on an unfragmented table or on a table that is not fragmented by expression.

977 No permission on fragment (dbspace-name).

The user does not have the required fragment-level privilege on the table fragment. This message is always followed by another message that identifies the privilege that the user lacks. If an INSERT statement fails, the second message is -271. If an UPDATE statement fails, the second message is -346. If a DELETE statement fails, the second message is -240.

978 No insert permission on the violations/diagnostics tables.

The user issued an INSERT, DELETE, or UPDATE statement on a table with filtering-mode objects. The user receives this message because the user lacks the INSERT privilege on the violations or diagnostics tables that are associated with this table. The user must have the INSERT privilege on the violations and diagnostics tables before the database server can write rows into the violations and diagnostics tables for that user.
Similarly, if the user issued a SET statement to change the object mode of a disabled constraint or a disabled unique index to the enabled or filtering mode, and if a violations table has been started for the target table, the user receives this message if the user lacks the INSERT privilege on the violations or diagnostics table associated with the target table.

979 The current transaction has been rolled back due to an internal error.

A server thread associated with your session has been suspended, most likely because of a serious internal error. Evidence about the problem has been gathered and written to an Assertion Failure file, and your online log should contain more information.
Before suspending the session thread, the server attempted to roll back all work performed by the current transaction. Your connection to the server might also have been broken, depending on the type of thread that was suspended. At a minimum, you will have to begin a new transaction.
Contact Informix Technical Support and provide them with your Assertion Failure file.

989 Unsupported datatype encountered. A datype which is unsupported in this database driver layer has been encountered.

993 Invalid statement handle.

994 Database driver could not be loaded.

There was an error whilst trying to load the requested database driver.

995 Incompatible database driver

The database driver you are trying to load is not compatible with the current compiler version.

996 The database connection cannot be completed with the specified connection parameters, because the server does not support one or more requested options.

Currently this indicates that the environment variable QXORA_NO_NULLORDER was not set, and the (Oracle) database is of a version less than 8.1.7. Such oracle versions cannot correctly emulation the default sorting order for Informix nulls.

997 Feature unsupported. This feature is unavailable in the current version of Hydra.

998 License error. The application has encountered a runtime restriction due to evaluation licenses for a product.

This error means that you have hit a license evaluation limit (this is probably the execution of 1500 SQL statements). Check that you have installed the relevant Querix license for the database that you are working with. To prevent this error whilst working with the informix database, you should have a license type of informix for V3 or informix4 for Hydra4GL version 4 installed.
If you have the license installed and still get this error, it might occur because your application has been compiled before the installation of this license. You need to recompile your application.

999 Generic database error. Check the native/ISAM error code.

Related articles

Page:

Compilation Error: Error opening DB driver
Page:

Compilation error on UNIX/Linux 'file not recognized'
Page:

Compilation error -4409
Page:

Can't connect to a database (error -994)
Page:

Runtime/Compiler errors
Page:

Error codes 900 – 999
Page:

Error codes 800 – 899
Page:

Error codes 700 – 799
Page:

Error codes 600 – 699
Page:

Error codes 500 – 599

Browser not supported