...
| Error | Details |
|---|---|
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-960
| Error | Details |
|---|---|
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-970
| Error | Details |
|---|
971-980
...
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-980
| Error | Details |
|---|---|
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.
|
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:
|
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-999
| Error | Details |
|---|---|
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
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...