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 't