An operating system error code with the meaning shown was 
unexpectedly returned to the database server. If the error recurs, 
please note all circumstances and contact the Informix Technical 
Support Department. 

Note: 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. It is probably the case 
that this implementation of the Informix database server uses 
"kernel locking"; that is, that it uses operating system facilities for 
locking rows of tables. The capacity of the operating system's lock 
table has been exceeded. Contact your system administrator and 
inquire about having the operating system configured to support 
more locks. Also examine your database application to see if it can 
use fewer locks, for example, by updating fewer rows in each 
transaction, or by locking whole tables instead of rows.

OnLine-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. 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. SQL 
products: A duplicate key value was used in the last INSERT or 
UPDATE.

-101	ISAM error: file is not open.

The ISAM processor has been asked to use an unopened file (table). 
C-ISAM programs: The program has tried to use a file before 
opening it with a call to isopen, or has tried to write to a file that was 
opened read-only. If the error recurs, please note all circumstances 
and contact the Informix Technical Support Department. 

-102	ISAM error: illegal argument to ISAM function.

A parameter presented to one of the C-ISAM functions is outside the 
range of acceptable values. C-ISAM programs: Review the 
parameters used in this function call, comparing them to the 
documentation for the function. If the error recurs, please note all 
circumstances and contact the Informix Technical Support 
Department.

-103	ISAM error: illegal key descriptor (too many parts or too long).

The ISAM processor has been given an invalid key descriptor. 
C-ISAM programs: Review the key descriptor. There is a maximum 
of 8 parts and 120 characters to each key descriptor. If the error 
recurs, please note all circumstances and contact the Informix 
Technical Support Department.

-104	ISAM error: too many files open.

The ISAM processor has reached its limit of open files. C-ISAM 
programs: Review the program logic and change it so as to have 
fewer files open concurrently. Use isclose to close unneeded files. 
SQL products: This query is too complex, using too many tables 
concurrently. Perform the query in steps, using temporary tables.

-105	ISAM error: bad isam file format.

The contents of an ISAM file (table or index) have been corrupted. 
C-ISAM: If transaction logging has been used, you can recover the 
file using the isrecover program. Otherwise re-create the file or 
restore it from backup. SQL products: Use the bcheck or secheck 
utility to get more information on the problem and possibly to 
correct it (use tbcheck with the INFORMIX-OnLine database server 
or oncheck with the INFORMIX-OnLine Dynamic Server). If the 
utility cannot recover the table or index, it will have to be re-created 
or restored.

-106	ISAM error: non-exclusive access.

The ISAM processor has been asked to add or drop an index when it 
does not have exclusive access. C-ISAM programs: Before doing this 
operation the file must be opened with exclusive access. Review the 
program logic and make sure it opens this file passing the 
ISEXCLLOCK flag to isopen. SQL products: This error can be 
returned on the INFORMIX-OnLine Dynamic Server or the 
INFORMIX-SE database server when an exclusive lock is required on 
a table. For example, this error appears when a second user tries to 
alter a table that has been locked by the first user.

-107	ISAM error: record is locked.

The record requested, or the file (table) that contains it, has been 
locked by another user request. This is normally a transient 
condition. A program can recover by rolling back the current 
transaction, waiting a short time, and re-executing the operation. 
Using interactive SQL: Redo the operation. C-ISAM programs: 
Review the program logic and make sure it is prepared to handle 
this case, which is a normal event in multiprogramming systems. 
You can get exclusive access to a table by passing the ISEXCLLOCK 
flag to isopen. SQL programs: Review the program logic and make 
sure it can handle this case, which is a normal event in 
multiprogramming systems. The simplest way to handle it is to use 
the command SET LOCK MODE TO WAIT. For bulk updates see the 
LOCK TABLE command and the EXCLUSIVE option of the DATABASE 
statement.

-108	ISAM error: key already exists.

The ISAM processor has been asked to create an index that already 
exists. C-ISAM programs: Review the program logic. This existing 
index must be deleted before defining another. If the error recurs, 
please note all circumstances and contact the Informix Technical 
Support Department..

-109	ISAM error: the key is the file's primary key.

The ISAM processor has been asked to delete the primary key index. 
C-ISAM programs: The primary key cannot be deleted by the 
isdelindex call. If the error recurs, please note all circumstances and 
contact the Informix Technical Support Department.

-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). C-ISAM programs: 
This is the normal signal of end of file. Use a different retrieval mode 
of isread to reposition the file. SQL products: See the SQL error 
message or return code.

-111	ISAM error: no record found.

The ISAM processor cannot locate the requested record. C-ISAM 
programs: Depending on the retrieval mode in use, there is no 
record with the requested index value or record number. Make sure 
the correct index is in use. 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. C-ISAM programs: Review the program 
logic. Before using the ISCURR retrieval mode the program must use 
another retrieval mode, for example ISFIRST, to establish a current 
record. If the error recurs, please note all circumstances and contact 
the Informix Technical Support Department.

-113	ISAM error: the file is locked.

The file (table) that was requested has been opened in exclusive 
mode by another user request. In systems that use files for locking, 
a tablename.lok file exists. Possibly such a file is residual, left behind 
when another program terminated abnormally. If you can be sure 
that is the case, you can release the lock by emptying that file. Lock 
files are not used in many systems, and are never used with the 
INFORMIX-OnLine Dynamic Server.

