Informix Messages and Corrections. Publication Date: March 1994
#  END OF VERSION INFORMATION
Informix Error 
Messages

1203	Cannot find message file. 

DataExtract cannot locate a needed message file. Check that the 
INFORMIXDIR and DBLANG environment variables are set with the 
appropriate pathname. Contact your system administrator if you 
need help with this action. 

1204	Type of terminal is unknown to the system. 

Check the setting of the TERM environment variable. Check that the 
database-name is spelled correctly. Contact your system 
administrator if you need help with this action. 

2005	Database database-name not found or not correct format. 

Check that the database-name is spelled correctly.

2008	The table table-name does not exist in the database. 

The table name included in the TABLE section of the form 
specification file is not found in the database specified in the 
DATABASE section. Check the spelling of the table name. 

2009	You have not selected 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: table-name. 

Check the accompanying message for an ndication of system action. 
The indicated tables are involved in the specified error(s).

4074	There is no C language compiler contained in any directory in your 
path.

This is a 4GL compiler message. A C compiler is needed 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.

This is a 4GL compiler message. Look up the message for -number.

4150	Program error at module, line number line.

This 4GL run-time message is caused by erroneous code detected in 
the indicated line (although the actual error or omission might be 
earlier in the program). Look for additional messages explaining the 
error.

4152	FORMS statement error number -number.

This is a 4GL run-time error. Look up the message for -number.

4153	SQL statement error number -number.

This is a 4GL run-time error. Look up the message for -number.

4154	Program stopped at module, line number line.

This is a 4GL run-time message giving details of where a program 
stopped due to an error. Look for additional messages explaining 
the error.

4155	4GL run-time error number -number.

This is a 4GL run-time error. Look up the message for -number.

4156	ISAM error number -number.

This is a 4GL run-time error. Look up the message for -number.

4157	SYSTEM error number -number.

This is a 4GL run-time error. Look up the message for -number.

8009	See error number errno. 

Check the accompanying message for an indication of system 
action. Locate the indicated error message in this section. 

19750	Invalid serial number. Please consult the Installation Instructions.

This is an RSAM error message indicating an incorrect serial 
number.

21957	Invalid block size.

You have specified too small a block size for the tape device in your 
onload or onunload command. The block size must be larger than 
the size (in kilobytes) indicated in the accompanying error message. 
The onload and onunload utilities require a block size parameter 
with a minimum value of 4 for 2-kilobyte-page machines, or 8 for 
4-kilobyte-page machines.

25500	The sqlexecd daemon is not licensed for remote use. 

You have entered an incorrect serial number or serial number key 
while running the Informix client/server product installation script. 
Obtain the proper serial number and key and reinstall your Informix 
client/server product software. 

25501	The sqlexecd daemon must be started by root. 

Log in as root and start the sqlexecd daemon process. 

25502	The sqlexecd daemon cannot execute the fork system call. 

Check with your system administrator for problems with the 
system. 

25503	Informix network support is not available in this version. 

This version of the sqlexecd daemon does not support these 
network connections. Check that the database or database server 
specified in the DBPATH environment variable is correct. See the 
system administrator to check on INFORMIX-NET licensing.

25504	The sqlexecd daemon cannot open a socket. 

Check that your TCP/IP network is installed and functioning 
properly throughout the network. 

25505	The sqlexecd daemon cannot bind a name to the socket. 

Reenter your request. If the problem persists, refer to your system 
manual for more information about the source of the problem. 

25506	The sqlexecd daemon cannot accept a connection on the socket. 

Check that your TCP/IP network is installed and functioning 
properly throughout the network. 

25507	The specified service name or protocol is unknown. 

The database administrator should check the sqlhosts file entry. If 
you are using the TCP protocol, make sure the service name appears 
in the /etc/services file and is correct. (If you are using NFS, use 
ypmake to check /etc/services.) If this service name was added after 
a default boot, it might not be recognized by the daemon.

25510	The database engine server-name could not be started by execv, 
system errno error number. 

Reenter your request. If the problem persists, refer to your system 
manual for more information about the source of the problem. 

25511	The sqlexecd daemon could not receive data from client. 

Check that your TCP/IP network is installed and functioning 
properly throughout the network. 

25512	The database engine program cannot be accessed. 

Make sure that you can access the requested database server 
program. 

