...
| Error | Details |
|---|---|
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-940
| Error | Details |
|---|
...
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-950
| 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
961-970
971-980
981-990
...