C-ISAM programs: Rerun the program after the file has been 
unlocked. SQL products: Tables are locked explicitly using the LOCK 
TABLE statement, and implicitly during the execution of the CREATE 
INDEX and ALTER TABLE commands. Rerun the program or query 
when the table has been unlocked.

-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. C-ISAM programs: This is a 
restriction of the product. You will have to choose a shorter filename. 
If the error recurs, please note all circumstances and contact the 
Informix Technical Support Department.

-115	ISAM error: cannot create lock file.

The ISAM processor has been asked to access a file or row using 
locking. Since this is an operating system in which files are used for 
locking, ISAM must create a tablename.lok file. When it tried to do so, 
it got an error code from the operating system. Possibly the disk is 
full; possibly your account does not have write permission in the 
relevant directory. Look for operating system error messages that 
may give more information.

-116	ISAM error: cannot allocate memory.

The ISAM processor needed to allocate memory for data storage and 
was unable to do so. Possibly there is some problem in the operating 
system; look for operating system error messages that may give 
more information. One cause: selecting a row containing large BYTE 
or TEXT columns into a temporary table or as part of an INSERT or 
UPDATE. In some versions, an entire row including BLOB values is 
buffered in memory. C-ISAM programs: Review the program, 
looking for any way it can use less memory. SQL products: simplify 
the program, form or report if possible.

-117	ISAM error: bad custom collating sequence.

This message is not displayed by any current Informix product. If 
the error recurs, please note all circumstances and contact the 
Informix Technical Support Department.

-118	ISAM error: cannot read log record.

The ISAM processor is trying to roll back a transaction or recover a 
file and has encountered an error reading the transaction log. Look 
for operating system error messages that may give more 
information. The dblog or selog utility can be used to get more 
information about the problem. If the file (table) cannot be 
recovered, it will have to be re-created or restored from backup.

-119	ISAM error: bad log record.

The ISAM processor is trying to roll back a transaction or recover a 
file and 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, it will have to be 
re-created or restored from backup.

-120	ISAM error: cannot open log file.

The ISAM processor is trying to open the transaction log file and has 
received an error from the operating system. Look for operating 
system error messages that may give more information. C-ISAM 
programs: Review the parameter passed to islogopen. Make sure it 
specifies the correct filename of an existing, writable log file, and 
includes a path if the file is not in the current directory. SQL products: 
The transaction log file is established with the START command. 
Make sure that the log file still exists in the same directory location 
as when START 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 
and has received an error from the operating system. One probable 
cause is that the disk is full. Look for operating system error 
messages that may give more information. The transaction log file 
can grow quite large. In order to reduce its size you must do two 
things. First, make a backup copy of the data file (C-ISAM) or all 
database files (SQL). Second, make the transaction log file an empty 
file. If these steps are performed routinely, the size of the log file can 
be controlled.

-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. C-ISAM 
programs: This file was not opened with logging. Review the calls to 
isopen and make sure ISTRANS parameter is included. SQL 
products: This database does not support transaction logging. If you 
are using the OnLine database server, have the system administrator 
enable logging for this database. Otherwise, use the START 
statement to begin transaction logging. In all cases, logging should 
only be started immediately after a full archive of the database has 
been taken.

-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. C-ISAM programs: Review the 
program logic to make sure that it calls isbegin before calling 
iscommit or isrollback. SQL products: Make sure 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 which is located on 
a disk attached to another machine and accessed using the Network 
File System (NFS). This is not supported. Database files must be on 
disks which are physically attached to the machine in which the 
ISAM processor is running. In order to use a database in a different 
machine you must install the INFORMIX-STAR or INFORMIX-NET 
networking software. Then an application in this machine can 
communicate with a database server running in the machine 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 and could not find a row at that location. C-ISAM programs: 
If using access by record number, review the number stored in 
isrecnum; it is invalid. Otherwise the current index may be 
damaged; run the bcheck or secheck utility. SQL products: The 
index has been damaged; run the bcheck or secheck utility to check 
and repair it if using the INFORMIX-SE database server. Run tbcheck 
if using the INFORMIX-OnLine database server  or oncheck if using 
the INFORMIX-OnLine Dynamic Server.

-127	ISAM error: no primary key.

The ISAM processor was called for a function which requires a 
unique primary-key index to exist, but no such index exists for this 
file. 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 may be 
damaged; run the bcheck or secheck utility. If the error recurs, 
please note all circumstances and contact the Informix Technical 
Support Department.

-128	ISAM error: no logging.

The ISAM processor was called for a function which requires a 
transaction log, but none exists for this file. C-ISAM programs: 
Review the creation of the data file. Before using such functions as 
isbegin the program must set up a log using islogopen. SQL 
products: This database does not support transaction logging. If you 
are using the OnLine database server, have the system administrator 
enable logging for this database. Otherwise, use the START 
statement to begin transaction logging. In all cases, logging should 
only be started immediately after a full archive of the database has 
been taken.

-129	ISAM error: too many users.

This implementation of ISAM uses