25514	The sqlexecd daemon cannot open the log file. 

Make sure that you can write to the requested log file. 

25515	Too many arguments were passed to the sqlexecd daemon. 

Verify that the versions of Informix client/server products running 
on the client and server are compatible. 

25518	Unknown network type specified in DBNETTYPE. Assuming 
STARLAN. 

Set the DBNETTYPE environment variable to either starlan or tcp/ip 
depending on your local network. This error message is not used by 
database servers beginning with Version 6.0.

25519	The sqlexecd daemon cannot open the network device. 

Reenter your request. If the problem persists, refer to your system 
manual for more information about the source of the problem. 

25520	The sqlexecd daemon cannot allocate the call structure. 

Reenter your request. If the problem persists, refer to your system 
manual for more information about the source of the problem. 

25521	The sqlexecd daemon cannot allocate the return structure. 

Reenter your request. If the problem persists, refer to your system 
manual for more information about the source of the problem. 

25522	The sqlexecd daemon cannot allocate the call structure. 

Reenter your request. If the problem persists, refer to your system 
manual for more information about the source of the problem. 

25523	The sqlexecd daemon cannot bind the network structures. 

There is another process running using the same service number. If 
the system administrator is not using the running sqlexecd process, 
kill it and start a new one. Or, add a new entry to /etc/services and 
start a daemon for the service using this new service number. Refer 
to your system manual for information about the source of the 
problem. 

25526	The sqlexecd daemon cannot listen on the network device. 

Reenter your request. 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 your network software and hardware are installed and 
functioning properly throughout the network. 

25529	The sqlexecd daemon cannot get a host structure. 

Check that the requested hostname is valid. Verify that the requested 
hostname has an entry in the /etc/hosts file. 

25530	The sqlexecd daemon cannot bind to the required port address.

Check to see if there is a daemon already running on that port 
address. 

25531	The sqlexecd daemon cannot bind to the required address.

Check to see if there is a daemon already running on that port 
address. 

25533	The sqlexecd daemon cannot close the network. 

Reenter your request. If the problem persists, refer to your system 
manual for more information about the source of the problem. 

25534	The sqlexecd daemon cannot allocate a structure. 

Reenter your request. If the problem persists, refer to your system 
manual for more information about the source of the problem. 

25535	Address translation failed in sqlexecd daemon. 

Reenter your request. If the problem persists, refer to your system 
manual for more information about the source of the problem. 

25537	The sqlexecd daemon cannot connect to network. 

Check that your TCP/IP or StarGROUP network is installed and 
functioning properly throughout the network. 

25543	The specified service name or protocol is unknown. 

Check the /etc/services file and verify that the requested 
servicename exists and that it uses the correct protocol. 

25544	The sqlexecd daemon cannot get a host structure. 

Check that the requested server name is valid. Verify that the 
requested server name, client address, and host names are defined 
in the /etc/hosts file.

25545	The sqlexecd daemon cannot advertise the specified service name. 

You are starting the sqlexecd daemon on a system running portable 
INFORMIX-OnLine for NetWare with IPX/SPX as the network 
protocol, but the daemon is unable to advertise the servicename for 
the database server on the INFORMIX-OnLine for NetWare network. 
Possible reasons include: another sqlexecd daemon is already using 
the same servicename, a recently stopped sqlexecd daemon with the 
same servicename was unable to de-advertise its service, or the 
portable INFORMIX-OnLine for NetWare software on your system is 
down.

The servicename of each database server must be unique across the 
entire INFORMIX-OnLine for NetWare network. The default 
servicename is sqlexec. If the name is already used by another 
sqlexecd daemon or database server on the network, use a different 
servicename to start the sqlexecd daemon. You can explicitly specify 
a servicename 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 servicename. When terminating an 
sqlexecd daemon, use the TERM signal (15) only (i.e., kill -15 
pid, or, kill pid). If a service is not terminated properly, 
depending on your portable INFORMIX-OnLine for NetWare 
configuration, it might take about three minutes for a terminated 
service to be de-advertised automatically.

32700	Cannot find license file.

The program cannot open the license file. It first tries to open the file 
specified by the user 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 to see if 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 to see 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.

32702	Cannot connect to a license daemon server.

If you edited the license file after installation, make sure that no 
mistake was made. 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. Make sure that the daemons on all license 
servers are still running and that the network is working properly.