0	Success.\
\
The operation succeeded. The database server returns this SQLCODE value\
to an application when an SQL statement executes successfully.\
\
|
100	No matching records found.\
\
The database server did not find any more data. This message is an ANSI-\
standard SQLCODE value. If you attempted to select or fetch data, you\
encountered the end of the data, or no data matched the criteria in the\
WHERE clause. Check for an empty table. Use this SQLCODE value to determine\
when a statement reaches the end of the data. For more information, see the\
discussion of SQLCODE in the IBM Informix ESQL/C Programmer's Manual. The\
database server can return this SQLCODE value to a running program.\
\
For the High-Performance Loader (HPL), this message can indicate that the\
map might be from a project other than the default project. Use the -p option\
in the onpload command line to provide a project name for mappings.\
\
|
1203	Cannot find message file.\
\
DataExtract cannot locate a needed message file. Check that you\
specified the appropriate pathname when you set the INFORMIXDIR and\
DBLANG environment variables. Contact your system administrator if you\
need help setting these environment variables.\
\
|
1204	Your system encountered an unknown type of terminal.\
\
Check that you set the TERM environment variable correctly. Check the\
database name for correct spelling. Contact your system administrator\
if you need help setting the environment variable.\
\
|
2005	Database database-name not found or not correct format.\
\
Check the database name for correct spelling.\
\
|
2008	The table table-name does not exist in the database.\
\
The database that is specified in the DATABASE section does not contain\
the table name that is included in the TABLE section of the form\
specification file. Check the table name for correct spelling.\
\
|
2009	You did not select any database tables.\
\
You must include one or more table names in the TABLES section of the\
form-specification file.\
\
|
2020	The following tables are involved in an error: table-name.\
\
Check the accompanying message for an indication of system action. The\
specified error involves the indicated tables.\
\
|
4074	Cannot find a C language compiler in any directory in your path.\
\
For this 4GL compiler message, you need a C compiler to finish\
compiling your program. Change your execution path so that a C compiler\
can be executed under the name cc.\
\
|
4102	See error number -number.\
\
For this 4GL compiler message, look up the message for -number.\
\
|
4150	Program error at module, line number line.\
\
The indicated line contains incorrect code that generated this 4GL\
runtime message. Sometimes the actual error or omission exists in the\
preceding lines of code. Look for additional messages that explain the\
error.\
\
|
4152	FORMS statement error number -number.\
\
For this 4GL runtime error, check the message for -number.\
\
|
4153	SQL statement error number -number.\
\
For this 4GL runtime error, check the message for -number.\
\
|
4154	Program stopped at module, line number line.\
\
This 4GL runtime message tells where a program stopped due to an\
error. Look for additional messages that explain the error.\
\
|
4155	4GL run-time error number -number.\
\
For this 4GL runtime error, check the message for -number.\
\
|
4156	ISAM error number -number.\
\
For this 4GL runtime error, check the message for -number.\
\
|
4157	SYSTEM error number -number.\
\
For this 4GL runtime error, check the message for -number.\
\
|
8009	See error number errno.\
\
Check the accompanying message for an indication of system action. Use\
the finderr utility to locate the indicated error message.\
\
|
12750	db <database_name>, tabid <table_identifier>: Must alter raw\
table to standard.\
\
Raw (nonlogging) tables exist in the database server that you are trying\
to revert to a previous version. Earlier versions of the database server\
do not support raw tables.\
\
To change the logging TYPE option of each table from RAW to STANDARD, use\
the ALTER TABLE statement. After altering the tables to STANDARD, you\
can revert the database server.\
\
|
16755	oninit: VPCLASS VPCLASS_name duplicate class name.\
\
The VPCLASS parameter in the onconfig file has a duplicate name. The\
VPCLASS name must be unique. Correct the onconfig file and restart\
oninit.\
\
|
16872	Logical Recovery Complete - no log replay was necessary.\
\
During restore, the database server determined that none of the dbspaces\
involved had any logging activity since they were backed up.  \
You do not need to look through log backups on tape because nothing\
would be found.\
\
You do not need to take any action.\
\
|
16888	Logslice successfully altered by adding logs.\
\
Logical logs were added to all new dbspaces in the altered dbslice.\
\
Perform a level-0 backup or fake backup to enable the new \
logical logs.\
\
|
16889	Dbslice successfully altered by adding dbspaces.\
\
Dbspaces were added to all named coservers.\
\
You do not need to take any action.\
\
|
19568	oninit: Too many VPCLASS parameters specified.\
\
Too many VPCLASS parameter lines exist in the onconfig file. Reduce\
the number of VPCLASS lines and restart oninit.\
\
|
19569	oninit: VPCLASS VPCLASS_name bad affinity specification.\
\
The affinity specification for the VPCLASS line is incorrect. Affinity\
is specified as a range where x is less than or equal to z, and both x\
and z are greater than zero.\
\
x: use processor x\
\
x - z: use processors in the range x to z inclusive\
\
|
19570	oninit: Cannot mix VPCLASS cpu and NUMCPUVPS, SINGLE_CPU_VP,\
AFF_SPROC, AFF_NPROCS, or NOAGE parameters.\
\
CPU VPs can be configured using either VPCLASS CPU or the old\
parameters NUMCPUVPS and so on. However, CPU VPs cannot be configured\
by mixing both formats.\
\
|
19571	oninit: Cannot mix VPCLASS aio and NUMAIOVPS parameters.\
\
AIO VPs can be configured with VPCLASS AIO or the old parameter\
NUMAIOVPS. However, AIO VPs cannot be configured with both formats.\
\
|
19572	oninit: VPCLASS VPCLASS_name number of VPs is out of the range 0\
to 10000.\
\
The initial number of VPs specified by a VPCLASS parameter line must be\
in the range 0 to 10,000. Correct the onconfig file and restart\
oninit.\
\
|
19573	oninit: VPCLASS VPCLASS_name maximum number of VPs is out of the\
range 1-10000.\
\
The maximum number of VPs specified by a VPCLASS parameter line must be\
in the range 0 to 10,000. Correct the onconfig file and restart\
oninit.\
\
|
19574	oninit: VPCLASS VPCLASS_name number of VPs is greater than the\
maximum specified.\
\
The initial number of VPs specified by a VPCLASS parameter is greater\
than the maximum specified by the same VPCLASS parameter. Correct the\
onconfig file and restart oninit.\
\
|
19575	oninit: VPCLASS VPCLASS_name bad scheduler specification.\
\
One of the options for a VPCLASS parameter is illegal. Check your\
Administrator's Guide for legal values. Correct the onconfig file and\
restart oninit.\
\
|
19750	Invalid serial number. Consult your installation guide.\
\
This RSAM error message indicates an incorrect serial number.\
\
|
19812	Illegal use of replication shadow columns.\
\
The specified operation cannot be performed on the replication shadow\
columns while replication is enabled.\
\
|
19813	Cannot add CRCOLS when the table already has replication shadow columns.\
\
The specified table was created with the WITH CRCOLS clause and\
therefore already has the replication shadow columns defined. You\
cannot alter this table to add CRCOLS to it.\
\
|
19814	Cannot drop CRCOLS when table does not have replication shadow columns.\
\
The specified table was not created with the WITH CRCOLS clause, or it\
has not been altered to include the CRCOLS. You cannot alter this table\
and drop the CRCOLS because these columns do not exist on this table.\
\
|
19815	Cannot create a temp table with CRCOLS.\
\
You cannot create a temporary table to include the replication shadow\
columns. If you did not intend to name a temporary table, check the\
spelling of the table name.\
\
|
19816	Cannot perform this operation on a table defined for replication.\
\
The specified operation cannot be performed on a table if replication\
is defined on the table. If you want to perform the specified\
operation, you must delete all replicates defined on this table.\
\
19989	Enterprise Replication is not in active state\
\
The specified operation cannot be performed on a table defined for\
replication if Enterprise replication is not in active state.\
If you want to perform the specified operation, you must start Enterprise\
Replication.\
\
19991	Table is not in Enterprise Replication alter mode\
\
The specified operation cannot be performed on a table defined for\
replication if the table is not in Enterprise Replication alter mode.\
If you want to perform the specified operation, you must put the table\
in Enterprise Replication alter mode.\
\
19992	Cannot perform insert/delete/update operations on a replicated table while the table is in alter mode\
\
The specified operation cannot be performed on a table defined for\
replication if the table is in Enterprise Replication alter mode.\
If you want to perform the specified operation, you must unset the\
Enterprise Replication alter mode.\
\
19993	Cannot modify a replicated column\
\
The specified operation cannot be performed on a table defined for\
replication. If you want to perform the specified operation,\
you must remove the column from the replicate definition, alter the column\
then add the column again to the replicate definition through\
Enterprise Replication remastering process.\
\
19994	Cannot drop a replicated column while the column is part of replicate definition\
\
The specified operation cannot be performed on a table defined for\
replication. If you want to perform the specified operation,\
you must remove the column from the replicate definition through\
Enterprise Replication remastering process.\
\
19995	Enterprise Replication error encountered while setting alter mode. See the message log file to get the Enterprise Replication error code.\
\
Enterprise Replication error encountered while performing the\
specified operation. See the message log file to get the\
Enterprise replication error code. If you want to perform the\
specified operation, correct the Enterprise Replication problem\
and reattempt the operation.\
\
19996	Enterprise Replication error encountered while unsetting alter mode. See message log file to get the Enterprise Replication error code\
\
Enterprise Replication error encountered while performing the\
specified operation. See the message log file to get the\
Enterprise replication error code. Correct the problem and clear\
the alter mode manually through cdr command line utility.\
\
|
19820	Informix OUTER JOIN and ANSI JOIN in the same query block.\
\
You cannot have Informix OUTER JOIN and ANSI JOIN in the same query\
block. Informix OUTER JOIN and ANSI JOIN are two different mechanisms\
and should not be combined in a single query. You can use only one of\
these.\
\
|
19821	Cannot rename a table using a synonym.\
\
You cannot use a synonym to perform a rename operation. Specify\
the <table-name> instead.\
\
To rename the synonym, drop the existing synonym and create a new one.\
\
|
19822	Cannot alter or truncate a table or drop a table or view using a synonym.\
\
You cannot use a synonym to perform an alter or truncate or drop on a table or a view.\
Specify the <table-name> or <view-name> instead.\
\
To drop the table or view or alter or truncate the table using the synonym, \
unset the environment variable USETABLENAME.\
\
To drop the synonym and not the table or view, specify \
DROP SYNONYM <synonym-name> instead.\
\
|
19823	Cannot use EXECUTE PROCEDURE INTO with the INSTEAD OF trigger.\
\
You cannot use EXECUTE PROCEDURE INTO with the INSTEAD OF trigger.\
\
|
19824	Cannot use BEFORE or AFTER action with the INSTEAD OF trigger.\
\
You cannot use the BEFORE or AFTER actions with the INSTEAD OF trigger.  You\
must use the FOR EACH ROW action with the INSTEAD OF trigger.\
\
|
19825	Cannot use WHEN clause if INSTEAD OF trigger is defined.\
\
You cannot use the WHEN clause to restrict the triggered action in \
INSTEAD OF trigger definitions.  The action of the triggering statement \
is always replaced by the specified triggered action on the base table \
(or tables) of the view on which the INSTEAD OF trigger is defined.\
\
|
19826	Cannot create INSTEAD OF trigger for a select event.\
\
You can create an INSTEAD OF trigger for an insert, update, or delete\
event, but not for a select event.\
\
|
19827	Cannot create an INSTEAD OF trigger on a table.\
\
You can only create an INSTEAD OF trigger on a view, not on a base\
table or synonym.\
\
|
21957	Invalid block size.\
\
You have specified inadequate block size for the tape device in your\
onload or onunload command. Make the block size larger than the size\
(in kilobytes) that the accompanying error message indicates. The\
onload and onunload utilities require a block-size parameter with a\
minimum value of 4 for 2-kilobyte-page computers or 8 for\
4-kilobyte-page computers.\
\
|
25500	The sqlexecd daemon is not licensed for remote use.\
\
You entered an incorrect serial number or serial-number key while you\
were running the IBM Informix client/server product installation script.\
Obtain the proper serial number and key and reinstall your IBM Informix\
client/server product.\
\
|
25501	You must log in as root to start the sqlexecd daemon.\
\
Log in as root and start the sqlexecd daemon process.\
\
|
25502	The sqlexecd daemon cannot execute the fork system call.\
\
Contact your system administrator to solve system problems.\
\
|
25503	Informix network features not supported on this product.\
\
The sqlexecd daemon does not support your network connections. Check\
that you specified the correct database or database server in the\
DBPATH environment variable. Consult your system administrator about\
IBM Informix NET licensing issues.\
\
|
25504	The sqlexecd daemon cannot open a socket.\
\
Check that you correctly installed the TCP/IP network. Check for\
malfunctions in the TCP/IP network.\
\
|
25505	The sqlexecd daemon cannot bind a name to the socket.\
\
Enter your request again. If the problem persists, refer to your system\
manual for more information.\
\
|
25506	The sqlexecd daemon cannot accept a connection on the socket.\
\
Check that you correctly installed the TCP/IP network. Check for\
malfunctions in the TCP/IP network.\
\
|
25510	execv could not start the database engine <server-name>, system\
errno <error number>.\
\
Enter your request again. If the problem persists, refer to your system\
manual for more information.\
\
|
25511	The sqlexecd daemon could not receive data from client.\
\
Check that you correctly installed the TCP/IP network. Check for\
malfunctions in the TCP/IP network.\
\
|
25512	Cannot access the database server program.\
\
Check that you can access the requested database server program.\
\
|
25514	The sqlexecd daemon cannot open the log file.\
\
Check that you can write to the requested log file.\
\
|
25515	You passed too many arguments to the sqlexecd daemon.\
\
Refer to your IBM Informix product manuals. Check the version information\
that is associated with your IBM Informix client/server products to verify\
compatibility between those products.\
\
|
-25507	You specified an unknown service name or protocol.\
\
Determine which of the following conditions produced this error and take the \
appropriate corrective actions:\
\
The value of the NETTYPE configuration parameter in the ONCONFIG file is not \
the same as the NETTYPE setting in the sqlhosts file. If the NETTYPE values \
are different, correct the incorrect value. If you update the ONCONFIG file, \
you must restart the database server.\
\
The correct service name is not in the /etc/services file. If you are using the TCP/IP protocol, check the /etc/services file. If you are using NFS, use the \
ypmake utility to check the /etc/services file. Sometimes the daemon does not \
recognize service names that are added after a default start-up. Add the \
correct service name if it is not present or restart your computer.\
\
The protocol entry in the ONCONFIG file or sqlhosts file is not supported by \
the operating system on your computer. For information about supported \
protocols, see the connectivity information section in the Administrator's \
Guide or the Client SDK release notes in the INFORMIXDIR/release directory. \
Correct the protocol entry in the ONCONFIG file or the sqlhosts file. If you \
update the ONCONFIG file, you must restart the database server.\
\
|
25518	You specified an unknown network type in DBNETTYPE.  Assuming STARLAN.\
\
If your network supports STARLAN connections, set the DBNETTYPE\
environment variable to starlan. If your network supports TCP/IP\
connections, set the DBNETTYPE environment variable to tcp/ip. IBM Informix\
Version 6.0 and later database servers do not use this message.\
\
|
25519	The sqlexecd daemon cannot open the network device.\
\
Enter your request again. If the problem persists, refer to your system\
manual for more information.\
\
|
25520	The sqlexecd daemon cannot allocate the call structure.\
\
Enter your request again. If the problem persists, refer to your system\
manual for more information.\
\
|
25521	The sqlexecd daemon cannot allocate the return structure.\
\
Enter your request again. If the problem persists, refer to your system\
manual for more information.\
\
|
25522	The sqlexecd daemon cannot allocate the call structure.\
\
Enter your request again. If the problem persists, refer to your system\
manual for more information.\
\
|
25523	The sqlexecd daemon cannot bind the network structures.\
\
The sqlexecd daemon process attempted to use the same service number\
that is allocated to another running process. Check that the system\
administrator does not need to use the running sqlexecd process, and\
then stop the sqlexecd process, and start a new one. Or add a new entry \
to the /etc/services file, and start a daemon for the service using the\
new service number. For more information, refer to your system manual.\
\
|
25526	The sqlexecd daemon cannot listen on the network device.\
\
Enter your request again. If the problem persists, run your network\
diagnostics to determine the source of the problem.\
\
|
25528	The sqlexecd daemon cannot accept a connection.\
\
Check that you correctly installed your network hardware and software.\
Check for malfunctions in the network.\
\
|
25529	The sqlexecd daemon cannot get a host structure.\
\
Check that you requested a valid host name. Verify that the /etc/hosts\
file contains the requested host-name entry.\
\
|
25530	The sqlexecd daemon cannot bind to the required port address.\
\
Check that no other daemons are running on the port address.\
\
|
25531	The sqlexecd daemon cannot bind to the required address.\
\
Check that no other daemons are running on the port address.\
\
|
25533	The sqlexecd daemon cannot close the network.\
\
Enter your request again. If the problem persists, refer to your system\
manual for more information.\
\
|
25534	The sqlexecd daemon cannot allocate a structure.\
\
Enter your request again. If the problem persists, refer to your system\
manual for more information.\
\
|
25535	Address translation failed in sqlexecd daemon.\
\
Enter your request again. If the problem persists, refer to your system\
manual for more information.\
\
|
25537	The sqlexecd daemon cannot connect to network.\
\
Check that you correctly installed your TCP/IP or StarGROUP network.\
Check for malfunctions in the network.\
\
|
25543	You specified an unknown service name or protocol.\
\
Examine the /etc/services file to verify that the requested service\
name exists. Also check that the /etc/services file specifies the\
correct protocol and/or port number.\
\
|
25544	The sqlexecd daemon cannot find a host structure.\
\
Check that you requested a valid database server name. Examine the /etc/hosts\
file to verify that you correctly defined the requested database server name,\
client address, and host names.\
\
|
29061	EDA warning (EDA_warning).\
\
The SQL statement has executed successfully, but the EDA client or\
server issued a warning. The EDA_warning field contains the warning\
information.\
\
The format of the EDA_warning field is the same as for the EDA_Error\
field that is described for error message -29060.\
\
|
32700	Cannot find license file.\
\
The program cannot open the license file. It first tries to open the\
file that the user specified in LM_LICENSE_FILE. If you have not set\
this environment variable, the program tries to open the license file\
in the default location $INFORMIXDIR/etc/ifmxld.dat. If you intend to\
use LM_LICENSE_FILE, check that you have set your license-file pathname\
correctly in that file.\
\
|
32701	Invalid license file syntax.\
\
This error occurs if the feature name, daemon name, or server name\
exceeds the maximum length allowed, or if the feature line is\
incomplete. If you have edited the license file after installation,\
check that you did not make a mistake. The maximum length for the\
server name is 32 characters. The feature name, daemon name, and\
feature lines are generated automatically during installation.\
\
|
25545	The sqlexecd daemon cannot advertise the specified service name.\
\
You are starting the sqlexecd daemon on a system that is running\
portable IBM Informix OnLine for NetWare with IPX/SPX as the network\
protocol, but the daemon is unable to advertise the service name for\
the database server on the NetWare network. It is possible that\
another sqlexecd daemon is already using the same service name, a\
recently stopped sqlexecd daemon with the same service name was unable\
to de-advertise its service, or the database server is down.\
\
The service name of each database server must be unique across the\
entire NetWare network. The default service name is sqlexec. If\
another sqlexecd daemon or database server on the network already uses\
the name, use a different service name to start the sqlexecd daemon.\
You can explicitly specify a service name as a parameter in the\
sqlexecd command line.\
\
If you are restarting a recently terminated sqlexecd daemon, the\
previous sqlexecd probably has not finished de-advertising or was\
unable to de-advertise the service name. When you terminate an sqlexecd\
daemon, use the TERM signal (15) only (that is, kill -15 pid or kill\
pid). If you do not terminate a service properly, depending on your\
database server configuration, it might take about three minutes for a\
terminated service to be de-advertised automatically.\
\
|
32702	Cannot connect to a license daemon server.\
\
If you edited the license file after installation, check that you did\
not make a mistake. This error occurs if the daemon name specified in\
the license-file feature line does not match the vendor-daemon name or\
if the attempt to connect the vendor daemon on all server nodes was\
unsuccessful. Check that the daemons on all license servers are still\
running and that the network is working properly.\
\
|
32703	Licensed number of users already reached. Check the daemon log.\
\
Check the network-licensing activities by using lmstat or by checking\
the license-daemon log file to decide whether you need to purchase more\
user capacity from IBM.\
\
|
32704	No such feature exists.\
\
The feature could not be found in the license file. Be sure that the\
license file contains the feature line for the product that you are\
trying to use and that the product is properly licensed.\
\
|
32705	No TCP/IP license service exists.\
\
Check the license file in use to ensure that the TCP/IP port number on\
the server line or lines is valid. If the TCP/IP port number is not\
valid, modify the license file to use a valid one.\
\
|
32706	No socket connection to license manager server.\
\
This error indicates that an internal error occurred during sending or\
receiving of the message. Note all observed behavior and any other\
error message. Check with the system administrator to ensure that the\
system is functioning properly.\
\
|
32707	Encryption code in license file is inconsistent.\
\
This error indicates that the code in a license-file line does not\
match the other data in the license file. This error usually occurs\
when all the software components are not built with the same encryption\
code. Check create_license.c, ls_vendor.c, and your application code\
carefully to make sure that they have the same vendor code. Do not\
modify the encryption code in the license file after it has been\
generated during installation.\
\
|
32708	Invalid host.\
\
This error occurs when the host ID specified in the license file does\
not match the node on which the software is running.\
\
|
32709	Feature has expired.\
\
The present date exceeds the expiration date of the feature in the\
license file. Decide if you want to change from an evaluation version\
to a regular version of this IBM Informix product and contact IBM for\
the procedure that you need.\
\
|
32710	Invalid date format in license file.\
\
Check that the date field in the license file is in the format\
dd-mmm-yyyy where dd is two digits for the day, mmm is three letters\
for the month, and yyyy is four digits for the year. The installation\
procedure generates these dates. If you did not modify the license file\
on those fields, report this problem, along with the output of the\
license file, to Technical Support at tsmail@us.ibm.com.\
\
|
32711	Invalid returned data from license daemon server.\
\
Be sure that no other services use the port numbers on the server\
lines. Check with your system administrator to ensure that the network\
is functioning properly. Check the license-daemon-server log for all\
error messages.\
\
|
32712	No server lines in license file.\
\
No server line exists in the license file. All nonzero license-count\
features need at least one server line.\
\
|
32713	Cannot find SERVER hostname in network database.\
\
Check all relevant system files, such as /etc/hosts, to ensure that the\
server host name is known across the network.\
\
|
32714	Cannot read data from license daemon server.\
\
Be sure that the daemons in all license servers are running. Check the\
daemon log for any error message.\
\
|
32715	Cannot write data to license daemon server.\
\
Check with your system administrator to ensure that the network is\
functioning properly. Also check the daemon log for other error\
messages.\
\
|
32716	License daemon server does not support this feature.\
\
The feature has expired or has not yet started, or the version of the\
product you are attempting to use is not the licensed version. Check\
that the license files in both the license-daemon servers and the\
computer that is running this IBM Informix licensed product are set up\
properly.\
\
|
32717	License daemon server busy (no majority).\
\
The license-daemon server is busy establishing a quorum of server nodes\
so that licensing can start. Retry this operation later.\
\
|
32718	License file does not support this version.\
\
Be sure that the version of the product that you are attempting to use\
is licensed. Check the license file to ensure that the version of the\
desired product on the feature line is the same as or later than the\
version that you want to use.\
\
|
32719	Feature checkin failure detected at license daemon server.\
\
The check-in request did not receive a proper reply from the vendor\
daemon. (The license might still be considered in use.) Check the\
daemon log output to see if there are any more error messages. If the\
error recurs, note all circumstances and contact \
Technical Support at tsmail@us.ibm.com.\
\
|
32720	License daemon server temporarily busy (new server connecting).\
\
The vendor daemon is busy establishing a quorum condition. New requests\
from clients are deferred during this period. Retry this operation\
later.\
\
|
32721	License daemon server does not support this version of this feature.\
\
The version that you are attempting to use is more recent than the\
version for which you are licensed. Check the feature line in the\
license file to ensure that the version of the desired product is the\
same as or later than the version that you are trying to use.\
\
|
32722	Request for more licenses than this feature supports.\
\
A checkout request was made for more licenses than are supported in the\
license file. Be sure that you did not make a change to the license\
checkout request to check out more licenses than it is capable of\
handling. Check out only one license for each request.\
\
|
32723	Cannot read license file.\
\
Be sure that the license file has the correct read permission.\
\
|
32724	Bad encryption handshake with daemon.\
\
The client performs an encryption handshake operation with the daemon\
before any licensing operations can occur. This handshake operation\
failed. Check with the system administrator to ensure that the system\
and the network are working properly. If the error recurs, note\
all circumstances and contact Technical Support tsmail@us.ibm.com.\
\
|
32725	Feature database corrupted in daemon.\
\
The runtime-feature data structures of the daemon are corrupt. This\
internal daemon error indicates that a serious problem exists. If the\
error recurs, note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
32726	Cannot allocate dynamic memory.\
\
The malloc() call failed to return sufficient memory. This error can\
occur while the system is reading the features from the license file\
(especially if the user has set an extremely long LM_LICENSE_FILE path).\
Check with your system administrator to ensure that the system is working\
properly.\
\
|
32727	Feature was never checked out.\
\
This message provides information to the user. It is not an error.\
\
|
32728	Clock setting check not available in daemon.\
\
This message provides information to the user. It is not an error.\
\
|
32766	Unknown error message number.\
\
The program that you have started cannot locate the Informix error\
message file. The INFORMIXDIR environment variable is probably not set\
properly. INFORMIXDIR points to the directory that contains the msg\
directory where message files are stored.\
\
|
32788	Dbspaces added to a mirrored Dbslice must be mirrored.\
\
The database administrator attempted to add dbspaces to an existing\
mirrored dbslice by using the ALTER DBSLICE ADD DBSPACE command\
without the MIRROR clause for each chunk.\
\
Reissue the ALTER DBSLICE ADD DBSPACE command with the MIRROR clause\
for each chunk.\
\
|
32789	Dbspaces added to a non-mirrored Dbslice must not be mirrored.\
\
The database administrator attempted to add dbspaces to an existing\
unmirrored dbslice by using the ALTER DBSLICE ADD DBSPACE command\
with at least one MIRROR clause for a chunk.\
\
Reissue the ALTER DBSLICE ADD DBSPACE command without the MIRROR clause\
for each chunk.\
\
|
32792	Coservers successfully blocked.\
\
The EBR BLOCK command completed successfully.\
\
|
32793	Coservers successfully unblocked.\
\
The EBR UNBLOCK command completed successfully.\
\
|
33987	External Space successfully created.\
\
The onspaces command that you used to create the external space was\
successful.\
\
|
33988	External space creation failed.\
\
The database server could not add the external space. Check the error\
returned with this failure.\
\
|
33989	External Space successfully dropped.\
\
The onspaces command that you used to drop the external space was\
successful.\
\
|
33990	External space drop fails.\
\
An attempt to drop the external space failed. Check the error\
associated with this failure.\
\
|
33991	External Space reference count not zero. Drop fails.\
\
The reference count for this external space was not 0. Check the\
reference count for the external space before you attempt to drop the\
space.\
\
|
33992	onmode: Unknown option argument.\
\
Unknown argument passed to onmode. Retry with the correct argument\
list.\
\
|
35201	SQLCODE used in SQL statement or declared as IN parameter.\
\
Remove SQLCODE from the SQL statement and/or remove IN from the\
parameter list. SQLCODE is an out parameter only.\
\
|
35202	SQLCODE parameter must be declared with type SQLCODE_TYPE.\
\
Only declare SQLCODE as an SQLCODE_TYPE parameter.\
\
|
35579	General Table Manager: Invalid argument.\
\
An invalid argument was passed while you were attempting to create a\
table. If this internal error recurs, note all circumstances\
and contact Technical Support at tsmail@us.ibm.com.\
\
|
35580	General Table Manager: No table allocated.\
\
The table has not been created or was deleted. If this internal error\
recurs, note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
35581	General Table Manager: No memory.\
\
Allocation of memory for a table or a table entry failed. Try to\
decrease the amount of memory that is used so some memory is freed for\
the table or table entry.\
\
|
35582	General Table Manager: Mutex cannot be created.\
\
Table or entry mutexes cannot be created. Try to decrease the amount of\
memory that is used so some memory is freed for the creation of the\
mutex.\
\
|
35583	General Table Manager: Duplicate keys not allowed.\
\
Table entries with the same key are not allowed. If this internal error\
recurs, note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
35584	General Table Manager: Table is full.\
\
Table is full and cannot be extended. If this internal error recurs,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
35585	General Table Manager: Entry is locked.\
\
Entry of a table is already locked (not yet used). If this internal\
error recurs, note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
35586	General Table Manager: Table is locked.\
\
Table is already locked (not yet used). If this internal error recurs,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
35587	General Table Manager: No entry.\
\
The required entry does not exist. If this internal error recurs,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
35588	General Table Manager: Invalid entry specification.\
\
The specification of an entry is invalid (for example, a NULL pointer).\
If this internal error recurs, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
35589	Running oninit without setuid causes use of descriptor limit.\
\
When you run the database server in developer mode (not suid to root), this\
message is a reminder that the number of file descriptors available to the\
database server is now limited by the shell from which the database server\
is initialized. File descriptors are needed for accessing chunks and\
making network connections. If the database server runs out of file\
descriptors, you need to choose one of the following solutions: limit the\
number of connections, limit the number of chunks used, or run as root.\
\
|
35590	You do not have the correct permission to run the database server\
without the -U option.\
\
The user was not root or informix and was not in the group informix.\
The only way to run the database server without permissions is with the -U\
option.\
\
|
35591	You must be the owner of this server to start it.\
\
You are attempting to boot the database server but are not the owner.\
Try again after you log in as the correct user.\
\
|
35592	You are not the owner of this server.\
\
You attempted to run onstat or onmode against a database server that you do\
not own.\
\
|
38002	Unknown event mnemonic or code event-mnemonic.\
\
An unknown event mnemonic or code was encountered in the audit trail.\
Check the event mnemonic or code, correct the command line or the load\
file, and try again.\
\
|
38005	Invalid path name, pathname (errcode = number).\
\
You have specified an invalid pathname. Check your entry and try\
again.\
\
|
38006	Invalid file name, filename (errcode = number).\
\
You have specified an invalid filename. Check your entry and try\
again.\
\
|
38007	No read permission on file filename.\
\
You do not have read permission for the specified file. Check the\
permissions and try again.\
\
|
38008	Cannot create file filename (errcode = number).\
\
The specified file cannot be created. Check the path and directory\
permissions and try again.\
\
|
38010	Internal error: Illegal use of set_msg (bounds exceeded).\
\
The set_msg function has exceeded the allocated storage in the error\
buffer. If the error recurs, note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
|
38047	Invalid serial number. Consult the installation instructions.\
\
You have entered a serial number that is not valid. Check the\
installation instructions for your product and try again.\
\
|
38053	Bad option usage: -u required for add.\
\
Your add command for onaudit is incomplete; you did not specify a user\
name. Check the usage information and try again.\
\
|
38054	Bad option usage: -u required for modify.\
\
Your modify command for onaudit is incomplete; you did not specify a\
user name. Check the usage information and try again.\
\
|
38055	Unknown option '-x'.\
\
Your command line for onaudit has incorrect or incomplete syntax. You\
have specified an unknown option. Check the usage information and try\
again.\
\
|
38060	Badly formatted mask/role/event definition at line line-number.\
\
The database server failed to parse the mask/role/event definition in a\
load file. Edit the load file and try again.\
\
|
38061	Actions must be the first argument to onaudit.\
\
Your command line for onaudit has incorrect or incomplete syntax.\
Actions must be the first argument. Check the usage information and try\
again.\
\
|
38062	Option without required argument found.\
\
Your command line for onaudit has incorrect or incomplete syntax. You\
have not included a required argument with an option. Check the usage\
information and try again.\
\
|
38064	No more than two events sets may be defined.\
\
Your command line for onaudit has incorrect or incomplete syntax. You\
have specified more than two event sets. Check the usage information\
and try again.\
\
|
38065	Unable to connect to shared memory.\
\
Confirm that the database server is up and try again.\
\
|
38083	Masks cannot be modified during a bulk operation (line line-number).\
\
The mask that was defined in a load file already exists. Either edit\
the load file or delete the existing definition.\
\
|
38084	OS mode auditing not supported for this platform.\
\
The -O option is not implemented for this platform. Delete it from the\
command and try again.\
\
|
38085	Cannot locate ONCONFIG file.\
\
The database server could not locate the $INFORMIXDIR/etc/$ONCONFIG\
file, and/or ADTPATH and/or DBSERVERNAME is not defined.\
\
|
38086	Badly formatted audit record found.\
\
The audit trail traversal contains a parsing error. Check the path and\
directory permissions and try again.\
\
|
38088	Failed to action user user-name -- error number occurred.\
\
This general onaudit failure message could indicate that a command is\
incorrect or incomplete, the database is inaccessible, or the user is\
not informix. Check the permissions, ID, and command-line syntax, and\
try again.\
\
|
38089	Failed to action -- error number occurred.\
\
This general onaudit failure message could indicate that a command is\
incorrect or incomplete, the database is inaccessible, or the user is\
not informix. Check the permissions, ID, and command-line syntax, and\
try again.\
\
|
38090	Skipped existing audit trail filename.\
\
The database server could not overwrite an existing audit-trail file.\
This message might appear when the database server comes up and\
ADTPATH holds old audit data. Remove all old audit trails.\
\
|
38091	Audit trail creation failed for filename.\
\
The database server could not open the next audit file because the call\
to aio_fopen() failed. Check that ADTPATH points to a valid directory\
to which the user or group informix can write.\
\
|
38092	Could not open next audit file.\
\
The database server could not open the next audit file because the call\
to aio_fopen() failed. Check that the ADTPATH points to a valid\
directory to which the user or group informix can write.\
\
|
38093	Informix level audit write failure (errcode = number).\
\
The database server could not write the current audit record to the\
audit-trail file. Check that ADTPATH points to a valid directory to\
which the user or group informix can write and that space is available.\
Also, check the directory and audit-trail file permissions.\
\
|
38094	string is invalid setting for ADTERR.\
\
The ONCONFIG file contains a bad parameter. Fix the ONCONFIG file so\
that the parameter is 0/1.\
\
|
38095	string is invalid setting for ADTMODE.\
\
The ONCONFIG file contains a bad parameter. Fix the ONCONFIG file so\
that the parameter is 0/1.\
\
|
43007	Data required to insert a row into table_name.\
\
An insert into this table cannot occur without the specified data.\
Verify that the required data exists before you attempt another insert\
in this table.\
\
|
43008	Failed to build WHERE clause for query.\
\
Attempt to build a WHERE clause for the specified query failed. Verify\
that the data needed to create the WHERE clause exists.\
\
|
43010	Missing data for table_name.\
\
Required data is missing. Verify that the data exists.\
\
|
43011	Updates to table_name primary key are not allowed.\
\
Updating the primary key for a table is not allowed. Delete the row and\
then insert a new row with the new primary key.\
\
|
43012	Unable to open connection to server.\
\
The database server is in an incorrect state. Bring the database server\
to the correct state. For a backup, the database server should be in\
online or quiescent mode. For a warm restore, the database server\
should be in online, quiescent, backup, or recovery mode. For a cold\
restore, the database server should be off-line. Use the onmode or\
oninit commands.\
\
|
43014	Unable to read ONCONFIG file parameters.\
\
The ONCONFIG file is inaccessible. It might be missing or have\
incorrect permission values. Verify that an ONCONFIG file exists and\
that its permissions are correct. For details, see your Administrator's\
Guide.\
\
|
43015	Unable to set INFORMIXSHMBASE.\
\
Unable to attach to shared memory. Contact your database system\
administrator.\
\
|
43018	Must be user root or informix.\
\
Only users root and informix and are allowed to execute ON-Bar. Log in\
as root or informix before you attempt the backup, restore, or database\
logging mode change.\
\
|
43036	User is not a member of the informix-admin group.\
\
Only users listed in the informix-admin group can execute ON-Bar. Ask\
your system administrator to add your user name to the informix-admin\
group.\
\
|
43039	Version version_number of the XBSA shared library is not compatible\
with version version_number of ON-Bar.\
\
Either IBM has not certified the XBSA shared library that the\
Storage Management Vendor provides, or an error occurred during\
installation of ON-Bar. Verify that ON-Bar was installed properly.\
Verify that the XBSA library is certified.\
\
|
43040	DB/BLOBspace dbspace_name/blobspace_name does not exist.\
\
Verify that the storage space exists in this database server.\
\
|
43043	Must restore logical logs from date_time or later.\
\
The user wants to stop the restore at a logical log that is too early.\
A storage-space backup occurred after the log that the user\
specified. Retry the restore up to the specified logical log or later.\
\
|
43047	Cannot warm restore-critical media: dbspace_name.\
\
The user wants to stop the restore at a logical log that is too early.\
A storage-space backup occurred after the log that the user\
specified. Retry the restore up to the specified logical log or later.\
\
|
71561	This command can be executed only by members of the informix-admin\
group.\
\
The account under which you are logged on might not be a member of the\
informix-admin group. Contact your Windows system administrator.\
\
|
71562	Use the -iy option to initialize the database server.\
\
The command-line option that was specified in the Control\
Panel->Services->Startup dialog box was -i. When the database\
server runs as a service, it does not prompt you for confirmation.\
\
If you are sure that you want to initialize the root dbspace\
completely, start the database server with the -iy option instead.\
\
|
71563	The database server cannot access INFORMIXDIRdbssodir or\
INFORMIXDIRaaodir.\
\
First, check access rights to path segments that lead to dbssodir and\
aaodir. If INFORMIXDIR 133844s on a network drive, make sure the oninit\
process privileges are not altered. In addition, make sure that the AAO\
and DBSSO group names in the following registry key are valid:\
\
HKEY_LOCAL_MACHINESOFTWAREInformixOnLineCurrentVersionSecurity\
\
|
71564	Warning: SYSTEM command not supported in SPL routines.\
\
Prior to Version 7.21, IBM Informix OnLine Dynamic Server for Windows NT\
did not support system commands in SPL routines (stored procedures).\
This feature was added in Version 7.21.\
\
Run the system command outside of the SPL routine.\
\
|
71565	The root dbspace is not large enough for the specified configuration.\
The actual size is xxx pages, and the required size is yyy pages.\
\
Try to free some space on the drive that contains the root dbspace and\
re-initialize the database server.\
\
|
71566	The value specified for TAPEDEV or LTAPEDEV in the ONCONFIG file\
is invalid.\
\
Specify a valid value for TAPEDEV and/or LTAPEDEV. For specific information\
about setting configuration parameters, see your administrator's guide. \
\
|
71567	The database server failed to start in Recovery Mode. Check Event\
Log for errors.\
\
Check the Event Log for errors from the database server and correct them.\
\
|
71568	oninit: DBSERVERNAME `servername' not found under SQLHOSTS key in\
the Registry.\
\
Add key into the registry. For more information, refer to your\
administrator's guide.\
\
|
71569	The database server failed to start in Recovery Mode.  Service\
already running.\
\
Check the registry settings for INFORMIXSERVER under the SQLHOSTS key.\
\
|
71570	System() command "<command-name>" in SPL routine cannot be\
executed because user "<username>" did not connect with a password.\
\
Log on again with a password and execute the SPL routine.\
\
|
71571	Insufficient buffer size for error message.\
\
The buffer size allocated for the error message is not sufficient. If\
the error recurs, note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
71572	System() command in SPL routine failed.\
\
Check the message log for more information.\
\
|
79511	Warning: DB_LOCALE environment variable does not match\
locale of the database.\
\
The dbaccess utility issues this message when you connect to a database\
that does not match the value of your $DB_LOCALE environment variable.\
For more information, see the section on performing code-set\
conversions in the IBM Informix GLS User's Guide.\
\
|
80622	Illegal DBSERVERNAME or DBSERVERALIAS:  <dbname> must\
begin with a letter.\
\
The onconfig file has a value for DBSERVERNAME or DBSERVERALIASES that does\
not begin with a letter.\
\
Edit the onconfig file. Make sure the DBSERVERNAME value and\
all DBSERVERALIASES values begin with a letter.\
\
|
-1	Not owner.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. Check the ownership and permissions of\
files and directories that are used in the current operation. Look for\
other operating-system error messages that might give more\
information.\
\
|
-2	No such file or directory.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. Look for other operating-system error\
messages that might give more information.\
\
|
-3	No such process.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. Look for other operating-system error\
messages that might give more information. If the error recurs,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-4	Interrupted system call.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. You might have pressed the interrupt\
key at a crucial moment, or the software might have generated an\
interrupt signal such as the UNIX command kill. Look for other\
operating-system error messages that might give more information. If\
the error recurs, note all circumstances and contact Technical Support\
at tsmail@us.ibm.com.\
\
|
-5	I/O error.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. Look for other operating-system error\
messages that might give more information. If the error recurs,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-6	No such device or address.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. You might have made an error when you\
configured the database software or in the REPORT TO clause of a\
report. Look for other operating-system error messages that might give\
more information.\
\
|
-7	Arg list too long.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. Look for other operating-system error\
messages that might give more information. If the error recurs,\
see the information about trapping errors in your Administrator's\
Guide or Reference to acquire additional diagnostics. Contact Technical \
Support at tsmail@us.ibm.com with the diagnostic information.\
\
|
-8	Exec format error.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. Look for other operating-system error\
messages that might give more information. If the error recurs,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-9	Bad file number.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. Look for other operating-system error\
messages that might give more information. If the error recurs,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-10	No children.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. Look for other operating-system error\
messages that might give more information. If the error recurs,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-11	No more processes.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. Look for other operating-system error\
messages that might give more information. If the error recurs,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
-12	Not enough core.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. Core probably refers to data space in\
memory that an operating-system function needed. Look for other\
operating-system error messages that might give more information.\
\
|
-13	Permission denied.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. This error code usually follows an\
attempt to execute a file that is not a program or shell script; it\
might reflect an error in a REPORT TO specification in a report. Look\
for other operating-system error messages that might give more\
information.\
\
|
-14	Bad address.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. Look for other operating-system error\
messages that might give more information. If the error recurs,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-15	Block device required.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. An error might exist in the\
configuration of the database software. That error might include an\
incorrect address in the chunk-device or tape-device parameters that\
were given to the database server. Look for other operating-system\
error messages that might give more information.\
\
|
-16	Mount device busy.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. Look for other operating-system error\
messages that might give more information. If the error recurs,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-17	File exists.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. This error may reflect an attempt in a\
REPORT TO specification to replace an existing file. Look for other\
operating-system error messages that might give more information.\
\
|
-18	Cross-device link.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-19	No such device.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. Look for other operating-system error\
messages that might give more information. If the error recurs,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-20	Not a directory.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. Look for other operating-system error\
messages that might give more information. Some database servers store\
databases as directories that are named database.dbs. If you place a\
file (not a directory) with the .dbs suffix in your DBPATH, this error\
might result.\
\
|
-21	Is a directory.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. A file-type operation has been\
directed to a directory. Some database servers store tables, indexes,\
and lock files as files with particular suffixes in the database\
directory. If a directory replaced such a file, this error might\
result. Look for other operating-system error messages that might give\
more information.\
\
|
-22	Invalid argument.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. Look for other operating-system error\
messages that might give more information. If the error recurs,\
refer to information about trapping errors in your Administrator's\
Guide or Reference to acquire additional diagnostics. Contact Technical\
Support at tsmail@us.ibm.com with the diagnostic information.\
\
|
-23	File table overflow.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. Look for other operating-system error\
messages that might give more information. If the error recurs,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
-24	Too many open files.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. This error probably reflects a limit\
that was configured in your operating system. Look for other\
operating-system error messages that might give more information.\
\
|
-25	Not a typewriter.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. An error might exist in the\
configuration of the database software. That error might include an\
incorrect address in the log-device parameter given to the database\
server. Look for other operating-system error messages that might give\
more information. If the error recurs, note all circumstances\
and contact Technical Support at tsmail@us.ibm.com.\
\
|
-26	Text file busy.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the current operation requires the\
use of a text file (such as the input file to LOAD or to a PRINT FILE\
statement in a report), retry the operation later. Look for other\
operating-system error messages that might give more information.\
\
|
-27	File too large.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. Check the documentation for your\
operating system to find out what too large might mean in the context\
of the current operation.\
\
|
-28	No space left on device.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. Either a database table or an ASCII\
output file has probably filled the available disk space. Look for\
other operating-system error messages that might give more\
information.\
\
|
-29	Illegal seek.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. Look for other operating-system error\
messages that might give more information, such as the device on which\
the error occurred. If the error recurs, note all circumstances\
and contact Technical Support at tsmail@us.ibm.com.\
\
|
-30	Read-only file system.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. An entire file system (a disk or disk\
partition) has been made read-only. Contact your system administrator\
to find out why.\
\
|
-31	Too many links.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. Look for other operating-system error\
messages that might give more information, especially which file or\
files are involved. If the error recurs, note all circumstances\
and contact Technical Support at tsmail@us.ibm.com.\
\
|
-32	Broken pipe.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. A pipe is a data path between two\
processes; a pipe is broken if one of the processes has unexpectedly\
quit while the other is waiting for data. Look for other\
operating-system error messages that might give more information,\
especially which processes were involved. If the error recurs,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-33	Argument too large.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-34	Result too large.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-35	Operation would block.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-36	Operation now in progress.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-37	Operation already in progress.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-38	Socket operation on non-socket.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. Look for other operating-system error\
messages that might give more information, particularly the operation\
in question and the processes that are involved. If the error recurs,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-39	Destination address required.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-40	Message too long.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-41	Protocol wrong type for socket.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-42	Option not supported by protocol.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-43	Protocol not supported.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-44	Socket type not supported.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-45	Operation not supported on socket.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstance, and contact Technical Support at tsmail@us.ibm.com.\
\
|
-46	Protocol family not supported.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-47	Address family not supported by protocol family.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-48	Address already in use.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-49	Can't assign requested address.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-50	Network is down.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If you are attempting to use\
IBM Informix STAR or IBM Informix NET, contact your system administrator to\
find out when the network will be backed up. If not, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-51	Network is unreachable.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If you are attempting to use\
IBM Informix STAR or IBM Informix NET, contact your system administrator to\
find out what the network problem is. If not, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-52	Network dropped connection on reset.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If you are attempting to use\
IBM Informix STAR or IBM Informix NET, contact your system administrator to\
report a network problem. If not, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-53	Software caused connection abort.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If you are attempting to use\
IBM Informix STAR or IBM Informix NET, contact your system administrator to\
report a network problem. If not, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-54	Connection reset by peer.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If you are attempting to use\
IBM Informix STAR or IBM Informix NET, contact your system administrator to\
report a network problem. If not, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-55	No buffer space available.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. Look for other operating-system error\
messages that might give more information, especially which file or \
files are involved. If the error recurs, note all circumstances\
and contact Technical Support at tsmail@us.ibm.com.\
\
-56	Socket is already connected.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-57	Socket is not connected.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-58	Can't send after socket shutdown.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-59	Too many references: can't splice.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-60	Connection timed out.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If you are attempting to use\
IBM Informix STAR or IBM Informix NET, contact your system administrator to\
report a network problem. If not, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-61	Connection refused.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If you are attempting to use\
IBM Informix STAR or IBM Informix NET, contact your system administrator to\
report a network problem. If not, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-62	Too many levels of symbolic links.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. The database server does not normally\
use symbolic links. Look for other operating-system error messages that\
might give more information, particularly which file or files were\
being accessed.\
\
|
-63	File name too long.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. An error might exist in the coding of\
a REPORT TO statement of a report. If not, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-64	Host is down.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If you are attempting to use\
IBM Informix STAR or IBM Informix NET, contact your system administrator to\
report a network problem. If not, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-65	Host is unreachable.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If you are attempting to use\
IBM Informix STAR or IBM Informix NET, contact your system administrator to\
report a network problem. If not, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-66	Directory not empty.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. Look for other operating-system error\
messages that might give more information, particularly what directory\
was being removed. If the error recurs, note all circumstances\
and contact Technical Support at tsmail@us.ibm.com.\
\
|
-67	Too many processes.\
\
Your application was unable to start a database server process or was\
unable to create a process that was needed for some subordinate\
function such as a REPORT TO pipe or a network-access program. This\
error probably reflects a limit configured in your operating system.\
Look for other operating-system error messages that might give more\
information.\
\
|
-68	Too many users.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. This error probably reflects a limit\
configured in your operating system. Look for other operating-system\
error messages that might give more information.\
\
|
-69	Disc quota exceeded.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. A disk-quota limit is probably\
configured in your operating system. Look for other operating-system\
error messages that might give more information, particularly the disk\
involved. Contact your system administrator to inquire about more\
liberal quotas.\
\
|
-70	Stale NFS file handle.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. An error exists in a file server on a\
networked file system. Although IBM Informix database servers do not\
support database access to NFS-mounted file systems, this error can\
occur when the database server executable files or other files that are\
related to the database server are located on an NFS-mounted disk. (In\
other words, the INFORMIXDIR environment variable names an NFS-mounted\
disk.) The error is usually transient, reflecting a crash and\
subsequent restart of the file server. Remount the file system to your\
workstation and rerun your application.\
\
|
-71	Too many levels of remote in path.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-72	Not a stream device.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. Look for other operating-system error\
messages that might give more information, particularly which device is\
involved. If the error recurs, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-73	Timer expired.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-74	Out of stream resources.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-75	No message of desired type.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-76	Not a data message.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Supportat tsmail@us.ibm.com.\
\
|
-77	Identifier removed.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-78	Deadlock situation detected/avoided.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
Under AIX, this code means connection timed out.\
\
|
-79	No record locks available.\
\
An operating-system error code with the meaning shown was unexpectedly\
returned to the database server. This implementation of the IBM Informix\
database server probably uses kernel locking, the use of the\
operating-system facilities to lock rows of tables. The capacity of the\
operating-system lock table has been exceeded. Contact your system\
administrator and inquire about configuring the operating system to\
support more locks. Also examine your database application to see if it\
can use fewer locks by updating fewer rows in each transaction or by\
locking whole tables instead of rows.\
\
|
-100	ISAM error: duplicate value for a record with unique key.\
\
A row that was to be inserted or updated has a key value that already\
exists in its index. For C-ISAM programs, a duplicate value was\
presented in the last call to iswrite, isrewrite, isrewcurr, or\
isaddindex. Review the program logic and the input data. For SQL\
products, a duplicate key value was used in the last INSERT or UPDATE.\
\
|
-101	ISAM error: file is not open.\
\
The program attempted to use an unopened file, table, partition,\
tablespace, or other storage object, or one of these whose access\
mode did not support the requested operation (for example, an\
attempt to write to a file that was opened in read-only mode).\
\
If the error recurs, refer to the information on trapping errors in\
your Administrator's Guide or Reference for additional diagnostics.\
Contact Technical Support at tsmail@us.ibm.com with the diagnostic information.\
\
|
-102	ISAM error: illegal argument to ISAM function.\
\
A parameter that was presented to one of the C-ISAM functions is\
outside the range of acceptable values. For C-ISAM programs, review the\
parameters that were used in this function call, and compare them to\
the documentation for the function. If the error recurs, refer\
to the information on trapping errors in your Administrator's\
Guide or Reference to acquire additional diagnostics. Contact Technical\
Support at tsmail@us.ibm.com with the diagnostic information.\
\
|
-103	ISAM error: illegal key descriptor (too many parts or too long).\
\
The ISAM processor has been given an invalid key descriptor. For C-ISAM\
programs, review the key descriptor. Each key descriptor has a maximum\
of 8 parts and 120 characters. If the error recurs, refer to the\
information on trapping errors in your Administrator's Guide or Reference to\
Appendix entitled "Trapping Errors" in your Administrator's Guide or Reference \
to acquire additional diagnostics. Contact Technical Support at \
tsmail@us.ibm.com with the diagnostic information.\
\
|
-104	ISAM error: too many files open.\
\
The ISAM processor has reached its limit of open files. For C-ISAM\
programs, review the program logic and change it so that fewer files\
are open concurrently. Use isclose to close unneeded files. For SQL\
products, this query is too complex; it uses too many tables\
concurrently. Perform the query in steps, and use temporary tables.\
\
|
-105	ISAM error: bad ISAM file format.\
\
The contents of an ISAM file (table or index) have been corrupted. For\
C-ISAM, if you used transaction logging, you can use the isrecover\
program to recover the file. Otherwise, re-create the file or restore\
it from backup. For SQL products, use the bcheck or secheck utility to\
get more information on the problem and possibly correct it (use\
the oncheck utility (or tbcheck with IBM Informix OnLine versions 6.0 and\
earlier). If the utility cannot recover the table or index, you will\
have to re-create or restore it.\
\
|
-106	ISAM error: non-exclusive access.\
\
The ISAM processor has been asked to add or drop an index but it does\
not have exclusive access. For C-ISAM programs, the file must be opened\
with exclusive access before you perform this operation. Review the\
program logic, and make sure that it opens this file by passing the\
ISEXCLLOCK flag to isopen. For SQL products, the database server\
returns this error when an exclusive lock is required on a table. For\
example, this error appears when a second user tries to alter a table\
that the first user has locked.\
Or the ISAM processor could not obtain access to the requested table or \
index because it has been opened exclusively by another user.\
This condition is normally transient, retry operation after some delay.  \
\
|
-107	ISAM error: record is locked.\
\
Another user request has locked the record that you requested or the\
file (table) that contains it. This condition is normally transient. A\
program can recover by rolling back the current transaction, waiting a\
short time, and re-executing the operation. For interactive SQL, redo\
the operation. For C-ISAM programs, review the program logic and make\
sure that it can handle this case, which is a normal event in\
multiprogramming systems. You can obtain exclusive access to a table by\
passing the ISEXCLLOCK flag to isopen. For SQL programs, review the\
program logic and make sure that it can handle this case, which is a\
normal event in multiprogramming systems. The simplest way to handle\
this error is to use the statement SET LOCK MODE TO WAIT. For bulk\
updates, see the LOCK TABLE statement and the EXCLUSIVE clause of the\
DATABASE statement.\
\
|
-108	ISAM error: key already exists.\
\
The ISAM processor has been asked to create an index that already\
exists. For C-ISAM programs, review the program logic. The program must\
delete this existing index before it defines another. If the error\
recurs, note all circumstances and contact Technical\
Support at tsmail@us.ibm.com.\
\
|
-109	ISAM error: the key is the file's primary key.\
\
The ISAM processor has been asked to delete the primary key index. For\
C-ISAM programs, the isdelindex call cannot delete the primary key. If\
the error recurs, note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-110	ISAM error: end or beginning of the file.\
\
Reading rows sequentially, forward or backward, the ISAM processor has\
reached one end of the file (table). For C-ISAM programs, this message\
is the normal signal for end of file. Use a different retrieval mode of\
isread to reposition the file. For SQL products, see the SQL error\
message or return code.\
\
|
-111	ISAM error: no record found.\
\
The ISAM processor cannot locate the requested record. For C-ISAM\
programs, no record was found with the requested index value or record\
number, depending on the retrieval mode in use. Make sure that the\
correct index is in use. For SQL products, see the SQL error message or\
return code. Probably no row was found for this query.\
\
|
-112	ISAM error: there is no current record.\
\
The ISAM processor has been asked to return the current record, but\
none has been established. For C-ISAM programs, review the program\
logic. Before the program uses the ISCURR retrieval mode, it must use\
another retrieval mode, such as ISFIRST, to establish a current record.\
If the error recurs, note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
|
-114	ISAM error: the file name is too long.\
\
The ISAM processor has been asked to open or create a file with a\
filename longer than 10 characters. For C-ISAM programs, this length\
exceeds the maximum for the product. Choose a shorter filename. If the\
error recurs, note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
|
-115	ISAM error: cannot create lock file.\
\
The ISAM processor has been asked to access a file or row using\
locking. Because this operating system uses files for locking, ISAM\
must create a tablename.lok file. When it tried to do so, it received\
an error code from the operating system. The disk might be full, or\
your account might not have write permission in the relevant directory.\
Look for operating-system error messages that might give more\
information.\
\
|
-113	ISAM error: the file is locked.\
\
Another user request has opened the file (table) that was requested in\
exclusive mode. In systems that use files for locking, a tablename.lok file\
exists. Possibly such a file was left behind when another program terminated\
abnormally. If you are sure that is the case, you can release the lock by\
emptying that file. Lock files are not used in many systems, and they are\
never used with IBM Informix Dynamic Server or IBM Informix OnLine Dynamic Server.\
\
This error occurs with IBM Informix Dynamic Server or IBM Informix OnLine Dynamic\
Server when a user attempts to access a table that has been locked.\
\
For C-ISAM programs, rerun the program after the file is unlocked. For\
SQL products, tables are locked explicitly using the LOCK TABLE statement\
and implicitly during the execution of the CREATE INDEX or ALTER TABLE\
statement. Rerun the program or query when the table is unlocked.\
\
If you get this error (-113) when using a transaction isolation mode of\
REPEATABLE READ or SERIALIZABLE, and if your query did not use an index\
(and therefore had to use a sequential scan of the entire table), the cause\
of the error might be that another user had either an exclusive lock or a\
promotable lock on at least one row in the table. If you are in REPEATABLE\
READ or SERIALIZABLE mode and your query requires a scan (search) of every\
single record in the table to find all the records that meet the conditions\
in the WHERE clause, then the engine will need to lock every record in the\
table to maintain the repeatability of the read. In practice, rather than\
locking every single record, the engine will try to lock the entire table.\
But if there are any exclusive locks, or even promotable locks, on any row\
in the table, then the engine will not be able to get a shared lock on the\
entire table, and the query will fail.\
\
|
-116	ISAM error: cannot allocate memory.\
\
The ISAM processor needed to allocate memory for data storage but was\
unable to do so. A problem may exist in the operating system; look for\
operating-system error messages that might give more information. One\
cause of this error might be selecting a row that contains large BYTE\
or TEXT columns into a temporary table or as part of an INSERT or\
UPDATE. In some releases, an entire row that includes BLOB values is\
buffered in memory. For C-ISAM programs, review the program to look for\
ways that it can use less memory. For SQL products, simplify the\
program, form, or report if possible.\
\
|
-117	ISAM error: bad custom collating sequence.\
\
No current IBM Informix product displays this message. If the error recurs,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-118	ISAM error: cannot read log record.\
\
The ISAM processor is trying to roll back a transaction or recover a\
file but has encountered an error while reading the transaction log.\
Look for operating-system error messages that might give more\
information. Use the dblog or selog utility to get more information\
about the problem. If the file (table) cannot be recovered, you will\
have to re-create it or restore it from backup.\
\
|
-119	ISAM error: bad log record.\
\
The ISAM processor is trying to roll back a transaction or recover a\
file but has encountered bad data in a transaction log record. The\
dblog or selog utility can be used to get more information about the\
problem. If the file (table) cannot be recovered, you will have to\
re-create it or restore it from backup.\
\
|
-120	ISAM error: cannot open log file.\
\
The ISAM processor is trying to open the transaction log file but has\
received an error from the operating system. Look for operating-system\
error messages that might give more information. For C-ISAM programs,\
review the parameter passed to islogopen. Make sure that it specifies\
the correct filename of an existing, writable log file and that it\
includes a path if the file is not in the current directory. For SQL\
products, the START DATABASE statement establishes the transaction log\
file. Make sure that the log file still exists in the same directory\
location as when START DATABASE was issued and that your account has\
write access to it.\
\
|
-121	ISAM error: cannot write log record.\
\
The ISAM processor is trying to add a record to the transaction log but\
has received an error from the operating system. The disk might be\
full. Look for operating-system error messages that might give more\
information. The transaction-log file can grow quite large. To reduce\
its size, you must do two things. First, make a backup copy of the data\
file (for C-ISAM) or all database files (for SQL). Second, make the\
transaction-log file an empty file. If you perform these steps\
routinely, you can control the size of the log file.\
\
|
-122	ISAM error: transaction not available.\
\
The ISAM processor has been asked to mark the start or end of a\
transaction, but transaction logging is not in effect. For C-ISAM\
programs, this file was not opened with logging. Review the calls to\
isopen, and make sure that the ISTRANS parameter is included. For SQL\
products, this database does not support transaction logging. If you\
are using the database server, have the database server administrator\
enable logging for this database. Otherwise, use the START DATABASE\
statement to begin transaction logging. In all cases, logging should\
only start immediately after the database has been fully backed up.\
\
|
-123	ISAM error: no shared memory.\
\
This implementation of ISAM uses shared memory; however, the\
shared-memory partition has not been established. Contact the system\
administrator or the person who installed the product.\
\
|
-124	ISAM error: no begin work yet.\
\
The ISAM processor has been asked to mark the end of a transaction, but\
no transaction has been started. For C-ISAM programs, review the\
program logic to make sure that it calls isbegin before it calls\
iscommit or isrollback. For SQL products, make sure that you execute\
BEGIN WORK before COMMIT WORK or ROLLBACK WORK.\
\
|
-125	ISAM error: can't use nfs.\
\
The ISAM processor has been asked to open a file that is located on a\
disk attached to another computer and that is accessed using the\
Network File System (NFS). This action is not supported. Database files\
must be on disks that are physically attached to the computer on which\
the ISAM processor is running. To use a database on a different\
computer, you must install the IBM Informix STAR or IBM Informix NET networking\
software. Then an application on this computer can communicate with a\
database server that is running on the computer to which the disks are\
attached.\
\
|
-126	ISAM error: bad row id.\
\
The ISAM processor was asked to retrieve a row by its physical location\
but could not find a row at that location.\
\
For C-ISAM programs, if you are using access by record number, review the\
number stored in isrecnum; it is invalid. Otherwise, the current index\
might be damaged; run the bcheck or secheck utility.\
\
For SQL products, the index has been damaged. Run the oncheck utility to\
check and repair the index if you are using IBM Informix Dynamic Server,\
IBM Informix Universal Server, or IBM Informix OnLine Dynamic Server. Run bcheck or\
secheck if you are using the IBM Informix SE database server. Run tbcheck if you\
are using the IBM Informix OnLine database server.\
\
|
-127	ISAM error: no primary key.\
\
The ISAM processor was called for a function that requires a unique\
primary-key index, but no such index exists for this file. For C-ISAM\
programs, review the design of the data file; it was created with a\
zero-part primary index (that is, for retrieval by record-number\
sequence). If that is not the case, the index might be damaged; run the\
bcheck or secheck utility. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-128	ISAM error: no logging.\
\
The ISAM processor was called for a function that requires a\
transaction log, but none exists for this file. For C-ISAM programs,\
review the creation of the data file. Before the program uses functions\
such as isbegin, it must set up a log using islogopen. For SQL\
products, this database does not support transaction logging. If you\
are using the database server, have the database server administrator\
enable logging for this database. Otherwise, use the START DATABASE\
statement to begin transaction logging. In all cases, start logging\
only immediately after the database has been fully backed up.\
\
|
-129	ISAM error: too many users.\
\
This implementation of ISAM uses shared memory, and it has reached the\
maximum number of concurrent users for which the shared memory was\
configured. You might need to increase the value of the USERTHREADS and\
TRANSACTIONS configuration parameters in the ONCONFIG file. If the\
problem recurs, contact the system administrator or the person who\
installed the product.\
\
The word users can be misleading; the limit is on the number of\
concurrent application programs using the database server. It is\
possible for one user to start multiple applications at the same time.\
For example, when a user starts the IBM Informix 4GL Programmer's\
Environment, it opens a session with the database server. When that\
user issues a command to compile a 4GL program, the 4GL compiler starts\
and also opens a session with the database server. During a compile,\
this user has two sessions running.\
\
|
-130	ISAM error: no such dbspace.\
\
This code indicates one of two problems. The most likely problem is\
that this operation specifies a dbspace by name (for example, in the IN\
clause of a CREATE TABLE statement or in the DBSPACETEMP environment\
variable setting), but that name has not been defined. You can run the\
tbstat or onstat utility with the -d option to see the names of defined\
dbspaces. Ask the database server administrator about creating a new dbspace.\
\
If the operation does not explicitly name a dbspace, or if the name is\
correct, the problem might be more serious. The error might reflect\
corruption of reserved pages in the root dbspace. Use the tbcheck or\
oncheck utility with the -cr option to check for this condition.\
\
|
-131	ISAM error: no free disk space.\
\
Not enough contiguous free disk space is available to complete the\
current operation. For C-ISAM programs, if transaction logging is in\
use, roll back the current transaction. Make some disk space available,\
and run the program again. For SQL products, roll back the current\
transaction, if possible. Contact the system administrator about\
acquiring more disk space for databases.\
\
|
-132	ISAM error: rowsize too big.\
\
The limit on a single row is the disk page size that the database\
server supports.\
\
Define the table differently, so that each row is shorter. Consider\
splitting the table into two or more tables or using more compact data\
types.\
\
|
-133	ISAM error: audit trail exists.\
\
The ISAM processor has been asked to operate on a file in a way that is\
incompatible with an audit trail, yet an audit trail exists for the\
file. For C-ISAM programs, you cannot call iscluster while an audit\
trail exists. First call isaudit with the AUDSTOP mode. For SQL\
products, you cannot create a clustered index on a table while it has\
an audit trail. First use the DROP AUDIT statement to drop the audit\
trail.\
\
|
-134	ISAM error: no more locks.\
\
The ISAM processor needs to lock a row or an index page, but no locks\
are available. The number of locks that an operation requires depends\
primarily on the number of rows that a single transaction modifies. You\
can reduce the number of locks that an operation needs by doing less in\
each transaction or by locking entire tables instead of locking rows.\
Depending on the implementation that you are using, the number of locks\
that is available is configured in one of three places: the\
operating-system kernel, the shared-memory segment, or the database\
server. Consult your database server administrator about making more\
locks available.\
\
|
-135	ISAM error: tblspace does not exist.\
\
This error might indicate corruption of control information in the root\
dbspace, a serious problem that might require restoring the system from\
archive. In the short term, roll back the current transaction, and\
terminate the application. Then the database server administrator\
should run the tbcheck, oncheck, or onutil utility.\
\
|
-137	ISAM error: chunk table overflow.\
\
The database system administrator sees this error message. The database\
server is configured to handle a certain number of disk chunks. The\
limit has been reached, so a chunk could not be added. Increase the\
CHUNKS parameter of the ONCONFIG file, and initialize shared memory.\
\
|
-138	ISAM error: dbspace table overflow.\
\
The database server administrator sees this error message. The database\
server is configured to handle a certain number of dbspaces. The limit\
has been reached, so a dbspace could not be added. Increase the\
DBSPACES parameter of the ONCONFIG file, and initialize shared memory.\
\
|
-136	ISAM error: no more extents.\
\
The database server needs to add an extent to a table but cannot\
do so. Either not enough disk space is available in the dbspace, or the\
table has been given the maximum number of extents that is allowed. The\
database server administrator can determine the cause as follows:\
\
    1.  Determine the tblspace number for the table. It is the value in\
	the partnum column of the systables table for this table.\
\
    2.  Convert the tblspace number to hexadecimal and extract its\
	most-significant 2 digits (the high-order byte). This chunk\
	number indicates where the table resides.\
\
    3.  Use the tbstat or onstat utility -t option to find out disk\
	usage for this table. Note particularly the values reported for\
	npages (disk pages available), nused (disk pages used), and\
	nextns (number of extents).\
\
If nused is less than npages, and nextns is large (over 200), the table\
has too many extents. The upper limit of extents per table is between 200\
and 50. The limit varies with the table definition and the\
disk-page size in use. Reallocate the table using fewer, larger\
extents. Unload the table data to a flat file. Drop the table.\
Re-create the table, specifying a first-extent size sufficient to hold\
all its current data and a next-extent size between one-fourth and\
one-sixteenth its current size. Then reload the data into the table.\
\
If nextns is small or the difference between npages and nused is less\
than the size of the next-extent size for the table, not enough disk\
space is available in the dbspace where the table resides. Use the\
chunk number from step 2 and the ON-Monitor or ON-Monitor Chunks\
display to determine the dbspace, then add a new chunk to that\
dbspace.\
\
|
-139	ISAM error: logfile table overflow.\
\
The database server administrator sees this error. The database server is\
configured to handle a certain number of logical logs. The limit has\
been reached, so a log could not be added. Increase the LOGSMAX\
parameter of the ONCONFIG file and initialize shared memory.\
\
|
-140	ISAM error: operation illegal on a DR secondary.\
\
A DR secondary server is meant for read-only operations. Any kind of write\
operation to a nontemporary dbspace is not allowed. For example, you cannot\
create a table in a regular dbspace, and you cannot do an insert, update, or\
delete operation on a table in a regular dbspace.\
\
Review your application logic and rewrite it to remove any operations that\
would write to a nontemporary dbspace.\
\
|
-140	ISAM error: global section disallowing access.\
\
This error occurs only in the VMS operating system. An internal error\
occurred during initialization of shared memory. If the error recurs, note\
all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-141	ISAM error: tblspace table overflow.\
\
The database server is configured to handle a certain number of\
open tblspaces (which correspond approximately to tables). This limit\
has been reached, so a table that is used in this statement could not\
be opened. In the short term, roll back the current transaction and\
then re-execute it when fewer concurrent operations are going on. To\
prevent recurrence, the database server administrator should configure \
the system to handle more open tblspaces. The TBLSPACES parameter of the\
ONCONFIG file sets the limit. The ovrtable count in the\
ON-Monitor or ON-Monitor Profile display reflects the number of times\
this error occurs.\
\
|
-142	ISAM error: overflow of tblspace page.\
\
An internal error (probably obsolete) occurred. If the error recurs,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-144	ISAM error: key value locked.\
\
The current operation inserts a row with a certain primary key value or\
updates a row with a certain primary key value, but a transaction that\
has not yet been committed has deleted that key value from the index.\
This error occurs only when the lock mode is set to NOT WAIT. Treat it\
the same as error -107 (record is locked). Roll back the current\
transaction, and re-execute it after a delay. Then, if the other\
transaction was committed, the lock no longer exists. If it was rolled\
back, the key exists, and this operation receives a duplicate-key\
error.\
\
|
-143	ISAM error: deadlock detected.\
\
The database server has detected an impending deadlock between\
your request and other, concurrent user requests. Each user request is\
waiting for a resource (a row or disk page) that is held by another\
request in the chain; if your requested operation went forward, the\
chain would be closed and all requests would be deadlocked. In the\
short term, treat this error the same as -107 (record is locked). Roll\
back the current transaction, and re-execute it after a delay. To\
prevent recurrence, review the design of the applications that use the\
same tables and execute concurrently. Various design strategies can\
minimize the probability of deadlock.\
\
When IBM Informix STAR is active, and your application is using tables in\
both this system and another system, deadlock detection is no longer\
deterministic but probabilistic, based on the duration of a delay\
waiting for resources in another system. The database server administrator \
can set the length of the delay after which deadlock is assumed.\
\
|
-145	ISAM error: system does not have disk mirroring.\
\
The database server administrator sees this error. This database server\
has not been initialized to support disk mirroring. Before you can add\
a mirror chunk, you must reconfigure the database server to support\
mirroring.\
\
|
-146	ISAM error: the other copy of this disk is currently disabled or\
non-existent.\
\
The database server administrator sees this error. You must bring the other\
chunk of this mirror pair to online status before you can take this\
chunk off line.\
\
|
-147	ISAM error: archive in progress.\
\
The database server administrator sees this error. The action that you have\
requested cannot be carried out while an archive is being made. For\
example, you cannot add a log or a mirror during archiving. Cancel the\
archive or wait until it is complete, and then reissue the command.\
\
|
-148	ISAM error: dbspace is not empty.\
\
The database server administrator sees this error. You cannot remove a dbspace\
until all tables that are in it have been dropped. To find the names of\
remaining tables, use the tbcheck or oncheck utility with the -pe\
option; its report lists tables by chunk within dbspaces.\
\
|
-149	ISAM error: IBM Informix OnLine daemon is no longer running.\
\
Your application was in communication with the database server, but the\
database server is no longer running. Your current transaction will be\
rolled back when the database server goes through fast recovery as it\
next starts up. Terminate the application, and contact the database\
server administrator to find out what happened and when the database\
server will be restarted.\
\
|
-150	The limits of the IBM Informix Demo Version have been exceeded.\
\
You are using a demonstration version of the database server. This\
version has severe limits on the number of tables and the size of the\
tables that it can manage. The current operation causes it to exceed\
one of those limits. Contact your IBM representative about buying\
the production version of the software.\
\
|
-151	ISAM error: Illegal value in varchar length field.\
\
This internal error occurs when the leading byte in a VARCHAR column on\
disk indicates a VARCHAR length greater than the column was defined to\
hold when the column was created.\
\
If the error recurs, refer to the information on trapping errors in your\
Administrator's Guide or Reference. To acquire additional diagnostics,\
contact Technical Support at tsmail@us.ibm.com with the diagnostic information.\
\
|
-152	ISAM error: Illegal message type received from remote process.\
\
This internal error should not occur. Note all the details about the\
network software in use and the version level of the database servers\
in this and the other host system. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-153	ISAM error: not in ISMANULOCK mode.\
\
The ISAM processor has been asked to lock or unlock the current file\
(table), but the file was not opened in the appropriate mode. For\
C-ISAM programs, review the uses of isopen, and make sure that the\
ISMANULOCK flag is passed when the program opens a table for manual\
locking. If the error recurs, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-154	ISAM error: Lock Timeout Expired.\
\
This network operation has been suspended, awaiting a response from\
another database server, for the maximum duration allowed. The local\
database server assumes that a distributed deadlock exists and that\
this user request is awaiting a resource that was locked by a user in a\
different system, which is awaiting a resource that this user owns.\
Roll back the current transaction, and retry it after a delay. If this\
error occurs frequently, ask the database server administrator to adjust\
the length of the deadlock time-out interval.\
\
This code is also returned when an explicit wait time limit expires;\
that is, if you have SET LOCK MODE TO WAIT 3, and your request is\
queued for more than 3 seconds for a lock, the operation ends with this\
ISAM error code.\
\
|
-155	ISAM error: Primary and Mirror chunks are bad.\
\
The primary chunk (and the mirror chunk, if one exists) are unusable.\
Roll back the current transaction and terminate the application.\
Contact the database server administrator. New disk chunks must be \
defined, and then the system must be restored.\
\
|
-157	ISAM error: Interrupted ISAM call.\
\
An interrupt that was detected from client process has terminated the\
operation. Restart the operation.\
\
|
-158	ISAM error: Operation disallowed on SMI pseudo table.\
\
You have attempted an SQL operation that is not supported on System\
Monitoring Interface (SMI) pseudo tables. Try another operation.\
\
|
-159	ISAM error: Collation sequence invalid.\
\
You are attempting to use a collation sequence that is either not\
supported or does not match the sequence originally used to create the\
ISAM file. Use islanginfo() to determine the language of the ISAM\
file.\
\
|
-160	ISAM error: only one TEXT or BYTE field may be open at any time.\
\
This internal error should not occur. The database server has called\
the isbopen function twice in a row. If the error recurs,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-161	ISAM error: no TEXT or BYTE field is open.\
\
This internal error should not occur. The database server has called a\
TEXT or BYTE function without first calling isbopen. If the error\
recurs, note all circumstances and contact Technical\
Support at tsmail@us.ibm.com.\
\
|
-162	ISAM error: Storage space does not exist.\
\
The most likely cause of this error is that the current statement\
attempts to define a BYTE or TEXT column using the clause IN blobspace,\
but no storage space of that name has been defined. However, if the\
storage space was correctly spelled and should exist, a reserved page in\
the root dbspace might have been corrupted. In that case, the database\
server administrator should run tbcheck -cr, oncheck -cr, or onutil to\
check the situation. If the statement makes no reference to TEXT or\
BYTE columns, possibly the root dbspace is full or corrupted; contact \
the database server administrator for further help.\
\
|
-163	ISAM error: begin and end page stamps are different.\
\
The database server is reporting evidence of corruption of the\
database. Each disk page has time stamps at each end that should be\
identical when the page is read from disk. This test of data integrity\
has failed, indicating either that a disk page was not fully written to\
disk or that one has been partially overwritten on disk or in memory.\
In any case, you should roll back the current transaction and terminate\
the application. Then notify the database server administrator, who should \
run the tbcheck, oncheck, or onutil utility to get more information about \
the failure.\
\
|
-164	ISAM error: TEXT or BYTE stamp is incorrect.\
\
This operation has returned an invalid BYTE or TEXT value. Possibly the\
data pages have been corrupted. Roll back the current transaction. Have\
the database server administrator use tbcheck -D, oncheck -D, or\
onutil to get more information about the problem.\
\
If the program is operating with Dirty Read or Committed Read\
isolation, this code might indicate that another process or thread has\
deleted the BYTE or TEXT value and its pages have been partly\
reallocated to an unrelated value. A program using Dirty Read isolation\
can read rows that have been deleted if the deletion has not yet been\
committed. If the deletion is committed while the program is reading a\
BYTE or TEXT value, and if the space allocated to the value is reused\
for some other program, this error code might be returned.\
\
When a program uses Committed Read isolation, it does not see a row\
that has been marked for deletion; however, no lock is placed on a row\
that is not read for update. BYTE or TEXT data is read in a second\
step, after the row has been fetched. During this lengthy step, it is\
possible for another program to delete the row and commit the deletion\
and for the storage space to be reused. To determine if this has occurred,\
the program should stop processing the BYTE or TEXT value and reread\
the row. If the program can no longer read the other fields in the\
row, the row has been deleted. If the program can still read the row,\
the storage space is corrupted.\
\
|
-165	ISAM error: TEXT or BYTE column does not exist.\
\
This internal error should not occur. The database server has called\
the isbcreate function for a table column that is not defined as BYTE\
or TEXT. If the error recurs, note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
|
-166	ISAM error: Storage space is full.\
\
This operation attempts to insert or update the value of a BYTE or TEXT\
column, but not enough space is available in the storage space in which\
that column is stored. Roll back the current transaction, and terminate\
the application. Then ask the database server administrator to add a\
chunk of disk space to this storage space.\
\
When BYTE and TEXT values are deleted or replaced, the pages that they\
occupy in the storage space do not become available for reuse until the\
logical log in which that transaction appears has been freed. A logical\
log has been freed if the log is backed up to tape and all transactions\
in the log are closed.\
\
|
-167	ISAM error: Storage-space size is not multiple of PAGESIZE.\
\
The database server administrator sees this error. When you define a\
storage space, you must specify a page size that is an integral multiple of\
the system page size. The system page size is set in the Parameters\
screen when the database server is first initialized.\
\
|
-168	ISAM error: archive is blocking storage space allocation.\
\
Allocation of disk pages in a storage space is frozen while an online\
archive is being made. Therefore, pages that contain TEXT or BYTE data\
at the time that the archive began are not freed and overwritten by new\
pages before they can be written to the archive tape. As soon as all\
the used pages in the chunk are archived, allocation in that chunk can\
resume. Normal row data can go on changing while the archive is being\
made because changed dbspace pages can be written, or rewritten, on the\
tape at any point.\
\
|
-169	ISAM error: Pages for TEXT or BYTE data can't be allocated from\
a chunk until chunk add is logged.\
\
When a storage space containing TEXT or BYTE data has been extended by\
adding a new chunk, no pages can be allocated until the log record\
showing the addition of the chunk has been logged. If this rule were\
not enforced, certain anomalies could occur during recovery. You do not\
have to wait until the log is full; you can run the tbmode or onmode\
utility with the -l option to force a switch to the next log.\
\
|
-170	ISAM error: illegal use of a storage space for TEXT or BYTE data.\
\
You attempted to add a log to a storage space for TEXT or BYTE data.\
You can add logs only to dbspaces.\
\
|
-171	ISAM error: ISAM file format change detected.\
\
A program that uses a particular locking method or index-node size has\
attempted to access an ISAM file that was created using a different\
locking method or index-node size.\
\
If you are migrating files from a platform that uses another index-node\
size, you must run the bcheck or secheck utility with the -s option\
against all of the ISAM files (.dat and .idx) to resize the index\
nodes.\
\
For IBM Informix SE, if you are migrating applications between platforms\
that use different locking methods, you must set the environment\
variable RESETLOCK to convert ISAM files as you access them. You can\
access all files for a given database by running UPDATE STATISTICS in\
that database, if time permits.\
\
For C-ISAM applications, if you are migrating applications between\
platforms that use different locking methods, you must set the\
environment variable RESETLOCK to convert C-ISAM files as you access\
them.\
\
|
-172	ISAM error: Unexpected internal error.\
\
You encountered an unanticipated internal event. Consult the online.log\
to see if the diagnostics preserved any additional information\
regarding this event. If the error recurs, refer to your Administrator's\
Guide to acquire additional diagnostics. Contact Technical Support at tsmail@us.ibm.com\
with the diagnostic information.\
\
|
-173	ISAM error: An error has occurred during logical log back up.\
\
This generic message indicates that the logical-log backup has failed.\
The SQL API also contains useful error text that is associated with\
this error.\
\
|
-174	ISAM error: An error has occurred during archive back up.\
\
This generic message indicates that the archive backup has failed. The\
SQL API also contains useful error text that is associated with this\
error.\
\
|
-175	ISAM error: An error has occurred during physical restore.\
\
This generic message indicates that the physical restore has failed.\
The SQL API also contains useful error text that is associated with\
this error.\
\
|
-176	ISAM error: An error has occurred during logical restore.\
\
This generic error indicates that the logical restore has failed. The\
SQL API also contains useful error text that is associated with this\
error.\
\
|
-178	ISAM error: Database is locked; pending change to logging mode.\
\
A request has been made to change the logging status of a database.\
Until a level-0 archive is done for all the storage spaces that the\
database uses, access to the database is blocked.\
\
|
-179	ISAM error: No free disk space for sort.\
\
While performing a sort, the database server did not find enough\
contiguous free disk space to create necessary temporary files. You\
might have insufficient disk space and need to make more disk space\
available before you run the program again. You might have made an\
error when you specified the names of temporary dbspaces in DBSPACETEMP\
or directory names in PSORT_DBTEMP. Check the spelling of your\
temporary space names as specified in DBSPACETEMP. If you specified\
multiple temporary dbspaces, check that you used colons (:) or commas\
(,) as delimiters.\
\
|
-181	ISAM error: No Optical Subsystem connection.\
\
The Optical subsystem is not present. This message usually means that\
you requested an Optical operation on a database server that\
is being used without the Optical subsystem or IBM Informix OnLine/Optical.\
\
|
-182	ISAM error: Duplicate optical BLOBSpace name.\
\
A storage space for TEXT or BYTE data has been defined with the same\
name as an Optical family name.\
\
-186	ISAM error: Cannot open partition. Online create/drop index in progress.\
\
The current operation is trying to open a partition on which a online \
create/drop index is in progress. Wait a short time, and try again. \
\
-187	ISAM error: User Defined Routine execution failed.\
\
A user-defined routine (UDR) failed to execute properly. Typically, this\
occurs when the UDR raises an error.\
\
For more specific information, see the message log.\
\
|
-188	ISAM error: Cannot add transaction logging on a DR primary with DR on.\
\
Transaction logging cannot be added to a database on the primary\
database server of a data replication (DR) pair while DR is in use.\
DR has to be turned off for transaction logging to be added.\
\
Adding transaction logging to a database after turning DR off requires\
bringing up the DR pair again through a level-0 archive on the primary\
database server and its physical restore on the secondary database\
server. Restarting DR is necessary to avoid DR failures due to\
inconsistencies between the primary and secondary database servers,\
caused by the addition of transaction logging.\
\
|
-190	ISAM error: Transaction table overflow.\
\
No more slots are available in the transaction table. To see this\
table, run onstat with the -x option.\
\
|
-191	ISAM error: No such chunk.\
\
The chunk that was specified to be dropped does not exist.\
\
|
-192	ISAM error: Cannot drop first chunk.\
\
The first chunk of a storage space is never a candidate to be\
dropped. Select a different chunk.\
\
|
-193	ISAM error: Chunk is busy.\
\
Logical recovery cannot roll forward a chunk add because the chunk\
already exists. This error results when the chunk is dropped from a\
storage space, or the space is dropped, and the chunk is reused\
for another storage space without a level-0 backup performed first.\
\
|
-194	ISAM error: Chunk not empty.\
\
A chunk is not empty and therefore cannot be dropped.\
\
|
-196	ISAM error: Operation not allowed in temporary dbspace.\
\
An operation was executed on a temporary dbspace that required\
functionality that temporary dbspaces do not provide (most likely\
logging). Use a nontemporary dbspace for this operation.\
\
|
-197	ISAM error: Partition recently appended to; can't open for\
write or logging.\
\
If this internal error recurs, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-199	ISAM error: Dbspace is full.\
\
The dbspace is full. If you are adding a logical log through onparams, there\
is not enough space in the dbspace for a log of the size specified. This\
error also occurs if you attempt to create a temporary table with log\
(the default log setting for temporary tables) when the DBSPACETEMP variable\
in ONCONFIG is set to TEMP or NOTCRITICAL. \
\
To add the logical log, either add one or more chunks to the dbspace or\
specify a smaller log size.\
\
To create temporary tables, either set DBSPACETEMP to ALL or create\
temporary tables with no log.\
\
-199	Smart Disk Error.\
\
An error has occurred with the Smart Disk system. For more information,\
see the accompanying message.\
\
|
-200	Identifier is too long.\
\
An SQL identifier exceeded the maximum number of characters. In IBM Informix\
Dynamic Server 9.2x or later, the maximum length for identifiers in SQL\
statements is 128 characters. In other Informix database servers, the\
maximum length for identifiers in SQL statements is 18 characters.\
\
Check that no identifier in the statement is longer than the maximum\
length and that no punctuation error, such as a missing space or comma,\
combines two identifiers into one.\
\
|
-198	Cannot alter table. Too many in-place alters of the table in progress.\
\
Informix limits the number of outstanding in-place ALTER TABLE requests\
to 255. A 256th in-place alter of a table was requested before the\
completion of the first in-place alter. Completion means that all rows\
of the table in the first in-place alter have been physically altered.\
\
To recover from this error, you must take one of the following steps:\
\
    *   Wait until the first in-place alter is complete, and issue\
	another in-place ALTER TABLE statement.\
\
    *   Change the format of the ALTER TABLE statement to request an\
	alter that does not add columns to the end of the table. Such a\
	statement will use the older algorithm instead of the in-place\
	alter algorithm.\
\
    *   Perform an update of each row in the table to force the\
	outstanding alters to complete. Because rows are only modified\
	to the latest schema as they are updated, the only way to force\
	an in-place alter to complete physically is to update each row\
	in the table. To accomplish this result, use a dummy update in\
	which a column in the table is set to its own value. The dummy\
	update forces the row to be updated to the latest schema in the\
	process without actually changing column values. Rows are\
	always altered to the latest schema, so a single pass through\
	the table that updates all rows will complete all outstanding\
	in-place alters.\
\
|
-201	A syntax error has occurred.\
\
This general error message indicates mistakes in the form of an SQL\
statement. Look for missing or extra punctuation (such as missing or\
extra commas, omission of parentheses around a subquery, and so on),\
keywords misspelled (such as VALEUS for VALUES), keywords misused (such\
as SET in an INSERT statement or INTO in a subquery), keywords out of\
sequence (such as a condition of "value IS NOT" instead of "NOT value\
IS"), or a reserved word used as an identifier.\
\
Database servers that provide full NIST compliance do not reserve any\
words; queries that work with these database servers might fail and\
return error -201 when they are used with earlier versions of IBM Informix\
database servers.\
\
The cause of this error might be an attempt to use round-robin syntax with\
CREATE INDEX or ALTER FRAGMENT INIT on an index. You cannot use round-robin\
indexes.\
\
|
-202	An illegal character has been found in the statement.\
\
A character that cannot be interpreted as part of an SQL statement is\
embedded in this statement. If a program constructed the statement, the\
character might be a nonprinting control character. Make sure the\
statement contains only printable ASCII characters, and reexecute it.\
\
|
-203	An illegal integer has been found in the statement.\
\
Where an integer value is expected, an unacceptable numeric constant\
appears. Inspect the statement and look for numbers that should be\
integers but that contain a decimal point or the letter e or that are\
larger than 2,147,483,647 ((2 to the 31st power) - 1).\
\
|
-204	An illegal floating point number has been found in the statement.\
\
A numeric constant that is punctuated like a floating-point number\
(with a decimal point and/or an exponent starting with e) is\
unacceptable. Possibly the exponent is larger than can be processed.\
\
|
-205	Cannot use ROWID for views with aggregates, group by,\
multiple tables, or derived expressions.\
\
The keyword ROWID stands for a virtual column that exists only in\
simple tables. This message refers to the ROWID of a table that is\
actually a view that is based on a selection involving aggregate\
functions, grouping, a join of two or more tables, or derived expressions.\
Such query products do not have ROWID columns. Therefore this view does not have\
a ROWID, even though it appears to be a table. In order to use ROWID in\
a query, you have to apply the query to the tables that underlie the\
view.\
\
|
-206	The specified table <table-name> is not in the database.\
\
The database server cannot find a table or view specified in the statement.\
The table or view might have been renamed or dropped from the database.\
\
You might also get this message if you omit the keyword "TYPE" when you are\
trying to grant USAGE privileges on a user-defined type. For example, the\
following GRANT statement is correct:\
\
   GRANT USAGE ON TYPE person_row_type TO usr2;\
\
The following GRANT statement, however, generates error -206:\
\
   GRANT USAGE ON person_row_type TO usr2;\
\
Check the names of tables and views in the statement or check for omission\
of the keyword "TYPE" in a GRANT statement. If the names are spelled as you\
intended and "TYPE" is not missing, check that you are using the database\
you want. To find the names of all tables in the database, query the \
systables table. To find the names of all views, query the sysviews table.\
\
|
-207	Cannot update cursor declared on more than one table.\
\
The cursor that is used in this statement was declared FOR UPDATE but\
with a SELECT statement that joins two or more tables. This action is\
not supported; the database server does not know how to distribute\
update values across multiple tables. If you declared the SELECT\
statement with the cursor, modify either it or the FOR UPDATE clause.\
If a program constructed the SELECT statement and associated it with\
the cursor dynamically, the program should inform its user not to use a\
multitable SELECT statement in this application. (This message occurs\
only with Version 4.0 or earlier.)\
\
|
-207	Cannot declare a SELECT INTO statement FOR UPDATE.\
\
When you declare a cursor, you may not use both the INTO clause and the\
FOR UPDATE clause. To use this cursor to update selected rows, omit the\
INTO clause. Instead, use an INTO clause on the FETCH statement (or in\
4GL, the FOREACH statement).\
\
|
-208	Memory allocation failed during query processing.\
\
The database server needed to allocate data-space memory in order to\
process the query, but none was available. This error may reflect a\
hardware limit, an operating-system configuration limit, or a temporary\
shortage of space.\
\
Try the query again after a delay. If it still fails, consult your\
system administrator. If possible, revise your query to join fewer\
tables, to order or group on fewer columns, or to operate in two or\
more separate statements. On DOS systems, exit to the operating-system\
command line, free some disk space or reduce the complexity of your\
program, and resubmit the program.\
\
In versions later than 5.01, only this error message informs you that\
the database server is unable to allocate memory.\
\
|
-209	Incompatible database format.\
\
An obsolete version of the database software built this database.\
Convert the database to work with the current software. Use the\
dbupdate utility. You will have to run it before you use the data.\
(This message is not current since Version 4.0.)\
\
|
-210	Explicit path name too long.\
\
This statement contains a file pathname that exceeds the maximum length\
of 64 characters. Inspect the statement to make sure that the pathname\
is that long. It is possible a punctuation error caused other\
parts of the statement to be included in the pathname. If this is not\
the case, either relocate the file or rename some directories along the \
path with shorter names.\
\
|
-212	Cannot add index.\
\
This statement attempts to add an index, either explicitly with CREATE\
INDEX or implicitly as part of processing a SELECT on multiple\
unindexed tables. In any case, some error prevents the index from being\
created. For more information, check the accompanying ISAM error code.\
Insufficient disk space is a common cause of this problem.\
\
|
-211	Cannot read system catalog <error-text>.\
\
The database server refers to the tables of the system catalog while it\
processes most statements. When it cannot read one of these important\
tables, a serious error results. Check the accompanying ISAM error code\
for more information. The effect of the error depends on the statement\
that is being executed and the particular table, as follows:\
\
    *   CREATE TABLE statement, systabauth not read; the table is\
	created, but PUBLIC is not granted authorization as it normally\
	is.\
\
    *   DROP TABLE statement, systables not read; no action taken.\
\
    *   DROP TABLE statement, sysviews not read; the table is dropped\
	but any views that depended on the table were not automatically\
	dropped.\
\
    *   DROP VIEW statement, sysviews not read; no action taken.\
\
    *   DROP INDEX statement, sysindexes or systables not read; no\
	action taken.\
\
    *   DROP SYNONYM statement, systables or syssynonyms not read; no\
	action taken.\
\
    *   DROP DATABASE statement, systables not read; no action taken.\
\
    *   START DATABASE statement, systables not read; no action taken.\
\
    *   DATABASE statement, systables or sysusers not read; the\
	database was not selected (no current database; for subsequent\
	operations, see error -349).\
\
Other statements might be partially complete before the error is detected.\
Roll back the current transaction and then investigate the cause of the\
error. Use the oncheck utility (secheck with IBM Informix SE or tbcheck with\
IBM Informix OnLine) to check and repair indexes. If necessary, restore the\
database from backup and logical-log tapes.\
\
|
-213	Statement interrupted by user.\
\
The database server received an interrupt signal from the user,\
probably because the user pressed the interrupt key (usually Delete or\
Control-C). The statement ended early. A program should roll back the\
current transaction and terminate gracefully. If the statement could\
modify a table, an interactive user should execute the ROLLBACK WORK\
statement to remove any partial modifications.\
\
|
-214	Cannot remove file for table table-name.\
\
The database server cannot completely remove the table. Check the\
accompanying ISAM error code for more information. Problems with\
operating-system file permissions, read-only files, or hardware might\
cause this error.\
\
|
-215	Cannot open file for table table-name.\
\
The database server cannot open the operating-system file or files in\
which the table is stored. Check the accompanying ISAM error code for\
more information. Problems with operating-system file permissions,\
insufficient memory, or hardware might cause this error.\
\
|
-216	Cannot remove index.\
\
The database server cannot completely drop an index. Check the\
accompanying ISAM error code for more information. Problems with\
operating-system file permissions, read-only files, or hardware\
might cause this error.\
\
|
-216	Cannot remove ISAM index on file.\
\
The database server cannot completely drop an index. Check the\
accompanying ISAM error code for more information. Problems with\
operating-system file permissions, read-only files, or hardware might\
cause this error.\
\
|
-217	Column column-name not found in any table in the query\
(or SLV is undefined).\
\
The name appears in the select list or WHERE clause of this query but is\
not defined in a table and does not appear as a statement local variable\
(SLV) definition. Check that the column name or SLV name and the names of\
the selected tables are spelled as you intended.\
\
If all names are spelled correctly, you are not using the right tables,\
the database has been changed, or you have not defined the SLV. If the\
name not found is a reference to a column, that column might have been\
renamed or dropped. If the name not found represents an SLV and you\
defined the SLV in the statement, make sure that the SLV definition\
appears before all other references to that SLV name.\
\
This error message can also appear during the execution of an ALTER TABLE\
statement when the engine tries to update views that depend on the table.\
\
|
-218	Synonym synonym-name not found.\
\
The synonym is not defined in this database. Check that the name is\
spelled as you intended. Check that you are using the right database.\
If so, the synonym was probably dropped. Possibly it was dropped\
automatically when the table for which it stood was dropped. To display\
all defined synonyms, query systables as follows:\
\
SELECT tabname FROM systables WHERE tabtype = 's'\
\
|
-219	Wildcard matching may not be used with non-character types.\
\
The WHERE clause in this statement includes a test of a noncharacter\
column using the LIKE or MATCHES keyword and the special characters\
that stand for multiple characters (for example, asterisk and question\
mark in MATCHES and percent and underscore with LIKE). Use these tests\
only with columns that are defined as CHAR or VARCHAR in the database.\
No automatic data conversion is provided. Check that the columns in the\
WHERE clause are as you intended. If so, the definition of the table\
has probably changed.\
\
|
-220	There is no FROM clause in the query.\
\
Every SELECT statement must include a FROM clause to name the table or\
tables that it queries. Check that FROM was spelled and that no extra\
semicolon ends the statement prematurely. To select only a constant, or\
to select the only value of a function that is unrelated to any table\
(such as USER or TODAY), you nevertheless have to name a table. You can\
select a known row from a system catalog, as in this example.\
\
SELECT 'today is', TODAY, 'and I am', USER FROM systables\
        WHERE tabid = 100\
\
The tabid value of the first user-defined table in a database is always\
100, so this query always returns exactly one row if any tables are\
defined. (Version 4.1 and later produce syntax error -201 when the\
FROM clause is missing.)\
\
|
-220	Cannot begin savepoint.\
\
Version 4.1 and later can detect this internal error. If the error\
recurs, note all circumstances and contact Technical Support at\
tsmail@us.ibm.com.\
\
|
-221	Cannot build temporary file for new table table-name.\
\
The database server cannot create a temporary disk file. The file\
should be created in the directory specified by the DBTEMP environment\
variable. If DBTEMP is not defined, the database server searches by\
default in the root directory for a subdirectory named tmp in which to\
create the temporary disk file. Check the accompanying ISAM error code,\
and look for operating-system error messages that might give more\
information. Possibly your account does not have write permission in\
that directory, or the disk might be full. Since Version 5.01,\
IBM Informix SE database server uses the DBTEMP environment variable, but\
IBM Informix Dynamic Server and IBM Informix OnLine Dynamic Server do not.\
\
|
-222	Cannot write to temporary file for new table table-name.\
\
The database server created a temporary disk file but received an error\
while it attempted to write into the file. Check the accompanying ISAM\
error code, and look for operating-system messages that might give more\
information. On UNIX systems, the file should have been created in the\
directory specified by the DBTEMP environment variable (/tmp by\
default); on DOS systems, the file should be in the current directory.\
Possibly that disk is full, or a hardware error occurred. Since Version\
5.01, the IBM Informix SE database server uses the DBTEMP environment\
variable, but IBM Informix Dynamic Server and IBM Informix OnLine Dynamic\
Server do not.\
\
|
-223	Duplicate table name table-name in the FROM clause.\
\
The table name appears twice in the list that follows the word FROM.\
Review the statement to see if you intended to name some other table\
the second time. If you intended to join a table to itself, use a table\
alias for the second and subsequent instances of the table. The\
following example shows one way to find customers with the same last\
name:\
\
SELECT main.lname, main.customer_num, sub.customer_num FROM customer\
main, customer sub WHERE main.lname = sub.lname AND main.rowid !=\
sub.rowid\
\
When you use table aliases (the words main and sub in the example), the\
table may be selected from two or more times.\
\
|
-224	Cannot open transaction log file.\
\
The database server cannot open the file in which transaction-log\
entries are made. No transactions can start until this file is\
repaired. (In an ANSI-compliant database, nothing can be done; in other\
databases, only queries can be made.) Report this problem to the\
database server administrator. For IBM Informix SE database servers, check\
the accompanying ISAM error code, and look for operating-system error\
messages that might give more information. A START DATABASE statement\
specifies the path to the log file. If the file has been deleted, you\
can re-create it as an empty file. If the path has changed, you can\
issue a new START DATABASE statement to redefine it.\
\
|
-225	Cannot create file for system catalog table-name.\
\
The database server is trying to create one of the tables for the\
system catalog, probably as part of a CREATE DATABASE statement. A\
problem with the host operating system prevents it. Check the\
accompanying ISAM error code for more information, and look for\
operating-system error messages. A shortage of disk space or\
operating-system file-access permission problems probably caused this\
error.\
\
|
-226	Cannot create index for system catalog table-name.\
\
The database server is trying to create one of the tables for the\
system catalog, probably as part of a CREATE DATABASE statement. It\
created the table, but a problem with the host operating system\
prevents it from making an index. Check the accompanying ISAM error\
code for more information, and look for operating-system error\
messages. Insufficient disk space probably caused this error.\
\
|
-227	DDL operations on ROWID prohibited.\
\
This statement attempts to change the column named ROWID. That column\
is a part of every table except a fragmented table. You can select it\
with a SELECT statement and compare it in a WHERE clause, but you\
cannot alter it with a DDL statement.\
\
|
-228	UPDATE or INSERT on ROWID prohibited.\
\
This statement names the column ROWID in the list of columns for\
insertion or update. The row ID is an intrinsic property that cannot be\
modified. You can select it in a SELECT statement and compare it in a\
WHERE clause, but you cannot modify its contents.\
\
|
-229	Could not open or create a temporary file.\
\
The database server cannot create a temporary disk file. The file\
should be created in the directory that the DBTEMP environment variable\
specifies (or /tmp by default on UNIX systems). Check the accompanying\
ISAM error code and look for operating-system error messages that\
might give more information. Possibly your account does not have write\
permission in that directory, or the disk is full. Since Version 5.01,\
the IBM Informix SE database server uses the DBTEMP environment variable,\
but IBM Informix Dynamic Server and IBM Informix OnLine Dynamic Server do not.\
\
On a UNIX system, try increasing the maximum number of open files\
(NFILES parameter on some systems) to approximately 400.\
\
|
-230	Could not read a temporary file.\
\
The database server created a temporary file in the directory specified\
by the DBTEMP environment variable (or /tmp by default on UNIX systems)\
but encountered an error when it tried to read the file back. Check the\
accompanying ISAM error code, and look for operating-system error\
messages that might give more information. Possibly a hardware failure\
occurred, or possibly another user erased the temporary file\
accidentally. Since Version 5.01, the IBM Informix  SE database server uses\
the DBTEMP environment variable, but IBM Informix Dynamic Server and\
IBM Informix OnLine Dynamic Server do not.\
\
|
-231	Cannot perform aggregate function with distinct on expression.\
\
This statement selects DISTINCT (expression) within an aggregate\
function. This action is not supported. Select the DISTINCT value and\
other columns into a temporary table; then select ALL from that table\
applying the aggregate function.\
\
|
-232	A SERIAL column column-name may not be updated.\
\
You cannot alter the contents of a column with the SERIAL data type in\
the UPDATE statement, even when the updating value is zero. (You can\
specify a value of zero for a serial column when you use the INSERT\
statement; the database server ignores the zero and inserts a generated\
number.) Revise the statement so that only nonserial columns are\
updated.\
\
|
-233	Cannot read record that is locked by another user.\
\
Another user has locked a row that this statement selects. If you\
executed the statement interactively, you can do one of two things. You\
can wait a short time and reenter the statement. Or you can execute the\
statement SET LOCK MODE TO WAIT, after which you will rarely see this\
message again.\
\
In a program, you should roll back the current transaction, wait for an\
interval of random length, and rerun the transaction. If you run the\
transaction with a LOCK MODE of WAIT, you can reduce the frequency of\
this error. But it can still arise in some cases, such as when deadlock\
is detected. An ISAM error code (-107, -113, -134, -143, -144, or\
-154) usually accompanies this error, and a program might need to make\
a different response to each of these errors.\
\
|
-234	Cannot insert into virtual column column-name.\
\
This INSERT statement is directed to a view, not to a real table, and\
one of the columns that is defined in the view is actually the value of\
an expression. Insertions and updates are not allowed on views that\
have such columns. Apply the INSERT to the real table on which the\
view is based.\
\
|
-235	Character column size is too big.\
\
This statement specifies a width for a column of CHAR data type that is\
greater than 32,767, or a width for a VARCHAR column that exceeds 255.\
If you need a column of this size, use the TEXT data type, which allows\
unlimited lengths. Otherwise, inspect the statement for typographical\
errors.\
\
|
-236	Number of columns in INSERT does not match number of VALUES.\
\
Each column that is named or implied in an INSERT statement must have a\
separate value expression. If the statement does not list specific\
columns, review the definition of the table for the number of columns\
and their data types. Also check that the list of expressions in the\
VALUES clause has no extra or missing comma that might result in an\
incorrect number of values. Be especially careful of long character\
strings and expressions with parentheses.\
\
|
-237	Cannot begin work.\
\
The database server cannot execute a BEGIN WORK statement. Check the\
accompanying ISAM error code for more information. A problem probably\
exits in accessing the transaction log.\
\
|
-238	Cannot commit work.\
\
The database server cannot execute a COMMIT WORK statement. Check the\
accompanying ISAM error code for more information. A problem probably\
exists in accessing the transaction log.\
\
|
-239	Could not insert new row - duplicate value in a UNIQUE INDEX\
column.\
\
The row that is being inserted (or being updated to have a new primary key)\
contains a duplicate value of some row that already exists, in a column or\
columns that are constrained to have unique values. Another cause of this\
error might be a locking conflict if the table lock mode is page. The new\
or updated row is not inserted.\
\
Roll back the current transaction and execute it again without any\
duplicate rows or with the locking conflict resolved.\
\
If you are using repeatable read isolation, then the error could be due\
to a unique constraint being violated. Refer to error -268.\
\
|
-240	Could not delete a row.\
\
The database server cannot finish execution of a DELETE statement. Roll\
back the current transaction; then check the accompanying ISAM error\
code for more specific information.\
\
|
-241	Cannot rollback work.\
\
The database server cannot execute a ROLLBACK WORK statement. Check the\
accompanying ISAM error code for more information. A problem probably\
exists in accessing the transaction log.\
\
|
-242	Could not open database table table-name.\
\
The database server cannot begin reading a table. Check the\
accompanying ISAM error code for more information. The problem might be\
file permissions, a hardware error, or a corrupted system catalog.\
Unless the ISAM error code or an operating-system message points to\
another cause, run the bcheck or secheck utility to verify file\
integrity.\
\
|
-243	Could not position within a table table-name.\
\
The database server cannot set the file position to a particular row\
within the file that represents a table. Check the accompanying ISAM\
error code for more information. A hardware error might have occurred,\
or the table or index might have been corrupted (truncated). Unless the\
ISAM error code or an operating-system message points to another cause, \
run the oncheck utility (secheck with IBM Informix SE or tbcheck with \
IBM Informix OnLine) to check and repair table and index. \
\
|
-244	Could not do a physical-order read to fetch next row.\
\
The database server cannot read the disk page that contains a row of a\
table. Check the accompanying ISAM error code for more information. A\
hardware problem might exist, or the table or index might have been corrupted. \
Unless the ISAM error code or an operating-system message points to another \
cause, run the oncheck utility (secheck with IBM Informix SE or tbcheck with \
IBM Informix OnLine) to check and repair table and index. \
\
|
-245	Could not position within a file via an index.\
\
The database server encountered an error when it attempted to look up a\
row through an index. Check the accompanying ISAM error code for more\
information. The table file or the index file might have been\
corrupted. Unless the ISAM error code or an operating-system message\
points to another cause, run the oncheck utility (secheck with IBM Informix \
SE or tbcheck with IBM Informix OnLine) to check and repair table and index.\
\
|
-246	Could not do an indexed read to get the next row.\
\
The database server encountered an error when it attempted to look up a\
row through an index. Check the accompanying ISAM error code for more\
information. The table file or the index file might have been\
corrupted. Unless the ISAM error code or an operating-system message\
points to another cause, run the oncheck utility (secheck with IBM Informix \
SE or tbcheck with IBM Informix OnLine) to check and repair table and index.\
\
|
-247	Rollforward database failed.\
\
The database server could not apply an audit trail to roll a database\
forward. Check the accompanying ISAM error code for more information.\
\
|
-248	Cannot commit savepoint.\
\
Version 4.1 and later products can detect this internal error. If the\
error recurs, note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
|
-249	Virtual column must have explicit name.\
\
When you select INTO TEMP, you are creating a table. As with any table,\
the columns of a temporary table must all have names. When you select a\
single column, the column in the temporary table receives the same\
name. When you select an expression, you must supply a name using a\
column alias, as in the following example:\
\
SELECT order_num, ship_date, ship_date + 14 expected\
        FROM orders INTO TEMP ord_dates\
\
The temporary table ord_dates has three columns, which are named\
order_num, ship_date, and expected. The same principle applies to a\
view: each column must have a name. When you select every column of a\
view from a table, the view can have the same column names by default.\
When you derive any column of a view from an expression, you must give\
all the columns explicit names, as in the following example:\
\
CREATE VIEW ord_dates(order_num, ship_date, expected)\
        AS SELECT order_num, ship_date, ship_date + 14 FROM orders\
\
|
-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.\
\
|
-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.\
\
|
-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.\
\
|
-253	Identifier length exceeds the maximum allowed by this version\
of the server.\
\
An SQL identifier exceeded the maximum number of characters. In IBM Informix\
Dynamic Server 9.2x or later, the maximum length for identifiers in SQL\
statements is 128 characters. In other Informix database servers, the maximum\
length for identifiers in SQL statements is 18 characters.\
\
Check that no identifier in the statement is longer than the maximum\
length and that no punctuation error, such as a missing space or comma,\
combines two identifiers into one.\
\
|
-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 columns that you referenced in\
the statement.\
\
Locate the text of the statement (in a PREPARE or DECLARE statement) and\
verify the number of placeholders. Then review the list in the INTO clause\
to see which item or items are incorrect.\
\
|
-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.\
\
|
-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.\
\
|
-257	System limit on maximum number of statements exceeded, maximum is\
count.\
\
The database server can handle only a fixed number of prepared SQL\
statements for each user. This limit includes statements that were\
prepared with the PREPARE statement and cursors that were declared with\
the DECLARE statement. This statement (PREPARE, DECLARE, or PREPARE\
IMMEDIATE) exceeds that limit and is not executed. The FREE statement\
releases prepared statements. Review the logic of your program, and\
change it so that it frees prepared statements when it no longer needs\
them.\
\
Version 5.0 and later database servers do not have this restriction.\
However, programs that must be compatible with earlier versions should\
use FREE to stay under the limit.\
\
|
-258	System error - invalid statement id received by the sqlexec\
process.\
\
The current statement (EXECUTE or OPEN) refers to a prepared SQL\
statement or a cursor that does not exist. Possibly the statement id is\
invalid, or possibly the statement was prepared and then released with\
the FREE statement. Review the program logic to make sure that the\
statement or cursor that is named in this statement is valid, has been\
properly prepared or declared, and has not been freed prior to this\
point.\
\
If the program executes a prepared DATABASE statement successfully, the\
database server automatically frees the prepared statement. As a\
result, if you free a prepared DATABASE statement, you will receive\
this error on the FREE statement. You can ignore it in this case.\
\
|
-259	Cursor not open.\
\
The current statement refers to a cursor that has not been opened.\
Review the logic of the program to see how it failed to execute the\
OPEN statement before it reached this point. Statements that end\
transactions (COMMIT WORK and ROLLBACK WORK) also close cursors unless\
the cursors are declared WITH HOLD.\
\
|
-260	Cannot execute a SELECT statement that is PREPAREd - must use\
cursor.\
\
Although you can prepare a SELECT statement, the only way you can then\
execute that SELECT statement is to associate its statement id with a\
cursor (use a DECLARE statement) and then open the cursor.\
\
An important exception is the SELECTINTO TEMP statement, which you can\
execute. You cannot use it with a cursor.\
\
You can execute other prepared statements with the EXECUTE statement.\
If you know the contents of this SELECT statement at the time you are\
writing the program, and if you are certain that it will return only a\
single row of data, you can embed it in the program. If it must be\
prepared dynamically while the program is running, revise your program\
to execute it through a cursor.\
\
|
-261	Cannot create file for table table-name.\
\
In general, the database server cannot create the file that will\
represent this table. Check the accompanying ISAM error code for more\
information. The file would be created in the database.dbs directory\
(unless you supplied an IN pathname clause) with IBM Informix SE. Its\
filename would begin with the first few letters of table-name,\
followed by a 3-digit number and the suffix .dat, or .idx.\
With IBM Informix SE, a problem might exist with file permissions, or\
possibly the disk is full.\
\
IBM Informix Dynamic Server, IBM Informix Universal Server, and IBM Informix OnLine\
Dynamic Server allow table fragmentation, which might involve extensive use\
of dbspaces. You need to check the dbspace that was specified for the table.\
If no dbspace was specified, then the dbspace in which the database was\
created is used. For database creation, if no dbspace is specified, then the\
rootdbs is used. The specified dbspace might not exist, or the disk might be\
full.\
\
|
-262	There is no current cursor.\
\
This internal error should not occur. Note all the details of the\
network software in use and the version number of the database servers\
in this and the other host system. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-263	Could not lock row for UPDATE.\
\
This statement, probably a FETCH statement that names a cursor\
declared FOR UPDATE, failed because the row it should have fetched\
could not be locked. Check the accompanying ISAM error code\
(usually -107, -113,-134, -143, -144, or -154) for more information.\
Probably another program is using the row (-107) or table (-113). You\
can use SET LOCKMODE TO WAIT to eliminate these errors, but detection\
of deadlock (-143 or -154) and lock table full (-134) can still occur.\
\
|
-264	Could not write to a temporary file.\
\
The database server created a temporary file in the directory that the\
DBTEMP environment variable (or /tmp by default on UNIX systems)\
specifies, but it encountered an error when it tried to write data into\
the file. Check the accompanying ISAM error code, and look for\
operating-system error messages that might give more information.\
Possibly a hardware failure occurred, or the disk is full. Since\
Version 5.01, the IBM Informix SE database server uses the DBTEMP\
environment variable, but IBM Informix Dynamic Server and IBM Informix OnLine\
Dynamic Server do not.\
\
|
-265	Load or insert cursors must be run within a transaction.\
\
You attempted to open an insert cursor. This database has a transaction\
log. In such a database, you must execute a BEGIN WORK statement\
before you open a cursor that is declared with an INSERT statement or\
with the FOR UPDATE clause. Revise the logic of your program so that it\
starts a transaction before it opens the cursor.\
\
You can ensure that the program also works in databases that do not\
have a transaction log. Change the program so that immediately after it\
executes the DATABASE statement, it saves the contents of the second\
element of the SQLAWARN array of warning flags in the SQL\
communications area. This element will contain a space if the database\
does not use transactions, and the letter W if it uses them. At each\
point where a transaction logically begins or ends, test the saved\
value. If it contains W, execute the transaction statement to begin or\
end a transaction.\
\
|
-266	There is no current row for UPDATE/DELETE cursor.\
\
The current statement uses the WHERE CURRENT OF cursor-name clause, but\
that cursor has not yet been associated with a current row. Either no\
FETCH statement has been executed since it was opened, or the most\
recent fetch resulted in an error so that no row was returned. Revise\
the logic of the program so that it always successfully fetches a row\
before it executes this statement.\
\
|
-267	The cursor has been previously released and is unavailable.\
\
The FREE statement released the resources that are attached to the\
cursor named in this statement, or possibly an automatic re-prepare \
was attempted while opening the cursor and it failed, leaving the cursor\
unavailable. Before you can use the cursor, you must again prepare the SQL \
statement that is associated with it. If the cursor was declared FOR a \
statement, re-execute its DECLARE statement. If the cursor was declared FOR \
a statement identifier, execute the PREPARE statement again.\
\
|
-268	Unique constraint <constraint-name> violated.\
\
During execution of this statement, a duplicate value was introduced\
into a column or columns that a unique constraint protects. The row\
with the duplicate value was not allowed into the table (not inserted\
or not updated). For IBM Informix Dynamic Server, any changes that this statement\
made prior to the discovery of the duplicate value have been rolled back. (The\
effects of preceding statements in the transaction, if there were any, remain\
in effect. They must be explicitly rolled back or committed.)\
\
This error occurs in a logging database. However, if you are using\
repeatable read isolation, error -239 will display instead.\
\
|
-269	Cannot add column column-name that does not accept nulls.\
\
This statement requests a new column that has the NOT NULL constraint.\
However, when a column is added to an existing table, null values have\
to be installed in the existing rows. Define a new table that includes\
this column, then INSERT the data from the old table into it to provide\
some suitable nonnull values for this column.\
\
|
-270	Could not position within a temporary file.\
\
The database server created a temporary file in the directory specified\
by the DBTEMP environment variable (or /tmp by default on UNIX systems)\
but encountered an error when it tried to position (seek) within it.\
Check the accompanying ISAM error code, and look for operating-system\
error messages that might give more information. Possibly a hardware\
failure occurred, or another user truncated the file. Since Version\
5.01, the IBM Informix SE database server uses the DBTEMP environment\
variable, but IBM Informix Dynamic Server and IBM Informix OnLine Dynamic Server\
do not.\
\
|
-271	Could not insert new row into the table.\
\
This problem has many possible causes, including a locked table or a\
full disk. Check the accompanying ISAM error code for more\
information.\
\
|
-272	No SELECT permission.\
\
The person who created this table has not granted Select privilege to\
your account name or to the public. The owner of the table or the DBA\
must grant this privilege before you can select data from the table.\
\
This error message may also occur if you are using the LOAD command in\
DB-Access because DB-Access uses the SELECT command to get information\
about a table before loading or inserting rows.\
\
|
-273	No UPDATE permission.\
\
The person who created this table has not granted Update privilege to\
your account name or to the public. The owner of the table or the DBA\
must grant this privilege before you can update a row in this table.\
\
|
-274	No DELETE permission.\
\
The person who created this table has not granted Delete privilege to\
your account name or to the public. The owner of the table or the DBA\
must grant this privilege before you can delete a row in this table.\
\
|
-275	No INSERT permission.\
\
The person who created this table has not granted Insert privilege to\
your account name or to the public. The owner of the table or the DBA\
must grant the privilege before you can insert a row into this table.\
\
|
-276	Cursor not found.\
\
The cursor that is named in this statement was not declared in the\
current session. The current session runs from the execution of a\
DATABASE statement to the next DATABASE or CLOSE DATABASE statement.\
Review the logic of the program to see that it executes the DECLARE\
statement for this cursor after the DATABASE statement.\
\
|
-277	UPDATE table table-name is not the same as the cursor table.\
\
This UPDATE WHERE CURRENT OF cursor statement refers to a different\
table than the table referenced by the SELECT statement that was\
declared with the cursor. Review the program logic to make sure that an\
update through a cursor updates only the table that the cursor is\
reading. This message also applies to cursor statements that use DELETE\
WHERE CURRENT OF.\
\
|
-278	Cannot rollback savepoint.\
\
This is an internal error. If the error recurs, please note all \
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-279	Cannot grant or revoke database privileges for table or view.\
\
This statement names one or more of the database-level privileges\
(CONNECT, RESOURCE, and DBA), but it also uses the ON table-name\
clause. A statement that does not mention a particular table (does not\
contain the ON clause) must grant or revoke the database-level\
privileges. The table-level privileges such as INSERT require an ON\
clause. Do not mix the two kinds in the same statement.\
\
|
-280	A quoted string exceeds 256 bytes.\
\
A character literal in this statement exceeds the maximum length. Check\
the punctuation and length of all quoted strings in the statement.\
Possibly two missing quotes make a long string out of two short ones.\
You must revise the statement to use a shorter character string.\
\
|
-281	Could not add index to a temporary table.\
\
Check the accompanying ISAM error code to find out the specific\
problem, and look for operating-system error messages that might give\
more information. Possibly the disk is full.\
\
|
-282	Found a quote for which there is no matching quote.\
\
Inspect the current statement, examining the punctuation of all quoted\
strings. To include the quote character in a literal string, use single\
apostrophes as string delimiters, as in the following example:\
\
SELECT '"', fname,'"', "''", lname, "''" FROM customer\
\
|
-283	Found a non-terminated comment ("{" with no matching "}").\
\
Inspect the current statement, and examine the punctuation of comments\
and quoted strings. You can use curly braces to insert comments into\
SQL statements, but the braces must balance. Or you can use the\
double-hyphen to append comments to the end of a line.\
\
|
-284	A subquery has returned not exactly one row.\
\
A subquery that is used in an expression in the place of a literal\
value must return only a single row and a single column. In this\
statement, a subquery has returned more than one row, and the database\
server cannot choose which returned value to use in the expression. You\
can ensure that a subquery will always return a single row. Use a WHERE\
clause that tests for equality on a column that has a unique index. Or\
select only an aggregate function. Review the subqueries, and check\
that they can return only a single row.\
\
This error can also occur when you use a singleton SELECT statement to\
retrieve multiple rows. You must use the DECLARE/OPEN/FETCH series of\
statements or the EXECUTE INTO statement to retrieve multiple rows.\
\
|
-285	Invalid cursor received by sqlexec.\
\
The cursor that this statement uses has not been properly declared or\
prepared, or the FREE statement has released it, or an automatic re-prepare\
has been attempted while opening the cursor but that operation failed,\
leaving the cursor unavailable. Review the program logic to ensure that the\
cursor has been declared. If it has, and if the DECLARE statement refers to\
a statement identifier, check that the referenced statement has been prepared.\
\
|
-286	Default value of the primary key column column-name is NULL.\
\
A column that is part of a primary key cannot have null as its default\
value.\
\
|
-287	Cannot add serial column column-name to table.\
\
You cannot add a column of SERIAL data type to an existing table. Such\
columns may not contain null values, but when you add a column, the\
database server must put null values in all existing rows. You can add\
a serial column in three steps. First, add the column with an INTEGER\
data type. Then update the table with nonnull, unique values in each\
row of the new column. Finally, use ALTER TABLE MODIFY to change the\
data type of the column to SERIAL.\
\
|
-288	Table table-name not locked by current user.\
\
This UNLOCK TABLE statement names a table that has not been locked. If\
you locked the table earlier, it has already been unlocked. Tables are\
unlocked automatically when a transaction ends or when the database is\
closed. If another user locked the table, you cannot unlock it.\
\
|
-289	Cannot lock table table-name in requested mode.\
\
The table is already locked in exclusive mode. You will have to wait\
for the table to be unlocked before you proceed.\
\
|
-290	Cursor not declared with FOR UPDATE clause.\
\
This statement attempts to update with a cursor that was not declared\
for update. The database server does not allow this action, as both a\
security measure that is designed to prevent program errors and a\
performance feature. To use a cursor with the UPDATE or DELETE\
statements, you must declare it for update. Review the program logic to\
make sure that this statement uses the intended cursor.\
\
In an ANSI-compliant database, any cursor can be used for updating; the\
FOR UPDATE clause is not required (and generates a warning).\
\
|
-291	Cannot change lock mode of table.\
\
The current LOCK TABLE statement cannot be executed because you have\
already locked the same table using a different mode (EXCLUSIVE or\
SHARE). To change the lock mode, arrange to unlock the table before\
you lock it again.\
\
|
-292	An implied insert column column-name does not accept NULLs.\
\
This INSERT statement does not supply values for all the columns in the\
table. At least one of the columns that it omits is constrained to be\
not null. Because the database server would have to insert a null value\
for every unmentioned column, it cannot perform this insert. Review the\
statement against the definition of the table. Possibly the definition\
of the table has been changed.\
\
|
-293	IS [NOT] NULL predicate may be used only with simple\
columns.\
\
The test for a null value can be applied only to a column name (not to\
a subscripted character column or an expression, for example).\
\
Review the use of these keywords in the WHERE clause and in any CASE\
statements.\
\
This message does not apply to 8.21 and later 8.x database servers,\
which allow expressions as arguments of the IS [NOT] NULL operator.\
\
|
-294	The column column-name must be in the GROUP BY list.\
\
In a grouping SELECT, you must list every nonaggregate column in the\
GROUP BY clause to ensure that a well-defined value exists for each\
selected column in each grouped row. A column contains either a single\
aggregate value or a value unique to that group. If a selected column\
were neither an aggregate nor in the list, two or more values for that\
column might possibly exist in some group, and the database server\
could not choose which value to display. Revise the query to include\
either the column name or its positional number in the clause.\
\
|
-295	Referenced and referencing tables have to be in the same database.\
\
Referential constraints cannot cross databases. In other words, both\
the referenced and referencing columns (or parent and child keys) must\
be in the same database.\
\
|
-296	Referenced table table-name not found.\
\
The table that is specified in a referential constraint does not\
exist.\
\
|
-297	Cannot find unique constraint or primary key on referenced\
table <table_name>.\
\
The database server cannot locate the referenced constraint in the\
sysconstraints system catalog table, and the referenced constraint\
was not created in the same ALTER TABLE statement as the referencing\
constraint. The referenced constraint might not exist, or a foreign key\
might refer to a table that has a unique constraint but not a\
primary-key constraint.\
\
Check that you have entered a valid column name with the appropriate\
constraints that are associated with it. If the referenced table has a\
unique constraint but no primary key, you must use the following form of\
the REFERENCES clause:\
\
   REFERENCES table_name (column_name)\
\
Valid constraint columns indicate an internal error. If the error\
recurs, note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-298	Cannot grant permission to public with grant option.\
\
The clause WITH GRANT OPTION allows the receiver of the grant to grant\
the same privilege to others. In this case, the receiver of the grant\
is PUBLIC. If this statement were executed, everyone would have the\
privilege, and everyone could grant the privilege. This operation is\
prohibited. Either name specific grantees, or omit the clause WITH\
GRANT OPTION.\
\
|
-299	Cannot grant permission to self.\
\
This GRANT statement includes your user id as one of the grantees. If\
you can grant the privilege, you already have the privilege. Rewrite\
the statement to omit your user name from the TO clause.\
\
|
-300	There are too many GROUP BY columns.\
\
The number of columns that can be listed in the GROUP BY clause is an\
implementation limit of the database server. All database servers\
support at least eight columns. Review the current statement to ensure\
that the punctuation of the GROUP BY clause is correct. If it is as you\
intended, you will have to find a way to make this query in two or more\
stages. Since you must list all nonaggregate selected columns in the\
GROUP BY clause, and the length of the list is restricted, you must\
select only the non-aggregate values that are required to distinguish\
each group. Put the group results in a temporary table, and join this\
table to the original table to select other non-aggregate values.\
\
|
-301	The total size of the GROUP BY columns is too big.\
\
The database server limits the total number of bytes in the combined\
columns that the GROUP BY clause lists. All database servers support at\
least 120 bytes. See the discussion of error -300 for more information.\
\
|
-302	No GRANT option or illegal option on multi-table view.\
\
This GRANT statement cannot be executed. The grantor does not have the right\
to grant the specified privilege for this table, the table name is a\
synonym, or the table is a view for which this option cannot be granted.\
If the grantor does have the right to grant the privilege, the table in\
question might be a synonym or a view that is not modifiable and cannot be\
used for insert, update, or delete operations.  Starting with version 9.40,\
you can define an INSTEAD OF trigger on the view to make it modifiable and\
then try this option.\
\
To grant any privilege for a table, you must be the owner of the table or you\
must have been granted the same privilege with the GRANT option. To use the\
AS GRANTOR clause, you must have DBA privilege.\
\
|
-303	Expression mixes columns with aggregates.\
\
This SELECT statement uses an aggregate function in its WHERE clause.\
This action is not allowed. The WHERE clause must be applied row by row\
as a table is scanned, but an aggregate function can only be calculated\
after all rows have been chosen and grouped. Review the statement with\
this fact in mind. If you intended to select only certain groups of\
records, you can put that test in the HAVING clause; it is applied to\
grouped rows.\
\
The text of this message is somewhat deceptive. You can, in fact, mix\
column names and aggregate functions in expressions. However, you can\
do so only in the select list or the HAVING clause (not in the WHERE\
clause), and the columns must appear in the GROUP BY clause.\
\
Database servers after Version 5.01 do not use this error message.\
\
|
-304	HAVING can only have expressions with aggregates or columns\
in GROUP BY clause.\
\
The HAVING clause is used to select completed rows after grouping has\
been done. Therefore, the only selected values that it can test are\
values that are available in completed groups of rows, namely the\
single columns that are named in the GROUP BY clause and aggregate\
values. Review the HAVING clause with this rule in mind. If you want to\
select particular rows before grouping has taken place, use the WHERE\
clause.\
\
|
-305	Subscripted column column-name is not of type CHAR, VARCHAR, TEXT\
nor BYTES.\
\
You may select substrings only from columns of the types mentioned.\
Review all uses of square brackets in this statement, and make sure\
that each follows the name of a column that has one of these types. If\
that is the case, verify that you are using the database you intended,\
and double-check the definition of the table. Possibly one of the\
columns in the table has been altered to use a different type.\
\
|
-306	Subscript out of range.\
\
This statement refers to a substring of a character variable. The\
substring values (two numbers in square brackets) are incorrect. The\
first is less than zero or greater than the length of the column, or\
the second is less than the first. Review all uses of square brackets\
in the statement to find the error. Possibly the size of a column has\
been altered and makes a substring fail that used to work.\
\
|
-307	Illegal subscript definition.\
\
This statement refers to a substring of a character variable. The\
substring values (two numbers in square brackets) are incorrect. The\
first is less than zero or greater than the length of the column, or\
the second is less than the first. Review all uses of square brackets\
in the statement to find the error. Possibly the size of a column has\
been altered and makes a substring fail that used to work.\
\
|
-308	Corresponding column types must be compatible for each UNION\
statement.\
\
All rows produced in a union of SELECT statements must have the same format,\
so the corresponding columns for each UNION statement must have the same\
data type or compatible data types. Two data types are compatible if you can\
convert one of them into the other; for example, int and float are\
compatible data types because you can convert int values to float values. In\
the current statement, a column in the second or subsequent SELECT statement\
does not agree with the corresponding column in a preceding SELECT statement.\
\
Review and compare all the SELECT statements. Check each point at which one\
statement selects a column that is not identical to a column in the\
preceding SELECT statement. If the column data types do not match, then one\
type must be convertible to the other type.\
\
|
-309	ORDER BY column or expression must be in SELECT list.\
\
An expression or column name is in the ORDER BY clause of this SELECT\
statement, but the expression or column name is not in the select\
list (the list of values that follows the word SELECT). This action is not\
supported when a UNIQUE or DISTINCT operator is being used in a query.\
\
When a UNIQUE or DISTINCT operator is being used in a query, all sort\
keys must be present in the output rows to determine the true order.\
Revise the statement to follow this rule.\
\
|
-310	Table table-name already exists in database.\
\
This statement tries to create a table with the name that is shown, but\
one with that name already exists. Only one table with a given name can\
exist in a single database. (In an ANSI-compliant database, the name of\
the user that created a table name qualifies it, so one table of a\
given name per user can exist.)\
\
Check the spelling of the name; if it is as you intended, and you are\
sure it should not exist, check that you are using the right database.\
You can review the names of all tables in this database by querying\
systables as follows:\
\
SELECT tabname FROM systables WHERE tabid > 99\
\
This statement will display only names of permanent tables, not\
temporary tables. Temporary tables do not appear in systables. If the\
name does not appear, end your database session and start a new one.\
Temporary tables will be dropped.\
\
|
-311	Cannot open system catalog table-name.\
\
The database server cannot access one of the tables in the system\
catalog. Check the accompanying ISAM error code for detailed\
information, and look for operating-system error messages that might\
give more information.\
\
|
-312	Cannot update system catalog table-name.\
\
The database server cannot record a change in the system-catalog\
table. Check the accompanying ISAM error code for more detailed\
information. Insufficient disk space is a common cause of this error.\
\
|
-313	Not owner of table.\
\
This statement tries to do something, such as dropping a table, that\
only the owner of the table or a user who has Database Administrator\
privileges can do. Check that the statement names the table you\
intended. If it does, you will have to get its owner or a DBA to\
execute this statement. To find out who to contact, you can query the\
system catalog as follows:\
\
SELECT tabname, owner FROM systables WHERE tabid > 99;\
SELECT username FROM sysusers WHERE usertype = 'D'\
\
|
-314	Table table-name currently in use.\
\
This statement tries to do something, such as dropping a table, that\
cannot be done while another user is using the table. Wait a short\
time, and try again. To ensure that no table is in use, open the\
database with DATABASE EXCLUSIVE.\
\
|
-315	No create index permission.\
\
This statement tries to create an index for a table. Either you do not\
have INDEX privilege on this table, or the table itself is a view or\
synonym. If the table that is named really is a table, contact the\
owner of the table or a database administrator (see the discussion of\
error -313) and ask to be granted this privilege.\
\
|
-316	Index <index-name> already exists in database.\
\
This statement tries to create an index with the name shown, but an\
index of that name already exists. Only one index of a given name\
can exist in a single database.\
\
Check the spelling of the name. If it is as you intended, and you\
are sure it should not exist, make sure you are using the right\
database. To review the names of all indexes and their owners, join\
systables and sysindexes as follows:\
\
   SELECT T.tabname, I.idxname, I.owner FROM systables T, sysindexes I\
          WHERE I.tabid = T.tabid AND T.tabid > 99\
\
|
-317	Must have the same number of selected columns in each UNION element.\
\
All rows that are produced in a union must have the same format, so\
each SELECT statement in the union must select the same number of\
columns. In this union, one of the second or subsequent SELECT\
statements does not list the same number of columns as the preceding\
one. Review the entire union, and check that all select lists are alike\
in number and data type. If no appropriate column exists for one of the\
statements, specify a literal value of the appropriate type at that\
position. For example, where you need to match a numeric column,\
specify a literal zero.\
\
|
-318	File with the same name as specified log file already exists.\
\
The transaction log file you specify in the WITH LOG IN clause cannot\
already exist. The database server must start a new log file; it cannot\
append log data to an old log file. An existing log file contains\
recovery information that might be crucial, so it does not simply empty\
an existing file. To begin logging for a database that has not been\
logged before, lock the database, copy all of the database directory to\
a backup medium, and use the START DATABASE statement to name a new\
file. To make a partial archive subsequently, lock the database, copy\
the log file to a backup medium and store it with the full archive,\
erase or rename the log file, and use the START DATABASE statement.\
\
|
-319	Index does not exist.\
\
This statement refers to an index that does not exist. Review the\
spelling of the index name; if it is as you intended, and you are sure\
it should exist, make sure you are using the right database.\
\
In an ANSI-compliant database, an index that you do not own must be\
qualified with its owner's name. See the discussion of error -316 for a\
way to check the names and owners of all indexes.\
\
|
-319	Index does not exist in ISAM file.\
\
This statement refers to an index that does not exist. (The reference\
to an ISAM file is not relevant; ignore it.) Review the spelling of the\
index name; if it is as you intended, and you are sure it should exist,\
make sure you are using the right database.\
\
In an ANSI-compliant database, an index that you do not own must be\
qualified with its owner's name. See the discussion of error -316 for a\
way to check the names and owners of all indexes.\
\
|
-320	Not owner of index.\
\
This statement tries to do something, such as dropping an index, that\
only the owner of the index or a user who has Database Administrator\
privileges can do. Check that the statement names the index that you\
intended. If it does, you will have to get its owner or a DBA to\
execute this statement. See the discussion of error -316 for a way to\
list the names and owners of indexes.\
\
|
-321	Cannot group by aggregate column.\
\
The GROUP BY clause in this statement refers to a selected value that\
is an aggregate function. This action is not supported. (It does not\
make sense to group rows using a value that cannot be computed until\
the group has been formed.) You can group rows by the value of columns\
or expressions on columns, but the expressions cannot include aggregate\
functions. Review the GROUP BY clause, and compare it to the select\
list. Possibly one of the column numbers in the GROUP BY clause is\
incorrect.\
\
|
-322	Cannot Alter view, Rename view or Create a trigger on a view. \
\
Starting with version 9.40, you can only create an INSTEAD OF trigger \
on a view.  You cannot create an INSTEAD OF trigger on a view created\
using WITH CHECK OPTION. \
\
Consider creating the trigger on the base table of the view or create\
a table with the same schema as the view and then define the trigger\
on the table.\
\
You can also receive this message if you issue the START VIOLATIONS\
TABLE statement or the STOP VIOLATIONS TABLE statement for a view. You\
must specify the name of a base table in both of these statements.\
\
-323	Cannot grant permission on temporary table.\
\
This GRANT statement names a temporary table. That action is not\
supported. Privileges are recorded only for permanent tables. Because\
temporary tables are not recorded in the system catalogs, no place\
exists to record privileges on them. Only the person who creates a\
temporary table can access it.\
\
|
-324	Ambiguous column column-name.\
\
The column name appears in more than one of the tables that are listed\
in the FROM clause of this query. The database server needs to know\
which columns to use. Revise the statement so that this name is\
prefixed by the name of its table (table-name.column) wherever it\
appears in the query. If the statement becomes unwieldy, give the table\
a shorter alias name in the FROM clause (see the discussion of error\
 -316 for an example).\
\
|
-325	Filename must be specified with a full path name.\
\
This error occurs if you attempt to create a table using the WITH LOG\
IN clause but do not specify a complete path to the log file. This\
error can also occur if you use IBM Informix SE to create database logging\
but do not specify the full path of the log file. Make sure to specify\
a full pathname, including the name of the log file, where the log file\
will reside.\
\
|
-326	Referential constraint has too many referenced columns.\
\
The specified referential constraint has more than 16 columns (or 8 in\
IBM Informix SE).\
\
|
-327	Cannot unlock table table-name within a transaction.\
\
The statement UNLOCK TABLE is not allowed within a transaction, that\
is, following the execution of BEGIN WORK. You can still use LOCK TABLE\
when you use transactions, but the table will be unlocked automatically\
when the transaction ends. All locks are released at the end of a\
transaction. In an ANSI-compliant database, BEGIN WORK is not used, a\
transaction is always in effect, and the UNLOCK TABLE statement is\
never used.\
\
|
-328	Column column-name already exists in table.\
\
This statement tries to add the column shown, but one with that name\
already exists. Check the spelling of the name; if it is as you\
intended, then the table is not arranged as you expected it to be. You\
can review the names of all the columns in a table by querying\
syscolumns. Supply a table-name in the following query:\
\
SELECT colname, colno FROM syscolumns C, systables T\
        WHERE C.tabid = T.tabid AND T.tabname = 'table-name'\
\
You can use RENAME COLUMN to change column names.\
\
|
-330	Cannot create database.\
\
Possibly you tried to create a database with the same name as one that\
already exists; if so, choose a different name. Otherwise, check the\
accompanying ISAM error code for more detailed information on the\
cause. Possibly a shortage of disk space or a problem with file\
permissions exists.\
\
|
-331	Cannot drop database directory.\
\
While the database server was executing the DROP DATABASE statement, it\
removed all database-related files from the dbname.dbs directory and\
tried to remove the directory itself, but an error occurred. Check the\
accompanying ISAM error code for more detailed information on the\
cause. The most likely cause is that you or another user created\
nondatabase files in the same directory, and the directory cannot be\
removed because it is not yet empty.\
\
|
-329	Database not found or no system permission or database is not logged.\
\
The database you tried to open is not visible to the database server.\
Check the spelling of the name. Possibly the database is located in a\
different database server (or network system), and you have omitted to\
specify the server name (or site name) with the database name. If you\
are sure the database should exist just as you spelled it, your next\
step depends on the database server you are using.\
\
If you are using IBM Informix SE, the visible databases are directories\
with names in the form dbname.dbs. You must be able to read from and\
write to them. The database server looks first in the current working\
directory and then in each directory named in the DBPATH environment\
variable. The most common cause of this error is an incorrect setting\
or no setting for the DBPATH environment variable.\
\
If you are using IBM Informix Dynamic Server, IBM Informix Universal Server, or\
IBM Informix OnLine Dynamic Server, the database does not exist as you spelled it.\
In some environments, two or more instances of the database server can run at\
once and each instance has its own collection of databases. For Version 6.0\
and later, the value of the INFORMIXSERVER environment variable determines the\
instance of the database server that you use. For Versions 5.1x and earlier, \
the ONCONFIG environment variable points to the configuration file that\
determines the instance. See your database server administrator if you think\
you might be using the wrong instance.\
\
If you are connected to a secondary database server, the database you tried\
to open might exist, but is not logged. Databases are required to be logged\
to be able to access them on secondary database servers.\
\
|
-332	Cannot access audit trail name information.\
\
An error occurred while reading the audit-trail file. Re-execute the\
latest statement; if the error recurs, the audit-trail file is corrupt.\
In that case you will need to drop and restart the audit.\
\
|
-333	The audit trail file already exists with a different name.\
\
Before you start a new audit trail, you must drop an existing one. Use\
the DROP AUDIT statement.\
\
|
-334	Cannot create audit trail.\
\
Some problem prevents the database server from initializing the\
audit-trail file. Check that you specified a complete, correct pathname\
for the file. Look for operating-system error messages that might give\
more information. Common problems include a lack of disk space and\
file-permission problems.\
\
|
-335	There is no audit trail for the specified table.\
\
This statement requires an audit trail to work, but no current audit\
trail exists for the table. Either none was ever started, or it was\
dropped. Check that you specified the table you intended. In a recovery\
situation (the statement was RECOVER TABLE), check that the table has\
just been restored from a backup copy. If so, the table did not have an\
audit trail at the time that this backup was made. If an audit trail\
was specified later, an unknown period remains between the backup and\
the start of auditing during which unaudited updates might have been\
made.\
\
|
-336	Cannot create or drop audit on a temporary table table-name.\
\
Temporary tables cannot be audited. The commands regarding audit trails\
will not accept the names of temporary tables. If you did not intend to\
name a temporary table, check the spelling of the table table-name. See\
the discussion of error -313 for a way to display the names of all\
permanent tables in the database.\
\
|
-337	Cannot create view on temporary table table-name.\
\
Views can be created only on permanent tables. The SELECT statement\
that defines the view in this latest statement contains the name of\
the temporary table, table-name. If you did not intend to name a\
temporary table, check the spelling of table-name. See the discussion\
of error -313 for a way to display the names of all permanent tables\
in the database.\
\
|
-338	Cannot drop audit trail.\
\
An unexpected error occurred during the execution of a DROP AUDIT\
statement. Check the accompanying ISAM error code for more detailed\
information.\
\
|
-339	The audit trail file name must be given in full directory path.\
\
The audit-trail file that is specified in the CREATE AUDIT statement\
requires a full directory path. Because it is not required to be in a\
particular directory, the database server cannot use the current\
directory or the DBPATH variable to search for it.\
\
|
-340	Cannot open audit trail file.\
\
The database server needs to use the audit-trail file for this table,\
but some unexpected problem prevents it. Likely causes include hardware\
errors, file-permission problems, or the accidental erasure of the\
file. Look for operating-system error messages that might give more\
information.\
\
|
-341	Could not read a row from audit trail file.\
\
The database server encountered an unexpected error while it was\
reading the audit trail for this table. Likely causes of the error\
include file-permission problems and hardware errors. Look for\
operating-system error messages that might give more information.\
\
|
-342	Remote host cannot execute statement.\
\
This statement was sent to a database server in a different system for\
execution. However, that database server does not support the requested\
function, possibly because it is an earlier version.\
\
|
-343	Row from audit trail was added to a different position than expected.\
\
While the database server was reconstructing a table from the audit\
trail, it found a discrepancy between the position of an inserted row\
now and the position that was recorded in the audit trail when the row\
was first inserted. Either the audit-trail file has been corrupted, or\
the audit-trail file is incomplete, with missing records for some\
alterations. The table cannot be recovered as it stands. Try the\
operation again after you make sure that the table has been restored to\
exactly the same state as when the audit trail was created. If the\
error recurs, rebuild the table by other means.\
\
|
-344	Cannot delete row - row in table does not match row in audit trail.\
\
While the database server was reconstructing a table from the audit\
trail, it found a discrepancy between the position of a deleted row now\
and the position that was recorded in the audit trail when the row was\
first deleted. Either the audit-trail file has been corrupted, or the\
audit-trail file is incomplete, with missing records for some\
alterations. The table cannot be recovered as it stands. Try the\
operation again after you make sure that the table has been restored to\
exactly the same state as when the audit trail was created. If the\
error recurs, rebuild the table by other means.\
\
|
-345	Cannot update row - row in table does not match row in audit trail.\
\
While the database server was reconstructing a table from the audit\
trail, it found a discrepancy between the contents of an updated row\
now and the contents that were recorded in the audit trail when the row\
was first updated. Either the audit-trail file has been corrupted, or\
the audit-trail file is incomplete, with missing records for some\
alterations. The table cannot be recovered as it stands. Try the\
operation again after you make sure that the table has been restored to\
exactly the state it had when the audit trail was created. If the error\
recurs, rebuild the table by other means.\
\
|
-346	Could not update a row in the table.\
\
While the database server was processing an UPDATE, it received an\
unexpected error. Check the accompanying ISAM error code for more\
detailed information on the cause. Possible causes include hardware\
errors and locking conflicts.\
\
|
-347	Could not open table for exclusive access.\
\
The database server cannot complete a LOCK TABLE statement or the\
implicit LOCK TABLE that must be performed as part of other statements\
that change the definition of a table (for example ALTER TABLE, RENAME,\
or CREATE INDEX). Check the accompanying ISAM error code for more\
detailed information on the cause. Possible causes include lock\
conflicts, a full lock table, or low-level problems with the host\
operating-system lock mechanism.\
\
|
-348	Could not read a row from the table.\
\
While the database server was trying to fetch a row from a table, it\
received an unexpected error. Check the accompanying ISAM error code\
for more detailed information on the cause. Possible causes include\
hardware errors and lock conflicts.\
\
|
-349	Database not selected yet.\
\
This statement cannot be executed because no current database exists.\
Either no current database has been established yet, or the current\
database was closed with a CLOSE DATABASE statement. You execute the\
DATABASE or CREATE DATABASE statement to establish a current database.\
\
|
-350	Index already exists on column.\
\
This CREATE INDEX statement cannot be executed because an index on the\
same column or combination of columns already exists. At most two\
indexes can exist on any combination of columns, one ascending and one\
descending. To display the indexes on a particular table, join\
sysindexes and systables. Supply table-name in the following\
statement:\
\
SELECT * FROM sysindexes, systables\
        WHERE sysindexes.tabid = systables.tabid\
           AND systables.tabname = 'table-name'\
\
The sysindexes table is not normalized (the part columns are a\
repeating group), so no simple SELECT statement will return all the\
column names in an index.\
\
|
-351	Database contains tables owned by other users.\
\
This DROP DATABASE or UPDATE STATISTICS statement cannot be carried out\
for the reason shown. It might destroy the work of others. In order to\
drop this database, you must first drop all tables that other users\
own. To do so, you must have database administrator privilege. See the\
discussion of error -313 for a way to list the names of all tables with\
their owners.\
\
|
-352	Column column-name not found.\
\
The column, or one of the columns, named in this CREATE INDEX statement\
does not exist. Review the spellings of all columns in the statement.\
See the discussion of error -328 for a way to list all column names in\
a table.\
\
|
-353	No table or view specified when granting/revoking privileges.\
\
This statement specifies one of the table-level privileges (ALTER,\
DELETE, INDEX, INSERT, SELECT, UPDATE, and ALL) but does not specify\
the table to which the privilege applies. When you grant or revoke a\
database-level privilege (CONNECT, DBA, RESOURCE), you cannot name a\
table, but when you grant or revoke a table-level privilege you must\
name a table.\
\
|
-354	Incorrect database or cursor name format.\
\
This statement contains the name of a database or a cursor in some invalid\
format. If the statement is part of a program, the name might have been\
passed in a host variable.\
\
The maximum length for database names and cursor names depends on the\
database server. In IBM Informix Dynamic Server 9.2x or later, the maximum length\
is 128 characters. For IBM Informix SE, database names should be no longer\
than 10 characters (fewer in some host operating systems). In other\
Informix database servers, the maximum length is 18 characters.\
\
Both database and cursor names must begin with a letter and contain only\
letters, numbers, and underscore characters. In IBM Informix OnLine Dynamic\
Server and later Informix database servers, database and cursor names can\
begin with an underscore. In Dynamic Server 9.2x or later, these names can\
include dollar-sign characters.\
\
In MS-DOS systems, filenames can be a maximum of 8 characters plus a\
3-character extension.\
\
|
-355	Cannot rename file for table.\
\
This RENAME statement cannot be completed because the database server\
got an unexpected error. Check the accompanying ISAM error code for\
more detailed information on the cause. Possible causes include\
hardware errors and file-permission problems.\
\
|
-356	Data type of the referencing and referenced columns do not match.\
\
The data types of the columns in the child constraint must be identical\
to those in the parent constraint.\
\
|
-357	Dependent table for view view-name has been altered.\
\
The view is based on data from a table that has been altered since the\
view was defined. The alteration removed or renamed a column that is\
used in the view. The view can no longer be used. Drop the view, and\
redefine it to use the current schema.\
\
|
-358	Must close current database before CREATE, START or ROLLFORWARD.\
\
These statements choose a new current database, but the present\
database must be closed first. Use the CLOSE DATABASE statement before\
this statement.\
\
|
-359	Cannot drop current database.\
\
The database that is currently open cannot be dropped. First use the\
CLOSE DATABASE statement; then you can drop it.\
\
|
-360	Cannot modify table or view used in subquery.\
\
The UPDATE, INSERT, or DELETE statement uses data taken from the same table\
in a subquery. This action is not allowed because of the danger of getting\
into an endless loop. Select the input data into a temporary table first,\
and then refer to the temporary table in the UPDATE or INSERT statement.\
\
|
-361	Column size too large.\
\
This internal error reflects a communications problem between the\
database server and the application. You should not see this error. If\
the error recurs, note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
|
-362	Can have only one column of serial/serial8 type.\
\
A table can have at most only one column of type SERIAL and one column\
of type SERIAL8. You are attempting to add a second column of type\
SERIAL or SERIAL8, or you are attempting to create a table with more\
than one column of either type. If you intended to have a foreign key\
(that is, a column that refers to a SERIAL or SERIAL8 column in a\
different table), the data type of the column in this table should be\
INTEGER or INTEGER8.\
\
|
-362	Can have only one column of serial type.\
\
Only one SERIAL column can exist in a table. This CREATE TABLE\
statement specifies two or more. Review the statement, and remove all\
but one of the columns with SERIAL data type. If you intended to have a\
foreign key (that is, a column that refers to a SERIAL column in a\
different table), the data type of the column in this table should be\
INTEGER.\
\
|
-363	CURSOR not on SELECT statement.\
\
The cursor named in this statement (probably an OPEN) has been\
associated with a prepared statement that is not a SELECT statement.\
Review the program logic, especially the DECLARE for the cursor, the\
statement id specified in it, and the PREPARE that set up that\
statement. If you intended to use a cursor with an INSERT statement,\
you can only do that when the INSERT statement is written as part of\
the DECLARE statement. If you intended to execute an SQL statement, do\
that directly with the EXECUTE statement, not indirectly through a\
cursor.\
\
This error is also returned when you attempt to associate a cursor with\
a SELECTINTO TEMP statement. Because of the INTO TEMP clause, the\
SELECT statement can return no rows and so cannot be used with a\
cursor.\
\
|
-364	Column column-name not declared for UPDATE OF.\
\
This UPDATE...WHERE CURRENT OF cursor-name statement refers to at least\
one column that does not appear in the FOR UPDATE OF clause of the\
DECLARE statement that declared the cursor. Since specific columns were\
listed in the cursor declaration, the database server will not allow\
others to be updated. Review the declaration and the uses of this\
cursor. Perhaps the noted column, and others, should be added to the\
declaration, or perhaps the OF clause should be dropped, allowing the\
cursor to update any column in the table.\
\
|
-365	Cursor must be on simple SELECT for FOR UPDATE.\
\
The cursor named in this statement (probably an OPEN statement) was\
declared with the FOR UPDATE clause. However, it has been associated\
with a SELECT statement that joins two or more tables or that uses\
UNIQUE, DISTINCT, GROUP BY, or UNION. Such a SELECT statement\
cannot be used in an update; there is no way to distribute the new\
data back into the multiple tables.\
\
Review the declaration of the cursor. If it is declared FOR\
statement id, also review the PREPARE statement that set\
up that statement. You might need two cursors, one for general queries\
and another specifically for updating.\
\
|
-366	The scale exceeds the maximum precision specified.\
\
A problem exists with the precision or scale of a DECIMAL or a MONEY\
data type in this statement. Review all uses of these types. The first\
should be declared as DECIMAL(p) or DECIMAL(p,s) where p, the precision\
(total number of digits) is between 1 and 32, and s, the scale (number\
of digits to the right of the decimal point) is no greater than p. The\
MONEY type follows the same rules.\
\
|
-367	Sums and averages cannot be computed for character columns.\
\
This statement contains a use of the SUM or AVG function applied to a\
column that has a character data type (CHAR or VARCHAR). If you did not\
intend to take the sum or average of character strings, review the\
spelling of column names against the table definition. If a character\
column actually contains numeric values in character form, you can\
trick the database server (Version 4.0 and later) into performing an\
automatic conversion. Instead of applying the function to the column\
name alone, apply it to the expression in parentheses (column+0).\
\
|
-368	Incompatible sqlexec module.\
\
The version of the database server does not agree with the version of\
the database library routines in the application program. This\
incompatibility must be resolved before the program can be executed.\
The database server is selected through the SQLEXEC environment\
variable (for database server versions prior to 6.0). It contains a\
complete pathname to the database server code, which is usually named\
sqlexec or sqlturbo (for database server versions prior to 6.0). The\
access routines linked into the program were chosen when the program\
was compiled. If the program you are running was supplied by Informix or IBM,\
then it or another IBM Informix product might have been installed\
incorrectly.\
\
|
-369	Invalid serial number. Consult your installation instructions.\
\
Some error has been made in the installation of your IBM Informix\
products. Check the value in the SQLEXEC environment variable (for\
database server versions prior to 6.0) and INFORMIXDIR environment\
variable; then consult the person who installed the software, and\
review the installation instructions.\
\
|
-370	Cannot drop last column.\
\
This ALTER TABLE DROP statement would drop every column from the\
table. At least one column must be retained. Revise the statement to\
leave one column. Or if you do not want the table at all, use DROP\
TABLE to remove it.\
\
|
-371	Cannot create unique index on column with duplicate data.\
\
This CREATE UNIQUE INDEX statement cannot be completed because the\
column (or columns) contains one or more duplicate rows. You can either\
create an ordinary index, accepting the duplicate values, or you can\
modify the table to remove the duplicates. To get a list of the\
duplicate values in a single column, first create the ordinary index.\
Then use a SELECT statement such as the following, filling in the table\
and column names:\
\
SELECT column FROM table main\
        WHERE 1 < ( SELECT COUNT(*) FROM table sub\
           WHERE main.column = sub.column )\
\
This statement can be extended to handle the case of multiple columns\
using AND.\
\
|
-372	Cannot alter table with audit trail on.\
\
Once an audit trail has been started for a table, the table should not\
be altered. If you must alter the table, do the following. Copy the\
table to a backup medium. Use DROP AUDIT to remove the audit trail.\
Delete the audit-trail file. Alter the table. Again, copy the table to\
a backup medium. Finally, use CREATE AUDIT to start a new audit trail.\
The first backup is needed to restore the table if a failure occurs\
while the table is being altered (a lengthy, disk-intensive procedure\
if the table is large). The second backup is required because, if the\
table has to be recovered later, the new audit trail must be applied\
against a backup that has the same layout of columns.\
\
|
-373	DBPATH too long.\
\
While the database server was trying to locate a database using the\
DBPATH environment variable, it constructed a full-path string that\
exceeds its limit of 80 characters. A limit exists on the length of one\
complete database directory pathname, from the starting slash or\
backslash through the .dbs suffix. You will have to locate your\
databases higher up in the directory hierarchy in order to use them.\
(The message text is misleading; there is no specific limit on the\
total length of the contents of DBPATH.)\
\
|
-374	Can only use column number in ORDER BY clause with UNION.\
\
This query has both a UNION clause and an ORDER BY clause. In a union\
query, in which multiple SELECT statements exist and the names of the\
selected columns in each statement are not necessarily the same, you\
cannot use column names or expressions in the ORDER BY clause.\
\
Instead, you must use column position numbers, with 1 representing the\
first selected column, 2 representing the second, and so on. Rewrite the\
query to use only numbers in the ORDER BY clause.\
\
|
-375	Cannot create log file for transaction.\
\
While the database server was trying to execute a START statement, it\
got an unexpected error in trying to create the transaction-log file.\
Check the accompanying ISAM error code for more detailed information on\
the cause. Typical causes include a shortage of disk space, file\
permission problems, or a limit on the number of open files.\
\
|
-376	Log file already exists.\
\
The transaction log file you specify in the WITH LOG IN clause must not\
already exist. The database server must start a log file fresh; it has\
no means of appending log data to an old log file. An existing log file\
contains recovery information that may be crucial, so it will not\
simply empty an existing file. To make a full backup, lock the\
database, copy all of the database directory to a backup medium, erase\
the log file (it is no longer needed), and use the START DATABASE\
statement. To make a partial backup, lock the database, copy the log\
file to a backup medium and store it with the full backup, erase or\
rename the log file, and use the START DATABASE statement.\
\
|
-377	Must terminate transaction before closing database.\
\
This statement (DATABASE, CREATE DATABASE, or CLOSE DATABASE) cannot be\
executed until the current transaction is finished.\
\
Use either COMMIT WORK or ROLLBACK WORK and then close the database.\
\
If you export a database and then import it, large-object handles (for\
images) will be different after you import the database. Therefore, if you\
use static html references for images and export the database and then\
import it, you will have to determine the new large-object handle for each\
static html reference.\
\
|
-378	Record currently locked by another user.\
\
A row of a table that this statement needs is not accessible because it\
has been locked. Check the accompanying ISAM error code for more\
detailed information. It will probably be -107, -113, -134, -143, -144,\
or -154. Each notes a slightly different relationship between your\
program and the other user's program. You can prevent most, but not\
all, occurrences of this error with SET LOCK MODE TO WAIT.\
\
For database servers prior to Version 4.1, this error message is\
produced in conjunction with the UPDATE and the DELETE WHERE CURRENT OF\
statements only. In Version 6.0, this error message is no longer used.\
\
|
-379	Cannot revoke privilege on columns.\
\
In the GRANT statement, you can grant UPDATE or SELECT privilege on\
specific columns. However, the REVOKE statement accepts only the\
keywords for the type of privilege; you cannot revoke access to\
specific columns. If you want to change the columns allowed to a\
certain user, you must first REVOKE the privilege in full, then GRANT\
it on the new list of columns.\
\
|
-380	Cannot erase log file.\
\
The database server, while trying to initialize a transaction log file,\
received an unexpected error. Check the accompanying ISAM error code\
for more detailed information on the cause. Typical causes include\
hardware errors and file permission problems.\
\
|
-381	Cannot grant to someone who has granted you the same privilege before.\
\
The privilege you are trying to grant is one that was first granted to\
you WITH GRANT OPTION. The user who made that grant is among the list\
of users in this present statement. For security reasons, you may not\
do a reciprocal grant. Rewrite the statement leaving out the name of\
your original patron. To see a list of the users to whom you may not\
grant, query systabauth as follows:\
\
SELECT grantor FROM systabauth WHERE grantee = USER\
\
|
-382	Same number of columns must be specified for view and select clause.\
\
In this VIEW statement, you have listed the names of the columns of the\
view. However, their number is different from the number of columns in\
the SELECT statement for the view. Check the punctuation of the two\
lists, and make sure that you have supplied a name for each item in the\
select list.\
\
|
-383	Need to specify view column names in the view definition.\
\
In this VIEW statement, you have not listed specific names for columns.\
That action is allowed when the SELECT statement selects only simple,\
named columns. However, the SELECT statement here selects one or more\
expressions. You must give names to these columns in a parenthesized\
list that follows the name of the view. Because you cannot give names\
for only some of the columns, you must list names for all.\
\
|
-384	Cannot modify non simple view.\
\
This statement attempts to modify (insert, delete, or update) rows in a\
view which does not have an appropriate INSTEAD OF trigger defined.\
Starting with version 9.40, you can define an INSTEAD OF trigger on a view.\
Without an INSTEAD OF trigger, this view is not modifiable because it is\
based on a SELECT statement that joins two or more tables or that selects\
calculated values or literal values. (You can DELETE from a view that\
selects from a single table even if some calculated values are\
selected.) Direct the statement against the actual\
table on which the view is based or define an INSTEAD OF\
trigger on the view to make it modifiable.\
\
|
-385	Data value out of range.\
\
This statement attempts to put data into a view that was defined WITH\
CHECK OPTION, so new data has to satisfy the tests in the WHERE clause\
in the view. However, one or more of the data values in this current\
statement does not meet that test, so the alteration was not performed.\
Roll back the current transaction. To see what tests new data must\
satisfy, display the definition of the view, as follows:\
\
SELECT seqno, viewtext FROM sysviews, systables\
        WHERE systables.tabname = 'viewname'\
           AND systables.tabid = sysviews.tabid\
        ORDER BY seqno\
\
|
-386	Column contains null values.\
\
This ALTER TABLE statement contains a MODIFY clause that assigns the\
NOT NULL attribute to an existing column. However, that column already\
contains one or more null values. The modification cannot be made until\
the null values have been deleted or updated to some nonnull value.\
\
|
-387	No connect permission.\
\
You cannot access the database that this statement requests because you\
have not been granted CONNECT privilege to it. Contact a person who has\
Database Administrator privilege to that database and ask to be granted\
CONNECT privileges to it.\
\
|
-388	No resource permission.\
\
If you issued a CREATE TABLE, CREATE INDEX, or CREATE PROCEDURE\
statement, you cannot execute this statement because your account has\
not been granted the RESOURCE privilege for this database. You need the\
RESOURCE privilege to create permanent tables, indexes on permanent\
tables, and procedures.\
\
If you issued a SET statement, START VIOLATIONS TABLE statement, or\
STOP VIOLATIONS TABLE statement, you cannot execute this statement\
because your account has not been granted the RESOURCE privilege for\
this database. You need the RESOURCE privilege to execute the SET\
statement for a constraint, trigger, or index defined on a table in the\
current database. You also need the RESOURCE privilege to execute the\
START VIOLATIONS TABLE or STOP VIOLATIONS TABLE statement on a base\
table in the current database.\
\
To recover from this error, contact a person who has the DBA privilege\
on this database and ask to be granted the RESOURCE privilege for the\
database.\
\
|
-388	No resource permission.\
\
If you issued a CREATE DATABASE statement in an 8.32 database server,\
you cannot execute this statement because you are not in the group\
specified in the ONCONFIG file parameter DBCREATE_GRP.\
\
To be included in the operating system group specified in DBCREATE_GRP,\
see your system administrator.\
\
|
-389	No DBA permission.\
\
This statement cannot be executed because you have not been granted DBA\
privilege for this database. Contact a person who has DBA privilege for\
the database and ask to be granted DBA privilege (or simply ask to have\
this statement executed for you).\
\
It is also possible that you received this message because you tried to\
register a user-defined routine that is written in a language for which you\
do not have usage privilege. If you do not have usage privilege for the\
language, ask one of the following users to grant this privilege to you:\
user informix or another user who has been granted the privilege with the\
option to grant the privilege to other users.\
\
|
-390	Synonym already used as table name or synonym.\
\
This CREATE SYNONYM statement names a synonym that is already in use.\
To see all the synonym and table names currently defined, query\
systables as follows:\
\
SELECT tabname, owner FROM systables WHERE tabid > 99\
\
|
-391	Cannot insert a null into column column-name.\
\
This statement tries to put a null value in the noted column. However,\
that column has been defined as NOT NULL. Roll back the current\
transaction. If this is a program, review the definition of the table,\
and change the program logic to not use null values for columns that\
cannot accept them.\
\
|
-392	System error - unexpected null pointer encountered.\
\
This internal error should not occur. If the error recurs, note\
all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-394	View view-name not found.\
\
The named view cannot be dropped as it does not exist. To see names of\
existing views, query systables as follows:\
\
SELECT tabname FROM systables WHERE tabtype = 'V'\
\
|
-395	The where clause contains an outer cartesian product.\
\
This query requests an outer join, but either the WHERE clause is missing\
in the query, or the conditions in the WHERE clause cause every row of the\
subordinate table to be selected for every row of the dominant table,\
resulting in a very large output. \
\
Review the query, and check that at least one condition in the WHERE clause\
relates each dominant-subordinate pair of tables in the query.\
\
|
-396	Illegal join between a nested outer table and a preserved table.\
\
This query requests an outer join, but the WHERE clause contains a\
condition that relates a nested subservient table to a preserved table\
that is not its immediate parent. This action is not supported. Review\
the query, and check that every condition that relates two tables is\
between a preserved table and its immediately subordinate table.\
\
|
-393	A condition in the where clause results in a two-sided outer\
join.\
\
This query requests an outer join, but one or more conditions in the WHERE\
clause interfere with the dominant-subordinate relationships between the\
joined tables in the FROM clause.\
\
Review the query, and verify that every condition that relates the joined\
tables is actually necessary and semantically correct.\
\
If an expression in the WHERE clause relates two subordinate tables, you\
must use parentheses around the joined tables in the FROM clause to\
enforce dominant-subordinate relationships. (Note: You cannot put a\
parenthesis directly after the FROM keyword.) The following example\
successfully returns a result:\
\
   SELECT c.company, o.order_date, i.total_price, m.manu_name\
      FROM customer c, OUTER (orders o, OUTER (items i, OUTER manufact m))\
         WHERE c.customer_num = o.customer_num\
            AND o.order_num = i.order_num\
            AND i.manu_code = m.manu_code;\
\
If you omit parentheses around the subordinate tables in the FROM clause,\
you must establish join conditions, or relationships, between the dominant\
table and each subordinate table in the WHERE clause. If a join condition is\
between two subordinate tables, the query will fail. The following example\
successfully returns a result:\
\
   SELECT c.company, o.order_date, c2.call_descr\
      FROM customer c, OUTER orders o, OUTER cust_calls c2\
         WHERE c.customer_num = o.customer_num\
            AND c.customer_num = c2.customer_num;\
\
Consider using the ANSI-SQL standard syntax for outer joins. For more\
information, refer to the IBM Informix Guide to SQL: Syntax.\
\
|
-397	System catalog <table-name> corrupted.\
\
This internal error should not occur. The database server has\
encountered something in one or more of the system catalog tables that\
violates integrity constraints.\
\
Run the oncheck utility if you are using IBM Informix Dynamic Server,\
IBM Informix Universal Server, or IBM Informix OnLine Dynamic Server. Run bcheck or\
secheck if you are using the IBM Informix SE database server. Run tbcheck if you\
are using the IBM Informix OnLine database server. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-398	Cursor manipulation must be within a transaction.\
\
An attempt to use an UPDATE or a DELETE WHERE CURRENT OF statement\
produces this error message. This statement would modify a table\
through a cursor. However, this database uses a transaction log. When\
that is the case, modifications made through a cursor must be placed\
within the bounds of a transaction.\
\
Review the program logic, and check that it executes a BEGIN WORK\
statement prior to this statement and that it ends the transaction at\
some reasonable point. If the program has to work with both databases\
that use transactions and those that do not, you can have it check the\
second element of the sqlwarn array of the SQL Communications Area.\
This area will contain the letter W after a DATABASE statement if the\
database has a transaction log, and a space if it does not.\
\
|
-399	Cannot access log file.\
\
This query refers to a table named syslog. A row in the systables\
catalog has syslog in the tabname column, but it is only a convenient\
place to store the pathname to the transaction-log file. Under\
IBM Informix SE, a table named syslog cannot exist in a database with\
logging. (In general, you should avoid table names that start with\
sys-, and syslog is not allowed.)\
\
|
-400	Fetch attempted on unopen cursor.\
\
This FETCH statement names a cursor that has never been opened or has\
been closed. Review the program logic, and check that it will open the\
cursor before this point and not accidentally close it. Unless a cursor\
is declared WITH HOLD, it is automatically closed by a COMMIT WORK or\
ROLLBACK WORK statement.\
\
|
-401	Fetch attempted on NULL cursor.\
\
This FETCH statement passed a cursor data structure that is invalid or\
that is a null pointer. Possibly the cursor has been freed with the FREE\
statement, or possibly an automatic re-prepare has been attempted while \
opening the cursor but that operation failed, leaving the cursor unavailable,\
or possibly the cursor data structure has been overwritten in memory.\
\
Version 5.0 or later database servers do not return this error code.\
See errors -267 and -404.\
\
|
-402	Address of a host variable is NULL.\
\
Review the way the program constructs the sqlda and related data\
structures; somehow it is setting up a null pointer. The error might be \
caused by using a row or collection host variable without having executed\
the necessary ALLOCATE statement.\
\
If the program is in IBM Informix 4GL or another language in which the sqlda \
is not constructed directly by the program, or if this statement refers only\
to host variables by name, this error should not occur. If the error\
recurs, note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-403	The size of a received row disagrees with the expected size.\
\
This internal error indicates a problem in the communication between\
the database server and the library functions that call it. Check that\
your program is at the same software level as the database server in\
use. If the error recurs, note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-404	The cursor or statement is not available.\
\
One of the following four situations occurred:\
\
You used a statement that names a cursor that was released with the\
FREE statement or that was released during a failed automatic re-prepare.\
Review the program logic and check that the cursor specified is declared \
and opened, but not freed, prior to reaching this statement.\
\
If the error occurred on a command that specifies a variable rather than a\
cursor, the statement was not prepared before you tried to execute it.\
\
The cursor or statement is not available because the connection to the server\
does not exist or was lost.\
\
The person who created this table has not granted Update privilege to\
your account name or to the public. The owner of the table or the DBA\
must grant this privilege before you can update a row in this table.\
\
|
-405	The Address of a host variable is not properly aligned.\
\
Review the way the program constructs the sqlda and related data\
structures; somehow it is setting up a pointer that is not word\
aligned. Also, make sure that all host variables are aligned on proper\
address boundaries for their types. If the program is in IBM Informix 4GL\
or another language in which the programmer has no control over storage\
alignments, this error should not occur. If the error recurs,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-406	Memory allocation failed.\
\
Something in the current statement required the allocation of memory\
for data storage, but the memory was not available. Several things can\
cause this error. For example, your application has a memory leak, you\
are asking for more resources than the system is configured to allow,\
or a problem with UNIX requires that you reboot the system. On a client PC,\
if the INFORMIXDIR environment variable or some GLS file is missing,\
a connection attempt fails with this error message.\
\
Rollback the current transaction. Look for ways to make this statement\
simpler or move less data. On UNIX, talk with the system administrator\
to solve memory problems or to look for ways to make the operating system\
give this program more virtual memory in which to run. On Windows, exit\
to the operating-system command line, free some disk space, and resubmit\
your program. On a client PC, make sure that the INFORMIXDIR environment\
variable is set and that all GLS files are available.\
\
|
-407	Error number zero received from the sqlexec process.\
\
This internal error indicates a problem in the communication between the\
database server and the library functions that call it. Make sure that your\
program software is compatible with the database engine in use. If the error\
recurs, note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-409	Sqlexec was not found or was not executable by the current user.\
\
Your application contacts the database server process while it starts\
up. This action uses the value in the SQLEXEC environment variable (for\
database server versions prior to 6.0); it should point to one of two\
executable files: sqlexec for IBM Informix SE or sqlturbo for\
IBM Informix OnLine (versions prior to 6.0). Ordinarily these files will\
reside in the lib subdirectory of the directory that the INFORMIXDIR\
environment variable names. Check that your SQLEXEC environment\
variable is set up properly and that your account has access to these\
directories and files.\
\
|
-408	Invalid message type received from the sqlexec process.\
 \
This internal error indicates a problem in the communication between the\
database server and the library functions that call it. Make sure that\
your program software is compatible with the database engine in use.\
\
This error can also occur if the CSM option is enabled on the database\
server side but not on the client application side, or vice versa. If you\
want to use a CSM, make sure that the CSM option is set in the sqlhosts\
file for both the database server and client application.\
\
This error can also occur if the confidentiality option of the CSM is\
enabled on the database server side but not on the client application\
side, or vice versa. If you want to use the confidentiality option of the\
CSM, make sure that the confidentiality option is set for both the\
database server and client application. Check your sqlhosts file and CSS\
configuration file.\
\
If the error recurs, note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
|
-410	Prepare statement failed or was not executed.\
\
This EXECUTE statement refers to a statement id that has not been\
prepared. Either no PREPARE statement was done, or one was done but\
returned an error code. Review the program logic to ensure that a\
statement is prepared and the PREPARE return code is checked. A\
negative error code from PREPARE usually reflects an error in the\
statement being prepared.\
\
|
-411	Cannot specify both host variables and descriptor.\
\
This statement has a USING DESCRIPTOR clause, but it also refers to a\
cursor that was declared with host variables (that is, with\
SELECT...INTO or INSERT using variables in the VALUES clause). The\
purpose of both the descriptor structure and host variable names is to\
specify the location of the data values, and only one method may be\
used. Review the declaration of the cursor, and settle on a single\
method of specifying the location of data values.\
\
|
-412	Command pointer is NULL.\
\
This statement (probably an EXECUTE or DECLARE) refers to a dynamic SQL\
statement that has never been prepared or that has been freed. Review\
the program logic to ensure that the statement has been prepared, the\
PREPARE did not return an error code, and the FREE statement has not\
been used to release the statement before this point.\
\
|
-413	Insert attempted on unopen cursor.\
\
This INSERT statement names a cursor that has never been opened or that\
has been closed. Review the program logic, and check that it will open\
the cursor before this point and not accidentally close it. An insert\
cursor is automatically closed by a COMMIT WORK or ROLLBACK WORK\
statement.\
\
|
-414	Insert attempted on NULL cursor.\
\
This PUT statement specifies a cursor that is invalid. Possibly the\
cursor has been freed with the FREE statement, or possibly an automatic \
re-prepare has been attempted while opening the cursor but that operation\
failed, leaving the cursor unavailable, or possibly the cursor data \
structure has been overwritten in memory.\
\
|
-415	Data conversion error.\
\
The database server is unable to convert between a program variable and\
a database column. It performs automatic data conversion in many cases\
but could not in this case. For instance, a character string will be\
converted to a numeric type so long as the string contains the digits\
of a valid number, or a float or decimal number will be converted to\
integer so long as the receiver has enough precision for the value.\
Review this statement, and inspect each program variable that does not\
have the same data type as the matching database column.\
\
|
-416	USING option with open statement is invalid for insert cursor.\
\
This OPEN statement refers to a cursor that was declared for an INSERT\
statement. The USING clause of the OPEN is not appropriate in this\
case; it is only used to specify the variables that are used with a\
SELECT statement. Review the program to ensure that the correct cursor\
has been used in this statement. If it has, and if the INSERT statement\
is written as part of the DECLARE statement, you can name the host\
variables directly in it. If the INSERT statement has been prepared,\
you can specify the host variables in a FROM clause in the PUT\
statement.\
\
|
-417	FLUSH can only be used on an insert cursor.\
\
This FLUSH statement refers to a cursor that is associated with a\
SELECT statement, not an INSERT statement. FLUSH is only appropriate\
with insert cursors. Review the program to ensure that the correct\
cursor has been named.\
\
|
-418	NULL SQLDA descriptor or host variable list encountered.\
\
Review the way the program constructs the sqlda and related data\
structures; somehow it is setting up a null pointer. If the program is\
in IBM Informix 4GL or another language in which the sqlda is not\
constructed directly by the program, or if this statement only refers\
to host variables by name, this error should not occur. If the error\
recurs, note all circumstances and contact Technical\
Support at tsmail@us.ibm.com.\
\
|
-419	SQLDATA pointer in SQLDA or host variable is null.\
\
Review the way the program constructs the sqlda and related data\
structures; somehow it is setting up a null pointer. If the program is\
in IBM Informix 4GL or another language in which the sqlda is not\
constructed directly by the program, or if this statement only refers\
to host variables by name, this error should not occur. If the error\
recurs, note all circumstances and contact Technical\
Support at tsmail@us.ibm.com.\
\
|
-420	Cannot execute remote sqlexec.\
\
Your application program is starting up and trying to make contact with\
the database server process in another computer. It does this using the\
contents of the SQLHOST environment variable. Check the SQLHOST\
variable, and verify that the IBM Informix NET or IBM Informix STAR service has\
been started in the other computer.\
\
|
-421	Unknown service for execution of remote sqlexec.\
\
Your application program is starting up and trying to make contact with\
a database server in a different computer. It uses information from the\
file /etc/services under the service entry sql, but this file was not\
found. Contact the person who installed IBM Informix NET on your system.\
\
|
-422	Flush attempted on unopen cursor.\
\
This FLUSH statement names a cursor that has never been opened or has\
been closed. Review the program logic to ensure that it will open the\
cursor before this point and not accidentally close it. An insert\
cursor is automatically closed by a COMMIT WORK or ROLLBACK WORK.\
\
|
-423	A FETCH CURRENT was attempted with no current row.\
\
This FETCH statement asks for the current row, but none exists. Either\
the cursor was just opened, or the previous fetch returned an error\
code, perhaps because it was at the end of the data. Review the program\
logic, and check that it uses a FETCH NEXT statement or other FETCH\
operation to establish a current row before it attempts this\
statement.\
\
|
-424	Cursor already declared from this prepared statement.\
\
This DECLARE statement associates a cursor with the name of a prepared\
statement. However, another DECLARE statement has already been\
executed, and it associates a different cursor with the same statement\
id. This action is not supported; a given statement can be associated\
with only one cursor. Check all the DECLARE statements in the program,\
and check that they all refer to unique statements.\
\
This error message should not appear for Version 5.0 and later.\
\
|
-425	Database is currently opened by another user.\
\
Another user has opened the requested database in exclusive mode, or\
you have more than one connection to the database server. Repeat the\
statement after a short delay or when the database is known to be idle.\
\
|
-426	Unknown values have already been supplied.\
\
This internal error should not occur. If this error recurs, note\
all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-427	Bind count routine called with a different count.\
\
This internal error should not occur. If you can find no direct cause\
for the error, note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
|
-428	Bind routine called too many times.\
\
This internal error should not occur. If you can find no direct cause\
for the error, note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
|
-429	Indicator variables should be 2-byte integers.\
\
This statement names as an indicator variable, a host variable that was\
not declared as a small integer. The value returned to an indicator\
variable is a small integer value. Review the statement, especially the\
use of host variables as indicator variables. Make sure the names of\
indicator variables are spelled correctly and that they are properly\
declared. In a 4GL program, this error should not occur. If the error\
recurs, note all circumstances and contact Technical\
Support at tsmail@us.ibm.com.\
\
|
-430	Type integer does not match size.\
\
This internal error indicates a problem in the communication between\
the database server and the library functions that call it. Check that\
your program is at the same software level as the database server in\
use. If the error recurs, note all circumstances and contact Technical\
Support at tsmail@us.ibm.com.\
\
|
-431	Type float does not match size.\
\
This internal error indicates a problem in the communication between\
the database server and the library functions that call it. Check that\
your program is at the same software level as the database server in\
use. If the error recurs, note all circumstances and contact Technical\
Support at tsmail@us.ibm.com.\
\
|
-432	Type date does not match size.\
\
This internal error indicates a problem in the communication between\
the database server and the library functions that call it. Check that\
your program is at the same software level as the database server in\
use. If the error recurs, note all circumstances and contact Technical\
Support at tsmail@us.ibm.com.\
\
|
-433	Type money does not match size.\
\
This internal error indicates a problem in the communication between\
the database server and the library functions that call it. Check that\
your program is at the same software level as the database server in\
use. If the error recurs, note all circumstances and contact Technical\
Support at tsmail@us.ibm.com.\
\
|
-434	Type decimal does not match size.\
\
This internal error indicates a problem in the communication between\
the database server and the library functions that call it. Check that\
your program is at the same software level as the database server in\
use. If the error recurs, note all circumstances and contact Technical\
Support at tsmail@us.ibm.com.\
\
|
-435	Time-out value must be -1 or greater.\
\
You provided an incorrect time-out value for your callback\
function/routine in IBM Informix ESQL/C or ESQL/COBOL. Check that your\
time-out value is -1 or greater.\
\
|
-436	Call back function must be defined when time-out value is 0 or greater.\
\
You did not provide a callback function with your time-out value. Make\
sure that you provide both.\
\
|
-437	Connection must be established before registering callback function.\
\
You attempted to register a callback function before you connected to a\
database server. You must first connect to a database server and then\
register your callback function.\
\
|
-438	Call back function must be NULL if time-out value is -1.\
\
You provided an incorrect value to unregister your callback function.\
Pass a null value, not a function pointer, to the callback function.\
\
|
-439	Database server is currently processing an SQL task.\
\
You attempted to call an SQL routine or attempted to execute an SQL\
statement within a signal handling function/routine or a callback\
function/procedure. Use only the sqldone() and sqlbreak() library\
functions inside your IBM Informix ESQL/C callback function. Use only the\
ECO-SQD and ECO-SQB library routines inside your ESQL/COBOL callback\
procedure. In addition, if you want to unregister your callback\
function in IBM Informix ESQL/C, you can invoke the sqlbreakcallback()\
callback registration function within your callback procedure. If you\
want to unregister your callback procedure in ESQL/COBOL, you can\
invoke the ECO-SQBCB callback registration routine within your callback\
procedure.\
\
|
-440	Cannot update more than one non-Informix DBMS within a\
transaction.\
\
In the application, an attempt was made to update data at more than one\
target DBMS accessed through a gateway. In a distributed transaction,\
at most one target DBMS accessed through a gateway can be updated.\
\
You need to rewrite the application so that it updates at\
most one DBMS accessed through a gateway in a single distributed\
transaction.\
\
|
-441	Possible inconsistent data at the target DBMS (\
) due to\
an aborted commit.\
\
Distributed commit processing failed due to a communication error,\
site failure, gateway failure, or other error with the target DBMS\
accessed through the gateway. Updates at all sites participating in\
the transaction have been rolled back with the possible exception of\
the target DBMS. The target DBMS might have committed its updates if\
the failure occurred after the commit message was processed by the\
target DBMS.\
\
If the updates on the target DBMS were committed, then the updates\
should be rolled back manually. Contact the target DBMS system\
administrator.\
\
|
-450	Illegal ESQL locator, or uninitialized blob variable in 4GL.\
\
A BYTE or TEXT host variable used in this statement is not valid. If\
this is a 4GL program, the variable has not been initialized by use of\
the LOCATE statement, or was freed after being located. Review the\
program logic to ensure all blob variables are located before use. If\
this is ESQL/C, the locator structure is invalid or uninitialized.\
Check that all locator structures are allocated and filled in before\
use.\
\
|
-451	Locator buffer size too small.\
\
The locator structure provided for a BYTE or TEXT value in this\
statement specifies a memory buffer that is smaller than the value (in\
the loc_bufsize field). The actual size is in loc_indicator. No data\
was transferred. Revise the program to use a larger buffer, to locate\
the value in a file instead of memory, or to pass the value in segments\
through a user-provided read function. Alternatively, you can specify\
a substring of the value in the SELECT statement. If this is a 4GL\
program, this error should not occur. If the error recurs, note\
all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-452	'loc_open()' failed.\
\
The loc_open() function provided in the locator structure for a BYTE or\
TEXT value in this statement was called and returned a negative return\
code. When the value is located using user-supplied functions\
(loc_loctype contains LOCUSER), this function is part of the program,\
and you have to diagnose its problems yourself. When the value is\
located in a file (loc_loctype contains LOCFILE or, in a 4GL program,\
the variable has been located in a file), this error indicates that the\
system-supplied loc_open() function was not able to open the file.\
Possibly the file does not exist, you do not have read permission for\
the file, or too many files are open.\
\
|
-453	'loc_close()' failed.\
\
The loc_close() function provided in the locator structure for a BYTE\
or TEXT value in this statement was called and returned a negative\
return code. When the value is located using user-supplied functions\
(loc_loctype contains LOCUSER), this function is part of the program,\
and you have to diagnose its problems yourself. When the value is\
located in a file (loc_loctype contains LOCFILE or, in a 4GL program,\
the variable has been located in a file), this error indicates that the\
system-supplied loc_close() function was not able to close the file.\
\
|
-454	'loc_read()' failed.\
\
The loc_read() function provided in the locator structure for a BYTE or\
TEXT value in this statement was called and returned a negative return\
code. When the value is located using user-supplied functions\
(loc_loctype contains LOCUSER), this function is part of the program\
and you have to diagnose its problems yourself. When the value is\
located in a file (loc_loctype contains LOCFILE or, in a 4GL program,\
the variable has been located in a file), this error indicates that the\
system-supplied loc_read() function was not able to read from the\
file.\
\
|
-455	'loc_write()' failed.\
\
The loc_write() function provided in the locator structure for a BYTE\
or TEXT value in this statement was called and returned a negative\
return code. When the value is located using user-supplied functions\
(loc_loctype contains LOCUSER), this function is part of the program\
and you have to diagnose its problems yourself. When the value is\
located in a file (loc_loctype contains LOCFILE or, in a 4GL program,\
the variable has been located in a file), this error indicates that the\
system-supplied loc_write() function was not able to write to the file.\
Possibly the disk is full, you do not have write permission for the\
disk, or a hardware error occurred.\
\
|
-456	Indicator value cannot fit in host variable.\
\
This internal error indicates a problem in the communication between\
the database server and the library functions that call it. Check that\
your program is at the same software level as the database server in\
use. If the error recurs, note all circumstance, and contact Technical\
Support at tsmail@us.ibm.com.\
\
|
-457	Database server terminated unexpectedly.\
\
The database server process or thread with which your application\
program was working has terminated. The DBA might have shut the system\
down. The next most likely cause is an internal error. Look for\
operating-system messages that might give more information. If the\
error recurs, note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
Check the ISAM error code that is returned with this error. If it\
is -129, the database server has not terminated but simply reached\
a limit on the number of concurrent user sessions (see the explanation\
of error -129).\
\
|
-458	Long transaction aborted.\
\
The database server ran out of log space in which to record this\
transaction. A transaction that is not fully recorded cannot be rolled\
back. To preserve database integrity, the operating system ended the\
transaction and rolled it back automatically. All changes made since\
the start of the transaction have been removed. Terminate the\
application, and replan it so that it modifies fewer rows per\
transaction. Alternatively, contact the database server administrator\
to discuss increasing the number or the size of the logical logs. Be\
prepared to talk about the number of rows being updated or inserted and\
the size of each row.\
\
-459	The database server was shut down.\
\
The database server instance that your application was using has been\
shut down by its operator. Your current transaction will be rolled back\
automatically when the database server starts up again. Rerun the\
application at that time.\
\
|
-460	Statement length exceeds maximum.\
\
The statement text in this PREPARE, DECLARE, or EXECUTE IMMEDIATE\
statement is longer than the database server can handle. The actual\
limit differs with different implementations, but it is always\
generous, in most cases up to 32,000 characters. Review the program\
logic to ensure that an error has not caused it to present a string\
that is longer than intended (for example, by overlaying the null\
string terminator byte in memory). If the text has the intended length,\
revise the program to present fewer statements at a time.\
\
|
-462	File close error.\
\
This statement reads a value from a BYTE or TEXT column into a file.\
The database server copied the data to the file but got an\
operating-system error when it closed the file. Check the accompanying\
ISAM error code for more information, and look for operating-system\
messages. Typical causes include lack of disk space and hardware\
errors.\
\
|
-463	File read error.\
\
This statement writes a value into a BYTE or TEXT column from a file.\
The database server got an operating-system error while reading the\
file. Check the accompanying ISAM error code for more information, and\
look for operating-system messages.\
\
|
-461	File open error.\
\
The database server could not open a file required to execute this\
statement. Sometimes this is a general error, possibly referring to a\
message file that the database server cannot find. At other times this\
error occurs because the locator (blob) structure field loc_loctype was\
set to LOCFNAME, but the database server could not open the file using\
the pathname in loc_fname and the flags in loc_oflags. Any of the\
following conditions can cause the database server to report this error:\
\
*  An environment variable setting is missing.\
\
*  Not enough disk space is available for opening the file.\
\
*  A file permission problem exists.\
\
*  The limit on the number of open files was reached.\
\
*  The database server could not access a blob of type LOCFNAME.\
\
*  The database server is on a different machine from the client.\
\
*  The statement transfers a value between a file and a BYTE or TEXT\
   column.\
\
*  The statement attempts to drop a database when a required file is not\
   available.\
\
Make sure your environment variables and file permissions are set\
correctly. For more information, check for any accompanying ISAM error\
code or operating-system message.\
\
|
-464	File write error.\
\
This statement reads a value from a BYTE or TEXT column into a file.The\
database server got an operating-system error while writing the data.\
Check the accompanying ISAM error code for more information, and look\
for operating-system messages. Typical causes include lack of disk\
space and hardware errors.\
\
|
-465	No more memory for locator buffer.\
\
This query returns a BYTE or TEXT value that is located in memory, and\
the locator structure asked (by setting -1 in loc_bufsize) that the\
database server allocate the memory. It was unable to get the necessary\
memory for a buffer. If you can use operating-system methods to\
allocate more data space memory to your program, do so and run it\
again. Alternatively, locate the value in a file, or use a substring to\
select the value in portions. If this is a 4GL program, this error\
should not occur. On DOS systems, exit to the operating-system command\
line, free some disk space, and resubmit your program. If the error\
recurs, note all circumstances and contact Technical\
Support at tsmail@us.ibm.com.\
\
|
-466	File length error.\
\
This statement stores a value in a BYTE or TEXT column from a file. The\
locator structures specified a length for the data in loc_locsize, but\
the database server found end of file before it had read that much\
data. Review the program to ensure that the input file was properly\
positioned and that the correct length was specified. Specify a length\
of -1 if the file should be read to its end. If this is a 4GL program,\
this error should not occur. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-467	Indicator object is missing.\
\
This program was compiled with the -icheck flag, and the current SQL\
statement did return a truncated or null value, for which an indicator\
would normally be set, to a host variable for which no indicator\
variable was specified. Revise the program to use indicator variables.\
\
|
-468	Cannot obtain user id from system: unable to start database server.\
\
Your application is trying to open communications to a database server.\
As part of this action, it has to read your user ID from the system\
password file, and it failed to do this. Look for operating-system\
error messages that might give more specific information. Consult with\
a system administrator to ensure that the file of user IDs is readable\
to all users.\
\
|
-469	This descriptor does not exist.\
\
The name of the system descriptor area that is specified does not exist\
in the list of system descriptor areas, so it has not been allocated.\
You must execute the ALLOCATE DESCRIPTOR statement to allocate this\
descriptor name before you use it.\
\
|
-470	The value of occurrence must be greater than 0.\
\
If you include the WITH MAX occurrences clause in the ALLOCATE\
DESCRIPTOR statement, you must specify a value of occurrences that is\
greater than zero. Change the value of occurrences to a positive\
integer, and execute the ALLOCATE DESCRIPTOR statement again.\
\
|
-471	An invalid descriptor name has been used.\
\
This error is generated if the name of the SQL descriptor is either an\
empty string or an uninitialized host variable. Descriptor names follow\
the same naming rules as identifiers. Check the name of the descriptor,\
and verify that it has been set with the SET DESCRIPTOR statement,\
allocated with the ALLOCATE DESCRIPTOR statement, or otherwise\
initialized.\
\
|
-472	Occurrence value is out of range.\
\
Change the value of the COUNT statement so that it is less than or\
equal to the occurrences and greater than zero, and try again.\
\
|
-473	The specified data type is not a X/Open standard type.\
\
This error is generated when a GET DESCRIPTOR or a SET DESCRIPTOR\
statement is executed in X/Open mode, and the value for the type field\
is not an X/Open standard type. Check the X/Open codes for data types\
again, and make sure that the correct type is being used.\
\
|
-474	Unknown field type.\
\
An unknown field type has been requested. Check that you are using one\
of the valid field types in X/Open mode, and try again. The valid field\
types are TYPE, LENGTH, PRECISION, SCALE, NULLABLE, INDICATOR, DATA,\
and NAME.\
\
|
-475	In a GET statement, if DATA is null, then INDICATOR must be specified.\
\
This X/Open rule indicates that you must request the INDICATOR value in\
the GET DESCRIPTOR statement when DATA is null.\
\
|
-476	The LENGTH field must be specified when the type is SQLCHAR.\
\
When you use a SET DESCRIPTOR statement, and TYPE is set to SQLCHAR,\
the LENGTH field must also be specified and set in the same SET\
DESCRIPTOR statement.\
\
|
-477	Buffer is too small.\
\
In a GET DESCRIPTOR statement, the buffer (the character host variable)\
that is specified to store the NAME entry is too small. Increase the\
buffer size, and call the GET DESCRIPTOR statement again. This error\
message also is displayed when the host variable is a FILE type, and\
the buffer used to store its name is too small.\
\
|
-478	User must specify TYPE.\
\
In the initial state, when you execute a SET DESCRIPTOR statement, you\
must specify TYPE as one of the fields to be set. Set the TYPE field in\
the SET DESCRIPTOR statement, and execute it again.\
\
|
-479	The number of DESCRIBED columns is greater than the allocated space.\
\
The number of columns in the table is larger than the allocated\
descriptor. Use the ALLOCATE DESCRIPTOR statement to reallocate a\
larger occurrence value, and try the DESCRIBE statement again.\
\
|
-480	A descriptor with the same name already exists.\
\
A system descriptor area with the same name has already been allocated,\
so this descriptor name is not unique. Change the name of this\
descriptor in the ALLOCATE DESCRIPTOR statement so that the descriptor\
is unique, and execute the statement again.\
\
|
-481	Invalid statement name or statement was not prepared.\
\
The statement has not been prepared, or the format of the statement name\
is not valid. A valid statement name does not exceed the maximum length,\
begins with a letter or underscore, does not contain any blanks or\
nonalphanumeric characters except underscores and, in IBM Informix Dynamic\
Server 9.2x or later, dollar-sign characters.\
\
The maximum length for statement names depends on the database server. In\
IBM Informix Dynamic Server 9.2x or later, the maximum length is 128 characters.In \
other IBM Informix database servers, the maximum length is 18 characters.\
\
|
-482	Invalid operation on a non-SCROLL cursor.\
\
You cannot issue a FETCH PRIOR, FETCH FIRST, FETCH LAST, FETCH CURRENT,\
FETCH RELATIVE n, or FETCH ABSOLUTE n statement with a non-scroll\
cursor. To do so, you must first declare the cursor as a scroll\
cursor.\
\
|
-483	SQL descriptor's name is too long. Limit is 128 characters.\
\
The maximum length for SQL descriptor names depends on the database server.\
In IBM Informix Dynamic Server 9.2 or later, the maximum length is 128 characters. In \
other Informix database servers, the maximum length is 18 characters.\
\
|
-484	Statement/cursor's name must be between 1 to 128 characters.\
\
The maximum length for statement and cursor names depends on the database\
server. In IBM Informix Dynamic Server, the maximum length is 128 characters.\
In other Informix database servers, the maximum length is 18 characters.\
\
|
-485	Number of host variables does not match SELECT list.\
\
This error can occur only if your database is ANSI compliant. The error\
indicates that the number of host variables in an ESQL statement is not\
the same as the number of values that the database server returns. In\
addition, a warning flag is placed in the third element of the sqlwarn\
structure of sqlca.\
\
The execution of the second statement in the following ESQL/C example\
returns this error:\
\
$create table mytab (i integer, f float)\
$select * into :var1 from mytab; --error\
\
If your database is not ANSI compliant, this and similar statements\
complete without error, and the values of the host variables are set in\
sequence to their respective returned values. If the number of returned\
values is smaller than the number of host variables, the remaining host\
variables are undefined. As with an ANSI-compliant database, a warning\
flag is placed in the third element of the sqlwarn structure of sqlca.\
\
|
-486	Illegal data type found during data conversions.\
\
The data type found in the system descriptor sqlvar entry is either\
invalid or uninitialized. You cannot use the GET DESCRIPTOR statement\
to get a value from an uninitialized sqlvar.\
\
|
-487	A cursor can only be declared as static or dynamic.\
\
The specified SQL statement requires you to declare a cursor as static\
or dynamic. Declare the cursor as static or dynamic, depending on which\
type of cursor is required, and retry the specified operation.\
\
|
-488	Invalid operation on cursor.\
\
An invalid operation has been attempted on a cursor. A cursor declared\
for a SELECT statement cannot be used in a PUT statement. Similarly, a\
cursor declared for an INSERT statement cannot be used in a FETCH\
statement. Check the program, and try again.\
\
|
-489	Exception number out of bounds.\
\
An exception number was requested that was either less than 1 or\
greater than the number of diagnostic entries in the diagnostic area.\
\
|
-490	Database was created without NLS functionality.\
\
You created a database that lacked NLS functionality.\
\
|
-491	DBNLS not set (LC_COLLATE must be string_value).\
\
Set the DBNLS environment variable to an appropriate value. Make sure\
LC_COLLATE is set to the specified string_value.\
\
|
-492	LANG or LC_COLLATE environment variable invalid.\
\
You specified an invalid value for a LANG or LC_COLLATE environment\
variable.\
\
|
-493	DBNLS not set (LC_CTYPE must be string_value).\
\
Set the DBNLS environment variable to an appropriate value. Make sure\
LC_TYPE is set to the specified string_value.\
\
|
-494	LANG or LC_CTYPE environment variable invalid.\
\
You specified an invalid value for a LANG or LC_CTYPE environment\
variable.\
\
|
-495	LANG or LC_MONETARY environment variable invalid.\
\
You specified an invalid value for a LANG or LC_MONETARY environment\
variable.\
\
|
-496	LANG or LC_NUMERIC environment variable invalid.\
\
You specified an invalid value for a LANG or LC_NUMERIC environment\
variable.\
\
|
-497	LANG or LC_TIME environment variable invalid.\
\
You specified an invalid value for a LANG or LC_TIME environment\
variable.\
\
|
-498	Bad cixtomsg file. Check installation.\
\
The version of the cixtomsg file, which holds the mapping table of\
SQLCODE to SQLSTATE values, is invalid. The cixtomsg file is located\
in the directory $INFORMIXDIR/msg. Check the date and size of the\
file. If the error recurs, note all circumstances and contact Technical\
Support at tsmail@us.ibm.com.\
\
|
-499	The operation causes a rowsize to exceed the allowable limit\
(32767).\
\
The maximum size of a table record is 32,767 bytes. Check the summary sizes\
of all the fields in the table. Make sure that the operation you have\
attempted does not lead to exceeding the maximum row size.\
\
|
-500	Clustered index index-name already exists in the table.\
\
A table may be clustered on only one index at a time. This table is\
already clustered on the index whose name is shown. Before you can\
cluster on another index, you must execute ALTER INDEX index-name TO\
NOT CLUSTER. To see which tables are clustered on which indexes, query\
sysindexes and systables as follows:\
\
SELECT tabname, idxname FROM systables T, sysindexes X\
        WHERE T.tabid = X.tabid AND X.clustered = 'C'\
\
|
-501	Index index-name is already not clustered.\
\
The table is no longer clustered on this index (if it ever was). Make\
sure that this is the index you meant; if so, you do not need to alter\
this index. For a way to see which tables are clustered, see the\
discussion of error -500.\
\
|
-502	Cannot cluster index.\
\
While the database server was building a new copy of the table with\
rows in clustered sequence, it got an unexpected error. Check the\
accompanying ISAM error code for more information. Typical causes\
include a shortage of disk space.\
\
|
-503	Too many tables locked.\
\
This database server in this host operating system has a limit on the\
number of tables that can be locked at one time. It was unable to lock\
the table you requested. Roll back the current transaction. Then\
redesign the operation to lock fewer tables, to use row-level locking,\
or to open the database in exclusive mode.\
\
|
-504	Cannot lock a view.\
\
This LOCK TABLE statement cannot be carried out because the table\
specified is really a view. Only real tables can be locked. Roll back\
the current transaction. Then redesign the operation to work against\
the real tables on which the view is based, or open the database in\
exclusive mode.\
\
|
-505	Number of columns in UPDATE does not match number of VALUES.\
\
This UPDATE statement uses a SET clause in which a list of column names\
is set equal to a list of expressions or to a SELECT statement. The\
number of columns on the left of the equal sign is not the same as the\
number of data values produced on the right. Roll back the current\
transaction. Then rewrite this statement. If a list of expressions is\
used, check the punctuation to ensure that each expression is distinct.\
If a SELECT statement is used, review it to see how many columns it\
returns.\
\
|
-506	Do not have permission to update all columns.\
\
Your account has been granted the privilege of updating specific\
columns, but this UPDATE statement updates all columns or columns for\
which you do not have the privilege. Contact the owner of the table or\
someone with Database Administrator privilege on this database, and ask\
to be granted full UPDATE privilege. For a way to list table owners,\
see the discussion of error -313.\
\
|
-507	Cursor cursor-name not found.\
\
The cursor that is named in the WHERE CURRENT OF clause in this UPDATE\
or DELETE statement does not exist. Review the spelling of the name. If\
it is as you intended, check the DECLARE statement to ensure that it\
has been executed. Also make sure that the cursor has not been freed\
with the FREE statement or during a failed automatic re-prepare attempt.\
\
|
-508	Cannot rename a temporary table.\
\
This RENAME TABLE statement cannot be executed because the specified\
table is temporary. You cannot rename a temporary table. Review the\
spelling of the table name. If it is as you intended, drop it, and\
create it again under a different name.\
\
|
-509	Cannot rename a column in a temporary table.\
\
This RENAME COLUMN statement cannot be executed because the specified\
table is temporary. You cannot rename a column in a temporary table.\
Review the spelling of the table name. If it is as you intended, drop\
it, and create it again with different columns.\
\
|
-510	Cannot create synonym for temporary table table-name.\
\
This CREATE SYNONYM statement cannot be executed because the specified\
table is temporary. Review the spelling of the table name. If it is as\
you intended, redesign the application. Either make the table\
permanent, or do not use a synonym.\
\
|
-511	Cannot modify system catalog table-name.\
\
You are not allowed to update, insert, or delete rows in this table. If\
you are absolutely sure that you must do so, sign on as user informix.\
That user account can modify most system-catalog tables. However, this\
very risky practice is not recommended unless you are specifically\
instructed by Technical Support at tsmail@us.ibm.com.\
\
|
-512	No References privilege on the referenced columns.\
\
You do not have References privilege on the referenced columns. The\
owner of the referenced table or a user who has References privilege\
with the grant option on that table can grant you this privilege using\
the GRANT statement.\
\
|
-513	Statement not available with this database server.\
\
You cannot do an xa_open() execution if another database is already open.\
Make sure that you have closed any open databases before executing xa_open().\
\
|
-514	Only DBA can create, drop, or grant for another user.\
\
This data definition statement specifies a table, view, index, or\
synonym that is owned by another user or grants a privilege as another\
user. Any of these things requires Database Administrator privilege,\
which you do not have on this database. If you intended to work on\
objects that you own, review the punctuation of the statement. At some\
point in it, you have qualified a name with the user ID of another\
account. Otherwise, get a DBA to grant you DBA privilege or to perform\
this operation for you.\
\
|
-515	Constraint constraint-name has already been dropped.\
\
You are trying to drop a constraint that has already been dropped in\
the same ALTER TABLE statement.\
\
|
-516	System error - temporary output file not created yet.\
\
This internal error indicates a problem in the communication between\
the database server and the library functions that call it. Check that\
your program is at the same software level as the database server in\
use. If the error recurs, note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-517	The total size of the index is too large or too many parts in\
index.\
\
All database servers have limits on the number of columns that can be\
included in an index and on the total number of bytes in a key (the sum\
of the widths of the columns). This CREATE INDEX statement would exceed\
that limit for this database server. IBM Informix Dynamic Server and\
IBM Informix Universal Server allow 16 key parts (columnar or functional) and\
a width of 390 bytes on a 2K page platform. On 4K page platforms or using a \
non-default page size allows greater than 390 bytes for the width of indexed \
columns. IBM Informix SE supports 8 columns and a width of 126 bytes.  Other \
Informix database servers allow 16 columns and 255 characters.\
\
|
-518	Child constraint constraint-name not found.\
\
If this internal error recurs, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-519	Cannot update column to illegal value.\
\
One of the values in this UPDATE statement is based on an expression\
that is in error. Check each expression in the SET clause for validity.\
Look in particular at uses of built-in functions such as LENGTH and\
DATE.\
\
|
-520	Cannot open database tblspace.\
\
The database server cannot locate the disk partition in which it has\
stored a table that is referenced in this command. Contact the database\
server administrator to find out what the problem is. Possibly the\
chunk that contains this tblspace has been taken off-line.\
\
|
-521	Cannot lock system catalog table-name.\
\
You cannot lock any of the tables that comprise the system catalog. All\
users need them at all times. The database server handles concurrent\
access to them correctly, so simply remove this statement from your\
program.\
\
|
-522	Table table-name not selected in query.\
\
You used a correlation name to qualify a column name in either a GROUP\
BY clause or a SET clause. Consider rewriting the statement in an SPL\
routine that you then use as the triggered action, passing the column\
value as an argument. In any case, you must rewrite the statement\
without a using a correlation name in the GROUP BY clause or the SET\
clause.\
\
|
-523	Can only recover, repair or drop table.\
\
This statement (RECOVER, REPAIR, or DROP) specifies a view. However,\
these statements are only supported for real tables, not views. In the\
case of DROP, if you drop any of the tables used in the view, the view\
will be removed as well. To recover or repair this table, you must\
recover or repair the tables on which the view is defined. For a way to\
list the names of tables that are views, see the discussion of error\
-394.\
\
|
-524	Lock table can only be used within a transaction.\
\
Because this database has a transaction log, a table can only be locked\
within a transaction. Review the program, and ensure that a BEGIN WORK\
statement is issued to start a transaction before this statement.\
\
|
-525	Failure to satisfy referential constraint constraint-name.\
\
During an ALTER TABLE or SET statement, you have added or re-enabled a\
referential constraint that the data in the table violates. Check that\
the data in the referencing column (child key) exists in the referenced\
column (parent key).\
\
|
-527	Lock Mode is not available on this system.\
\
You tried to use the SET LOCK MODE TO WAIT statement on IBM Informix SE,\
but your IBM Informix SE database server uses CREATE LOCKING rather than\
System V locking. If the error recurs, note all circumstances\
and contact Technical Support at tsmail@us.ibm.com.\
\
The database server cannot execute the SET LOCK MODE TO WAIT statement\
because the host operating system does not have adequate support for\
locking to permit waiting for a lock to be released. On this system,\
your program will be notified when a table or row is locked (with an\
error such as -233 or -378); your program determines what to do next,\
such as rolling back the transaction and trying it again.\
\
|
-526	Updates are not allowed on a scroll cursor.\
\
For a DECLARE statement, the clause FOR UPDATE is not allowed in\
conjunction with the SCROLL keyword. For an UPDATE statement in an\
ANSI-compliant database (in which the FOR UPDATE clause is not required\
when declaring a cursor for update), the cursor named in this statement\
was declared with the SCROLL keyword and may not be used for updates.\
The way a scroll cursor is implemented makes it unsafe for updating a\
table, since it will sometimes not reflect the current state of the\
selected rows. If you want to use a scroll cursor to examine rows and\
then update them, you may redesign your application in the following\
way (among many). Use the scroll cursor to select also the ROWID of\
each row. Declare a second, nonscrolling cursor that selects one row\
for update based on its ROWID. When it is time to update a selected\
row:\
\
    *   Open the update cursor using the ROWID value found by the\
	scrolling cursor.\
\
    *   Fetch the row, and check the error code (the row might have\
	been deleted).\
\
    *   If the fetch succeeded, verify that the row contents are\
	unchanged from those selected by the scrolling cursor (the row\
	is now locked, so it cannot change further, but it might have\
	changed between the two fetches).\
\
    *   If the row is unchanged, update it using the nonscrolling cursor.\
\
    *   Close the nonscrolling cursor.\
\
    *   This procedure ensures that the update reflects the current\
	state of the table but also retains the convenience of the\
	scrolling cursor. A fetch by ROWID of a recently fetched row\
	will usually entail no disk activity and so will not cost much\
	time.\
\
|
-528	Maximum output rowsize max-size exceeded.\
\
The total number of bytes that this statement selects exceeds the\
maximum that can be passed between the database server and the program.\
Make sure that the columns selected are the ones that you intended.\
Check that you have not named some very wide character column by\
mistake, neglected to specify a substring, or specified too long a\
substring. If the selection is what you require, rewrite this SELECT\
statement into two or more statements, each of which selects only some\
of the fields. If it is a join of several tables, you might best select\
all desired data INTO TEMP; then select individual columns of the\
temporary table. If this is a fetch via a cursor in a program, you\
might revise the program as follows. First, change the cursor to select\
only the ROWID of the desired row. Second, augment the FETCH statement\
with a series of SELECT statements, each of which selects one or a few\
columns WHERE ROWID = the saved row ID.\
\
|
-529	Cannot attach to shared memory.\
\
This error message appears prior to Version 6.0. Your application\
program is unable to initialize its connection to the database server\
because you are using a shared-memory implementation. Either the\
database shared memory has not been initialized, or the maximum number\
of users has already started using the system. Check the accompanying\
ISAM error code for more information.\
\
|
-529	Cannot attach to transaction.\
\
This error message appears beginning with Version 6.0. Your application\
program is unable to initialize its connection to the database server\
because you are using a shared-memory implementation. Either the\
database shared memory has not been initialized, or the maximum number\
of users has already started using the system. Check the accompanying\
ISAM error code for more information.\
\
|
-530	Check constraint constraint-name failed.\
\
The check constraint placed on the table column was violated. To see the\
check constraint associated with the column, query the syschecks system\
catalog table. However, you must know the constrid for the check constraint\
before you query syschecks. (The constrid is assigned in the sysconstraints\
system catalog table.) Use the following subquery to show the check\
constraint for constraint-name:\
\
SELECT * FROM syschecks\
        WHERE constrid = (SELECT constrid FROM sysconstraints\
           WHERE constrname = constraint-name)\
\
|
-531	Duplicate column column-name exists in view.\
\
This CREATE VIEW statement gives a list of column names, and at least\
one of them appears twice in the list. Review the list of column names,\
and make sure that each appears only once.\
\
|
-532	Cannot alter temporary table table-name.\
\
The table shown is only a temporary table. It will vanish when this\
session ends. Such tables cannot be altered. To alter the shape of the\
table, simply drop it, and re-create it.\
\
|
-533	Extent size too small, minimum size is number k.\
\
The size that is specified for a disk extent (either the EXTENT SIZE or\
the NEXT SIZE clause) must be at least four times the disk page size,\
as shown. Generally, set EXTENT SIZE large enough to hold all of the\
rows as you initially estimate them, and set NEXT SIZE at an eighth or\
a quarter of that.\
\
|
-534	Could not insert new row into table, table is locked.\
\
Database servers at Version 4.0 and later do not return this error. In\
earlier versions, its meaning is the same as error -271 with ISAM error\
code -113. Roll back the current transaction, and run it again when the\
table has been unlocked.\
\
|
-534	Cannot open EXPLAIN output file.\
\
The statement SET EXPLAIN ON has been executed, and the database server\
is trying to open the file sqexplain.out in the current working\
directory. An operating-system error of some kind prevents it. See the\
ISAM error code for more information. Look for operating-system error\
messages that might give more detail. Likely problems include a lack of\
write permissions in the current directory and a full disk. This error\
message appears beginning with Version 4.1.\
\
|
-535	Already in transaction.\
\
This BEGIN WORK statement is redundant; a transaction is already in\
progress. If this is a program, review its logic to make sure it has\
not accidentally failed to end the previous transaction.\
\
|
-536	Number of columns in child constraint does not match number of\
cols in parent constraint.\
\
The number of referencing columns (child key) does not match the number\
of referenced columns (parent key) in the referential constraint. Check\
that a one-to-one relationship exists between referenced and\
referencing columns.\
\
|
-537	Constraint column column-name not found in table.\
\
The column that is specified in a constraint definition does not\
exist.\
\
|
-538	Cursor cursor-name has already been declared.\
\
The cursor that is named in this DECLARE statement has also been named\
in a DECLARE statement that was executed earlier. Possibly the same\
DECLARE is being executed in a loop, or possibly the program meant to\
execute a FREE statement for this cursor but did not. Review the\
program logic to ensure that it executes only a single DECLARE for each\
cursor (except after freeing one).\
\
|
-539	DBTEMP too long.\
\
The pathname in the DBTEMP environment variable exceeds the limit on\
pathnames, which is 80 characters. You will have to locate the\
temporary directory higher in the directory hierarchy. Since Version\
5.01, the IBM Informix SE database server uses the DBTEMP environment\
variable, but IBM Informix Dynamic Server and IBM Informix OnLine Dynamic\
Server do not.\
\
|
-540	Write failed on constraints.\
\
An error occurred while defining a constraint. Possibly you have\
defined a constraint whose name duplicates the name of another\
constraint, table, or index. If this is the case, repeat the statement,\
specifying a unique name. Otherwise, check the accompanying ISAM error\
code for more information.\
\
|
-541	User does not have ALTER privilege.\
\
You must have the correct privilege before you can alter the name of a\
table or the names, types, or number of columns in it. You must also\
have the correct privileges to set the object modes for constraints\
and triggers.\
\
You must be the owner of the database object, have Database \
Administrator privilege in the database, or be granted ALTER privilege \
for the database object by its owner or a DBA. See the discussion of\
error -313 for a way to list the owners of tables and users with \
DBA privilege.\
\
|
-542	Cannot specify a column more than once in a constraint, trigger,\
or index.\
\
You name the same column more than once in the triggering column list\
of an update trigger. Remove the duplicate occurrence of the column\
name, and try again. This error also will appear if duplicate column\
names exist in the index list.\
\
|
-543	ESCAPE character must be only one byte.\
\
In the WHERE clause, a subclause ESCAPE char contains more than one\
character as char. Review the punctuation of the clause, and revise it\
so that it specifies just one byte character.\
\
|
-544	Cannot have aggregates within aggregates.\
\
The statement contains a call on an aggregate function within the\
parameter list for another aggregate function, such as\
SUM(MAX(column)). This action is not supported because all aggregates\
are calculated over the same groups of rows. If you did not intend an\
expression of this sort, look for missing or misplaced parentheses. If\
you did intend it, rethink the query. For example, you might select the\
MAX values into a temporary table and then take their SUM.\
\
|
-545	No write permission for table table-name.\
\
Check the accompanying ISAM error code for more information. With this\
database server, a database is a directory with the name dbname.dbs,\
while tables and indexes are files within that directory. You need to\
have read and write access to all these files in order to exercise\
normal database functions.\
\
|
-546	Cannot have host variables when creating a view view-name.\
\
This statement either prepares or executes a CREATE VIEW statement in\
which the SELECT statement refers to host variables. This action is not\
supported. The SELECT statement in a view can be executed from any\
program and cannot rely on the variables of one program. Review the\
CREATE VIEW statement, and make sure that it does not contain the names\
of any host variables, an INTO clause, or a ? placeholder.\
\
Database servers after Version 5.01 do not use this error message.\
\
|
-547	Must rollforward database in the directory where the database is.\
\
Before you execute the ROLLFORWARD statement, make the current\
directory the directory that contains the dbname.dbs directory for the\
database. Then execute the statement again.\
\
|
-548	No referential constraint or trigger allowed on a TEMP table.\
\
You cannot create a constraint or a trigger on a temporary (TEMP)\
table. Consider creating the temporary table as a permanent table in\
the database. If this option is feasible, create the table, and then\
create the trigger on it.\
\
|
-549	Column column-name in UNIQUE constraint is not a column in the table.\
\
The column appears in the list of columns for a UNIQUE clause, but it\
is not one of the columns defined in this table. Check the spelling of\
all column names in this statement. If they are as you intend, then\
check the definition of the table. See the discussion of error -328 for\
a way to list all column names in a table.\
\
Database servers after Version 5.01 do not use this error message.\
\
|
-550	Total length of columns in constraint is too long.\
\
The total size of all the columns listed in a UNIQUE, PRIMARY KEY, or\
FOREIGN KEY clause is limited. The limit depends on the database server\
in use, but all servers support a total of 120 bytes. The limit is the\
same as the restriction on the total size of all columns in a composite\
index. For additional information, see the CREATE TABLE statement in\
the IBM Informix Guide to SQL: Syntax.\
\
|
-551	The constraint contains too many columns.\
\
The total number of columns listed in a UNIQUE, PRIMARY KEY, or FOREIGN\
KEY clause is limited. The limit depends on the database server in use,\
but all database servers support eight columns. The limit is the same as\
the restriction on the number of columns in a composite index. For\
additional information, refer to the CREATE INDEX statement in the\
IBM Informix Guide to SQL: Syntax.\
\
|
-552	Blob host variables are disallowed in multi-statement prepares.\
\
This EXECUTE statement executes a prepared list of multiple statements.\
One or more of the host variables supplied for the ? placeholders in\
the list is a locator structure for a TEXT or BYTE value. This action\
is not allowed. Statements that refer to TEXT or BYTE variables may be\
prepared and executed, but they must be single statements, not part of\
a multistatement list.\
\
|
-553	Mkdbsdir not found in $INFORMIXDIR/bin. Consult your installation\
instructions.\
\
An executable program, mkdbsdir, is used to create the initial contents\
of the database directory during a CREATE DATABASE statement. It is\
distributed with the database server and should be found in the bin\
subdirectory of the directory that the INFORMIXDIR environment variable\
names, but it was not. Check the setting of INFORMIXDIR, and then\
consult with the person who installed the software.\
\
|
-554	Syntax disallowed in this database server.\
\
The database server that you are using does not support this statement\
or some clause in it. When a program starts, the database server in use\
is chosen based on the SQLEXEC environment variable (for database\
servers prior to Version 6.0). Several small differences in statement\
syntax exist between IBM Informix SE and other IBM Informix database servers.\
For example, IBM Informix SE supports the IN 'pathname' clause of the\
CREATE TABLE statement while other IBM Informix database servers support\
the IN dbspace clause instead.\
\
|
-555	Cannot use a select or any of the database statements in a\
multi-query prepare.\
\
The statement text that is presented with this PREPARE statement has\
multiple statements divided by semicolons, and one is a SELECT,\
DATABASE, CREATE DATABASE, or CLOSE DATABASE statement. These\
statements must always be prepared as one-statement texts. Check the\
statement text string, and make sure that you intended multiple\
statements. If you did, revise the program to execute these four\
statement types alone.\
\
|
-556	Cannot create, drop, or modify an object that is external to current database.\
\
This statement attempts to create, drop, or alter an object in an\
external database, one other than the current database. You can only\
read the contents of an external database.\
\
If you make the external database your current database, you can\
modify the contents. Review all uses of names beginning with <dbname>,\
which refers to an object in the external database <dbname>.\
\
|
-558	Changrp not found in $INFORMIXDIR/bin. Consult your installation\
instructions.\
\
This command requires the presence of an executable program named\
changrp, which is normally installed as part of the database server. It\
should be in the bin subdirectory of the directory that INFORMIXDIR\
environment variable names. Check the value in that variable, and then\
consult with the person who installed the software.\
\
|
-557	Cannot locate table that is external to the current database\
after <level-count> levels of synonym mapping.\
\
One of the tables named in this query was in fact a synonym, and it\
pointed outside the current database. It named another synonym that\
pointed outside its database, and so on for <level-count> synonyms\
with no real table being found. The database server has given up on\
the query in case an endless chain of synonyms exists.\
\
To review the synonyms in the current database that refer to external\
databases, query systables and syssyntable as follows:\
\
SELECT T.tabname synonym, servername, dbname, user, S.tabname\
   FROM systables T, syssyntable S\
      WHERE T.tabtype = 'S' AND T.tabid = S.tabid AND S.btabid IS NULL\
\
To follow a chain of synonyms through external databases, use a similar\
query in the external database and substitute for servername, dbname,\
and tabname the values that the preceding query returns each time.\
\
SELECT T.tabname synonym, servername, dbname, user, S.tabname\
        FROM dbname@servername:systables T, dbname@servername:syssyntable S\
           WHERE T.tabtype = 'S' AND T.tabname = 'tabname'\
              AND T.tabid = S.tabid\
\
When this query returns no row, the requested tabname is not defined as\
a synonym in that database (it is a table, a view, or not defined).\
\
|
-559	Cannot create a synonym on top of another synonym.\
\
This CREATE SYNONYM statement names another synonym. Making a chain of\
synonyms is not supported. See the discussion of error -218 for a way\
to list the names of all synonyms. To have a second synonym with the\
same meaning as the first, find out the meaning of the other synonym.\
Then make a new synonym to refer to the same base table. To see the\
base table for a given synonym, query systables and syssyntable as\
follows, substituting the name of the synonym:\
\
SELECT T.tabname synonym, S.* FROM systables T, syssyntable S\
        WHERE T.tabname = name AND T.tabid = S.tabid\
\
If btabid is defined in the resulting display, the synonym refers to a\
table in that current database with that tabid; otherwise, it refers to\
an external database.\
\
|
-560	Synonym with tabid number not found in systables.\
\
Either the systables or syssyntable system catalog, or an index on one\
of these, has been corrupted. Run the bcheck or secheck utility. Be\
prepared to drop and re-create all synonyms.\
\
|
-561	Sums and averages cannot be computed on datetime values.\
\
This statement applies an aggregate function such as SUM to a column\
that has the type DATETIME. The function is not defined on this data\
type since arithmetic is not. Review the use of aggregate functions.\
You will have to revise the query.\
\
|
-562	Database conversion failed.\
\
You are running a new version of the database server, and you just\
opened a database for the first time with this level of the software.\
The database server tried to upgrade the database automatically,\
probably by defining an additional system-catalog table. An unexpected\
error occurred. Check the accompanying ISAM error code for more\
information. If the error recurs, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
Database servers after Version 5.01 do not use this error message.\
\
|
-563	Cannot acquire exclusive lock for database conversion.\
\
You are running a new version of the database server, and you have just\
opened a database for the first time with this level of the software.\
The database server has tried to upgrade the database automatically,\
probably by defining an additional system catalog table. However, it\
needs to lock the database for exclusive use to do this conversion, and\
some other user has the database open. Wait a short time, and try this\
statement again. At that time, the database might be free (or another\
user's action might have updated it).\
\
|
-564	Cannot sort rows.\
\
This internal error reflects an unexpected condition during a sort.\
Check the accompanying ISAM error code for more information. If the\
error recurs, note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
|
-565	Cannot read sorted rows.\
\
This internal error reflects an unexpected condition during a sort.\
Check the accompanying ISAM error code for more information. If the\
error recurs note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
|
-566	Cannot initiate sort.\
\
This internal error reflects an unexpected condition during a sort.\
Check the accompanying ISAM error code for more information. If the\
error recurs, note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
|
-567	Cannot write sorted rows.\
\
This internal error reflects an unexpected condition during a sort.\
Check the accompanying ISAM error code for more information. If the\
error recurs, note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
|
-568	Cannot reference an external database without logging.\
\
This statement refers to a database other than the current database.\
However, the current database uses transaction logging, and the\
external one does not. This action is not supported; the databases\
that are used in a single transaction must all use logging or all not\
use it.\
\
|
-569	Cannot reference an external database with logging.\
\
This statement refers to a database other than the current database.\
However, the current database does not use transaction logging, and the\
external one does. This action is not supported; the databases that are\
used in a single transaction must all use logging or all not use it.\
\
|
-570	Cannot reference an external ANSI database.\
\
This statement refers to a database other than the current database.\
However, the current database is not ANSI compliant, and the external\
one is. This action is not supported; the databases that are used in a\
single transaction must all be ANSI compliant, or all must not be.\
\
|
-571	Cannot reference an external non-ANSI database.\
\
This statement refers to a database other than the current database.\
However, the current database is ANSI compliant, and the external one\
is not. This action is not supported; the databases used in a single\
transaction must all be ANSI compliant, or all must not be.\
\
|
-572	The specified wait duration is too long.\
\
The maximum time that you can specify as the WAIT time in SET LOCK MODE\
is 32,767 seconds. Review this statement, and make sure it specifies\
the duration in seconds that you intended. If so, either use a shorter\
duration, or (since 32,767 seconds is more than 9 hours) simply omit\
the duration to specify an indefinite wait.\
\
|
-573	Cannot set log to buffered in a mode ANSI database.\
\
This statement tries to apply BUFFERED LOG mode, but the database is\
ANSI compliant; that is, it was created with the clause MODE ANSI. One\
aspect of ANSI compliance is that all transactions are logged\
immediately during the execution of the COMMIT WORK statement. The use\
of a buffered log entails a deferred write of log records. It improves\
performance at some slight risk of failing to log a transaction. Such a\
risk is not allowed under the standard; an ANSI-compliant database must\
use unbuffered logging.\
\
|
-574	A subquery has returned not exactly one column.\
\
This statement contains a subquery (a SELECT statement within parentheses)\
to represent a single value (on one side of a relational operator such as\
equals). Such a subquery must return exactly one row and one column;\
otherwise, it is unclear which value the subquery represents. This\
subquery has returned more than one value. This error can occur if you\
specify the ITEM keyword in a collection subquery with more than one element\
in the projection list.\
\
Review all subqueries to make sure that they can return at most one column\
(by listing only one expression after SELECT) and at most one row (by\
testing a unique key in the WHERE clause). For a collection subquery, either\
drop the ITEM keyword or make sure that the projection list contains only one\
element.\
\
|
-575	LENGTH() requires string type values.\
\
This statement contains a use of LENGTH that is applied to a column or\
an expression that is not a character type (not CHAR or VARCHAR). This\
action is not supported. Review the uses of LENGTH, and make sure they\
apply only to character values.\
\
|
-576	Cannot specify CONSTRAINT name for TEMP table.\
\
You cannot specify a constraint (either UNIQUE, PRIMARY KEY, or CHECK)\
name for constraints placed on temporary tables. This action is not\
supported for a temporary table. However, you can specify that a column\
receives one of these constraints, and you can specify a list of\
columns as having a constraint, but you may not use the CONSTRAINT\
constraint-name clause. Temporary tables and their indexes are not\
recorded in the usual system catalog tables.\
\
|
-577	A constraint of the same type already exists on the column set.\
\
You have placed a constraint (either UNIQUE, PRIMARY KEY, FOREIGN KEY,\
or CHECK) on a set of columns, but a constraint of the same type on\
those columns already exists. In the case of a FOREIGN KEY, this error\
only occurs if the same foreign-key set of columns references the same\
existing parent key set of columns. Either the constraint was\
established when the table was created, or it was added later. Because\
the constraint already exists, it is not added again.\
\
|
-578	Owner name is too long.\
\
This statement contains an owner name that qualifies the name of a\
table, view, index or synonym, and the owner name is longer than the\
maximum of 8 characters (for example, overly_long.tablename). Review\
the punctuation and spelling of all identifiers. Possibly an omitted\
space or comma causes two names to run together. To check the names of\
all known owners, select the owner column of the relevant system\
catalog: systables, sysindexes, or syssynonyms.\
\
|
-579	Not owner of synonym.\
\
You do not own the synonym that is specified in this DROP SYNONYM\
statement. To drop an object you do not own, you must have Database\
Administrator privilege.\
\
|
-580	Cannot revoke permission.\
\
This REVOKE statement cannot be carried out. Either it revokes a\
database-level privilege, but you are not a Database Administrator in\
this database, or it revokes a table-level privilege that your account\
name did not grant. Review the privilege and the user names in the\
statement to ensure that they are correct. To summarize the table-level\
privileges you have granted, query systabauth as follows:\
\
SELECT A.grantee, T.tabname FROM systabauth A, systables T\
        WHERE A.grantor = USER AND A.tabid = T.tabid\
\
|
-581	Error loading message file.\
\
This SET EXPLAIN statement could not be completed because the database\
server was unable to find the file of message templates it uses when it\
prepares explanatory output. Consult with the person who installed the\
IBM Informix software.\
\
|
-582	Database does not have logging.\
\
This ROLLFORWARD statement could not be executed because this database\
does not have a transaction log. The rollforward operation uses the\
transaction log as its input. Since no transactions have been logged,\
the database cannot be rolled forward.\
\
|
-583	View permissions no longer valid -- permissions on remote objects\
revoked.\
\
This statement queries a view that is based on tables in external\
databases (databases other than the current database). However, in one\
or more of those external databases, your account does not have the\
necessary table-level privilege on a table that the view uses, or\
possibly your CONNECT privilege for an external database has been\
revoked. For a way to display the definition of a view, see the\
discussion of error -385. In the view definition, look for table names\
that are qualified with database names and possibly site names.\
\
|
-584	Cannot rename system catalog.\
\
This RENAME TABLE statement cannot be carried out because it would\
rename one of the tables that make up the system catalog. The names of\
these tables cannot be changed; the database server uses them.\
\
|
-585	Cannot rename column in system catalog.\
\
This RENAME COLUMN statement cannot be carried out because it would\
rename a column of one of the tables that make up the system catalog.\
The database server relies on these column names for internal queries,\
and you cannot change them.\
\
|
-586	Cursor is already open.\
\
This database is operating in ANSI compliance (it was created or\
started MODE ANSI). By the rules of ANSI SQL, a cursor must always be\
closed before it can be reopened. Review the logic of the program.\
Possibly it was originally written to take advantage of one of the\
Informix extensions to SQL: if a cursor is reopened, it is\
automatically closed and opened. In the current database, that action\
is not allowed.\
\
|
-587	Cannot delete file filename.\
\
Version 4.0 and later do not use this message. For previous versions,\
check the accompanying ISAM error code for more information.\
\
|
-588	Invalid host variable number.\
\
Database servers starting with Version 4.1 detect this internal error.\
If the error recurs, pleasnote all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-589	Cannot update multiple sites within a single transaction.\
\
This database server supports only single-site update. The operations\
within one transaction can modify data at only one site in the network.\
Some preceding statement within this transaction has already modified\
data at one site; the current statement would modify data at a second\
site. The statement is not executed. Roll back the current transaction.\
Examine the application in the light of this restriction. Check the\
names of all tables that UPDATE, INSERT, and DELETE statements affect\
to make sure they are all in the same database or in databases that the\
same database server holds. (Check the definition of any synonyms.\
Synonyms can make tables in external databases appear to be in the\
current database.)\
\
Database servers after Version 5.01 do not use this error message.\
\
|
-590	Routine cache corrupted.\
\
If this internal error recurs, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-590	Procedure cache corrupted.\
\
If this internal error recurs, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-591	Invalid default value for column/variable <column-name>/\
<variable-name>.\
\
The specified default value is the wrong type or is too long for a column\
or an SPL-routine variable.\
\
To specify a valid default value for a column, use the DEFAULT clause in a\
CREATE TABLE statement. To specify a valid default value for a variable in an\
SPL routine, use the DEFAULT clause in a DEFINE statement.\
\
|
-592	Cannot specify column to be not null when the default value is null.\
\
This CREATE or ALTER TABLE statement specifies that a column may not\
contain nulls (the NOT NULL clause), but it also has a DEFAULT clause\
giving the default value for new rows as NULL. This contradiction is\
not allowed.\
\
|
-593	Cannot specify default value for SERIAL column.\
\
This CREATE or ALTER TABLE statement specifies that a column has a\
SERIAL data type, but it also has a DEFAULT clause for the column. The\
database server generates values for a SERIAL column each time a row is\
created, so the DEFAULT clause is meaningless.\
\
|
-594	Cannot specify non-null default value for TEXT or BYTE column.\
\
This CREATE or ALTER TABLE statement specifies that a column has a data\
type of BYTE or TEXT. It also has a DEFAULT clause for the column that\
specifies something other than NULL. You can only designate the default\
value NULL for columns of TEXT or BYTE data type.\
\
|
-595	Bad use of aggregate in this context.\
\
An aggregate function was used outside an SQL statement inside an SPL\
routine expression, or it was used inside a check constraint.\
\
An example of the error follows:\
\
LET var = MAX(another_var) + 10; -- error\
\
An SPL routine expression, or the expression in a check constraint,\
can refer to only a single value, so the use of an aggregate function\
is meaningless.\
\
|
-596	Bad EXIT/CONTINUE statement. Not within a statement-name loop.\
\
The SPL routine EXIT and CONTINUE statements must be placed within\
a FOREACH, WHILE, or FOR loop.\
\
|
-597	[Internal] Premature End Of Buffer.\
\
If this internal error recurs, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-598	Bad cursor name cursor-name.\
\
Inside an SPL routine, a nonexistent cursor name was specified in\
an UPDATE/DELETE...WHERE CURRENT OF statement.\
\
FOREACH cur1 \
        FOR SELECT col INTO var FROM tab UPDATE tab \
        SET col = proc(var) \
        WHERE CURRENT OF bad_cur_name; -- error \
END FOREACH\
\
|
-599	Cannot mix IBM Informix Dynamic Server syntax with \
        IBM Informix SE syntax.\
\
Syntax specific to IBM Informix Dynamic Server and to the IBM Informix SE\
database server was mixed in the same statement. Use the appropriate syntax\
for your database server.\
\
-600	Cannot create TEXT or BYTE value.\
\
This statement creates a new BYTE or TEXT value, but some unexpected\
error prevented the creation of that value. Roll back the current\
transaction. Check the accompanying ISAM error code for more\
information. Possibly the storage space or tbspace has filled up, or\
you are not referring to a valid storage space. If the error recurs,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-601	Cannot delete TEXT or BYTE value.\
\
This statement replaces or deletes a BYTE or TEXT value, but some\
unexpected error prevented the deletion of the old value. Roll back the\
current transaction. Check the accompanying ISAM error code for more\
information. Possibly a hardware error or data corruption of the\
storage space or tblspace occurred. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-602	Cannot open TEXT or BYTE value.\
\
This statement refers to a BYTE or TEXT value, but some unexpected\
error prevented locating the value. Roll back the current transaction.\
Check the accompanying ISAM error code for more information. Possibly a\
hardware error or data corruption of the storage space or tblspace\
occurred. If the error recurs, note all circumstance, and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-603	Cannot close TEXT or BYTE value.\
\
This statement writes a BYTE or TEXT value, but some unexpected error\
prevented finishing the creation of the value. Roll back the current\
transaction. Check the accompanying ISAM error code for more\
information. Possibly a hardware error or data corruption of the\
storage space or tblspace occurred. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-604	Cannot read TEXT or BYTE value.\
\
This statement refers to a BYTE or TEXT value, but some unexpected\
error prevented access to the value. Roll back the current transaction.\
Check the accompanying ISAM error code for more information; possibly a\
hardware error or data corruption of the storage space or tblspace\
occurred. If the error recurs, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-605	Cannot write TEXT or BYTE value.\
\
This statement writes a BYTE or TEXT value, but some unexpected error\
prevented the creation of the value. Roll back the current transaction.\
Check the accompanying ISAM error code for more information; possibly a\
hardware error or data corruption of the storage space or tblspace\
occurred. One possible cause is that the storage space for this column is\
full. Another is that although a new chunk has been assigned to the\
storage space, pages cannot be allocated in it until the addition of the\
chunk has been logged and the log file closed. The database server\
administrator can use the tbmode -l or onmode -l command to force a log\
file to be closed. If the error recurs, note all circumstances\
and contact Technical Support at tsmail@us.ibm.com.\
\
|
-606	Invalid storage-space name for TEXT or BYTE data.\
\
If this statement refers to a storage space (for example, the CREATE\
TABLE statement might create a column with type TEXT IN blobspace-name),\
the name is invalid or does not exist. Review the identifiers intended\
as storage-space names. If they are spelled as you intended, consult\
with the database server administrator to find out whether they exist\
and are online. If the statement does not refer to a storage space,\
this is an internal error. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-607	Text/Byte subscript error.\
\
This statement refers to a TEXT or BYTE value that uses substring\
notation (numbers in square brackets that follow the name). However,\
the substring is not correctly written. Review all uses of substrings,\
and make sure that the first number in each is greater than zero but\
not greater than the length of the value; the second number is not less\
than the first; and the numbers are separated by a comma.\
\
|
-608	Illegal attempt to convert Text/Byte data type.\
\
This statement is written to imply a conversion from a TEXT or BYTE\
value to another data type, for example, by combining it with other\
types in an expression or by inserting it into a column of another\
type. This action is not supported; TEXT and BYTE columns can only be\
selected or be copied into other columns of the same type. Check that\
the statement names the columns you intended and that they have the\
data types you thought.\
\
|
-609	Illegal attempt to use Text/Byte host variable.\
\
This statement uses a host variable that is a TEXT or BYTE locator\
structure but combines it with data of some other type (for instance,\
in an expression or by inserting it into a column of another type).\
This action is not supported; host variables of these types may only be\
used for selecting from, creating, or inserting into columns of the\
same type.\
\
|
-610	Index not allowed on TEXT or BYTE columns.\
\
This CREATE INDEX statement names a column of the TEXT or BYTE type;\
however, these types are not supported for indexing. Because no defined\
lexical ordering exists for these types, the database server does not\
know how to sort or compare them. Therefore it cannot build an inverted\
index. Possibly you understand the data well enough to understand how\
to extract an ordered set of key values from it. If so, perform the\
extraction into a separate column in the same table, and index that\
column.\
\
|
-611	Scroll cursor can't select TEXT or BYTE columns.\
\
The cursor that is named in this statement is associated with a SELECT\
statement that returns one or more TEXT or BYTE columns. Also, the\
cursor is declared with the SCROLL keyword. This action is not\
supported.Rows that are fetched through a scroll cursor are also stored\
in a temporary table. Because of the bulk of TEXT and BYTE values,\
this action would produce an unacceptable cost in time and disk space.\
Revise the declaration of the cursor to select the desired columns of\
other types and also the ROWID. After you fetch a row through the\
scrolling cursor, use a separate, nonscrolling cursor to fetch the BYTE\
or TEXT values, WHERE ROWID=host-var.\
\
|
-612	TEXT and BYTE columns are not allowed in the "group by" clause.\
\
This SELECT statement selects one or more BYTE or TEXT values and also\
specifies those columns in the GROUP BY clause. This action is not\
supported. Since no defined lexical order to BYTE or TEXT values\
exists, the database server cannot order or compare them. Therefore it\
cannot group rows on their values. (This condition is true even of\
substrings selected from a BYTE or TEXT column.) Review your SELECT\
statement to ensure that the correct columns are named in the GROUP BY\
clause.\
\
|
-613	TEXT and BYTE columns are not allowed in the "distinct" clause.\
\
This statement specifies DISTINCT values, but it also selects a BYTE or\
TEXT value. The database server does not know how to compare or order\
these values, so it cannot sort them, and it cannot locate duplicate\
values. You cannot use the DISTINCT keyword when these data types are\
selected. Reword your SELECT statement to either remove the keyword or\
select only normal columns.\
\
|
-614	TEXT and BYTE columns are not allowed in the "order by" clause.\
\
This SELECT statement selects one or more BYTE or TEXT values, and also\
specifies those columns in the ORDER BY clause. This action is not\
supported. Because no defined lexical order to BYTE or TEXT values\
exists, the database server cannot order them. (This is true even of\
substrings selected from a BYTE or TEXT column.) Review your SELECT\
statement to ensure that he correct columns are named in the ORDER BY\
clause.\
\
|
-615	TEXT and BYTE columns are not allowed in this expression.\
\
This statement uses an aggregate function, such as COUNT, SUM, MIN, MAX, or\
AVG, but applies it to a column that has the BYTE or TEXT data type. This\
action is not supported.\
\
Review the use of each aggregate function to make sure that it is not applied\
to a BYTE or TEXT column.\
\
|
-616	A TEXT or BYTE subscript is not allowed within this context.\
\
This UPDATE or INSERT statement specifies a subscripted column of BYTE\
or TEXT data type as a destination. Subscript notation is not allowed\
in this context; a BYTE or TEXT (or any other) value must be replaced\
in full. Revise the statement to assign into whole columns.\
\
|
-617	A TEXT or BYTE data type must be supplied within this context.\
\
This statement assigns a value that is not a simple large object to a BYTE or \
TEXT column or assigns a BYTE or TEXT column to a column that is not a simple \
large object. Neither action is supported. BYTE and TEXT values must be \
assigned as whole units to columns of the same type. Check that the statement \
specifies the columns that you intended.\
\
|
-618	Error on copying TEXT or BYTE data.\
\
This statement copies a BYTE or TEXT value from one row to another, but\
some unexpected error interfered with the operation. Roll back the\
current transaction. Check the accompanying ISAM error code for more\
information; possibly a hardware error, data corruption of the\
storage space or tblspace, or a shortage of disk space exists, or an\
invalid storage space was named. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-619	A TEXT or BYTE error has occurred in the front-end application.\
\
This statement transfers a BYTE or TEXT value between the database and\
the user program, but something has happened to prevent that. For\
example, perhaps it was not possible to allocate a buffer for a value\
that was located in memory. Check the accompanying ISAM error code for\
more information.\
\
|
-620	Unable to update next extent size.\
\
This internal error indicates the database server cannot change an\
internal data structure (not a system catalog) that is stored in the\
root dbspace. Check the accompanying ISAM error code for more\
information. Possibly corruption of the root dbspace occurred. Have the\
database server administrator run the oncheck, onutil, or tbcheck utility.\
\
|
-621	Unable to update new lock level.\
\
This internal error indicates that the database server is unable to\
convert a lock from shared to exclusive. Check the accompanying ISAM\
error code for more information. Possibly a hardware error or a problem\
with shared memory exists. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-622	Error on locating constraint index index-name.\
\
This internal error shows that the database server is trying to test a\
new or updated row for uniqueness under a UNIQUE or PRIMARY KEY\
constraint, but the index that implements the constraint cannot be\
found. Check the accompanying ISAM error code for more information.\
Corruption of the system catalog tables or the root dbspace or a\
hardware problem might have occurred. If the error recurs, note\
all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-623	Unable to find CONSTRAINT constraint-name.\
\
The constraint specified in this statement cannot be found. Review the\
spelling of the name shown. If it is as you intended, check the names\
of existing named constraints by querying the sysconstraints table as\
shown in the following example. If the owner name shown for the desired\
constraint is not yours, you need to be a Database Administrator to\
reference it (and, if this database is ANSI compliant, you need to\
qualify the name with its owner-name).\
\
SELECT constrname, owner FROM informix.sysconstraints\
\
|
-624	Unable to drop CONSTRAINT constraint-name.\
\
This internal error shows that the database server had an unexpected\
error while dropping a constraint or the index that implemented it.\
Check the accompanying ISAM error code for more information. Corruption\
of the system catalogs or the root dbspace might have occurred, or a\
hardware problem might exist. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-625	Constraint name constraint-name already exists.\
\
The constraint name already exists. Review the spelling. If it is as\
you intended, you must select another name, or drop and redefine the\
existing constraint. See the discussion of error -623 for a way to list\
all constraints.\
\
|
-626	Cannot obtain or set serial value.\
\
This internal error message does not refer to a problem with a SERIAL\
column in a table that you defined. The database server uses unique\
integer values for many purposes (for example, the table ID number for\
a new or altered table). An internal error has made it impossible to\
generate a new, unique number. For example, in host systems that use\
files for locking, something might have prevented the creation of a\
lock file. Check the accompanying ISAM error code for more information.\
If the error recurs, note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-627	Cannot prepare coordinator for two-phase commit.\
\
Because the coordinator cannot prepare this IBM Informix STAR two-phase\
commit transaction, all participants eventually roll back all work that\
is associated with the transaction. No administrative intervention is\
required. See the ISAM error for more information about why the\
database server could not prepare to commit the local transaction.\
\
|
-628	Cannot end two-phase commit transaction at coordinator.\
\
The database server acting as coordinator for the transaction cannot\
end this IBM Informix STAR two-phase commit transaction, and the\
transaction remains open. Eventually, IBM Informix STAR automatic recovery\
mechanics will end the transaction. No administrative intervention is\
required. See the ISAM error for more information about why the\
database server could not end the transaction properly.\
\
|
-629	Cannot end heuristically rolled back transaction.\
\
The database server acting as coordinator for the transaction cannot\
end this IBM Informix STAR two-phase commit transaction, and the\
transaction remains open. Eventually, IBM Informix STAR automatic recovery\
mechanics will end it. No administrative intervention is required. See\
the ISAM error for more information about why the database server could\
not end the transaction properly.\
\
|
-630	Cannot prepare database server server-name for commit.\
\
The specified database server cannot prepare the local transaction\
associated with this IBM Informix STAR two-phase commit transaction.\
Eventually, all participants roll back all work associated with the\
transaction. No administrative intervention is required. See the ISAM\
error for more information about why the database server could not\
prepare to commit the local transaction.\
\
|
-631	Cannot create optical cluster on column that is not TEXT or BYTE.\
\
You can only create optical clusters on columns of TEXT or BYTE data\
type. The column name is some other type. Check that the column is the\
one you meant to specify, and review the definition of the table.\
\
|
-632	Cannot create optical cluster.\
\
An attempt to create an optical cluster has failed. See the ISAM error\
for more information.\
\
|
-633	Cannot drop optical cluster.\
\
An attempt to drop an optical cluster has failed. See the ISAM error\
for more information.\
\
|
-634	Object does not exist.\
\
You are trying to drop a trigger that does not exist. Check that you\
are spelling the name of the trigger correctly. Also, you might query\
the systriggers system catalog table to review the names of triggers in\
the database.\
\
|
-635	Not owner of object.\
\
You are trying to drop a database object that you do not own. You might query\
the appropriate system catalog table to see who owns the object. (For \
example, for a trigger, query the systriggers table.) You probably need \
to ask the owner of the database object or the database administrator \
to drop the object.\
\
|
-636	Total size of key fields is too large or there are too many key fields.\
\
You have violated one of the following constraints on the cluster key\
that is specified in the ON clause of the CREATE OPTICAL CLUSTER\
statement:\
\
    *   The number of columns included in a composite cluster key\
	exceeds 16.\
\
    *   The length of a CHARACTER column exceeds 256 bytes.\
\
|
-637	Cannot alter optical cluster.\
\
An attempt to alter the size of an optical cluster has failed. See the\
ISAM error for more information.\
\
|
-638	Cannot cluster TEXT or BYTE columns on non-optical media.\
\
You can create an optical cluster only on TEXT or BYTE columns that are\
stored on optical media. Check that you have not specified the name of\
a TEXT or BYTE column that is stored in a storage space.\
\
|
-639	Cannot cluster TEXT or BYTE columns on different optical families.\
\
All of the TEXT or BYTE columns specified in the FOR clause of the CREATE\
OPTICAL CLUSTER statement must belong to the same optical family. Check\
that the columns that are specified for an optical cluster do not\
belong to different families.\
\
|
-640	QPlan sanity failure line-number.\
\
Running UPDATE STATISTICS might fix this internal error. If the error\
recurs, note all circumstances and contact Technical\
Support at tsmail@us.ibm.com.\
\
|
-641	Cannot reserve/release family on non-optical media.\
\
The family name that is specified in the RESERVE or RELEASE statement\
must exist on optical media. Check that you have not specified a\
storage space with either of these statements.\
\
|
-642	Family name must be a character string.\
\
The optical family name that is specified in the RESERVE or RELEASE\
statement must be either a character string, or a host or procedural\
variable that evaluates to a character string. If you specified a\
character string, check that you enclosed it in quotes.\
\
|
-643	Volume must be a number.\
\
The volume argument in the RESERVE or RELEASE statements must be\
INTEGER or SMALLINT.\
\
|
-644	FAMILY(), VOLUME(), and DESCR() require BLOB column on optical medium.\
\
The argument to the FAMILY(), VOLUME(), or DESCR() function must be a\
TEXT or BYTE column that is stored on optical media. Check that you\
have not specified a column of a different data type or a TEXT or\
BYTE column that is stored in a storage space.\
\
|
-645	Cannot reserve volume.\
\
An attempt to reserve an optical volume with the RESERVE statement has\
failed. See the error from the optical subsystem (an error in the -7000\
to -7199 range) for more information.\
\
|
-646	Cannot release volume.\
\
An attempt to release a requested optical volume with the RELEASE\
statement has failed. See the error from the optical subsystem (an\
error in the -7000 to -7199 range) for more information.\
\
|
-647	Error evaluating math library function function-name.\
\
The data type of the argument is correct, but the value passed to the\
function is not appropriate for the math function. Check that you are\
passing a legitimate value to the function.\
\
|
-648	Cannot open DEBUG file for SPL routine trace.\
\
An error occurred trying to open DEBUG trace file. This error can occur\
when one of the directories in the specified debug file name does not\
exist, or the directory is write protected. Check that the directory\
path is valid and that group informix can write to the directory.\
\
|
-649	The debug file name must be a NON-NULL CHAR or VARCHAR.\
\
The argument that is specified for the debug file in the SET DEBUG\
statement must be a character data type.\
\
|
-650	Maximum varchar size has been exceeded.\
\
This statement specifies a VARCHAR(m, r) column with a maximum width m\
greater than allowed (255). Check the punctuation of the column\
definition. If it is as you intended, redesign the table to use a\
VARCHAR width that ranges from 1 character to 255 characters.\
\
|
-651	Reserved column size > maximum column size (varchar).\
\
This statement specifies a VARCHAR(m, r) column with a reserved width r\
that is greater than the maximum width m. Check the punctuation of the\
column definition. If it is as you intended, revise the statement so\
that m is greater than or equal to r.\
\
|
-652	Local variables do not allow default values.\
\
An attempt was made to define a local variable with a default value.\
Only global variables and parameters can have default values.\
\
An example of the error follows:\
\
DEFINE var INT DEFAULT 10; -- error\
\
The correction is as follows:\
\
DEFINE var INT;\
LET var = 10;\
\
|
-653	Variables declared as LIKE cannot be global.\
\
A global variable was defined as LIKE. LIKE variables must be local\
variables.\
\
An example of the error follows:\
\
DEFINE GLOBAL var LIKE tab.col; -- error\
\
Correction: Do not use the LIKE keyword with global variables. Instead,\
specify the data type explicitly.\
\
|
-654	Bad use of PROCEDURE declaration type.\
\
The procedure declaration was used either in the parameters or the\
RETURNING clause. SPL routines cannot accept or return procedures.\
\
An example of the error follows:\
\
CREATE PROCEDURE testproc (proc1 procedure) -- error\
        RETURNING procedure; -- error\
	...\
	END PROCEDURE\
\
Correction: Do not attempt to use the procedure declaration type within\
a parameter or the RETURNING clause.\
\
|
-655	RETURN value count does not match procedure declaration.\
\
The number of values that a procedure was declared to return in the\
RETURNING clause does not match the number of values in a RETURN\
clause.\
\
An example of the error follows:\
\
CREATE PROCEDURE testproc () RETURNING INT, INT;\
	...\
	RETURN 1,2,3; -- error\
	...\
	RETURN 1; -- error\
        END PROCEDURE\
\
Correction: In this example, return exactly two arguments.\
\
|
-656	Routine is not declared to return values.\
\
When the routine was declared, it did not contain a RETURNING clause to\
indicate that the routine would not return any value, but then a RETURN\
statement was found in the body of the routine.\
\
An example of the error follows:\
\
CREATE ROUTINE testproc() DEFINE a INT;\
        LET a = 10;\
        RETURN a + 1; -- error\
        END ROUTINE\
\
Correction: Add a RETURNING clause before the DEFINE statement, or\
remove the RETURN statement.\
\
|
-657	Cannot create a procedure within a procedure.\
\
You cannot have a CREATE PROCEDURE statement within a CREATE PROCEDURE\
statement.\
\
|
-658	Variables declared as GLOBAL require a default value.\
\
A global variable was not given a default value. Global variables\
require a default value.\
\
Example of error:\
\
DEFINE GLOBAL glob INT; -- error\
\
Correction:\
\
DEFINE GLOBAL glob INT DEFAULT 10;\
\
|
-659	INTO TEMP table required for SELECT statement.\
\
A SELECT statement did not specify where to put the returned values.\
SELECT statements within a procedure require either an INTO TEMP clause\
or an INTO clause that references the appropriate procedural\
variables.\
\
Example of error:\
\
CREATE PROCEDURE testproc()\
	...\
	SELECT col1, col2 FROM tab; -- error\
        END PROCEDURE\
\
Correction:\
\
CREATE PROCEDURE testproc()\
	...\
	SELECT col1, col2 INTO var1, var2 FROM tab;\
        SELECT col1, col2 FROM tab INTO TEMP another_table;\
        END PROCEDURE\
\
|
-660	Loop variable variable-name cannot be modified.\
\
An attempt was made to modify the value of a loop variable in a FOR\
statement. Loop variables cannot be modified inside a loop.\
\
Example of error:\
\
FOR i IN (1,2,3,4)\
        LET i = i + 1; -- error\
        END FOR\
\
Correction: Use another variable in the LET statement.\
\
|
-661	Number of variables does not match number of values returned.\
\
The number of variables on the left side of a LET statement does not\
match the number of values on the right side.\
\
Example of error:\
\
LET a,b = 10,20,39;\
LET i,j = proc1()+proc2();\
LET a,b = (SELECT c1 FROM tab)\
\
Correction: Match the number of expressions on both sides of the LET\
statement.\
\
|
-662	Loop variable variable-name specified more than once.\
\
A loop variable was used more than once in a FOREACH statement.\
\
Example of error:\
\
FOREACH SELECT col1, col2 INTO var, var FROM tab -- error\
	...\
	END FOREACH\
\
Correction:\
\
FOREACH SELECT col1, col2 INTO var1, var2 FROM tab\
	...\
	END FOREACH\
\
|
-663	You are using more than one procedure-calling syntax for\
procedure procedure-name.\
\
While calling a procedure, some of the arguments were named, but others\
were not.\
\
Example of error:\
\
LET var = proc (arg1 = 10, 20, arg3 = 30); -- error\
\
Correction:\
\
LET var = proc (arg1 = 10, arg2 = 20, arg3 = 30); --correct\
LET var = proc (10,20,30);--correct\
\
|
-664	Wrong number of arguments to system function function-name.\
\
You have specified an incorrect number of arguments for the function \
function_name. Check that you are passing the correct number of arguments\
to the function.\
\
|
-665	Internal error on semantics - code-number.\
\
If this internal error recurs, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-666	Variable variable-name must be declared INTEGER or SMALLINT.\
\
In a FOR statement, loop variables that contain ranges must be declared\
to be INT or SMALLINT.\
\
Example of error:\
\
DEFINE var CHAR(10);\
FOR var IN (e1, e2 TO e3, e4) -- error\
	...\
	END FOR;\
\
Correction: Because the FOR statement contains a range operator (the TO\
clause), var must be declared as INT or SMALLINT.\
\
|
-667	Variable variable-name not declared.\
\
The specified variable was not declared. Check the spelling of the\
undeclared variable to ensure that it is not causing the error.\
\
|
-669	Variable variable-name redeclared.\
\
A variable has been declared twice in the same scope. See the IBM Informix\
Guide to SQL: Tutorial for an explanation of the scope of\
procedural variables.\
\
|
-668	The system command cannot be executed or it exited with a non-zero status.\
\
Either a system call failed in the operating system or the command that\
was executed exited with a non-zero status.  \
\
The following example shows a statement that might cause the system \
command to fail with an error:\
\
SYSTEM 'hello';\
\
Make sure that the system command is not trying to run a function or program \
that is not in your path or that is not applicable to the environment.\
\
Make sure that you have provided a user ID and password when connecting\
to the database server.  The database server must have the user's\
password in order to execute a command on behalf of that user.\
\
On Windows platforms, make sure the following Advanced User Rights have\
been assigned to user "informix": Act as part of the operating system;\
Increase quotas; Replace a process level token.\
\
The following example shows a statement that will fails with error -668\
and the ISAM error explanation '-255 Not in a transaction':\
\
SYSTEM 'exit 255';\
\
|
-670	Variable variable-name declared as SERIAL type.\
\
The SERIAL data type is not a legal procedure type. Use the INTEGER\
data type to match the SQL SERIAL data type.\
\
|
-671	Routine invocation routine-name has duplicate parameter name.\
\
A routine call named a parameter more than once.\
\
Example of error:\
\
LET var = proc (arg1 = 10, arg2 = 20, arg1 = 30);-- error\
\
|
-671	Procedure call procedure-name has duplicate parameter name.\
\
A procedure call named a parameter more than once.\
\
Example of error:\
\
LET var = proc (arg1 = 10, arg2 = 20, arg1 = 30);-- error\
\
|
-672	Invalid data structure execution-tree.\
\
If this internal error recurs, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-673	Routine routine-name already exists in database.\
\
You attempted to create a routine that already exists in the database.\
If you want to create a new version of the routine, use the DROP\
ROUTINE statement to drop the routine before you attempt to create the\
new version of the routine.\
\
|
-674	Routine <routine-name> cannot be resolved.\
\
You called a routine that does not exist in the database, you do not\
have permission to execute the routine, or you called the routine\
with too few or too many arguments. If a prepared statement invokes a\
user-defined routine and your application or another application drops\
the routine before the prepared statement is executed, you will\
receive this error.\
\
You might also see this error message if you write an expression that\
calls an SPL routine (stored procedure) that returns no values. For\
an SPL routine to be usable in an expression, the routine must return\
a value.\
\
Check that the name of the routine is correct, that you have execute\
permission, and that you specified the correct number of arguments\
to execute a routine. For a prepared statement that refers to the routine,\
make sure that the routine still exists when you execute the statement.\
\
|
-675	Illegal SQL statement in SPL routine.\
\
An SQL statement that is not allowed in an SPL routine was executed.\
This error occurs when a routine is called from an SQL data\
manipulation statement.\
\
Example of error:\
\
CREATE PROCEDURE testproc (arg INT, id INT) RETURNING INT;\
        UPDATE tab SET col = arg WHERE key = id; -- error\
        RETURN id;\
        END PROCEDURE;\
\
SELECT col FROM tab WHERE testproc(tab.col, tab.key) = 10;\
\
Do not use statements such as the preceding UPDATE statement in SPL\
routines.\
\
|
-676	Invalid check constraint column.\
\
A check constraint that is specified at the column level can reference\
only that column. To specify a check constraint that spans more than\
one column, specify the check constraint at the table level. You cannot\
create a check constraint for columns across tables.\
\
|
-677	Check constraint cannot contain subqueries or procedures.\
\
A check constraint cannot contain a subquery or a procedure. Subqueries\
are disallowed in check constraints because they depend on the state of\
the database. For data integrity, the evaluation of a check constraint\
must not vary or depend on the state of the database.\
\
Example of error:\
\
   CREATE TABLE new_stock (\
       stock_num   SERIAL PRIMARY KEY,\
       unit_price  MONEY CHECK (unit_price >=\
                   (SELECT unit_price FROM stock WHERE manu_code = 'HRO')),\
       manu_code   CHAR(3));\
\
Verify that your statement does not have a subquery or procedure in a\
check constraint.\
\
|
-678	Invalid subscript for column column-name in check constraint.\
\
A subscripted column in a check constraint has subscripts outside the\
bounds of the column. Check that the bounds specified in the\
subscripted column do not exceed the maximum length of the column. If\
you know the table name of the column, use the following subquery to\
query the system-catalog tables to find out the maximum length of the\
column:\
\
SELECT collength FROM syscolumns WHERE colname = 'column-name'\
        AND tabid = (SELECT tabid FROM systables\
           WHERE tabname = 'table-name')\
\
|
-679	Cannot read constraint violation data for constraint constraint-name.\
\
See the ISAM error for more information. If this internal error recurs, note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-680	Cannot write constraint violation data for constraint constraint-name.\
\
See the ISAM error for more information. If this internal error recurs,\
pase note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-681	Column specified more than once in the INSERT list.\
\
The error occurs if the user specifies a column name more than once in\
the INSERT column list.\
\
|
-682	Error reading constraint index on table table-name.\
\
The system was unable to validate the constraint. See the ISAM error\
for more information. If this internal error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-683	Specified STEP expression will not traverse RANGE.\
\
The evaluated value of the STEP expression in the FOR statement will\
lead to an infinite loop.\
\
Example of error:\
\
   FOR i = 10 TO 20\
           STEP -1; -- error\
                ...\
           END FOR\
\
Correction: Correct either the range or the step expressions so that\
the incremented values are within the range.\
\
|
-684	Function <routine-name> returns too many values.\
\
The number of returned values from a function is more than the number\
of values that the caller expects.\
\
Example of error:\
\
   CREATE ROUTINE testroutine(arg INT) RETURNING INT, INT;\
           RETURN 1,2;\
           END ROUTINE\
\
   SELECT col FROM tab WHERE col = testroutine(1); -- error\
\
|
-685	Function <function-name> returns too few values.\
\
The number of returned values from a function is less than the number\
of values that the caller expects.\
\
Example of error:\
\
   CREATE ROUTINE testroutine (arg INT) RETURNING INT, INT;\
           RETURN 1,2;\
           END ROUTINE\
\
   UPDATE tab SET (c1, c2, c3) = (testroutine(1)); -- error\
\
|
-686	Function <function-name> has returned more than one row.\
\
A function returned more than one row of values (for example, it\
executed RETURN...WITH RESUME) when the caller expected only one row of\
values.\
\
Example of error:\
\
   CREATE FUNCTION testroutine (limit INT) RETURNING INT;\
           DEFINE i INT;\
           FOR i IN (1 TO limit)\
               RETURN i WITH RESUME;\
           END FOR\
           END FUNCTION;\
\
   CREATE FUNCTION gettest() RETURNING INT;\
           DEFINE var INT;\
           LET var = testroutine (10); -- error\
           RETURN var;\
           END FUNCTION;\
\
|
-687	Set debug file before tracing SPL routines.\
\
A TRACE statement was executed before a SET DEBUG FILE statement. The\
destination of the output of the TRACE statement is unknown. This error can\
also apply to the TRACE OFF statement. \
\
Example of error:\
\
    TRACE procedure; -- error\
\
Correction:\
\
    SET DEBUG FILE TO 'trace.out';\
    TRACE procedure;\
\
|
-688	Variable variable-name must be declared CHAR or VARCHAR.\
\
You declared the variable as a data type other than CHAR or VARCHAR.\
Correct the declaration, and try again.\
\
|
-689	Global variable variable-name declared inconsistently.\
\
Two or more procedures were executed that defined the same global\
variable with different data types.\
\
Example of error:\
\
CREATE PROCEDURE test1()\
        DEFINE GLOBAL glob INT DEFAULT 10;\
	...\
	END PROCEDURE\
\
CREATE PROCEDURE test2()\
        DEFINE GLOBAL glob CHAR (9) DEFAULT USER;\
	...\
	END PROCEDURE\
\
Correction: Declare global variables consistently. (Using appropriate\
naming conventions would be useful.) Two variables of the same data\
type but different lengths are considered inconsistent.\
\
|
-690	Cannot read keys from referencing table table-name.\
\
The referential constraint could not be validated. See the ISAM error\
for more information. If you are using cascading deletes, database\
logging must be on.\
\
|
-691	Missing key in referenced table for referential constraint\
constraint-name.\
\
A referential constraint has been violated. This condition usually\
occurs when you are trying to insert a value into or update the value\
of a column that is part of a referential constraint. The value you are\
trying to enter does not exist in the referenced (parent-key)\
column. If you are using cascading deletes, database logging must be\
on.\
\
|
-692	Key value for constraint constraint-name is still being referenced.\
\
You have violated a referential constraint. This situation usually\
occurs when you are trying to delete a row in a column (parent key)\
that another row (child key) is referencing. If you are using cascading\
deletes, database logging must be on.\
\
|
-693	System command expects a non-null value.\
\
A null value was passed to the SYSTEM statement.\
\
Example of error:\
\
DEFINE c CHAR(100);\
        LET c = NULL;\
	...\
	SYSTEM c; -- error\
\
|
-694	Too many arguments passed to procedure procedure-name.\
\
More arguments were passed to a procedure than a procedure was declared\
to accept.\
\
|
-695	Argument is not a parameter of procedure procedure-name.\
\
A named parameter was passed to a procedure, but the named parameter\
does not exist.\
\
Example of error:\
\
CREATE PROCEDURE testproc (arg1 INT, arg2 INT) RETURNING INT;\
	...\
	RETURN 1;\
        END PROCEDURE\
\
SELECT col FROM tab WHERE testproc (arg1 = 10, arg5 = 20); -- error\
\
|
-697	STEP expression evaluated to ZERO.\
\
The STEP expression of a FOR statement evaluated to zero.\
\
Example of error:\
\
LET e = -1;\
FOR i = 10 TO 20\
        STEP e+1; -- error\
        ...\
        END FOR\
\
Correction: Change the STEP expression so that it evaluates to a\
nonzero value.\
\
|
-698	Inconsistent transaction. Number and names of servers rolled\
back - servers.\
\
This message is returned if an IBM Informix STAR two-phase commit or a\
distributed transaction is implemented with a mixed result. That is,\
some database servers participating in the transaction rolled back\
their parts of the global transaction, but other database servers\
committed their parts of the global transaction. The number of database\
servers that rolled back work is always accurate, but the list of\
server names (specified by DBSERVERNAME values) can be incomplete. If a\
large number of servers rolled back work, the list might be truncated\
to save space. Refer to the message log of the coordinator database\
server for a complete list of server names. If this error message is\
returned, you must determine whether your networked database system is\
in an inconsistent state. This procedure is described in detail in your\
Administrator's Guide.\
\
|
-696	Variable variable-name has undefined value.\
\
An SPL variable was referenced or a row field was set before \
a value was assigned.\
\
Example of error:\
\
DEFINE my_row_var1 (last_name CHAR(20), id INTEGER);\
DEFINE i, j INT; \
\
LET i = j + 1;                -- error\
LET my_row_var1.id = new_id;  -- error\
\
While\
\
LET my_row_var1 = ROW(NULL::CHAR(20), NULL::INTEGER)::person_rt;\
LET my_row_var1.id = new_id;  -- success\
\
Correction: Assign all variables and parameters valid values before\
you use them.\
\
Row type variables are allowed in SPL routines. Such\
variables must be initialized before they are used. To initialize\
a row type variable, you must initialize the entire variable.\
Initializing each field will not substitute for initializing the\
entire variable, and in fact you cannot initialize the individual\
fields until after you have initialized the entire variable. The\
following example shows correct and incorrect initialization of\
row type variables in SPL.  \
\
-- Example showing that row type variables in SPL must have the entire\
-- variable initialized. It is not sufficient to initialize the fields\
-- without initializing the entire variable.\
 \
   CREATE DATABASE tango;\
\
   drop table table1;\
   drop row type person_rt restrict;\
   drop function create_person_rt;\
   \
   CREATE ROW TYPE person_rt (last_name CHAR(20), id INTEGER);\
   \
   CREATE FUNCTION create_person_rt(new_name CHAR(20), new_id INTEGER)\
   RETURNING person_rt;\
   DEFINE my_row_var1 person_rt;\
   -- You cannot initialize the individual fields of the variable until you\
   -- have initialized the entire variable. If the following statement were \
   -- executed at this point, it would fail with error -696.\
   -- LET my_row_var1.id = new_id;   \
   -- Initialize the entire variable.\
   LET my_row_var1 = ROW(NULL::CHAR(20), NULL::INTEGER)::person_rt;\
   -- Now set the individual fields.\
   LET my_row_var1.id = new_id;\
   LET my_row_var1.last_name = new_name;  \
   RETURN my_row_var1;\
   END FUNCTION;\
    \
-- Sample usage:\
 \
   CREATE TABLE table1 (person_column person_rt);\
   INSERT INTO table1 (person_column) VALUES (create_person_rt('Uhuru', 128));\
    \
   CLOSE DATABASE;\
 \
   You must initialize the entire variable because the engine can\
   track whether or not the entire variable has been initialized\
   but cannot track initialization on a field-by-field basis.\
\
|
-699	Transaction heuristically rolled back.\
\
This message is returned if all participating database servers\
heuristically roll back an IBM Informix STAR two-phase commit transaction.\
Because all database servers rolled back the transaction, the networked\
database system remains consistent.\
\
|
-700	Statement is invalid within a global transaction.\
\
This error is generated when a user attempts to execute a BEGIN WORK,\
COMMIT WORK, or ROLLBACK WORK statement within a global transaction.\
\
|
-701	Statement is invalid within the XA environment.\
\
This error is generated when you attempt to execute any of the\
following statements within an X/Open distributed\
transaction-processing environment:\
\
    *   CLOSE DATABASE\
\
    *   CREATE DATABASE\
\
    *   DROP DATABASE\
\
    *   SET LOG\
\
Within this environment, you can execute a single DATABASE statement\
after an xa_open call to specify a current database. However, after\
this database is selected, no other DATABASE statement can be executed.\
This error is generated when you attempt to execute a second DATABASE\
statement.\
\
|
-702	Cannot open database in exclusive mode.\
\
Within an X/Open distributed transaction processing environment, you\
cannot open a database in exclusive mode.\
\
|
-703	Primary key on table table-name has a field with a null key value.\
\
An attempt was made either to insert a null value into a column that is\
part of a primary key, or to add a primary constraint to a table that\
has a NULL value in one of the key columns.\
\
|
-704	Primary key already exists on the table.\
\
A table can have only one primary key.\
\
|
-705	Cannot drop/modify procedure procedure-name. It is currently in use.\
 \
An attempt was made either to drop a currently executing procedure or\
to run UPDATE STATISTICS on a currently running procedure. This\
condition can occur if a procedure tries to drop itself or if a nested\
procedure tries to drop a procedure that called it.\
\
Example of error:\
\
   CREATE PROCEDURE testproc()\
   ...\
   DROP PROCEDURE testproc; -- error \
   END PROCEDURE\
\
Correction: You can use an ON EXCEPTION statement to trap this error\
and not carry out the DROP PROCEDURE or UPDATE STATISTICS statement.\
\
This error also occurs if you try to drop a function or procedure\
that a functional index is using.\
\
This error also occurs if you try to drop a function or procedure\
that a xadatasource type is using.\
\
-706	Execute privilege denied on procedure procedure-name.\
\
A user who does not own the procedure or is not DBA must have Execute\
privilege in order to run a procedure.\
\
|
-707	TEXT and BYTE columns in optical cluster must be distinct.\
\
The same column is specified more than once in the column list of the\
FOR clause in the CREATE OPTICAL CLUSTER statement. Change your\
statement so that no column appears more than once.\
\
|
-708	Optical cluster cluster-name already exists.\
\
You have attempted to create a new optical cluster with the name of an\
existing cluster. You must either drop the existing cluster or\
re-execute your statement using a different cluster name.\
\
|
-709	TEXT and BYTE column column-name is already clustered.\
\
You have already created an optical cluster using the named column.\
Because a single column can be part of only one optical cluster, your\
attempt to create a new cluster on this column has failed.\
\
|
-712	Cannot insert encoded BLOB descriptor in non-optical BLOB columns.\
\
You have attempted to use the DESCR() function to insert an encoded\
blob descriptor into a TEXT or BYTE column that is stored in a dbspace\
or blobspace. You can use this function only to insert descriptors into\
blob columns that are stored on optical media.\
\
|
-710	Table <table-name> has been dropped, altered, or renamed.\
\
This error can occur with explicitly prepared statements. These statements\
have the following form:\
\
    PREPARE statement id FROM "quoted_string"\
\
After a statement has been prepared in the database server and before\
execution of the statement, a table to which the statement refers might have\
been renamed or altered, possibly changing the structure of the table.\
Problems might occur as a result. Adding an index to the table after\
preparing the statement can also invalidate the statement.\
\
This error can also occur with SPL routines. Before the database server\
executes a new SPL routine the first time, it optimizes the code\
(statements) in the SPL routine. Optimization makes the code depend on\
the structure of the tables that the procedure references. If the table\
structure changes after the procedure is optimized, but before it is\
executed, this error can occur.\
\
The Auto Re-prepare feature allows the database server to check prepared \
statements and stored procedures prior to execution for changes to any tables\
that they reference. This feature prevents many of the common causes for the\
-710 error.\
\
When the Auto Re-prepare feature is enabled the following semantics apply:\
\
Before execution of a prepared statement or SPL routine the database server\
checks to determine if the structure of directly or indirectly referenced\
tables may have changed. If changes are detected the statement is checked\
prior to re-prepare:\
\
    * A change in the number or type of columns in the SELECT list will result\
      in error -710 being raised. In this case the application should prepare\
      and execute the statement again to allow the database server to \
      re-describe the SELECT list.\
\
    * For other changes the database server automatically re-prepares the\
      statement. If this is successful the statement will then be executed.\
\
Stored procedures are re-optimized and executed if the reoptimization succeeds.\
\
An error that occurs during the re-prepare of a statement or re-optimization of\
a SPL routine is returned to the application in place of the -710 error.\
\
When the Auto Re-pepare feature is not enabled the following semantics apply:\
\
A subsequent OPEN command for a cursor will fail if the cursor refers to the\
invalid prepared statement; the failure will occur even if the OPEN command has\
the WITH REOPTIMIZATION clause.\
\
If an index was added after the statement was prepared, you must prepare the\
statement again and declare the cursor again. You cannot simply reopen the\
cursor if it was based on a prepared statement that is no longer valid.\
\
This error can also occur if the table referenced by the statement has \
any foreign key references to tables that were renamed after the statement\
was prepared.\
\
Each SPL routine is optimized the first time that it is run (not when\
it is created). This behavior means that an SPL routine might succeed\
the first time it is run but fail later under virtually identical\
circumstances. The failure of an SPL routine can also be intermittent\
because failure during one execution forces an internal warning to\
reoptimize the procedure before the next execution.\
 \
The database server keeps a list of tables that the SPL routine\
references explicitly. Whenever any of these explicitly referenced tables is\
modified, the database server reoptimizes the procedure the next time the\
procedure is executed.\
\
However, if the SPL routine depends on a table that is referenced only\
indirectly, the database server cannot detect the need to reoptimize the\
procedure after that table is changed. For example, a table can be\
referenced indirectly if the SPL routine invokes a trigger. If a table\
that is referenced by the trigger (but not directly by the SPL routine)\
is changed, the database server does not know that it should reoptimize the\
SPL routine before running it. When the procedure is run after the\
table has been changed, this error can occur.\
\
Use one of two methods to recover from this error:\
\
    *   Issue the UPDATE STATISTICS statement to force reoptimization of the\
        procedure.\
\
    *   Rerun the procedure.\
\
To prevent this error, you can force reoptimization of the SPL routine.\
To force reoptimization, execute the following statement:\
\
    UPDATE STATISTICS FOR PROCEDURE procedure_name\
\
You can add this statement to your program in either of the following ways:\
\
    *   Place the UPDATE STATISTICS statement after each statement that\
        changes the mode of an object.\
\
    *   Place the UPDATE STATISTICS statement before each execution of the\
        SPL routine.\
\
For efficiency, you can put the UPDATE STATISTICS statement with the action\
that occurs less frequently in the program (change of object mode or\
execution of the procedure). In most cases, the action that occurs less\
frequently in the program is the change of object mode.\
\
When you follow this method of recovering from this error, you must execute\
the UPDATE STATISTICS statement for each procedure that references the \
changed tables indirectly unless the procedure also references the tables\
explicitly.\
\
You can also recover from this error by simply rerunning the SPL routine.\
The first time that the stored procedure fails, the database server\
marks the procedure as in need of reoptimization. The next time that\
you run the procedure, the database server reoptimizes the procedure before\
running it. However, running the SPL routine twice might be neither\
practical nor safe. A safer choice is to use the UPDATE STATISTICS statement\
to force reoptimization of the procedure.\
\
-711	Cannot insert encoded BLOB descriptor.\
\
An attempt to insert an encoded blob descriptor by means of the DESCR()\
function has failed. See the ISAM error for more information.\
\
|
-713	Cannot decode encoded BLOB descriptor.\
\
The decoding of a blob descriptor prior to its insertion into a data\
row has failed. See the error from the optical subsystem (an error in\
the -7000 to -7199 range) for more information.\
\
|
-714	Cannot encode BLOB descriptor.\
\
The encoding of a blob descriptor for storage on optical media has\
failed. See the error from the optical subsystem (in the -7000 to -7199\
range) for more information.\
\
|
-715	Transaction state error.\
\
An error occurred in retrieving a transaction state. See the ISAM error\
for more information.\
\
|
-716	Possible inconsistent transaction. Unknown servers are server-name-list.\
\
This message appears after an administrator ends a coordinator\
database server process, thread, or session using tbmode -z or onmode\
-z any time after the coordinator issues its decision either to commit\
or roll back a two-phase commit transaction. You must examine the\
message log or the logical log at each of the database servers for\
which the status is listed as unknown to determine whether the local\
transaction was committed or rolled back. If some participating\
database servers rolled back the transaction, and others committed it,\
you must determine whether your networked database system is in an\
inconsistent state. This procedure is described in detail in your\
Administrator's Guide.\
\
|
-717	Invalid argument passed to system function function-name.\
\
An invalid data type has been passed to one of the arithmetic functions\
(HEX(), TRUNC(), ROUND()).\
\
|
-718	Statement is invalid while a global transaction is suspended.\
\
If a database server that is acting as a Resource Manager in an X/Open\
distributed transaction-processing environment has suspended a\
transaction, its next statement must be xa_start. All other statements\
are disallowed.\
\
|
-719	Loop variable variable-name cannot be declared GLOBAL.\
\
A global variable cannot be used as a loop variable. Redefine the\
variable to be local to the loop, or use another (local) variable as\
the loop variable.\
\
|
-720	Number of columns in FOREACH SELECT does not match number of variables.\
\
A mismatch exists in the number of columns the SELECT returns and the\
number of variables that are specified in the INTO list. Correct the\
number of variables in the INTO list.\
\
|
-721	SPL routine (<routine-name>) is no longer valid.\
\
You are attempting to execute a procedure from an EXECUTE statement,\
but it has been redefined since the PREPARE statement was run. You must\
use the PREPARE statement again on the EXECUTE PROCEDURE statement.\
\
For example, the following sequence of code would cause this error:\
\
$prepare pr_stat from 'execute procedure testproc()';\
	...\
	/* drop procedure testproc create procedure testproc() ......\
	[same application or different] */\
	...\
	$execute pr_stat;/* triggers error -721 */\
\
|
-722	Out of stack space.\
\
The database server has run out of memory for stack space. Ask the\
Informix database administrator to increase the STACKSIZE parameter\
that is specified in the $ONCONFIG file to allocate more memory. The \
database server must be restarted for the change to take effect.\
\
|
-723	Cannot disable logging in an ANSI-compliant database.\
\
You attempted to use the START DATABASE <database> WITH NO LOG syntax\
to remove database logging on an SE database that is ANSI compliant.\
You cannot turn off logging by running this statement on this kind of\
database.\
\
|
-724	System initialization file $INFORMIXDIR/cnv50t60.sql is missing.\
\
Check that $INFORMIXDIR/cnv50t60.sql is in place and readable. If it\
is, and the system still fails, reinstall the system.\
\
|
-725	Error occurred while reading system initialization file\
$INFORMIXDIR/cnv50t60.sql.\
\
Check that the script file $INFORMIXDIR/cnv50t60.sql is readable. If it\
is, and the failure still occurs, reinstall the product.\
\
|
-726	First argument to dbinfo() must be a quoted string constant.\
\
The first argument to dbinfo() should be a quoted string constant. If\
the first argument to dbinfo() is the string 'version', then the second\
argument should also be a quoted string constant.\
\
|
-726	First argument to dbinfo() must be a quoted string constant.\
\
Check that the first argument to dbinfo() is a quoted string that\
corresponds to one of the following values: 'dbspace', 'sqlca.sqlerrd1',\
or 'sqlca.sqlerrd2'.\
\
|
-727	Invalid or NULL tblspace number given to dbinfo(dbspace).\
\
You called the dbinfo() function with the 'dbspace' string constant as\
the first parameter. You must provide either the number of a valid\
tablespace or an expression that evaluates to such a number as the\
second parameter. Check that you supplied a number as your second\
parameter and that it corresponds to the number of a valid tablespace.\
\
|
-728	Unknown first argument of dbinfo(<argument>).\
\
Check that the first argument to dbinfo() is a quoted string that corresponds\
to one of the following values: 'dbspace', 'version', 'sqlca.sqlerrd1',\
'sqlca.sqlerrd2', 'sessionid', 'coserverid', 'utc_to_datetime',\
'utc_current', 'get_tz', or 'dbhostname'.\
\
|
-728	Unknown first argument of dbinfo argument-name.\
\
The valid arguments to the dbinfo() function are the quoted string\
'dbspace' followed by the number of a valid tablespace, or one of the\
following two values: 'sqlca.sqlerrd1' or 'sqlca.sqlerrd2'. Check that\
you supplied one of these values and enclosed the string in quotes.\
\
|
-729	Trigger has no triggered action.\
\
Your CREATE TRIGGER statement does not include a triggered action. Add\
a triggered action list to the trigger definition, and resubmit the\
CREATE TRIGGER statement.\
\
|
-730	Cannot specify REFERENCING if trigger does not have FOR EACH ROW.\
\
You included a REFERENCING clause in a CREATE TRIGGER statement that\
does not include a FOR EACH ROW triggered-action section. Either remove\
the REFERENCING clause or, if it is appropriate, add the missing\
keywords FOR EACH ROW, followed by the triggered actions that are to\
occur at that time.\
\
|
-731	Invalid use of column reference in trigger body.\
\
For insert and delete triggers, the offending column is being used in\
the INTO clause of the EXECUTE PROCEDURE statement (which is only\
allowed for an update trigger). Remove the column names from the INTO\
clause.\
\
|
-732	Incorrect use of old or new values correlation name inside trigger.\
\
You cannot use the new or old correlation name outside the FOR EACH ROW\
section or in the INTO clause of the EXECUTE PROCEDURE statement. You\
cannot use the new or old correlation name to qualify the SELECT COUNT\
DISTINCT column. For example, the following statement returns this\
error:\
\
SELECT COUNT (DISTINCT oldname.colname)\
\
You cannot specify an old correlation name for an insert trigger. You\
cannot specify a new correlation name for a delete trigger.\
\
|
-733	Cannot reference procedure variable in CREATE TRIGGER or CREATE VIEW\
statement.\
\
You have a CREATE TRIGGER or CREATE VIEW statement inside an SPL\
routine, and within the CREATE TRIGGER or CREATE VIEW statement,\
you reference a variable that is defined in the SPL routine.\
This action is not legal. Remove the reference to the SPL-routine\
variable from the CREATE TRIGGER or CREATE VIEW statement and try again.\
\
|
-734	Object name matches old or new values correlation name.\
\
This error is returned in three cases:\
\
    *   The name of the triggering table or the synonym, if it is used,\
	matches the old or new correlation name in the REFERENCING\
	clause.\
\
    *   The name of a table or a synonym that is referenced in the\
	action clause matches either the old or new correlation name in\
	the REFERENCING clause.\
\
    *   The old correlation name matches the new correlation name.\
\
Change either the correlation name or the table name, and execute the\
CREATE TRIGGER statement again.\
\
|
-735	Cannot reference table that participates in cascaded delete.\
\
If a child table is referenced in a correlated subquery that is part of\
a DELETE statement, the child table cannot be one of the tables on\
which a delete would cascade. This action is not allowed because the\
result depends on the order in which the rows are processed. Rewrite\
your query so that the child table is not referenced in a correlated\
subquery.\
\
|
-736    The RESOLUTION and SAMPLING SIZE clauses are not valid for the \
LOW mode of the UPDATE STATISTICS statement.\
\
Because data distributions are constructed only in the MEDIUM or HIGH\
modes of the UPDATE STATISTICS statement, specifying the resolution or \
sampling size is not meaningful in LOW mode. \
\
Remove the RESOLUTION clause and the SAMPLING SIZE clause from the statement.\
\
To use the SAMPLING SIZE clause, change the mode to MEDIUM. To use the \
RESOLUTION clause, change the mode to MEDIUM or HIGH.\
\
|
-737    The confidence value and the SAMPLING SIZE clause are not valid for the \
HIGH mode of the UPDATE STATISTICS statement.\
\
Remove the confidence value and the SAMPLING SIZE clause from the statement. \
\
For example, the following statement has a confidence value of 0.99:\
\
UPDATE STATISTICS HIGH RESOLUTION 0.1 0.99;\
\
The corrected statement is:\
\
UPDATE STATISTICS HIGH RESOLUTION 0.1;\
\
If you want a distribution that is based upon sampling rather than one\
that uses all of the data in a column, change the mode from HIGH to MEDIUM \
and you specify number of samples using the SAMPLING SIZE clause.\
\
|
-738	DROP DISTRIBUTIONS is only valid in LOW mode.\
\
By default, LOW mode does not remove distributions, so you need to use\
the DROP DISTRIBUTIONS clause. To remove HIGH or MEDIUM distributions,\
use the DROP DISTRIBUTIONS clause.\
\
|
-739	Confidence must be in the range [0.80, 0.99] (inclusive).\
\
If the value of the confidence desired is greater than 0.99, use HIGH\
mode. A value of less than 0.80 is not allowed because it will probably\
yield a poor distribution. If you are reducing the confidence to reduce\
the time that is required to execute the UPDATE STATISTICS statement,\
consider using a larger resolution value.\
\
|
-740	Resolution must be greater than 0.005 and less than, or equal to, 10.0.\
\
The value of this parameter determines how finely the data distribution\
is resolved. A resolution of 10.0 implies that the accuracy of any\
estimate for the application of any single selection filter is limited\
to (+ or -) 5 percent. A value greater than 10.0 would be of little\
value because it would not provide sufficient detail about the\
distribution of the data.\
\
|
-741	Trigger for the same event already exists.\
\
You are creating a trigger for an event, but another trigger already\
exists for that event. You can have only one insert or delete trigger\
on a table. If you are defining multiple triggers that occur on an\
update, the column lists in the UPDATE statements must be mutually\
exclusive. You cannot name a column as a triggering column in more than\
one UPDATE clause.\
\
|
-742	Trigger and cascading-delete referential constraint cannot coexist.\
\
Delete triggers cannot coexist with referential constraints.\
\
This error occurs if you try to add a delete cascade foreign key to a table \
that already has a delete trigger on it. This error also occurs if you try\
to add a delete trigger to a table that already has a delete cascade foreign\
key.\
\
|
-743	Object object_name already exists in database.\
\
You are trying to define an object that already exists in the database.\
\
|
-744	Illegal SQL statement in trigger.\
\
This error is returned when the triggered SQL statement is BEGIN WORK,\
COMMIT WORK, ROLLBACK WORK, or SET CONSTRAINTS. These statements are\
not allowed as triggered actions. Remove the offending statement.\
\
|
-745	Trigger execution has failed.\
\
This message is defined for general use to apply to error conditions\
that you specify in an SPL routine that is a triggered action.\
\
|
-746	message-string\
\
You supply message-string for this message. You can apply this message \
to error conditions that you specify in an SPL routine. The corrective\
action for this error depends on the condition that caused it. You, the user,\
define both the condition and the message text.\
\
|
-747	Table or column matches object referenced in triggering statement.\
\
This error is returned when a triggered SQL statement acts on the\
triggering table, or when both statements are updates, and the column\
that is updated in the triggered action is the same as the column that\
the triggering statement updates.\
\
|
-748	Exceeded limit on maximum number of cascaded triggers.\
\
You exceeded the maximum number of cascading triggers, which is 61. You\
may be setting off triggers without realizing it. You can query the\
systriggers system catalog table to find out what triggers exist in the\
database. To trace the triggered actions, place the action clause of\
the initial trigger in an SPL routine, and use the SPL TRACE\
statement.\
\
|
-749	Remote cursor operation disallowed with pre-5.01 server.\
\
An external database server before Version 5.01 sent the triggering\
statement or cursor operation. This action is not allowed.\
\
|
-750	Invalid distribution format found for table_name.\
\
This internal error should not occur unless the database has been\
corrupted in some way. To rebuild the distribution, use UPDATE\
STATISTICS. If the error recurs, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-751	Remote procedure execution disallowed with pre-5.01 server.\
\
The action clause of the trigger contains an SPL routine that is\
not called in a data manipulation statement, and an external database\
server before Version 5.01 will execute the procedure. This action is\
not allowed. An SPL routine that is called within a data\
manipulation statement cannot execute certain SQL statements, including\
transaction-related statements. Transaction-related statements are not\
allowed within an SPL routine that is a triggered action. A database\
server before Version 5.01 cannot check for this condition, so\
the procedure is not allowed. If possible, execute the procedure on a\
Version 5.01 or later database server.\
\
|
-752	All Smart Disk devices are busy.\
\
Wait a while and retry your Smart Disk operation.\
\
|
-753	Access denied - Single user limit has been exceeded.\
\
Licensing enforcement is configured for only one user; multiple users\
cannot use the product at the same time. If you are using the product\
from a remote computer, the product is licensed only for a nonnetworked\
environment.If you are using the product from a local computer, wait\
until the current user exits and try again.\
\
|
-754	Cannot access the license file.\
\
The system cannot find the user license file. The user license file\
might not have been installed, or it might have been installed\
improperly. Also, you might not have the correct file or directory\
permissions to access the user license file. Consult your installation\
documentation.\
\
|
-755	Cannot access the license file to release license.\
\
You might not have appropriate permission for your particular action.\
Check with your system administrator.\
\
|
-756	Evaluation version has expired.\
\
The evaluation version of this product will work only for a specified\
period of time. This version allows you to evaluate the product but not\
use it permanently. When the evaluation version expires, call IBM\
to order a standard version of the product.\
\
|
-757	File open for light append can't pseudo close.\
\
If this internal error recurs, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-758	Cannot implicitly reconnect to the new server server_name.\
\
If you use the CONNECT TO statement to connect to a server, you cannot\
implicitly reconnect to another server through one of the DATABASE\
statements (DATABASE, START DATABASE, and so on). You must switch to it\
with the SET CONNECTION statement.\
\
|
-759	Cannot use database commands in an explicit database connection.\
\
If you use the CONNECT TO database@server syntax to connect to a database\
and server, you cannot select another database until you disconnect your\
current connection.\
\
|
-760	Remote procedure must commit or rollback before returning.\
\
Your remote procedure must execute a COMMIT WORK or ROLLBACK WORK\
statement before that procedure returns control to your application.\
\
|
-761	INFORMIXSERVER does not match either DBSERVERNAME or DBSERVERALIASES.\
\
Your INFORMIXSERVER environment variable does not match the\
DBSERVERNAME or any of the DBSERVERALIASES settings in the ONCONFIG\
configuration file of the server to which you are trying to connect.\
Check your environment variables and the ONCONFIG configuration file.\
Check that INFORMIXSERVER matches one of the settings in the ONCONFIG\
file.\
\
|
-762	Stack overflow occurred during statement parse.\
\
This error indicates that an internal memory limitation in the SQL\
parser has been reached. This condition can occur if your query\
contains many nested expressions. For example, the query might contain\
many occurrences of AND and/or OR in the WHERE clause. To work around\
this condition, rewrite the query to eliminate some of the nested\
expressions.\
\
|
-763	Error in auditing environment initialization.\
\
This all-purpose message indicates a problem when a user tries to\
connect to a secure database server. Contact your security\
administrator or DBA for how to proceed.\
\
|
-764	Only DBA can run update statistics on a database in this mode.\
\
You tried to run the UPDATE STATISTICS statement with the DROP\
DISTRIBUTIONS clause on the entire database in a mode other than LOW.\
Only user informix or the database administrator can do perform this\
action.\
\
|
-765	Cannot EXECUTE a statement that has been DECLAREd.\
\
You cannot execute a prepared statement that has been declared.\
However, to specify output variables for a prepared singleton SELECT\
statement, use EXECUTE INTO (or EXECUTE PROCEDURE INTO) instead of\
executing DECLARE, OPEN, and FETCH statements.\
\
|
-766	String must be null terminated.\
\
With IBM Informix ESQL/C, if you use a host variable in an INSERT statement\
or in the WHERE clause of an SQL statement, and the database is ANSI\
compliant, the string must be null terminated.\
\
|
-767	Cannot UPDATE/INSERT a remote table using views with check options.\
\
You cannot perform an UPDATE or INSERT operation on a table that\
resides across a network when you are using views that have check\
options. Remove the all check options from the view, or perform the\
UPDATE/INSERT locally.\
\
|
-768	Internal error in routine routine-name.\
\
If this internal error recurs, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-769	Internal - iterator execution/phase error parameter.\
\
If you cannot find a direct cause for this internal error, note\
all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-770	Bad fragment id specified.\
\
If you cannot find a direct cause for this internal error, note\
all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-771	Bad table lock id specified.\
\
If you cannot find a direct cause for this internal error, note\
all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-772	Record/key doesn't qualify for any table/index fragment.\
\
This error can occur during a record insert or update. The most likely\
cause is an incorrect fragmentation specification that did not specify\
a REMAINDER. The easiest correction is to add a REMAINDER fragment to\
your SQL statement. However, the best correction is probably to\
reexamine the original fragmentation specification, figure out what is\
wrong, and fix it with an ALTER FRAGMENT statement.\
\
|
-773	Expression required for new fragment.\
\
When you add a fragment to an expression-based fragmentation strategy,\
you must specify an expression for the new fragment. Restate your SQL\
statement to include a fragment expression.\
\
|
-774	Cannot specify fragment expressions with a round-robin fragmentation.\
\
If table fragmentation is based on a round-robin strategy, you cannot\
specify a fragment expression during an ALTER FRAGMENT operation.\
\
|
-775	Fragment partition name not used by table/index.\
\
The partition that is specified during an ALTER FRAGMENT operation is\
incorrect because that partition contains no fragment. \
Specify a partition that has a fragment. Partition names default to the\
dbspace name if not specified at create time.\
\
|
-776	Alter fragment error: unable to move rows to new fragmentation scheme.\
\
During an ALTER FRAGMENT operation, the rows could not be moved to\
another fragmentation strategy. See the accompanying ISAM error for\
more information on why the ALTER FRAGMENT operation failed.\
\
|
-777	Internal - function not valid on fragmented table.\
\
If you cannot find a direct cause for this internal error, note\
all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-778	Unable to alter fragmentation scheme on index.\
\
During an ALTER FRAGMENT operation, the fragmentation strategy for the\
index could not be altered. See the accompanying ISAM error for more\
information on why the ALTER FRAGMENT operation failed.\
\
|
-779	Duplicate table name in the alter fragment specification.\
\
You cannot attach the same table multiple times. Check that your alter\
fragment specification attaches the same table only once.\
\
|
-780	Table/index is not fragmented.\
\
You cannot perform the ALTER FRAGMENT operation because the table or\
index is not fragmented. Fragment the table or index, or do not perform\
the fragmentation operation.\
\
|
-781	Cannot alter fragmentation on a temp table.\
\
You tried to alter a fragment that is based on a temporary table. In\
general, dynamic modification of a TEMP table is not allowed. You must\
re-create the temporary table if you require a different fragmentation\
scheme.\
\
|
-782	Attached table is fragmented.\
\
When you attach tables, the consumed table cannot be fragmented.\
\
|
-783	Cannot attach because of incompatible schema.\
\
Incompatible table schemas do not allow you to perform an attach. When\
you perform an attach, the table schemas must be identical and tables must\
be compatiable from LBAC perspective. Use the ALTER TABLE statement to \
make the schemas identical, the surviving table and consumed table\
to be protected by the same security policy, and make the protected \
columns to be protected by the same set of security labels. Then perform \
an ALTER FRAGMENT...ATTACH operation.\
\
|
-784	Cannot detach because of the existing referential constraints.\
\
Existing referential constraints do not allow you to perform a detach.\
You must drop the referential constraints before you perform the detach\
on the dbspace/partition or table.\
\
|
-785	Cannot drop column because of table or index fragmentation.\
\
You must alter fragmentation expressions to remove references to the\
column before the column can be dropped.\
\
|
-786	Table being attached to is not in the attach list.\
 \
The surviving table is either nonfragmented or hash-fragmented and must\
appear in the attach list in order for its existing fragment to be \
properly positioned in the resulting fragmentation scheme.\
\
|
-787	Index fragmented same-as-table cannot be altered.\
\
If you do not specify storage-spec in a CREATE INDEX statement, the\
indexes are fragmented the same as the underlying table, subject to all\
the restrictions on fragmented indexes. For example, an error is\
returned if the underlying fragmentation strategy is round-robin, and\
the index is unique. You cannot alter this type of index fragmentation.\
If you want to change the index fragmentation, use the INIT option of\
ALTER INDEX to detach the index. That operation makes the index and\
table independent and lets you alter each independently.\
\
|
-788	Unknown operator/type.\
\
If you cannot find a direct cause for this internal error, note\
all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-789	Internal error, expression not properly defined.\
\
If you cannot find a direct cause for this internal error, note\
all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-790	Rowids already exist on table.\
\
You cannot create rowids multiple times. You attempted to add rowids to\
a table that was already defined with rowids. Do not run the command\
that caused this error.\
\
|
-791	Cannot open the Informix password file.\
\
Check the INFORMIXDIR environment variable to ensure that it is set to\
the correct value. Also, check INFORMIXDIRETCPASSWD, the Informix\
password file. If the Informix password file is corrupted or deleted,\
reinstall the IBM Informix SE database server.\
\
-795	Error in finding interrupt. The Informix NET for Windows TSR probably\
is not loaded.\
\
If you intend to communicate with an IBM Informix OnLine for NetWare\
database server across a network, you must run the INETIPX.EXE TSR\
(terminate-and-stay-resident program) in the DOS environment. Check\
that you have enough memory to load this TSR.\
\
|
-800	Corresponding types must be compatible in CASE expression.\
\
All the result values in all the WHEN clauses in the CASE expression should be\
of compatible types. In the linearized use of the CASE expression, the\
value-expression that follows the CASE keyword should be compatible with the\
value-expressions that follow all the WHEN keywords in the CASE expression.\
Reissue the query after modifying the CASE expression so that all\
related expressions are of compatible types.\
\
|
-801	SQL Edit buffer is full.\
\
The text editor cannot expand the buffer in which it stores your SQL\
statements because no more data space memory is available. If you have\
multiple statements in the buffer, execute them one at a time.\
\
|
-802	Cannot open file for run.\
\
The SQL command file that you specified cannot be opened for reading.\
Review the filename that you specified. If it is spelled as you\
intended, check that it exists in the current directory or in a\
directory that is named in the DBPATH environment variable and that\
your account has read permission for it.\
\
|
-803	The file is too large for internal editing.\
\
The SQL command file that you selected with the Choose option is too\
large for the edit buffer to hold. The size of the edit buffer is\
dynamic, and the program was unable to allocate enough memory to hold\
the contents of the command file. (In DOS, this error also appears if\
the command file exceeds 64 kilobytes.) Check that you specified the\
file you intended and that it is in fact an SQL command file. If it is\
the file that you intended, break it into smaller parts, and use them\
separately.\
\
|
-804	Comment has no end.\
\
This statement includes a comment that is enclosed in braces ({ }), but\
the closing brace is missing. Review the punctuation of the statement,\
and check that all braces appear in matching pairs.\
\
|
-805	Cannot open file for load.\
\
The input file that is specified in this LOAD statement could not be\
opened. Check the accompanying ISAM error code for more information.\
Possibly a more complete pathname is needed, the file does not exist,\
or your account does not have read permission for the file or a\
directory in which it resides.\
\
|
-806	Cannot open file for unload.\
\
The output file that is specified in this UNLOAD statement could not be\
opened. Check the accompanying ISAM error code for more information.\
Possibly a more complete pathname is needed; the file exists, but your\
account does not have write permission for it; or the disk is full.\
\
|
-807	Cannot open file for output.\
\
The program cannot create the file that you specified with the Save\
option. The file should be saved in the current directory. Possibly\
your account does not have write permission in that directory. Possibly\
a read-only file of the same name exists (to eliminate this\
possibility, try to save the file under a different name). Possibly the\
disk is full. Look for operating-system error messages that might give\
more information.\
\
|
-808	Cannot open file for choose.\
\
The SQL command file that you specified for the Choose menu option\
cannot be opened for input. Check that the file is in the current\
directory and readable to your account.\
\
|
-809	SQL Syntax error has occurred.\
\
The INSERT statement in this LOAD/UNLOAD/INFO statement has invalid syntax.\
Review it for punctuation and use of keywords.\
\
|
-810	Cannot open file for save.\
\
The SQL command file could not be saved. Check that your account has\
operating-system permission to write in the current directory and that\
the disk is not full.\
\
|
-811	Cannot open printer for output.\
\
The application is trying to open the device that is specified in the\
DBPRINT environment variable but is failing. Check the setting of that\
variable, and rerun the program.\
\
|
-812	Cannot open pipe for output.\
\
Under the Output option, you selected To-pipe and specified a program\
or command to receive the output. However, Informix SQL was unable to\
open the pipe to that program or command. Review the program or command\
that you typed to ensure that it is a syntactically valid UNIX or DOS\
command and that it names only programs that are in your current\
execution path. Also look for operating-system error messages; you\
might have exceeded a system quota on memory or processes.\
\
|
-813	Cannot write to pipe for output (no reading process).\
\
Under the Output option, you sent output to a command or program\
through a pipe. Although the pipe was established (indicating that the\
command had correct syntax and named existing programs), it has since\
closed unexpectedly. This condition indicates that the (first) program\
in the pipe terminated before it had received all the output. Possibly\
it quit due to an error, or possibly you or another user terminated it\
with a kill command. Look for messages from the pipe program that\
might explain why it quit.\
\
|
-816	Cannot write file (check file permissions).\
\
The file that is specified in the prior command cannot be written.\
Probably your account does not have operating-system permission to\
write to the file. Check the permissions, and run the program again.\
\
|
-817	Cannot read file (check file permissions).\
\
The file that is specified in the prior command cannot be read.\
Probably your account does not have operating-system permission to read\
the file. Check the permissions, and run the program again.\
\
|
-818	Specified user menu not found.\
\
The user menu that was requested cannot be found. Check the spelling of\
the menu name. If it is as you intended, check the contents of the\
sysmenus table in the current database; the menu might not be defined\
in this database.\
\
|
-819	There are no menu items in the menu.\
\
The menu that you selected contains no items. You can choose a\
different menu or modify the current one. If you think that the menu\
should have items, check the contents of the sysmenuitems table in the\
current database.\
\
|
-820	No more data to display.\
\
The display of selected rows is finished. With no scrolling display,\
you cannot show the rows again. Restart the query from the beginning,\
or enter a new query.\
\
|
-821	Cannot open file for default report.\
\
You requested creation of a default-report specification. This file is\
saved in the current directory, but some problem prevented it. Possibly\
the disk is full, or possibly your account does not have\
operating-system permission to write in that location.\
\
|
-822	Statements are already saved.\
\
The current SQL statement has already been saved under the name that is\
shown at the top of the screen. (This message does not appear to occur\
any longer.)\
\
|
-823	There are no statements to run.\
\
You selected the Run option, but no SQL statement has been entered.\
Either enter a statement, or use Choose to load one.\
\
|
-824	Missing values clause on insert statement.\
\
Probably no current IBM Informix product returns this message. If this\
message does appear, refer to the discussion of error -836. If the\
error recurs, note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
|
-825	Program not found.\
\
No supporting executable file could be located. The file should have\
existed in the directory that the INFORMIXDIR environment variable\
names. Consult the person who installed the IBM Informix software.\
\
|
-826	Fork system call failed.\
\
This internal error indicates an inability to start a subordinate\
process. Possibly it stems from an attempt to enter vi from DB-Access\
when using the Use-editor option. Look for operating-system error\
messages that might give more information. Retry the operation. If the\
error recurs, contact your system administrator. In DOS systems, you\
probably are out of memory; exit to the operating-system command line,\
and resubmit your program.\
\
|
-827	Database not found.\
\
See the discussion of error -329.\
\
|
-828	Command file not found.\
\
The SQL command file that you specified is not found in the current\
directory or in the directory that is listed in the DBPATH environment\
variable. Check the spelling of the name and the setting of DBPATH.\
\
|
-829	Form not found.\
\
The compiled form specification that you specified is not found in the\
current directory or in the directory that is listed in the DBPATH\
environment variable. Check the spelling of the name and the setting of\
DBPATH.\
\
|
-830	Report not found.\
\
The compiled report specification that you specified is not found in\
the current directory or in the directory that is listed in the DBPATH\
environment variable. Check the spelling of the name and the setting of\
DBPATH.\
\
|
-831	Error found in Report specifications.\
\
One or more errors was found during compilation of the report\
specification. Edit the report-specification file, and compile it\
again. Follow the prompts to see the error messages. To look them up,\
use the finderr utility.\
\
|
-832	Error found in Form specifications.\
\
One or more errors was found during compilation of the report\
specification. Edit the report specification file, and compile it\
again. Follow the prompts to see the error messages. To look them up,\
use the finderr utility.\
\
|
-833	Saceprep could not compile Report.\
\
The report compiler, saceprep, encountered an error while it was\
compiling a report specification. Look for other error messages, from\
saceprep and the operating system, that might give more information.\
\
|
-834	Sformbld could not compile Form.\
\
The report compiler, sformbld, encountered an error while it was\
compiling a report specification. Look for other error messages, from\
sformbld and the operating system, that might give more information.\
\
|
-835	Current clause is invalid in interactive mode.\
\
The WHERE CURRENT OF clause is meaningful only in a program that uses a\
cursor to read rows. In this interactive context, you must specify a\
condition other than CURRENT in your WHERE clause.\
\
|
-836	Insert statement has no values clause.\
\
The INSERT statement that was entered as part of this LOAD statement\
requires a VALUES clause. Revise the statement to include one.\
\
|
-837	There is not enough memory available.\
\
Informix SQL needed to allocate memory for one of a number of small\
work areas but was not able to do so. Stop the program, and restart it.\
If this action does not eliminate the problem, see your system\
administrator about getting more memory. On DOS systems, you need to\
free some disk space.\
\
Database servers after Version 4.1 do not produce this error message.\
For a related error, see error message -208.\
\
|
-838	A line in the load file is too long.\
\
Each line of the input file to LOAD must be read into storage in full\
to be processed. Informix SQL resizes its memory buffer as required to\
hold the current line. But in this case, it was not able to allocate a\
large enough buffer. This error is most likely when the load file\
contains TEXT or BYTE data values or very large CHAR values. All of the\
values for one row must be contained in one line of the file. If you\
cannot rerun the program with more memory available, modify the input\
file to have fewer or shorter values in each row. Or use the dbload\
utility to try to load the file.\
\
|
-839	Table not found.\
\
You specified the name of a table that does not exist in the current\
database. Review the spelling of the table name, and check that you\
are using the correct database. Refer to the discussion of error -310\
for a way to display all table names.\
\
|
-840	Name is too long.\
\
Names of databases, reports, forms, and other files must be 10\
characters or shorter. Select a new, shorter name, and repeat this\
operation. In DOS systems, filenames can be a maximum of 8 characters\
plus a 3-character extension.\
\
|
-841	Name must start with a letter or "_" and contain letters, digits,\
or "_".\
\
Names of databases, reports, forms, and other files must conform to\
this rule. Repeat this operation with a name that conforms to the\
rule. Beginning with Version 6.0, the name of the following\
identifiers, as well as server and cursor names, can begin with an\
underscore: column, connection, constraint, database, index, procedure,\
synonym, table, trigger, and view.\
\
|
-842	Cannot read temp file.\
\
Informix SQL created a temporary file; now it is trying to read back\
the temporary file. However, it received an unexpected operating-system\
return code. Possibly you or another user removed the file, or possibly\
a hardware error occurred.\
\
|
-843	Cannot write temp file.\
\
Informix SQL is trying to write the current SQL source file into a\
temporary file for editing but received an unexpected operating-system\
return code. Look for operating-system error messages that might give\
more information. On UNIX systems, possibly your account does not have\
write access to /tmp or the directory that is named in the DBTEMP\
environment variable, or the disk might be full. With Version 5.01 and\
later, the IBM Informix SE database server uses the DBTEMP environment\
variable, but IBM Informix Dynamic Server and IBM Informix OnLine Dynamic Server \
do not.\
\
|
-844	Statement is too long -- out of memory.\
\
Informix SQL was unable to allocate a memory buffer large enough to\
hold this statement. Find a way to shorten the statement, or run it in\
two or more parts.\
\
|
-845	There are no user-menus in the database.\
\
This database does not contain the sysmenus table, it is empty, or\
possibly the top-level menu is not named main. Check that you are using\
the database you intended. Consult with the person who defined the user\
menus for this database.\
\
|
-846	Number of values in load file is not equal to number of columns.\
\
The LOAD processor counts the delimiters in the first line of the file\
to determine the number of values in the load file. One delimiter must\
exist for each column in the table or for each column in the list of\
columns if one is specified. Check that you specified the file that you\
intended and that it uses the correct delimiter character. An empty line\
in the text can also cause this error.\
\
If the LOAD statement does not specify a delimiter, verify that the default\
delimiter matches the delimiter that is used in the file. If you are in\
doubt about the default delimiter, specify the delimiter in the LOAD\
statement.\
\
|
-847	Error in load file line number.\
\
A problem exists with the data on the indicated line of the load data\
file. The operation stopped after it inserted lines up to but not\
including the line that is noted (number-1 rows have been inserted). If\
this operation is inside a transaction, roll back the transaction. If\
not, either delete the inserted rows from the table or remove the used\
lines from the file before you repeat the operation. To correct the\
file, look for additional error messages that might help isolate the\
problem. Possibly not enough, or too many, fields (delimiters) exist on\
the indicated line. Possibly a data conversion problem exists, (for\
example, nonnumeric characters in a numeric field, an improperly\
formatted DATETIME value, or a character string that is too long).\
Possibly a null (zero-length) field exists in a column where nulls are\
not allowed. Edit the load file to correct the problem. Look for\
similar problems in following lines, and then repeat the operation.\
\
|
-848	Form4gl could not compile Form.\
\
You asked for a form specification to be compiled, but the form\
compiler reported one or more errors. Correct the errors in the form\
specification, and repeat the operation. The error messages are in the\
formname.err file.\
\
|
-849	Warning found in Form specifications.\
\
You asked for a form specification to be compiled, and it was done, but\
the form compiler reported one or more warnings. You are not required\
to correct a warning before you try the form, but it is recommended\
it. The error messages are in the formname.err file.\
\
|
-850	User does not have permission to modify this menu.\
\
Only the user who created the sysmenus table in this database can\
modify the menu structure. That user first selected the Modify option\
of the User-Menu display while this database was current. To determine\
who that user is, query systables as follows:\
\
SELECT owner FROM systables WHERE tabname LIKE 'sysmenu*'\
\
If this action is not appropriate, ask that person to drop the sysmenus\
and sysmenuitems tables, and then have the person who should maintain\
the menus re-create them.\
\
|
-851	Cannot drop file (check file permissions).\
\
You requested that a file be dropped, but it could not be dropped,\
probably because your account does not have write permissions on it or\
on the directory in which it is stored. Use operating-system commands\
to check the file permissions.\
\
|
-852	Write failed. count rows unloaded (check ulimit or disk space).\
\
After writing count lines of output to the unload file, an error\
occurred trying to write the next line. Look for operating-system\
messages that might give more information. Possible causes include a\
full disk or a disk quota limit.\
\
|
-853	Current transaction has been rolled back due to error or missing\
COMMIT WORK.\
\
While Informix SQL was executing SQL statements from a command file, it\
received an error return code or reached the end of the file but found\
no COMMIT WORK statement. Since a transaction was in progress (either\
the file contained BEGIN WORK, or the database is ANSI compliant),\
Informix SQL rolled the transaction back. (It cannot leave the\
transaction open, and it cannot assume success even when no error was\
returned.)\
\
|
-854	Back end not found. Or back end is busy.\
\
In DOS, the application cannot establish a connection to the local\
IBM Informix SE engine or to the IBM Informix NET PC communications module.\
\
The SE engine (for accessing a local database) or the IBM Informix NET PC\
communications module (for accessing a remote database) must be loaded\
before trying to connect to it by means of, for example, a DATABASE\
statement. To load the SE engine, run PSTARTSQ. To load the\
IBM Informix NET PC communications module, run REMSQL.\
\
If the SE engine or the IBM Informix NET PC communications module has\
previously been loaded, and you get this error message, either another\
application currently has a connection to the SE engine, or the\
IBM Informix NET PC communications module (they can have only one\
connection at a time), or the current application encountered an\
internal error and lost the connection.\
\
If another application has a connection to the SE engine or to the\
IBM Informix NET PC communications module, you must first release that\
connection before you can connect the current application. If the other\
application is a 4GL or an ESQL/C program, that application releases\
its connection by executing a CLOSE DATABASE statement, calling the\
SQLEXIT( ) function, or exiting.\
\
In extreme situations where an internal error has occurred, you must\
exit the application and stop the SE engine or the IBM Informix NET PC\
communications module from the DOS command line. To stop the SE engine,\
run PSTARTSQ with the -T option. After you stop the SE engine, run\
PSTARTSQ with no options to reload it. To stop the IBM Informix NET PC\
communications module, run SETNET with the -T option. After you stop\
the IBM Informix NET PC communications module, run REMSQL to reload it.\
\
This error message also might appear when a client Windows application\
uses the wrong .DLL file to connect to a database server across a\
network. Client Windows applications that work with IBM Informix NET PC\
Version 4.1 (such as Version 4.1 ESQL/C) can also work with\
IBM Informix NET for Windows Version 5.01. Check to see whether\
IBM Informix NET PC Version 4.1 and IBM Informix NET for Windows Version 5.01\
reside on the same client computer concurrently. If so, check that\
Version 5.01 of the LDLLSQLW.DLL file appears in your PATH environment\
variable setting before Version 4.1 of the LDLLSQLW.DLL file. In\
addition, Version 4.1 of the LDLLSQLW.DLL file must not reside in the\
current directory, the Windows directory, the Windows SYSTEM\
directory, or the directory that contains the executable file of the\
application that you are running.\
\
|
-855	Cannot drop rowids on a non-fragmented table.\
\
You tried to use the ALTER TABLE...DROP syntax to drop the rowid column\
on a table that is not fragmented. A non-fragmented table has a rowid\
column, but you cannot drop it.\
\
|
-856	Rowids already exist on table.\
\
A rowid column already exists for the specified table. You cannot\
create a rowid for a table more than once. Change your SQL statement.\
\
|
-857	Rowids do not exist on table.\
\
You cannot drop a nonexistent rowid. You specified a rowid that does\
not exist in the specified table. Avoid using rowids in your SQL\
statement. Instead, use a primary key to delete data.\
\
|
-858	Cannot specify the same partition/space name twice in a fragmentation specification.\
\
You specified the same dbspace or same partition name more than once in \
a fragmentation specification. Change the fragmentation specification to \
use different dbspaces/partition for each fragment.\
\
|
-859	"Distributions Only" is not meaningful in an update statistics LOW\
request.\
\
You cannot specify the DISTRIBUTIONS ONLY option in the LOW mode of the\
UPDATE STATISTICS statement.\
\
|
-860	A fragmented object must have more than one fragment.\
\
You fragmented an object into one fragment. To put the object in a\
single dbspace, use the IN clause instead of the FRAGMENT BY clause.\
\
|
-861	Cannot create new PDQ thread.\
\
See the accompanying ISAM error for more information.\
\
|
-862	Alter fragment attach must have at least one consumed table specified.\
\
You have not specified a table to be consumed. See the syntax and usage\
for ALTER FRAGMENT... ATTACH in the IBM Informix Guide to SQL: Syntax.\
\
|
-863	Cannot detach a table with rowids.\
\
You must first drop rowids before you use ALTER FRAGMENT... DETACH. See\
the syntax and usage in the IBM Informix Guide to SQL: Syntax.\
\
|
-864	Cannot attach a table with rowids.\
\
You must first drop the rowids on the surviving table before you attach\
the table.\
\
|
-865	Cannot add or drop rowids in combination with other\
alter table options.\
\
You must use separate statements to add or drop rowids with an ALTER\
TABLE... ADD or ALTER TABLE... DROP statement.\
\
|
-866	Cannot attach tables that contain serial fields.\
\
Before you use an ALTER FRAGMENT... ATTACH statement, you must drop any\
serial fields or modify the column type.\
\
|
-867	Cannot generate new rowid.\
\
See the accompanying ISAM error for more information. A table cannot\
hold more than 2 gigabytes of records if it has serial or rowid\
columns.\
\
|
-868	Cannot check constraints on the attaching table.\
\
You cannot attach a table if a check, referential, primary-key, or not null\
constraint exists on the surviving table.\
\
Drop any check, referential, primary-key, or not null constraint. Then\
attach the table and if you still want to use the constraint, re-create it.\
\
|
-869	Subqueries not allowed in fragmentation expressions.\
\
A fragmentation expression can reference only columns from the current\
table and data values from a single row. The restrictions disallow\
subqueries.\
\
|
-870	Cannot specify duplicate remainder fragments.\
\
You specified duplicate remainder fragments. Remove one of the\
remainder fragments from your SQL statement.\
\
|
-871	Remainder fragment must be specified last.\
\
If you specify a REMAINDER, it must be the last fragment expression.\
Rewrite your syntax so that you specify the remainder fragment last.\
\
|
-872	Invalid fragment strategy or expression for the unique index.\
\
The round-robin method cannot fragment unique indexes. If the\
expression method fragments the indexes, all the columns that are used\
in the fragmentation expressions must also be part of the index key.\
\
|
-873	Invalid fragment expression column.\
\
You cannot use columns from different tables in a fragment expression.\
\
|
-874	Floating point exception error has occurred.\
\
This internal error affects the cost calculations that the query\
optimizer makes. If the error recurs, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-875	Incompatible Access Mode and Isolation Level.\
\
If you set the access mode to READ-WRITE, you cannot set the isolation\
level to READ-UNCOMMITTED.\
\
|
-876	Cannot issue SET TRANSACTION once a transaction has started.\
\
When a transaction is active, do not issue a SET TRANSACTION statement.\
A transaction becomes active when a DDL or a DML statement is issued.\
The only statements that you can place between the BEGIN WORK and the\
SET TRANSACTION statements are SET statements such as SET EXPLAIN, SET\
CONSTRAINT, SET DATASKIP, and so on.\
\
|
-877	Isolation Level previously set by "Set Transaction".\
\
Your program attempted to reset the isolation level that a preceding\
SET TRANSACTION statement established. Do not use a SET ISOLATION\
statement after a SET TRANSACTION statement.\
\
|
-878	Invalid operation for a READ-ONLY transaction.\
\
You specified a READ-ONLY transaction in a SET TRANSACTION statement\
and then attempted to alter the database. In other words, READ-ONLY\
ensures that you can read data, but you cannot alter data. If you want\
to alter the data, specify READ WRITE in the SET TRANSACTION statement.\
If you only want to read the data, correct your program so that it does\
not attempt to alter the data.\
\
|
-879	Trim character must be null or have a length of 1.\
\
The TRIM function evaluated to NULL. However, the TRIM character value\
expression must be null or contain a single character. Your program is\
incorrectly written. Every time the TRIM function evaluates to NULL,\
the value your program inserts into the TRIM character value expression\
is not null or contains more than one character. Correct, recompile,\
and rerun your program.\
\
|
-880	Trim character and trim source must be of string data type.\
\
You used a TRIM function where the TRIM character value expression and\
the source character value expression were conflicting data types. The\
character and source value expressions must be the string data type.\
Check the syntax of the TRIM function, and check that the character and\
source values contain string data type values.\
\
|
-881	Resulting string length from TRIM exceeds the limit.\
\
The TRIM function returned a string whose length did not span a range\
from 1 to 255 characters for VARCHAR or 1 to 32739 for LVARCHAR. The TRIM\
function returns a VARCHAR or LVARCHAR string depending upon its operand\
type. A VARCHAR string must have a length that ranges from 1 character \
to 255 characters. A LAVARCHAR string must have a length that ranges \
from 1 character to 32739 characters. Check that the TRIM function returns\
strings whose length is within the range of its returned type.\
\
|
-882	Cannot create rowids on a non-fragmented table.\
\
You tried to use the ALTER TABLE... ADD syntax to add a rowid column to\
a table that is not fragmented. This usage is not valid. If a rowid\
column already exists, rowids already exist on non-fragmented tables.\
\
|
-883	Cannot evaluate the fragmentation expression.\
\
A fragmentation expression in your program is invalid. Check the\
expression, and correct it. Check the logic of that expression. Also,\
some components of that expression might be NULL or might not represent\
existing or defined elements such as columns, hash values, ranges, index\
key values, and so on.\
\
|
-884	Cannot alter an index on a temporary table.\
\
Your program attempted to alter an index on a temporary table. Correct\
your program to avoid altering indexes on temporary tables.\
\
|
-885	Invalid or NULL utc time given to dbinfo(utc_to_datetime).\
\
You attempted to pass an invalid or NULL value to the dbinfo()\
function. Make sure you pass a valid or non-null value to the dbinfo()\
function.\
\
|
-886	Cannot drop table or view because of existing dependencies.\
\
When you issue a DROP TABLE or DROP VIEW statement, you cannot drop the\
table or view if you specify the RESTRICT option and a view or\
foreign-key constraint exists that depends on that table or view.\
\
You also cannot drop a table if you specify the RESTRICT option and a\
violations and diagnostics table exists for that table.\
\
|
-887	Cannot revoke because of dependent privileges, views, or constraints.\
\
You cannot use the RESTRICT option to REVOKE a privilege if that action\
will cause abandoned privileges, abandoned views, or abandoned table\
constraints. Refer to the IBM Informix Guide to SQL: Tutorial for more\
information.\
\
|
-888	Cannot attach a table with primary-key constraints.\
\
You cannot attach a table if a primary-key or unique constraint exists on\
the surviving table or consumed table.\
\
Drop the primary-key constraint and then attach the table. If you still\
want to use the primary-key constraint, re-create it.\
\
|
-889	Internal dataskip condition, should reposition to next row and continue.\
\
If this internal error recurs, note all circumstance, and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-891	Temporary table objects can only be enabled.\
\
You cannot change the object mode of a temporary table object to the\
disabled or filtering object mode.\
\
|
-892	Cannot disable object object-name due to other active objects using it.\
\
Other objects are using this object. If the object being disabled is an\
index, then a unique constraint, primary constraint, or referential\
constraint might be using that object. If the object is a unique or a\
primary-key constraint, then a referential constraint might be using\
that object.\
\
|
-893	Cannot activate/create object object-name because of its dependencies.\
\
The user has issued a SET statement to set a database object to the\
enabled or filtering object mode, or the user has issued a CREATE\
INDEX, CREATE TRIGGER, or CREATE TABLE statement to create a database\
object in the enabled or filtering object mode. However, this object\
needs other disabled objects. For example, before enabling a\
referential constraint on a table, the user must first enable the\
indexes that the constraint needs.\
\
|
-894	Cannot find object object-name.\
\
The object name that the user specified explicitly in the SET statement\
is not found in the database.\
\
|
-896	Violations table is not started for the target table.\
\
This error occurs in either of the following cases:\
\
   1. A STOP VIOLATIONS TABLE was executed before the START VIOLATIONS\
      TABLE statement or after the START VIOLATIONS TABLE statement was\
      rolled back.\
\
   2. A violations table has not been started for the target table\
      and an INSERT, DELETE, or UPDATE statement fails to satisfy any\
      filtering-mode object on the target table.\
\
A violations table must exist before execution of the STOP VIOLATIONS\
statement.\
\
To prevent this error, you can start a violations table for the\
target table.\
\
|
-895	Cannot create violations/diagnostics table.\
\
The user has issued a START VIOLATIONS TABLE statement for a target\
table. The database server is not able to create the violations and\
diagnostics tables for this target table. Any one of the following\
situations might be the reason for the failure:\
\
    *   The target table already has a violations and diagnostics table.\
\
    *   The names that are specified for the violations and diagnostics\
	table in the START VIOLATIONS TABLE statement are not valid.\
	For example, if you omitted the USING clause from the statement\
	and the number of characters in the target table name plus four\
	characters is longer than the maximum identifier length, the\
	generated names of the violations and diagnostics tables would\
	be longer than the maximum identifier length. If the names of\
	the violations and diagnostics tables are invalid for this\
	reason, the user can give explicit names to the violations and\
	diagnostics tables in the USING clause of the START VIOLATIONS\
	TABLE statement to rectify the problem.\
\
    *   The names that were specified for the violations and\
	diagnostics tables in the START VIOLATIONS TABLE statement\
	match the names of existing tables in the database.\
\
    *   The target table contains columns with the names\
	informix_tupleid or informix_optype. Because these two column\
	names would duplicate the informix_tupleid or informix_optype\
	columns in the violations table, the database server cannot\
	create the violations table.\
\
    *   The target table is a temporary table.\
\
    *   The target table is serving as a violations or diagnostics\
	table for some other table.\
\
    *   The target table is a system catalog table.\
\
|
-897	Cannot modify/drop a violations/diagnostics table.\
\
The user has tried to alter or drop a table that is serving as a\
violations table or a diagnostics table for another table.\
\
|
-898	Cannot alter a table which has associated violations/diagnostics tables.\
\
The user has tried to add, drop, or modify a column in a table that has\
a violations and diagnostics table associated with it.\
\
|
-899	Too many violations.\
\
The number of records in the diagnostics table either exceeds or will\
exceed the limit that is specified. Limits are specified in the \
MAX VIOLATIONS clause of the START VIOLATIONS TABLE statement for \
Extended Parallel Server or the MAX ROWS clause for other \
IBM Informix database servers. \
\
When a single statement on the target table (such as an INSERT or \
SET statement) causes more records to be inserted into the \
diagnostics table than the limit that is specified by the MAX\
ROWS clause, this error is returned to the user who issued the\
statement on the target table.\
\
|
-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 IBM Informix STAR or\
IBM Informix NET software is correctly installed.\
\
|
-904	Authorization file not on licensed Informix SQL server.\
\
This message indicates that the installation of the IBM Informix networking\
software was not completed correctly. Review the installation steps on\
the workstation and on the network server to make sure that it was\
completed without error.\
\
|
-905	Cannot locate sqlexec service /tcp service in /etc/services.\
\
The IBM Informix STAR or IBM Informix NET software has not been properly\
installed on this system. In particular, entries in the\
system-configuration file /etc/services (UNIX) or etcservices (DOS)\
have not been made. Contact the person who installs your IBM Informix\
software.\
\
|
-906	Cannot locate remote system (check DBPATH).\
\
IBM 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 IBM Informix STAR or IBM Informix NET installed\
and active. This message appears prior to Version 6.0.\
\
|
-907	Cannot create socket on current database server.\
\
IBM Informix STAR or IBM 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 IBM 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 IBM 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 IBM Informix Dynamic Server database from \
        an IBM 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 IBM Informix SE and the other is\
another IBM 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.\
\
-911	System error - Cannot read from pipe.\
\
This internal error reflects a failure in communication between your\
application and the IBM Informix STAR or IBM Informix NET software. Look for\
operating-system error messages that might give more information.\
Restart the application. If the problem recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-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 IBM Informix STAR or IBM Informix NET software. Look for\
operating-system error messages that might give more information.\
Restart the application. If the problem recurs, note all\
circumstances and contact Technical Support at tsmaius.ibm.com.\
\
|
-915	Cannot create an IBM Informix SE database from an IBM 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 IBM Informix SE and the other is\
another IBM 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.\
\
|
-916	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 IBM Informix STAR or IBM 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,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-919	System error. Wrong number of arguments to database server process.\
\
This internal error reflects a failure in communication between your\
application, IBM Informix STAR or IBM 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 IBM Informix NET/IBM Informix STAR\
Installation and Configuration Guide for a compatibility chart).\
Recompile and relink your application program if necessary. If the\
problem recurs, note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
|
-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,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
For a Windows 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\
IBM Informix NET/IBM 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	IBM is licensed to access the current database server only.\
\
This version of the IBM Informix product is not licensed for network use.\
Locate the version of the software that is licensed for use with\
IBM Informix STAR or IBM 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	IBM is not licensed to access the specified database server.\
\
If you have installed an IBM Informix 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 IBM Informix product to access both\
local and remote databases, contact your IBM representative\
for details on purchasing the appropriate IBM Informix product.\
\
|
-925	The protocol type should be tcp.\
\
The protocol type that is shown in the $INFORMIXDIR/etc/sqlhosts file\
(or in INFORMIXetcsqlhosts on IBM 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 IBM representative about upgrading this database server\
to full IBM Informix STAR status. If you believe that you have IBM Informix STAR\
installed, check the contents of the INFORMIXDIR environment variable. If\
you are using IBM Informix OnLine for NetWare, you cannot access tables or\
databases on remote systems unless you have IBM 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 IBM 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 IBM Informix NET PC systems.\
\
|
-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.\
\
|
-930	Cannot connect to remote host sitename.\
\
IBM Informix STAR or IBM 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 etcservices (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 IBM Informix OnLine\
for NetWare, check the etcservices 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 (IBM Informix STAR, IBM Informix NET,\
IBM 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 IBM 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, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-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 IBM Informix NET/IBM Informix STAR Installation and\
Configuration Guide for the correct setting. If you are using\
IBM 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\
IBM Informix OnLine for NetWare. The client application, IBM Informix NET or\
IBM 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 IBM 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\
IBM 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.\
\
|
-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", "limit" or "skip" in this context.\
\
This statement uses FIRST N , LIMIT N or SKIP M 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).\
\
You entered a value for a version that this command does not support. \
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'.\
\
|
\
|
\
-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	User username is not known on the database server.\
\
This statement refers to a database on another computer system, but the\
other database server does not accept your account name. You must have \
a valid trusted login identity on any database server you access remotely.\
See your database administrator about putting your login ID in \
'sysuser:sysauth' on the remote server. This message appears on PAM enabled \
servers.\
\
|
-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.\
\
|
-951	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.\
\
|
-952	User (<user-id>)'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 IBM Informix software. This message appears with Version 6.0\
and later.\
\
|
-953	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 IBM 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 IBM Informix NET/IBM Informix STAR Installation and\
Configuration Guide. This message appears prior to Version 6.0.\
\
|
-954	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 IBM Informix STAR or IBM 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,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com. This\
message appears prior to Version 6.0.\
\
|
-955	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, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com. 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.\
\
|
-956	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 IBM 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.\
\
Note the specifics of your system when this internal error\
occurred, and contact Technical Support at tsmail@us.ibm.com.\
\
|
-958	Temp table <table-name> 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 = <table-name>\
\
If the name exists, review this name by querying the systables table\
in <dbsname>:\
\
    SELECT tabname FROM <dbsname>:systables\
           WHERE tabname = <table-name>\
\
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. Contact \
Technical Support at tsmail@us.ibm.com 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.\
\
|
-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. 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/partition-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 Technical Support at tsmail@us.ibm.com and provide them with your\
Assertion Failure file.\
\
|
-999	Not implemented yet.\
\
This error means the functionality being exercised is not currently\
implemented. Check the documentation and release notes that\
describe this current restriction in this particular release for this\
product. If this condition is not described in the regular documentation\
or the release notes and recurs, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-1003	Invalid ACCEPTKEY set in the environment.\
\
The key that the ACCEPTKEY environment variable specifies is not\
decipherable; either it does not start with F, or it has an invalid\
number. Specify a different key.\
\
|
-1004	The selected ACCEPTKEY has been preassigned for ISQL.\
\
The key that the ACCEPTKEY environment variable specifies is one that\
IBM Informix SQL always uses. Set a different value in the environment\
variable.\
\
|
-1005	Your specified termcap file cannot be read.\
\
The TERMCAP environment variable specifies a file that cannot be\
opened. Either it does not exist, or your account does not have\
operating-system permissions to read it. Check the environment variable\
and the file that it names.\
\
|
-1006	Error number.\
\
The error code that is shown was returned, but the program could not\
display the message text for that number, probably because one of the\
.iem message files is missing from the directory that the INFORMIXDIR\
environment variable specifies. Look up the number in the finderr utility.\
Also consult with the person who installed the IBM Informix software to find\
out why the message files are not available.\
\
|
-1007	Invalid value for the INFORMIXTERM environment variable.\
\
The only valid settings for the INFORMIXTERM environment variables are\
termcap and terminfo. Setting the variable to termcap (or leaving it\
undefined) directs 4GL to use the TERMCAP facility for terminal\
control. Setting it to terminfo causes 4GL to use the TERMINFO\
facility. Other settings, including variations of the words termcap and\
terminfo with capital letters in them, cause this error.\
\
|
-1008	Termcap entry too long.\
\
The contents of the TERMCAP environment variable, or of the termcap\
entry from the termcap database, are read into storage when the\
application is initializing. However, the memory buffer that is\
allocated to hold the termcap entry is 1,024 bytes, and the entry in\
use is longer than that. Use a simpler termcap.\
\
|
-1009	Bad termcap entry.\
\
The contents of the TERMCAP environment variable, or of the termcap\
entry from the termcap database, are read into storage when the\
application is initializing. While the program was doing this, it found\
improper punctuation in the termcap entry. A colon separator did not\
appear where one was expected. Review the specified termcap, and choose\
a different one or correct the one that is in use.\
\
|
-1010	Too many tc= indirections.\
\
In a termcap definition for a terminal, the entry tc= causes the use of\
a definition for default values for a different terminal. That terminal\
might also have a tc= entry, and so on. However, 4GL cannot follow more\
than four tc= commands. The termcap definition in use at this time (as\
the TERM or TERMCAP environment variable specifies) exceeds the limit.\
Write or find a termcap definition that is more self contained.\
\
|
-1101	Variable address is NULL.\
\
If this internal error recurs, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-1102	Field name not found in form.\
\
A field name listed in an INPUT, INPUT ARRAY, CONSTRUCT, SCROLL or\
DISPLAY statement does not appear in the form specification of the\
screen form that is currently displayed. Review the program logic to\
ensure that the intended window is current, the intended form is\
displayed in it, and all the field names in the statement are spelled\
correctly.\
\
A common problem is the attempted use of field tags instead of field\
names. The field tag is the name that is written in the screen picture\
and that appears at the left side of the ATTRIBUTES statement for that\
field. It is not the name of the field for input or display purposes.\
The field name is the column name with which it is associated. This\
name appears to the right of the equal sign in the ATTRIBUTES section.\
\
   ATTRIBUTES\
\
   f000 = customer.customer_num,color=red;\
\
The name of the field in the preceding example is customer_num. Use of\
the tag f000 in an INPUT statement will produce an error.\
\
|
-1103	This value is not among the valid possibilities.\
\
A list or range of acceptable values has been established for this\
column (via an INCLUDE attribute in the form-specification file). You\
must enter a value within the acceptable range.\
\
For 4GL programs, -1301 replaces this error.\
\
|
-1104	The two entries were not the same. Try again.\
\
To guard against typographical errors, this field has been designated\
VERIFY (in the form specification file). The value in this field must\
be entered twice, identically. Carefully reenter the data.\
Alternatively, you can cancel the form entry with the Interrupt key\
(usually CTRL-C, but see the operating instructions that the program\
author supplied).\
\
For 4GL programs, -1302 replaces this error.\
\
|
-1105	You cannot use this editing feature because a picture exists.\
\
This field is defined (in the form specification file) with a PICTURE\
attribute to specify its format. You cannot use certain editing keys\
(for example, CTRL-A, CTRL-D, and CTRL-X) while you are editing such a\
field. Use only printable characters and the backspace to enter the\
value.\
\
For 4GL programs, -1303 replaces this error.\
\
|
-1106	Error in field.\
\
You entered a value in this field that cannot be stored in the program\
variable that is meant to receive it. For example, possibly you entered\
a decimal number when the application provided only an integer\
variable, or you entered a character string that is longer than the\
application expected. Note all the circumstances and then discuss the\
problem with the person who wrote the application program.\
\
For 4GL programs, -1304 replaces this error.\
\
|
-1107	Field subscript out of bounds.\
\
The subscript of a screen array in an INPUT, DISPLAY, or CONSTRUCT\
statement is either less than 1 or greater than the number of fields in\
the array. Review the program source in conjunction with the form\
specification to see where the error lies.\
\
|
-1108	Record not in form.\
\
The screen record that is named in an INPUT ARRAY or DISPLAY ARRAY\
statement does not appear in the screen form that is now displayed.\
Review the program source in conjunction with the form specification to\
see if the screen record names match.\
\
|
-1109	List and record field counts differ.\
\
The number of program variables does not agree with the number of\
screen fields in a CONSTRUCT, INPUT, INPUT ARRAY, DISPLAY, or DISPLAY\
ARRAY statement. Review the statement in conjunction with the form\
specification to see where the error lies. Common problems include a\
change in the definition of a screen record that is not reflected in\
every statement that uses the record, and a change in a program record\
that is not reflected in the form design.\
\
|
-1110	Form file not found.\
\
The form file that is specified in an OPEN FORM statement was not\
found. Inspect the "form-file" parameter of the statement. It should\
not include the file suffix.frm. However, if the form is not in the\
current directory, it should include a complete path to the file.\
\
|
-1111	Field table offset out of bounds.\
\
If this internal error recurs, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-1112	A form is incompatible with the current 4GL version. Rebuild your form.\
\
The form file that is specified in an OPEN FORM statement is not\
acceptable. Possibly it was corrupted in some way, or it was compiled\
with a version of the Form Compiler that is not compatible with the\
version of the 4GL compiler that compiled this program. Use a current\
version of the Form Compiler to recompile the form specification.\
\
|
-1113	Memory allocation error.\
\
A BYTE or TEXT variable has been located in memory, and a value has\
been assigned to the variable. However, not enough data memory is\
available to hold the variable. Review the program, and locate the\
large value in a file instead.\
\
For 4GL programs, -1319 replaces this error.\
\
|
-1114	No form has been displayed.\
\
The current statement requires the use of a screen form. For example,\
DISPLAY...TO or an INPUT statement must use the fields of a form.\
However, the DISPLAY FORM statement has not been executed since the\
current window was opened. Review the program logic to ensure that it\
opens and displays a form before it tries to use a form.\
\
|
-1115	Numeric value too long for field.\
\
4GL tried to format a numeric value for display in a form field, but\
the resulting string was too long for the field. Review the program\
logic to find out what large numeric value is being assigned.\
\
For 4GL programs that were compiled at Version 5.0 and later or that\
are running under 4GL/GX, this error cannot occur.\
\
|
-1116	Default value from form field cannot be converted to\
input variable type.\
\
This statement takes input from a form field whose default value (which\
the ATTRIBUTES keyword DEFAULT specifies in the form) is not compatible\
with the program variable that receives it. Review all the program\
variables that are named in this statement, and compare them to the\
definitions of the fields in the form specification. Check that each\
variable corresponds to the intended field and has a compatible data\
type.\
\
|
-1117	Cannot convert date value to string.\
\
This message is not believed to be in use in any current product. If\
the error recurs, note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
|
-1119	NEXT FIELD name not found in form.\
\
This statement (INPUT or INPUT ARRAY) contains a NEXT FIELD clause that\
names a field that is not defined in the form. Perhaps the form has\
been changed, but the program has not. Also see the note for error\
message -1102.\
\
For 4GL programs, -1371 replaces this error.\
\
|
-1120	Message file not found.\
\
The message file that is specified in the HELP FILE clause of the most\
recent OPTIONS statement does not exist. Find that OPTIONS statement in\
the program, and review the "help-file" parameter. It must contain the\
complete filename of the prepared message file. If the file is not in\
the current directory, it must have a full pathname. Message files are\
prepared with the mkmessage utility.\
\
For 4GL programs, -1227 replaces this error.\
\
|
-1121	Message number not found in message file.\
\
A message number that is given in the HELP clause of an INPUT, PROMPT,\
or MENU statement cannot be found in the current message file. The\
most- recently executed OPTIONS HELP FILE statement establishes the\
message file. Find that statement in the program, and verify that the\
message file is the one that you intended. Then review the source of\
that message file, and ensure that it contains definitions for all the\
message numbers that are used in the program. Recompile the message\
file with the mkmessage utility, and try the program again.\
\
For 4GL programs, -1228 replaces this error.\
\
|
-1122	Incompatible message file.\
\
The message file that is named in the most-recently executed OPTIONS\
HELP FILE statement was not acceptable. Possibly it has been corrupted\
in some way. Possibly the OPTIONS statement named the message source\
file instead of the compiled message file (the output of mkmessage).\
Possibly the file was compiled with an outdated version of the\
mkmessage utility. Recompile the message file with the current version\
of the utility, and review the program source to make sure that it\
names the correct file.\
\
For 4GL programs, -1229 replaces this error.\
\
|
-1123	No help file specified.\
\
This INPUT, PROMPT, or MENU statement contains a HELP help-number\
clause; however, no message file has been established. The OPTIONS HELP\
FILE statement establishes the message file, but none has yet been\
executed. Review the program logic, and modify it to execute an\
OPTIONS statement with a HELP FILE clause before it is needed.\
\
For 4GL programs, -1343 replaces this error.\
\
|
-1124	This field requires an entered value.\
\
The cursor is in a form field that has been designated REQUIRED. You\
must enter some value before the cursor can move on to another field.\
However, to enter a null value, type any printable character and then\
backspace. Alternatively, you can cancel the form entry with the\
Interrupt key (usually CTRL-C, but see the operating instructions that\
the program author supplied).\
\
For 4GL programs, -1305 replaces this error.\
\
|
-1125	Type again for verification.\
\
The cursor is in a form field that has been designated VERIFY. You must\
enter the value twice, identically, before the cursor can move on to\
another field. This requirement helps to ensure that no typographical\
errors occur during data entry. Alternatively, you can cancel form\
entry with the Interrupt key (usually CTRL-C, but see the operating\
instructions that the program author supplied).\
\
For 4GL programs, -1306 replaces this error.\
\
|
-1126	Cannot insert another row - the input array is full.\
\
You are entering data into an array of records that is represented in\
the program by an array of program variables. That array is now full;\
no place is available to store another record. Press the ACCEPT key\
(usually ESCAPE, but see the operating instructions that the program\
author supplied) to process the records that you have entered.\
\
For 4GL programs, -1307 replaces this error.\
\
|
-1127	Cannot delete row - it has no data.\
\
You pressed the Delete Row function key (usually F2, but see the\
operating instructions that the program author supplied) in an empty\
row. Nothing was deleted.\
\
For 4GL programs, -1308 replaces this error.\
\
|
-1128	There are no more rows in the direction you are going.\
\
You are attempting to scroll an array of records farther than it can\
go, either scrolling up at the top or scrolling down at the bottom of\
the array. Further attempts will have the same result.\
\
For 4GL programs, -1309 replaces this error.\
\
|
-1129	Field in BEFORE/AFTER clause not found in form.\
\
This statement includes a BEFORE FIELD clause or an AFTER FIELD clause\
that names a field that is not defined in the form that is currently\
displayed. Review the program to ensure that the intended form was\
displayed, and review this statement against the form specification to\
ensure that existing fields are named. Also see the note on field names\
for error message -1102.\
\
|
-1130	You cannot have multiple BEFORE clauses for the same field.\
\
This statement includes at least two BEFORE FIELD clauses that name the\
same form field. Only one is supported. Find all the BEFORE FIELD\
clauses relate to one field, and combine them into a single clause.\
\
|
-1131	You cannot have multiple AFTER clauses for the same field.\
\
This statement includes at least two AFTER FIELD clauses that name the\
same form field. Only one is supported. Find all the AFTER FIELD\
clauses that relate to one field, and combine them into a single\
clause.\
\
|
-1132	The destination string of the CONSTRUCT statement is not large enough.\
\
The outcome of a CONSTRUCT statement is a character string that\
contains all the conditions that the user entered. This string is in a\
form suitable for use as the WHERE clause of a SELECT statement. In\
this CONSTRUCT statement, the result string is longer than the program\
variable that is specified to receive it. As a general rule, the length\
of the variable must allow enough room for the names of all the screen\
fields that are used in the statement, plus room for the field contents\
and for punctuation and relational operators. Review the statement,\
and revise the definition of the receiving variable accordingly.\
\
|
-1133	The NEXT OPTION name is not in the menu.\
\
This MENU statement contains a NEXT OPTION clause that names a\
menu-option that is not defined in the statement. The string that\
follows NEXT OPTION must be identical to one that follows a COMMAND\
clause in the same MENU statement. Review the statement to ensure that\
these clauses agree with each other.\
\
|
-1134	There is no termcap entry for this function key.\
\
The key that is specified in one clause of this OPTIONS statement is\
not defined in the termcap file (or the terminfo file if you are using\
it instead). Review the HELP KEY, INSERT KEY, NEXT KEY, PREVIOUS KEY,\
and DELETE KEY clauses. Compare the function keys that they specify to\
the current termcap definition.\
\
|
-1135	The row or column number in DISPLAY AT exceeds the limits of your\
terminal.\
\
Review the DISPLAY...AT statement. Make sure that the position numbers\
are in the correct order (row number first, then column) and that they\
make sense for the current terminal or window. The dimensions of the\
terminal for UNIX systems are determined when the program starts by\
reading termcap information (or terminfo information, depending on the\
value of the INFORMIXTERM environment variable). A screen location that\
is correct for one user of the program might not be correct for all. On\
DOS systems, the window size is always 24 lines by 80 characters.\
\
|
-1136	Window is too large to fit on the screen.\
\
The window dimensions that are specified in the WITH clause of this\
OPEN WINDOW statement conflict with the size of the screen. The entire\
window cannot be displayed, so the statement is not executed. If the\
WITH clause specifies dimensions, you can use smaller ones; if it\
specifies a form, the SCREEN statement in the form specification sets\
the dimensions. Alternatively, you might be able to get the window\
into the screen by changing the origin that is provided in the AT\
clause. The dimensions of the terminal for UNIX systems are determined\
when the program starts by reading termcap information (or terminfo\
information, depending on the value of the INFORMIXTERM environment\
variable). Screen dimensions that are correct for one user of the\
program might not be correct for all. On DOS systems, the window size\
is always 24 lines by 80 characters.\
\
|
-1137	Cannot open window.\
\
The cause of the problem is a lack of data memory. Change the logic of\
the program to keep fewer windows open concurrently, or use fewer\
global variables.\
\
For 4GL programs, -1319 replaces this error.\
\
|
-1138	Border does not fit on screen. Window is too large.\
\
The window that this OPEN WINDOW statement describes cannot be opened\
because its border does not fit on the screen. Despite the wording of\
the message, the window is not necessarily too large for the screen.\
However, one or more of its borders (top, bottom, left, or right)\
cannot be drawn. The position of the window is set in the OPEN WINDOWS\
statement; check that it starts no higher than row 2 and no farther\
left than column 2 (or else remove the BORDER attribute). The OPEN\
WINDOW statement or the form that it names sets the size of the\
window.\
\
The dimensions of the terminal for UNIX systems are determined when the\
program starts by reading termcap information (or terminfo information,\
depending on the value of the INFORMIXTERM environment variable). If\
the termcap entry includes sg#1 (terminfo: xmc#1), 4GL reserves an\
additional column to the left and right of a bordered window. On DOS\
systems, the window size is always 24 lines by 80 characters.\
\
|
-1139	Form line cannot be set using LAST keyword.\
\
This OPTIONS statement includes a FORM LINE clause that uses LAST. You\
can specify an absolute form line or one relative to FIRST, but you\
cannot specify it relative to LAST.\
\
|
-1140	NEXT OPTION is a hidden option.\
\
The option that is named in this NEXT OPTION statement has previously\
been hidden with the HIDE OPTION statement. Because it is not visible\
to the user, it cannot be highlighted as the next choice.\
\
|
-1141	Cannot close window with active INPUT, DISPLAY ARRAY, or MENU statement.\
\
This CLOSE WINDOW statement cannot be executed because an input\
operation is still active in that window. The CLOSE WINDOW statement\
must have been contained in, or called from within, the input statement\
itself. Review the program logic, and revise it so that the statement\
completes before the window is closed.\
\
|
-1142	Window is too small to display this form.\
\
The window dimensions of the current window are too small to contain\
the form that is to be displayed. Review the window dimensions, and\
compare them to all forms that will be displayed in that window. The\
dimensions of the form are established in the form-specification file\
with the SCREEN statement. The dimensions of the window are set during\
the OPEN WINDOW statement, either directly or by opening the window\
WITH a particular form.\
\
|
-1143	Window is already open.\
\
This OPEN WINDOW statement names a window that is already open. Review\
the program logic, and see whether it should contain a CLOSE WINDOW\
statement, or whether it should simply use a CURRENT WINDOW statement\
to bring the open window to the top.\
\
|
-1144	Cannot open window. Window origin is not on the screen.\
\
The row and column position in the AT clause of this OPEN WINDOW\
statement points off the physical screen. The statement is not\
executed. Review the program, and check that the numbers are in the\
correct order (first row, then column). The dimensions of the terminal\
are determined when the program starts by reading termcap information\
(or terminfo information, depending on the value of the INFORMIXTERM\
environment variable), so a window origin that is correct for some\
users might not be correct for all.\
\
|
-1145	Cannot open ERROR window.\
\
4GL attempted to open a one-line, 80-column window in which to display\
an error message but was not able to do so. Possible causes include a\
shortage of data memory and internal errors.\
\
For 4GL programs, -1319 replaces this error.\
\
|
-1146	PROMPT message is too long to fit in the window.\
\
Although 4GL truncates the output of MESSAGE and COMMENT to fit the\
window dimensions, it does not do so for PROMPT and the user's\
response. Reduce the length of the prompt string, or make the window\
larger. You could display most of the prompting text with DISPLAY and\
then prompt with a single space or colon.\
\
|
-1147	You cannot CLOSE, CLEAR or make CURRENT an unopened window.\
\
This CLOSE WINDOW, CLEAR WINDOW, or CURRENT WINDOW statement names a\
window that has not been opened or has been closed. Review the program\
logic to ensure that it does not refer to an unopened window except to\
open it.\
\
|
-1148	Size of a window may not be negative.\
\
The AT clause of this OPEN WINDOW statement uses a negative number. The\
row and column sizes must be positive integers. Revise the statement.\
\
|
-1149	An unknown code has been detected in the form.\
\
The screen form that is currently displayed is unacceptable in some\
way. Possibly it has been corrupted; possibly it was compiled by an\
obsolete version of form4gl. Recompile the form. If the problem recurs,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-1150	Window is too small to display this menu.\
\
Review the OPEN WINDOW statement for the current window in conjunction\
with this MENU statement. The window must be at least two rows tall,\
and it must be wide enough to display the menu title, the longest\
option name, two sets of three-dot ellipses, and six spaces. Revise the\
program to make the window larger or to give the menu a shorter name\
and shorter options.\
\
|
-1151	IBM Informix 4GL Run Time Facility.\
\
This message is not believed to be in use in any current product. If\
the error recurs, note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
|
-1152	Enter value in range.\
\
This error message is a version of message -1103/-1301, which is used\
by IBM Informix 4GL/RF with handheld terminals that have very small\
screens. See message -1103.\
\
|
-1153	Bad verify -- reenter.\
\
This message is a version of message -1104/-1302, which is used by\
IBM Informix 4GL/RF with handheld terminals that have very small screens.\
See message -1104.\
\
|
-1154	Cannot use edit key.\
\
This message is a version of message -1105/-1303, which is used by\
IBM Informix 4GL/RF with handheld terminals that have very small screens.\
See message -1105.\
\
|
-1155	Enter value in field.\
\
This message is a version of message -1124/-1305, which is used by\
IBM Informix 4GL/RF with handheld terminals that have very small screens.\
See message -1124.\
\
|
-1156	Enter value again.\
\
This message is a version of message -1125/-1306, which is used by\
IBM Informix 4GL/RF with handheld terminals that have very small screens.\
See message -1125.\
\
|
-1157	No more rows.\
\
This message is a version of message -1127/-1309, which is used by\
IBM Informix 4GL/RF with handheld terminals that have very small screens.\
See message -1127.\
\
|
-1158	FMP has run out of memory.\
\
FMP refers to IBM Informix 4GL/RF. See the installation documentation for\
your system.\
\
|
-1159	FMP has exceeded its number of concurrent INPUT statements.\
\
FMP refers to IBM Informix 4GL/RF. See the installation documentation for\
your system.\
\
|
-1160	FMP has exceeded its number of concurrent DISPLAY ARRAY statements.\
\
FMP refers to IBM Informix 4GL/RF. See the installation documentation for\
your system.\
\
|
-1161	FMP currently is not in the midst of an INPUT statement.\
\
FMP refers to IBM Informix 4GL/RF. See the installation documentation for\
your system.\
\
|
-1162	FMP has exceeded the number of concurrently open forms.\
\
FMP refers to IBM Informix 4GL/RF. See the installation documentation for\
your system.\
\
|
-1163	The FMP version number is incompatible with the 4GL program. Relink\
the 4GL program and run again.\
\
FMP refers to IBM Informix 4GL/RF. See the installation documentation for\
your system.\
\
|
-1164	A NEXT FIELD specified in the instructions section of the form is\
not used within the current input statement.\
\
The current form field has a NEXT FIELD specification (in the\
INSTRUCTIONS section of the form). However, the specified next field is\
not named in the current INPUT statement, so the cursor cannot move to\
that field.\
\
|
-1165	This statement is not allowed for the FMP.\
\
FMP refers to IBM Informix 4GL/RF. See the installation documentation for\
your system.\
\
|
-1166	An illegal code has been received from the FMP.\
\
FMP refers to IBM Informix 4GL/RF. See the installation documentation for\
your system.\
\
|
-1167	An unknown form name has been received by the FMP.\
\
FMP refers to IBM Informix 4GL/RF. See the installation documentation for\
your system.\
\
|
-1168	Command does not appear in the menu.\
\
The SHOW OPTION, HIDE OPTION, or NEXT OPTION statement cannot refer to\
an option (command) that does not exist. Check the spelling of the name\
of the option.\
\
|
-1170	The type of your terminal is unknown to the system.\
\
Check the setting of your TERM environment variable and the setting of\
your TERMCAP or TERMINFO environment variable. Check with your system\
administrator if you need help with this action.\
\
|
-1171	A disallowed data type has been encountered by the FMP.\
\
FMP refers to IBM Informix 4GL/RF. See the installation documentation for\
your system.\
\
|
-1176	A COMMAND KEY value occurs elsewhere in the current menu.\
\
In the indicated MENU statement, you defined a key value in more than\
one COMMAND KEY keylist or both in a COMMAND KEY keylist and as the\
default activation key for one or more nonhidden COMMAND clauses (for\
example, that key value is also the first character of one or more\
menu-option strings). This condition is illegal because MENU has no way\
to resolve what to do if the given keystroke occurs.\
\
A given key might appear as the default activation key for more than\
one COMMAND (without the KEY clause) because the user will be prompted\
for subsequent keystrokes until a unique string is obtained. This\
action is not possible with COMMAND KEY because only one keystroke is\
compared.\
\
If a COMMAND is currently hidden (by using the HIDE OPTION keywords),\
its default activation key is ignored and does not trigger this\
particular error condition.\
\
-1200	Number is too large for a DECIMAL data type.\
\
The float DECIMAL data type accommodates numbers from 10 to the -130th\
power through 10 to the 124th power in absolute value. The precision\
(number of significant digits) varies from 1 to 32; however, the source\
of this error is not the length of the number but its magnitude.\
\
|
-1201	Number is too small for a DECIMAL data type.\
\
The DECIMAL data type accommodates numbers from 10 to the -130th power\
through 10 to the 124th power in absolute value. The precision (number\
of significant digits) varies from 1 to 32; however, the source of this\
error is not the length of the number but its magnitude.\
\
|
-1202	An attempt was made to divide by zero.\
\
Zero cannot be a divisor. In some cases, this error arises because the\
divisor is a character value that does not convert properly to\
numeric.\
\
|
-1203	Values used in a MATCH must both be type CHARACTER.\
\
The MATCHES relationship applies only to character data; both of its\
operands must be CHAR or VARCHAR columns or variables, or literal\
character strings. If you need to apply a regular-expression pattern\
match to a numeric value, you can do so in 4GL. Assign the numeric\
value to a CHAR variable, and test that variable.\
\
|
-1204	Invalid year in date.\
\
The year in a DATE value or literal is invalid. For example, the\
number 0000 is not acceptable as the year.\
\
|
-1205	Invalid month in date.\
\
The month in a DATE value or literal must be a one- or two-digit number\
from 1 to 12.\
\
|
-1206	Invalid day in date.\
\
The day number in a DATE value or literal must a one- or two-digit number\
from 1 to 28 (or 29 in a leap year), 30, or 31, depending on the month that\
accompanies it.\
\
|
-1207	Converted value does not fit into the allotted space.\
\
A noncharacter value, after conversion to a character string, is too\
long to fit in the buffer that was provided.\
\
If the conversion was automatic, change the program to provide a larger\
host variable to receive the string.\
\
If this action was an explicit call to conversion function, pass a\
larger buffer.\
\
|
-1208	There is no conversion from non-character values to character values.\
\
If you are using a database server prior to Version 4.0, no automatic\
conversion from numeric values to character values occurs in SQL\
statements such as INSERT and UPDATE. Check that the specified value\
for each column agrees with the data type of that column. If you use a\
Version 4.0 or later database server, this message should not appear.\
\
|
-1209	Without any delimiters, this date must contain exactly 6 or 8 digits.\
\
When a literal date value is entered in numeric form, not enclosed in\
quotes to make it a character string, it must be entered as a number of\
precisely 6 digits (representing mmddyy) or 8 digits (representing\
mmddyyyy). Because no punctuation is present, a date with any other\
number of digits is ambiguous; it cannot be divided into month, day,\
and year with certainty.\
\
|
-1210	Date could not be converted to month/day/year format.\
\
The DATE type is compatible with the INTEGER type, but not all integer\
values are valid dates. This error arises in attempts to convert to\
character from a date whose numeric value is less than -693,594 or\
greater than 2,958,464. Numbers that are outside this range have no\
representation as dates.\
\
You may also see this message if you try to use the VARIANCE() or\
STDEV() functions on an inappropriate data type, such as DATE.\
\
|
-1211	Out of memory.\
\
4GL cannot allocate memory for a small, temporary work area that is\
used for processing an expression. To avoid this error, simplify the\
program in almost any way to release enough space\
\
|
-1212	Date conversion format must contain a month, day, and year component.\
\
When a date value is converted between internal binary format and\
display or entry format, a pattern directs the conversion. When\
conversion is done automatically, the pattern comes from the\
environment variable DBDATE. When it is done with an explicit call to\
the rfmtdate(), rdefmtdate(), or USING functions, a pattern string is\
passed as a parameter. In any case, the pattern string (the format of\
the message) must include letters that show the location of the three\
parts of the date: 2 or 3 letters d; 2 or 3 letters m; and either 2 or 4\
letters y.\
\
|
-1213	A character to numeric conversion process failed.\
\
A character value is being converted to numeric form for storage in a\
numeric column or variable. However, the character string cannot be\
interpreted as a number. It contains some characters other than white\
space, digits, a sign, a decimal, or the letter e; or the parts are in\
the wrong order, so the number cannot be deciphered.\
\
If you are using NLS, the decimal character or thousands separator\
might be wrong for your locale.\
\
|
-1214	Value too large to fit in a SMALLINT.\
\
The SMALLINT data type can accept numbers with absolute values from 0\
through 32,767 (plus or minus (2 to the 15th power) - 1). To store\
numbers that are outside this range, redefine the column or variable to\
use INTEGER or DECIMAL type. (The value -32,768 is a 16-bit value but\
is not acceptable; it indicates a null value in 4GL.)\
\
|
-1215	Value too large to fit in an INTEGER.\
\
The INTEGER or SERIAL data type can accept numbers with absolute values\
from 0 through 2,147,483,647 (plus or minus (2 to the 31st power) - 1).\
\
To store numbers that are outside this range, redefine the column or\
variable to use the INT8 or SERIAL8 data type or the DECIMAL data type.\
For more information on valid ranges of data types, see the IBM Informix Guide\
to SQL: Reference.\
\
|
-1216	Illegal exponent.\
\
The exponent of a numeric literal cannot exceed 32,767. In fact, none\
of the available data types can accommodate an exponent that large.\
However, the exponent itself triggers this message before checking the\
destination of the number. Check the statement for missing or misplaced\
punctuation that might have caused two numbers to run together.\
\
|
-1217	The format string is too large.\
\
The pattern string that is used to format a date (either the DBDATE\
environment variable or the pattern that is passed to rfmtdate() or the\
USING function) is too long. The limit is 80 bytes.\
\
|
-1218	String to date conversion error.\
\
The input to the rstrdate() function does not properly represent a\
date: either it has nondigits where digits are expected, an unexpected\
delimiter, or numbers that are too large or are inconsistent.\
\
|
-1219	Numeric value from database is too large for COBOL data item.\
\
This message is not believed to be in use in any current product. If\
the error recurs, note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
|
-1220	Numeric value from database is too small for COBOL data item.\
\
This message is not believed to be in use in any current product. If\
the error recurs, note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
|
-1221	Cannot convert null data types.\
\
This message is not believed to be in use in any current product. If\
the error recurs, note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
|
-1222	Value will not fit in a SMALLFLOAT.\
\
The SMALLFLOAT data type can accept numbers within a certain range of\
exponents. The maximum and minimum exponent values are different\
depending on the host operating system (the range is the same as that\
supported by the C compiler for float values in this system). In the\
current statement, a constant number is being converted for storage in\
a FLOAT variable or column, and the exponent is too large or too\
small.\
\
|
-1223	Value will not fit in a FLOAT.\
\
The FLOAT data type can accept numbers within a certain range of\
exponents. The maximum and minimum exponent values are different\
depending on the host operating system (the range is the same as that\
supported by the C compiler for double values in this host system). In\
the current statement, a constant number is being converted for storage\
in a FLOAT variable or column, and the exponent is too large or too\
small.\
\
|
-1224	Invalid decimal number.\
\
This message is not believed to be in use in any current product. If\
the error recurs, note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
|
-1225	Column does not admit a NULL value.\
\
This statement attempted to store a null value in a column that has\
been defined as not allowing nulls. Review the definition of the table,\
and revise the statement so that it supplies values for all required\
columns.\
\
|
-1226	Decimal or money value exceeds maximum precision.\
\
The client is attempting to convert a number into a DECIMAL or MONEY variable.\
However, the number has more digits to the left of the decimal\
point than the declaration of the variable allows. Revise the program to\
assign the converted number to a variable with an appropriate precision. \
\
|
-1227	Message file not found.\
\
4GL cannot locate a file of message texts. The file should have a\
suffix of .iem and be in the product directory, $INFORMIXDIR/msg.\
Reinstall such files from the distribution materials. If you have\
started to modify the user-message file, 4glusr.msg, check that its\
compiled form has been replaced in the correct directory.\
\
|
-1228	Message number not found in message file.\
\
4GL cannot find a message number that should appear in a message file\
that was installed with the product. Reinstall all files of type .iem\
from the distribution materials. If you have modified the contents of\
the file, 4glusr.msg, review all deletions that you might have made,\
and recompile that file.\
\
|
-1229	Incompatible message file.\
\
4GL is trying to look up a message text in a message file, but the file\
contents do not match the current version of the product. Possibly the\
file is corrupt; possibly a message file from a prior version is present.\
The file has a suffix of .iem and exists in the etc subdirectory of the\
path that the INFORMIXDIR environment variable identifies. Reinstall such\
files from the distribution materials. If you have started to modify the\
user-message file, 4glusr.msg, make sure that you are recompiling it with\
a current version of the mkmessage utility.\
\
|
-1230	Bad message file name formulation.\
\
An invalid filename has been supplied for the message file that is used\
for displaying error messages such as the ones in this book, so the\
file cannot be opened. Check the value of the DBLANG environment\
variable, if one is specified.\
\
|
-1231	Cannot seek within message file.\
\
The application is trying to look up a message text in a message file\
but receives an error code when it tries to position within the file.\
This situation indicates some problem with the file itself; possibly it\
has been corrupted or truncated. Reinstall all files of type .iem from\
the distribution materials. If you have modified the user-message file,\
4glusr.msg, recompile it as well.\
\
|
-1232	Message buffer too small.\
\
4GL is reading a message text from a compiled message file but cannot\
resize the buffer to be large enough to hold the complete message. This\
situation might indicate a critical shortage of data space, but more\
probably it indicates a corrupted or invalid message file. Reinstall\
all files of type .iem from the distribution materials. If you have\
modified the user-message file, 4glusr.msg, recompile it as well.\
\
|
-1233	Invalid hour, minute, or second.\
\
This message is not believed to be in use in any current product. If\
the error recurs, note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
|
-1234	Function may be applied only to datetime data types.\
\
This message is not believed to be in use in any current product. If\
the error recurs, note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
|
-1235	Character host variable is too short for the data.\
\
In an ESQL/C program, the program has attempted to fetch a column value\
into a host variable that is not large enough. Use the DESCRIBE command\
to find out the sizes of column values.\
\
If this error arises in a 4GL program, note all circumstances\
and contact Technical Support at tsmail@us.ibm.com.\
\
|
-1236	Bad era date.\
\
The era name or the era offset that is given in the input string is\
invalid or has not been entered in the required format. Check that the\
era name and offset are valid and in the proper order in the input\
string. Check the format against the value of DBTIME, DBDATE, or the\
format string passed to the SQL API function, whichever is\
appropriate.\
\
|
-1237	Bad era name.\
\
The date format requires an era name, but no name that matches the era\
names in the GLS locale could be found in the input string. Check that\
you are using the correct locale and that you entered the era name\
correctly.\
\
|
-1238	Bad era initialization.\
\
Contact Technical Support at tsmail@us.ibm.com regarding this internal error.\
\
|
-1239	Era year overflow.\
\
The era offset that is given is not within the range for the era that\
is specified. Check that the era offset is within the valid range for\
the era that is specified.\
\
|
-1250	Unable to create pipes.\
\
Your application is using an operating-system facility called a pipe to\
initialize its communication with the database server. The operating\
system returned an unexpected error. Look for operating-system error\
messages that might give more information.\
\
|
-1251	Unable to create shared memory. semget failed.\
\
Your application is initializing its communication with the database\
server, which is a version that uses shared memory for communications.\
An unexpected error has occurred with an operating-system function,\
semget. Look for operating-system messages that might give more\
information. Consult with the person who installed the IBM Informix\
shared-memory product.\
\
|
-1252	Unable to create shared memory. shmget failed.\
\
Your application is initializing its communication with the database\
server, which is a version that uses shared memory for communications.\
An unexpected error has occurred with an operating-system function,\
shmget. Look for operating-system messages that might give more\
information. Consult with the person who installed the IBM Informix\
shared-memory product.\
\
|
-1254	Unable to connect to remote host.\
\
The program is attempting to open a database that a database server in\
another system manages, but it could not open a network connection to\
the other system. Check the site name that the DATABASE or CREATE\
DATABASE statement specifies. If it is as you intended, look for other\
error messages from the networking component or the operating system.\
Contact the operator of the other system to verify that it is active\
and accepting network connections.\
\
|
-1257	Operating system cannot fork process for back end.\
\
Back end refers to the database server. In this an internal error, look\
for operating-system messages that might give more detail. In DOS\
systems, you probably are out of memory; exit to the operating-system\
command line, and resubmit your program. After you verify that no\
system limit or local problem exists, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-1258	Cannot attach to shared memory used to communicate with back end.\
\
Back end refers to the database server. In this internal error, look\
for operating-system messages that might give more detail. After you\
verify that no system limit or local problem exists, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-1260	It is not possible to convert between the specified types.\
\
The database server attempts any data conversion that makes sense. Some\
conversions, however, are not supported, such as INTERVAL to DATE, DATETIME\
to MONEY, CHAR to LIST, or CHAR to SET. Possibly you referenced the wrong\
variable or column. Check that you have specified the data types that you\
intended and that literal representations of data values are correctly\
formatted.\
\
|
-1261	Too many digits in the first field of datetime or interval.\
\
The first field of a DATETIME literal must contain either 1 or 2 digits\
(if it is not a YEAR) or else 2 or 4 digits (if it is a YEAR). The\
first field of an INTERVAL literal represents a count of units and can\
have up to 9 digits, depending on the precision that is specified in\
its qualifier. Review the DATETIME and INTERVAL literals in this\
statement, and correct them.\
\
|
-1262	Non-numeric character in datetime or interval.\
\
The form of a DATETIME or INTERVAL literal is very limited. One can\
contain only decimal digits and the allowed delimiters: the hyphen\
between year, month, and day numbers; the space between day and hour;\
the colon between hour, minute, and second; and the decimal point\
between second and fraction. Any other characters, or these characters\
in the wrong order, produce an error.\
\
|
-1263	A field in a datetime or interval is out of range or incorrect.\
\
Inspect the DATE, DATETIME, and INTERVAL literals in this statement;\
at least one of them contains at least one incorrect field.\
\
In a DATE or DATETIME literal, the year might be zero, the month might be other\
than 1 to 12, or the day might be other than 1 to 31 or inappropriate for the\
month. Also in a DATETIME literal, the hour might be other than 0 to 23, the\
minute or second might be other than 0 to 59, or the fraction might have too\
many digits for the specified precision.\
\
In an INTERVAL literal, the constraints are the same except that the\
first field is a count and can have as many digits as the qualifier\
specifies.\
\
|
-1264	Extra characters at the end of a datetime or interval.\
\
Only spaces can follow a DATETIME or INTERVAL literal. Inspect this\
statement for missing or incorrect punctuation.\
\
|
-1265	Overflow occurred on a datetime or interval operation.\
\
Both DATETIME and INTERVAL values are stored internally as DECIMAL\
values. In this statement, an arithmetic operation that uses DATETIME\
and/or INTERVAL values has caused an arithmetic overflow. This\
situation should not occur. Check the precision that is specified for\
an INTERVAL value. If the INTERVAL value that you want to enter is\
greater than the default number of digits that are allowed for that\
field, you must explicitly identify the number of significant digits in\
your definition. If the error recurs, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-1266	Intervals or Datetimes are incompatible for the operation.\
\
Some arithmetic combinations of DATETIME, INTERVAL, and numeric values\
are meaningless and are not allowed. Review the arithmetic expressions\
in this statement. Possibly one of them is using a DATETIME or INTERVAL\
column or variable by mistake. If not, see your SQL reference material\
for the valid use of these data types.\
\
|
-1267	The result of a datetime computation is out of range.\
\
In this statement, a DATETIME computation produced a value that cannot be\
stored. This situation can occur, for example, if a large interval is added\
to a DATETIME value. This error can also occur if the resultant date does\
not exist, such as Feb 29, 1999.\
\
Review the expressions in the statement and see if you can change the\
sequence of operations to avoid the overflow.\
\
|
-1268	Invalid datetime or interval qualifier.\
\
This statement contains a DATETIME or INTERVAL qualifier that is not\
acceptable. These qualifiers can contain only the words YEAR, MONTH,\
DAY, HOUR, MINUTE, SECOND, FRACTION, and TO. A number from 1 to 5 in\
parentheses can follow FRACTION. Inspect the statement for missing\
punctuation and misspelled words. A common error is adding an s, as in\
MINUTES.\
\
|
-1269	Locator conversion error.\
\
This message was issued because a function that requires an argument\
that is a locator (a reference to a BYTE or TEXT value) received\
something other than a valid locator (such as a NULL parameter, or an\
argument of any other data type).\
\
Review the program logic to make sure the arguments are correct.\
\
|
-1270	Interval literal may not have embedded minus sign.\
\
You can use a minus sign as an arithmetic operator between an INTERVAL\
literal and other values, and you can use a minus sign as a prefix to\
an INTERVAL literal to indicate it is a negative quantity. However, you\
cannot embed a minus sign among the fields of the literal. If you did\
not intend to do this, inspect the statement for missing or misplaced\
punctuation.\
\
|
-1271	Missing decimal point in datetime or interval fraction.\
\
A decimal point is expected to appear in a DATETIME or INTERVAL literal\
when the qualifier of the literal contains the word FRACTION. This\
statement has such a literal, but no decimal point was found. Inspect\
the literal qualifiers for missing or misplaced punctuation.\
\
|
-1272	No input buffer has been specified.\
\
You have not specified an input string for this function, so the\
conversion cannot proceed. Set the input-string argument, and call the\
function again. (This function might require that you define\
formatting directives with the DBTIME environment variable.)\
\
|
-1273	Output buffer is NULL or too small to hold the result.\
\
This error is returned when the function is called and the address\
space for the output buffer is null or smaller than the format-string\
length. Redefine the size of the address, and execute the function\
again. (This function might require that you define formatting\
directives with the DBTIME environment variable.)\
\
|
-1274	No output buffer has been specified.\
\
The output buffer length is zero, or the buffer pointer is a null\
pointer. Database servers after Version 5.01 do not use this error\
message.\
\
|
-1275	Invalid field width or precision in datetime or interval format string.\
\
The field width or precision in DATETIME or INTERVAL format\
specification must make sense. The field width must be a decimal\
number, with a leading zero or minus ( - ) sign. If a precision\
specification is present, it must also be decimal, separated from the\
field-width specification by a period.\
\
|
-1276	Format conversion character not supported.\
\
A format conversion character in the format string is not valid. Check\
the string against the table of format conversion directives for\
DATETIME and INTERVAL format conversion functions in the manual for\
your embedded language product. See also the discussion of the DBTIME\
environment variable in the IBM Informix Guide to SQL:\
Reference.\
\
|
-1277	Input does not match format specification.\
\
Check that the ASCII string that contains a DATETIME or INTERVAL value\
conforms to the format string. For example, a percent character in a\
DATETIME or INTERVAL ASCII string must have a matching "%" sequence in the\
format string. See also the discussion of the DBTIME environment variable in\
the IBM Informix Guide to SQL: Reference.\
\
|
-1278	Invalid escape sequence.\
\
Check the pattern-matching string that the LIKE or MATCHES clause of\
the statement specifies. In an ANSI database, the only valid characters\
that can be escaped are: , _, and the escape character for the LIKE\
clause, and *, ?, [, ], and the escape character for the MATCHES\
clause.\
\
|
-1279	Value exceeds string column length.\
\
This message applies only to ANSI databases. You attempted to insert into a\
CHAR, NCHAR, VARCHAR, NVARCHAR or LVARCHAR column using a string host\
variable, but the string is too long.\
\
|
-1280	Library API incompatibility found in libgen.so.\
\
The libgen.so shared library compiled with your client application is\
incompatible with the version in the $INFORMIXDIR/lib directory.\
Recompile your application with INFORMIXDIR set to the path of the new\
libgen.so shared library.\
\
|
-1281	Library API incompatibility found in libos.so.\
\
The libos.so shared library compiled with your client application is\
incompatible with the version in the $INFORMIXDIR/lib directory.\
Recompile your application with INFORMIXDIR set to the path of the new\
libos.so shared library.\
\
|
-1282	Library API incompatibility found in libsql.so.\
\
The libsql.so shared library compiled with your client application is\
incompatible with the version in the $INFORMIXDIR/lib directory.\
Recompile your application with INFORMIXDIR set to the path of the new\
libsql.so shared library.\
\
|
-1283	Library API incompatibility found in libgls.so.\
\
The libgls.so shared library compiled with your client application is\
incompatible with the version in the $INFORMIXDIR/lib directory.\
Recompile your application with INFORMIXDIR set to the path of the new\
libgls.so shared library.\
\
|
-1284	Value will not fit in an INT8.\
\
The INT8 or SERIAL8 data type can accept numbers with absolute values\
from 0 through 9,223,372,036,854,775,807 (plus or minus (2 to the\
63rd power) - 1).\
\
To store numbers that are outside this range, redefine the column or\
variable to use the DECIMAL data type. For more information on valid\
ranges of data types, see the IBM Informix Guide to SQL: Reference.\
\
|
-1285	Internal error: data type unknown.\
\
If this internal error recurs, please note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-1301	This value is not among the valid possibilities.\
\
A list or range of acceptable values has been established for this\
column (via an INCLUDE attribute in the form-specification file). You\
must enter a value within the acceptable range.\
\
|
-1302	The two entries were not the same. Try again.\
\
To guard against typographical errors, this field has been designated\
VERIFY (in the form-specification file). You must enter the value in\
this field twice, identically. Carefully reenter the data.\
Alternatively, you can cancel the form entry with the Interrupt key\
(usually CTRL-C, but see the operating instructions that the program\
author supplied).\
\
|
-1303	You cannot use this editing feature because a picture exists.\
\
This field is defined (in the form-specification file) with a PICTURE\
attribute to specify its format. You cannot use certain editing keys\
(for example, CTRL-A, CTRL-D, and CTRL-X) while you are editing such a\
field. Use only printable characters and backspace to enter the value.\
\
|
-1304	Error in field.\
\
You entered a value in this field that cannot be stored in the program\
variable that is meant to receive it. For example, possibly you entered\
a decimal number when the application provided only an integer\
variable, or you entered a character string that is longer than the\
application expected. Note all the circumstances and then discuss the\
problem with the person who wrote the application program.\
\
|
-1305	This field requires an entered value.\
\
The cursor is in a form field that has been designated REQUIRED. You\
must enter some value before the cursor can move to another field. To\
enter a null value, type any printable character and then backspace.\
Alternatively, you can cancel the form entry with the Interrupt key\
(usually CTRL-C, but see the operating instructions that the program\
author supplied).\
\
|
-1306	Type again for verification.\
\
The cursor is in a form field that has been designated VERIFY. You must\
enter the value twice, identically, before the cursor can move to\
another field. This procedure helps to ensure that no typographical\
errors occur during data entry. Alternatively, you can cancel the form\
entry with the Interrupt key (usually CTRL-C, but see the operating\
instructions that the program author supplied).\
\
|
-1307	Cannot insert another row - the input array is full.\
\
You are entering data into an array of records that is represented in\
the program by an array of program variables. That array is now full;\
no place is available to store another record. Press the ACCEPT key\
(usually ESCAPE, but see the operating instructions that the program\
author supplied) to process the records that you have entered.\
\
|
-1308	Cannot delete row - it has no data.\
\
You pressed the Delete Row function key (usually F2, but see the\
operating instructions that the program author supplied) in an empty\
row. Nothing was deleted.\
\
|
-1309	There are no more rows in the direction you are going.\
\
You are attempting to scroll an array of records farther than it can\
go, either scrolling up at the top or scrolling down at the bottom of\
the array. Further attempts will have the same result.\
\
|
-1310	Exiting the current function without executing a RETURN statement.\
\
The current function does not return void but is about to exit without\
executing a RETURN statement.\
\
|
-1312	FORMS statement error number number.\
\
A problem exists with a screen form. Look up error number in this\
document. Consider it in relation to the current statement.\
\
|
-1313	SQL statement error number number.\
\
The current statement calls on the database server that detected an\
error and returned an error code number. Look up number in this\
document. Also look for other error messages.\
\
|
-1314	Program stopped at statement, line number line.\
\
At the indicated point in the program, an error was detected. Look for\
other error messages that give details of the error. Use the numbers in\
this message to locate the error in the program source file.\
\
|
-1315	4GL run-time error number number.\
\
The program stopped because an error was detected. Look up error code\
number in this document. Also look for other error messages for more\
details.\
\
|
-1316	ISAM error number number.\
\
The current statement called on the database server, which detected an\
error (probably reported in a display of error -1313). This message\
contains additional detail on the cause of the error. Look up number in\
this document.\
\
|
-1317	A numeric conversion error has occurred due to incompatibility\
between a calling program and its function parameters or between a variable\
and its assigned expression.\
\
4GL converts between one data type and another automatically whenever\
it can do so without losing information. In the current statement, it\
could not do so. Look first for function calls, and inspect the values\
that are passed as parameters. Check that the values that are passed\
agree in type with the parameters as they are defined in the function\
bodies. (An example of such an error would be calling a function\
fun("X") when within the function its parameter was defined as an\
integer.) If the statement is a LET statement, check that the value\
that is computed on the right can be accommodated in the variable that\
is named on the left.\
\
|
-1318	A parameter count mismatch has occurred between the calling function\
and the called function.\
\
Either too many or too few parameters were given in the call to the\
function. The call is probably in a different source module from the\
called functions. Inspect the definition of the function, and check\
all places where it is called to ensure that they use the number of\
parameters that it declares.\
\
|
-1319	The 4GL program has run out of runtime data space memory.\
\
You must reduce the data space that the program requires. Review the\
size of large character variables and the dimensions of arrays. You\
might need to split the program into separate programs that load\
separately, if that is possible.\
\
|
-1320	A function has not returned the correct number of values expected\
by the calling function.\
\
If the function was invoked as part of an expression, then it returned\
more than one value. If a CALL invoked it, the number of expressions\
that follow the RETURN statement (in the function) was different from\
the number of variables that are listed in the RETURNING clause (in the\
CALL statement).\
\
Check that the correct function was called. Review the logic of the\
function, especially its RETURN statements, to ensure that it always\
returns the expected number of values.\
\
|
-1321	A validation error has occurred as a result of the VALIDATE command.\
\
The VALIDATE statement tests the current value of variables against\
rules that are stored in the syscolval table. It has detected a\
mismatch. Ordinarily, the program would use the WHENEVER statement to\
trap this error and display or correct the erroneous values. Inspect\
the VALIDATE statement to see which variables were being tested and\
find out why they were wrong.\
\
|
-1322	A report output file cannot be opened.\
\
The file that the REPORT TO statement specifies cannot be opened. Check\
that your account has permission to write such a file, that the disk is\
not full, and that you have not exceeded some limit on the number of\
open files.\
\
|
-1323	A report output pipe cannot be opened.\
\
The pipe that the REPORT TO PIPE statement specifies could not be\
started. Check that all programs that are named in it exist and are\
accessible from your execution path. Also look for operating-system\
messages that might give more specific errors.\
\
|
-1324	A report output file cannot be written to.\
\
The file that the REPORT TO statement specifies was opened, but an\
error occurred while writing to it. Possibly the disk is full. Look for\
operating- system messages that might give more information.\
\
|
-1326	An array variable has been referenced outside of its specified\
dimensions.\
\
The subscript expression for an array has produced a number that is\
either less than one or greater than the number of elements in the\
array. Review the program logic that leads up to this statement to\
determine how the error was made.\
\
|
-1327	An insert statement could not be prepared for inserting rows into\
a temporary table used for a report.\
\
Within the report function, 4GL generated an SQL statement to save rows\
into a temporary table. The dynamic preparation of the statement (see\
the reference material on the PREPARE statement) produced an error.\
Probably the database tables are not defined now, at execution time, as\
they were when the program was compiled. Either the database has been\
changed, or the program has selected a different database than the one\
that was current during compilation. Possibly the database\
administrator has revoked SELECT privilege from you for one or more of\
the tables that the report uses. Look for other error messages that\
might give more details.\
\
|
-1329	A database index could not be created for a temporary database\
table needed for a report.\
\
Within the report definition, 4GL generated SQL statements to save rows\
into a temporary table. However, an index could not be created on the\
temporary table. Probably an index with the same name already exists in\
the database. (The sorting index is named "i_reportname"; for example,\
"i_order_rpt".) Possibly no disk space is available in the file system\
or dbspace. Another possibility with some database servers is that you\
have exceeded an operating-system limit on open files. Look for other\
error messages that might give more details.\
\
|
-1328	A temporary table needed for a report could not be created in\
the selected database. The user must have permission to create tables in\
the selected database.\
\
Within the report definition, 4GL generated an SQL statement to save\
rows into a temporary table, but the temporary table could not be\
created. Probably no disk space is left in the database, or you\
already have a table in your current database with the same name as the\
temporary table that the report definition is attempting to create as a\
sorting table.\
\
Another possible cause is that the report name is too long. It should be 16\
characters or fewer if your database server allows only table names\
up to 18 characters long, to leave room for the "t_" prefix.\
\
The sorting table is named "t_reportname". For example, a report named\
"order_rpt" would name its sorting table "t_order_rpt". Users should\
avoid beginning table names with "t_".\
\
Another possible cause of this error with some database servers is that\
you have exceeded an operating-system limit on open files.\
\
Look for other error messages that might give more details.\
\
|
-1330	A row could not be inserted into a temporary report table.\
\
Within the report definition, 4GL generated SQL statements that would\
save rows into a temporary table. However, an error occurred while rows\
were being inserted. Probably no disk space is left in the database.\
Look for other error messages that might give more details.\
\
|
-1331	A row could not be fetched from a temporary report table.\
\
Within the report definition, 4GL generated SQL statements to select\
rows from a temporary table. The table was built successfully but now\
an error occurred while rows were being retrieved from it. Almost the\
only possible cause is a hardware failure or an error in the database\
server. Check for operating-system messages that might give more\
details.\
\
|
-1332	A character variable has referenced subscripts that are out of range.\
\
In the current statement, a variable that is used in taking a substring\
of a character value contains a number less than one or a number\
greater than the size of the variable, or the first substring\
expression is larger than the second. Review the program logic that\
leads up to this statement to find the cause of the error.\
\
|
-1333	Strings of length > 512 cannot be returned from function calls.\
\
The current RETURN statement contains an expression that evaluates to a\
character string longer than 512 characters. This situation is not\
supported. Review the logic of the function, and modify it so that it\
does not return such a long character value. You can assign a longer\
string to a global variable.\
\
|
-1335	A report is accepting output or being finished before it has been\
started.\
\
The program executed an OUTPUT TO REPORT or FINISH REPORT statement\
before it executed a START REPORT. Review the program logic that leads\
up to this statement to find the cause of the error.\
\
|
-1336	Module name in the pcode file contains pcode version compile-version.\
This program can run pcode version runner-version. Run the pcode compiler\
with the -V option to check the pcode version that it produces. Then\
recompile all modules of your program, and run it again.\
\
The program runner or a customized runner must be the same software\
version as the program compiler. To check that the programs are at the\
same level, execute each with the -V option. That option displays their\
version numbers. When you determine that you are using compatible\
software, recompile your program.\
\
|
-1334	The 4GL program cannot allocate any more space for temporary\
string storage.\
\
You should not see this message from a program that is compiled at a\
version later than Version 4.1; however, programs that are compiled by\
4GL Version 4.1 and earlier must deal with this issue.\
\
Temporary string storage is used while evaluating a character\
expression. It is allocated by a simple algorithm from a fixed-size\
buffer. Space in this buffer is not reclaimed until the last pending\
character expression is finished. Because most expressions complete\
immediately, the string buffer is normally emptied as fast as it is\
used.\
\
However, when expressions involve function calls, expression evaluation\
is suspended during the function call. The buffer is not cleared until\
the function returns. For example, temporary space is used for the\
literal "###" and the result of the USING operator in the following\
statement:\
\
LET charvar = numvar USING '###', myfunc()\
\
These pending values remain in the string buffer for the duration of\
the call to myfunc(). If the aggregate total of all temporary character\
values that are used during the evaluation of myfunc() and its\
sub-functions exceeds the buffer size, this error occurs.\
\
You can usually prevent the error by isolating function calls in\
separate statements, as in the following example:\
\
LET charvar = myfunc()\
LET charvar = numvar USING '###', charvar clipped\
\
The string buffer is free during the call to myfunc() in the first\
statement and free again as soon as the second statement completes.\
\
The short form of a WHEN clause in a CASE statement also creates a\
suspended character expression. In the following example, temporary\
string storage is tied up throughout the calls to func_A() and\
func_B().\
\
CASE charvar\
        WHEN 'A' CALL func_A()\
        WHEN 'B' CALL func_B()\
...\
\
The longer form of the WHEN clause does not do this because evaluation\
of the character expression is completed before the function call\
begins.\
\
CASE\
        WHEN charvar = 'A' CALL func_A()\
        WHEN charvar = 'B' CALL func_B()\
\
Finally, a known error in some versions of IBM Informix-4GL Version 4.1\
causes a spurious error of this type when the WORDWRAP clause appears\
in a PRINT statement. If the error recurs, note all\
circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-1337	The variable name has been redefined with a different type or length.\
\
The variable that is shown is defined in the GLOBALS section of two or\
more modules, but it is defined differently in some modules than in\
others. Possibly modules were compiled at different times, with some\
change to the common GLOBALS file between. Possibly the variable is\
declared as a module variable in some module that does not include the\
GLOBALS file.\
\
|
-1338	The function name has not been defined in any module in the program.\
\
The named function is called from at least one module of the program,\
but it is defined in none. If you are using the Programmer's\
Environment, possibly one module was not defined as part of a\
multimodule program. If you are working at the command line, possibly\
one or more compiled .4go modules were omitted when the program files\
were concatenated to form the .4gi file.\
\
|
-1339	Global variable name cannot be found in the descriptor table.\
\
This error indicates an internal problem in the runner. If the error\
recurs, note all circumstances and contact Technical\
Support at tsmail@us.ibm.com.\
\
|
-1340	The error log has not been started.\
\
The program called the errorlog() function without first calling the\
startlog() function. Review the program logic to find out the cause of\
this error.\
\
|
-1343	No help file specified.\
\
This INPUT, PROMPT, or MENU statement contains a HELP help-number\
clause; however, no message file has been established. The OPTIONS HELP\
FILE statement establishes the message file, but the statement has not\
yet been executed. Review the program logic, and modify it to execute\
an OPTIONS statement with a HELP FILE clause before it is needed.\
\
|
-1344	IBM Informix Run Time Facility.\
\
No current IBM Informix product displays this message.\
\
|
-1345	Undefined opcode.\
\
The p-code file for the program (whose file suffix is .4go) has become\
corrupted. Recompile the whole program, and run it again. If the same\
error occurs, check that you are running the identical version of both\
the p-code compiler and the p-code runner. If the error recurs,\
note all circumstances and contact Technical Support at tsmail@us.ibm.com.\
\
|
-1346	Number is too large for a DECIMAL data type.\
\
The DECIMAL data type accommodates numbers from 10 to the -130th power\
through 10 to the 124th power in absolute value. The precision (number\
of significant digits) varies from 1 to 32; however, the source of this\
error is not the length of the number but its magnitude.\
\
|
-1347	Number is too small for a DECIMAL data type.\
\
The DECIMAL data type accommodates numbers from 10 to the -130th power\
through 10 to the 124th power in absolute value. The precision (number\
of significant digits) varies from 1 to 32; however, the source of this\
error is not the length of the number but its magnitude.\
\
|
-1348	An attempt was made to divide by zero.\
\
Zero cannot be a divisor. In some cases, this error arises because the\
divisor is a character value that does not convert properly to numeric.\
\
|
-1349	Character to numeric conversion error.\
\
A character value is being converted to numeric form for storage in a\
numeric column or variable. However, the character string cannot be\
interpreted as a number. It contains some characters other than white\
space, digits, a sign, a decimal, or the letter e, or else the parts\
are in the wrong order so that the number cannot be deciphered.\
\
|
-1350	It is not possible to convert between the specified types.\
\
The system will attempt any data conversion that makes sense. However,\
some conversions, such as INTERVAL to DATE, or DATETIME to MONEY, are\
not supported. Possibly you referenced the wrong variable or column.\
Check that you have specified the data types that you intended and that\
you formatted literal representations of data values correctly.\
\
|
-1351	The function (or report) name has already been defined. Function\
and report cannot both have the same name.\
\
Each function (or report, which is similar to a function) must have a\
unique name within the program. You must change either this use or the\
prior one.\
\
|
-1352	name may not be used as both a function (or report) name and\
a variable name.\
\
The name that is shown has been defined at least two ways. Names at the\
global or module level (function names, report names, and names of\
global or module variables) must be unique. Locate all the definitions\
of this name, and change all but one of them.\
\
|
-1353	Use '!' to edit TEXT and BYTE fields.\
\
The built-in form editor cannot deal with TEXT or BYTE columns.\
However, you can designate an external program that can display or edit\
a value from a TEXT or BYTE column. To call the external program for\
any field, put the cursor in that field, and key the exclamation mark\
(!) character. If an external program has been defined (with the\
PROGRAM attribute in the form specification), it will be started. In a\
TEXT field, if no external program is specified in the form, the\
program that the DBEDIT environment variable names will be started.\
\
|
-1355	Cannot build temporary file.\
\
A TEXT or BYTE variable has been located in a temporary file using the\
LOCATE statement. The current statement assigns a value into that\
variable, so 4GL attempted to create the temporary file, but an error\
occurred. Possibly no disk space is available, or your account does not\
have permission to create a temporary file. 4GL creates a temporary\
file in the directory that the DBTEMP environment variable specifies.\
Look for operating-system error messages that might give more\
information. Check the value of DBTEMP. Since Version 5.01, the\
IBM Informix SE database server uses the DBTEMP environment variable, but\
IBM Informix  Dynamic Server and IBM Informix OnLine Dynamic Server do not.\
\
|
-1356	Write error on temporary file filename.\
\
The operating system signalled an error during output to a temporary\
file in which a TEXT or BYTE variable was being saved. Possibly the\
disk is full, or a hardware failure occurred. For more information,\
look for operating-system messages.\
\
|
-1357	Read error on temporary file filename.\
\
The operating system signalled an error during input from a temporary\
file in which a TEXT or BYTE variable was saved. Possibly a hardware\
failure occurred. For more information, look for operating-system\
messages.\
\
|
-1358	Write error on TEXT or BYTE file filename.\
\
The operating system signalled an error during output to a temporary\
file in which a TEXT or BYTE variable was being saved. Possibly the\
disk is full, or a hardware failure occurred. For more information,\
look for operating-system messages.\
\
|
-1359	Read error on TEXT or BYTE file filename.\
\
The operating system signalled an error during output to a temporary\
file in which a TEXT or BYTE variable was being saved. Possibly the\
disk is full, or a hardware failure occurred. For more information,\
look for operating-system messages.\
\
|
-1360	No PROGRAM= clause for this field.\
\
You pressed the exclamation-mark key (!) while the cursor was in a TEXT\
or BYTE field. However, no external program has been designated for\
this field (with the PROGRAM attribute in the form-specification file).\
If this field is a TEXT field, you can set the DBEDIT environment\
variable before you start the program to specify a text editor.\
\
|
-1361	Illegal TEXT or BYTE file name. Null names are not permitted.\
\
The BYTE or TEXT variable has been located in a file using the 4GL\
statement LOCATE. However, the filename that is given for the variable\
is a null string. Because the file does not exist, 4GL cannot do\
anything with it.\
\
|
-1362	4GL runtime stack violation.\
\
The program attempted to access outside the boundaries of the stack. If\
the error recurs, note all circumstances and contact\
Technical Support at tsmail@us.ibm.com.\
\
|
-1363	A fatal internal error has occurred - Application Terminating.\
\
The program attempted to access outside the memory that belongs to the\
application. If the error recurs, note all circumstances and\
contact Technical Support at tsmail@us.ibm.com.\
\
|
-1364	Error recovery setup failed - Application Terminating.\
\
The mechanism that allows the application to catch and handle internal\
errors could not complete its actions. Return to DOS, and restart\
Windows.\
\
|
-1365	Application appname not found.\
\
The Application Launcher, fglaunch, did not find the requested\
application.\
\
|
-1366	Unable to load application appname.\
\
The Application Launcher, fglaunch, could not load the requested\
application. The DLL does not have the required NewEra entry points, so\
it must not be a NewEra DLL. Check to see if the NewEra DLL has the\
same name as an existing system DLL.\
\
|
-1367	DLL dllname is not a resource DLL - Application Terminating.\
\
The program options for the Application Launcher, fglaunch, specified\
that the DLL dllname included resources, but no resources were found,\
\
|
-1371	The field fieldname does not exist in the current form.\
\
The indicated field name has been given to the NEXT FIELD statement or\
to the pf_nxfield() function, but it is not defined in the current\
form. A common error is to confuse the tag name, which is used in the\
screen layout and to the left of the equal sign in the ATTRIBUTES\
section, with the field name, which is the column name used to the\
right of the equal sign in the ATTRIBUTES section. Use the latter when\
you refer to fields.\
\
|
-1