The SQLBYTE simple large object data could not be converted to HEXASCII, or the SQLTEXT simple large object data has invalid character data (characters not in the code set).
Remove the invalid characters from the input data.
The target database table cannot be accessed.
For more information, use the finderr or Informix Error Messages utility.
A memory allocation error occurred. Probably the system is out of virtual shared memory.
Run onpload again when fewer users are on the system.
For UNIX, increase the amount of available shared memory with the UNIX kernel configuration.
For Windows, reduce the number of applications running concurrently.
System memory cannot be allocated for communications. This situation should only happen if all system resources are consumed.
Note the circumstances and contact Technical Support.
A TCP socket cannot be opened.
See your errno.h file.
An error occurred when onpload attempted to open a TLI connection.
Check that TLI services are installed on the operating system. See your tiuser.h file.
UNIX Only
You may be specifying a driver incorrectly. If the Driver Class specification is not Fixed, Cobol, or Delimited, either the onpload custom-driver shared library is not in the pathname, or the custom-driver shared library is not installed correctly.
For information on building a shared library, see Rebuilding the Shared-Library File. Make sure your driver is configured correctly for Fixed, Cobol, or Delimited.
UNIX Only
This message is generated by ipload when it cannot connect to the onpload socket service.
See /usr/include/errno.h.
UNIX Only
An error occurred when onpload attempted to open a TLI connection.
Check that TLI services are installed on the operating system. See /usr/include/tiuser.h (t_error_num).
UNIX Only
The target database server cannot be opened.
For more information, use the finderr or Informix Error Messages utility.
A possible permissions problem exists for onpload or oninit.
Note the circumstances and contact Technical Support.
The object constraints are disabled during the load and re-enabled after the load. An error occurred when onpload attempted to disable the object constraints.
For more information, use the finderr or Informix Error Messages utility.
You attempted to use express mode to load a table that has child-table records that refer to it. Express mode does not support this condition. (The onpload utility cannot disable the primary key constraint when child-table records refer to the load table.)
Perform the load in deluxe mode or remove the constraint in question.
You attempted to use express mode to load an HDR replicated table. Express mode does not support this condition.
Perform the load in deluxe mode.
The index objects are set to filtering mode during the load and re-enabled after the load. An error occurred when onpload attempted to set the indexes objects to filtering mode.
For more information, use the finderr or Informix Error Messages utility.
The ipldd09a.so shared library path is not set in the plconfig file.
If the default location is not correct, set the correct shared library path in the plconfig file using the HPL_DYNAMIC_LIB_PATH configuration parameter.
The onpload process could not find the required user-defined function in the shared library.
Restart the onpload load or unload with the correct shared library or function name in the pload job definition.
Cannot access the systable table to get dictionary information for the indicated table.
For more information, use the finderr or Informix Error Messages utility.
The pload utility cannot start because it failed to initialize the shared library-handling functionality.
Ensure that the computer has the proper resources and that the shared library has been built properly.
The data type for the load file is different than the data type for the database server. The code set does not exist in the $INFORMIXDIR/gls/cvx or %INFORMIXDIR%\gls\cvx directory where x is the version number of the cv subdirectory.
Check that the file exists. Check the file for permissions.
A memory-allocation error or database-integrity error occurred when onpload accessed the onpload database.
Use oncheck to check the maps, mapitem, mapoption, formats, and formatitem tables for consistency. If the tables are consistent, a referential integrity problem between the map and the format the map references might exist. If the problems persists, contact Technical Support.
The onpload utility could not load the shared library from the library_location path and failed with error_message.
For more information, use the finderr or Informix Error Messages utility. Correct the problem and reload the shared library.
No delimiter is found when onpload scans for an end-of-record delimiter in the load data.
Check that the end-of-record delimiter specification is correct, or that you have the correct data file. Note differences in the end-of-line characters between UNIX and Windows.
An internal error occurred when onpload attempted to open the load or unload file.
Note the circumstances and contact Technical Support.
The record references a filename that should contain a simple large object, but the file cannot be located.
Check that the simple-large-object file exists.
The target database cannot be opened.
For more information, use the finderr or Informix Error Messages utility.
The file cannot be opened.
See your errno.h file.
A TCP socket cannot be opened.
See your errno.h file.
The load table is fragmented by row ID. Express mode does not support this condition.
Perform the load in deluxe mode.
The table-row size exceeds page size. Express mode does not support this condition.
Perform the load in deluxe mode.
The load file cannot be accessed. This error might result from operating-system limitations; the onpload utility cannot load successfully from a file (on disk) that is longer than 2 gigabytes.
See your errno.h file.
Data loaded by onpload violates the object constraints specified for the table. The records that violate the object constraints have been placed in the violations table, and the reason code for each violation is listed in the diagnostics table.
Review the information in the violations and diagnostics tables.
The unload query does not contain a FROM clause.
Rewrite the query so that it contains a FROM clause.
The unload query does not contain a FROM clause.
Rewrite the query so that it contains a FROM clause.
The object constraints are disabled during the load and re-enabled after the load. An error occurred when onpload attempted to reset object constraints back to their original state.
For more information, use the finderr or Informix Error Messages utility.
An error occurred when onpload attempted to set up the violations table for the load table.
For more information, use the finderr or Informix Error Messages utility.
If a violations table exists on the load table, violations can be turned off during the load. An error occurred when onpload attempted to turn off violations detection.
For more information, use the finderr or Informix Error Messages utility.
The server determined that the query cannot be executed in parallel.
Remove non-parallel aspects of the query, such as non-parallel UDRs, or unload to a single device.
The unload file cannot be accessed.
See your errno.h file.
The code-set conversion caused the number of bytes in the BYTE and TEXT data to expand or contract when onpload unloaded the data into a fixed-format record. The onpload utility cannot update the BYTE and TEXT data tag in the record that specifies the length of the BYTE and TEXT data at this stage.
To unload this data, use a delimited format.
The onpload tried to convert the old database when onpload ran for the first time on the new database server. This conversion failed because of the error referenced in the error message.
For more information, use the finderr or Informix Error Messages utility. Resolve this before you rerun onpload.
Database conversion fails because the current user running onpload does not have sufficient privileges to convert the onpload database.
Run the onpload job as user informix once.
The custom function specified in a map option was not located in ipldd09a.so. The shared library extension is platform specific; for example, the .so extension is specific for Solaris and is probably different on other platforms.
For information on how to configure the custom function library, see Appendix E. Custom-Conversion Functions.
UNIX Only
The tape data is not blocked in a multiple of the record size, so that the last block of data contained bytes that are discarded. This situation occurs on devices with stream cartridges that allow writing to the device only in whole blocks.
If necessary, manually enter the discarded data.
A mapping option specifies an environment variable as the default value, but expansion of the environment variable requires more space than allocated to the column.
Use a shorter default value, or expand the length of the column.
A TCP socket cannot be accessed.
See your errno.h file.
An error occurred when onpload attempted to open the load or unload file.
Check that the file exists. Check the file for permissions.
An integrity problem exists in the onpload database. The format for the map does not exist, or a problem exists with the format or formatitem table.
For more information, use the finderr or Informix Error Messages utility.
The requested map for the load or unload does not exist, or a problem exists with the onpload database.
For more information, use the finderr or Informix Error Messages utility.
An access error occurred on the sysmaster database on the target server where onpload attempted to perform the load or unload job.
For more information, use the finderr or Informix Error Messages utility.
The target database table cannot be accessed.
For more information, use the finderr or Informix Error Messages utility.
AIO buffer size is less than required size.
Increase the specified buffer size in the PLCONFIG file.
A server error occurred when onpload closed the onpload or target database.
For more information, use the finderr or Informix Error Messages utility.
An error occurred when onpload closed the load or unload file.
See your errno.h file
A conversion error occurred when onpload attempted to convert the record data to the database column type.
For more information, use the finderr or Informix Error Messages utility. If the load map indicates that the data field is mapped to the correct column, check that the supplied data is valid.
Cannot access information about the load table.
Check the validity of the table in the target database.
The onpload utility is unable to use the autogenerated formats and maps to create entries in a table in the onpload database.
For more information, use the finderr or Informix Error Messages utility.
The unload query cannot be processed.
For more information, use the finderr or Informix Error Messages utility.
An internal error occurred in onpload. Probably the server went down.
Note the circumstances and contact Technical Support.
The onpload utility is unable to use the autogenerated formats and maps to create entries in a table in the onpload database.
For more information, use the finderr or Informix Error Messages utility.
An error occurred listening on a Socket connection.
See your errno.h file.
An error occurred listening on a TLI connection.
See /usr/include/tiuser.h (t_error_num).
UNIX Only
A conversion error occurred when onpload attempted to convert the column data to the record field type.
For more information, use the finderr or Informix Error Messages utility. Check the load map to verify that the column is mapped to the correct record field.
A conversion error occurred in a record.
No action is required.
An internal error occurred in onpload. Probably the server went down.
Note the circumstances and contact Technical Support.
An error occurred when onpload attempted to set up an insert cursor on the load table.
For more information, use the finderr or Informix Error Messages utility.
The unload query cannot be processed.
For more information, use the finderr or Informix Error Messages utility.
An internal error occurred when onpload attempted to access the onpload database.
For more information, use the finderr or Informix Error Messages utility.
The unload query cannot be processed.
For more information, use the finderr or Informix Error Messages utility.
This critical initialization error probably means that the operating kernel does not have enough shared memory or semaphores configured or that the allocated shared memory was removed.
On UNIX, increase shared memory or semaphores. On Windows, repeat the operation.
If the condition persists, contact Technical Support.
An error occurred reading a socket or TLI connection, based on the type of connection specified in ONCONFIG file.
See your errno.h file.
An access error occurred when onpload attempted to set the isolation level for an unload job.
For more information, use the finderr or Informix Error Messages utility.
This critical initialization error probably means that the operating system kernel does not have enough shared memory or semaphores configured, or that the allocated shared memory has been removed.
On UNIX, increase shared memory or semaphores. On Windows, repeat the operation.
If the condition persists, contact Technical Support.
An error occurred writing a socket or TLI connection, based on the type of connection specified in ONCONFIG file.
See your errno.h file.
Stream buffer size is less than required size.
Increase the specified buffer size in the PLCONFIG file.
All the shared-memory keys in the key range tried by onpload are currently allocated.
Wait until another onpload session finishes. If the problem persists, contact Technical Support.
An attempt to execute the PIPE type device in the device array failed.
Make sure the PIPE entry in the device array is a valid, executable program. Pipes are only supported on UNIX.
This is an internal error.
Cannot start the load session with the server.
Note the circumstances and contact Technical Support.
An internal error occurred in onpload. Probably the server went down.
Note the circumstances and contact Technical Support.
An internal communication problem exists between the server and onpload.
Note the circumstances and contact Technical Support.
The device array specifies that the file is a disk file, but it is not.
Change the type of the file in the device-array definition, or make sure that the file is a disk file.
An internal error occurred, or a user sent an interrupt to onpload.
If a user did not generate this interrupt, contact Technical Support.
This critical initialization error probably means that the UNIX kernel does not have enough shared memory or semaphores configured.
Increase shared memory or semaphores. If the condition persists, contact Technical Support.
An internal error occurred in onpload. The most likely cause is a lack of shared memory.
Note the circumstances and contact Technical Support.
A critical internal error occurred.
Note the circumstances and contact Technical Support.
A critical internal error occurred.
Note the circumstances and contact Technical Support.
This critical initialization error probably means that the operating system kernel does not have enough shared memory or semaphores configured.
On UNIX, increase shared memory or semaphores. On Windows, repeat the operation.
If the condition persists, contact Technical Support.
The count of rows being loaded became corrupt. This message can appear if a deluxe load job aborts with an error.
Contact IBM Technical Support.
The data being loaded or unloaded has invalid character data.
Make sure that you specified the correct data type on the format definition.
The simple large object or extended type field being loaded was classed as HEXASCII, but the data contains a non-HEXASCII character.
Fix the data.
The simple large object data field being loaded was classed as HEXASCII, but the data contains a non-HEXASCII character.
Fix the data.
Incorrect project name was specified for onpload.
Check the given project name and restart onpload.
The count of rows being loaded became corrupt. This message can appear if a deluxe load job aborts with an error.
Contact IBM Technical Support.
The command line specified an invalid session ID for the job to run. An entry for the entered session ID must exist in the session table of the onpload database in order to run the job.
Make sure the session ID on the command line matches the correct session ID in the session table.
Incorrect tape was mounted.
Mount the correct tape.
Incorrect map was specified to onpload. You must use a load map for a load job and an unload map for an unload job.
Verify that you are using the correct map type.
An internal error occurred in onpload.
Note the circumstances and contact Technical Support.
This critical initialization error probably means that the operating system kernel does not have enough shared memory or semaphores configured.
On UNIX, increase shared memory or semaphores. On Windows, repeat the operation.
If the condition persists, contact Technical Support.
This critical initialization error probably means that the operating system kernel does not have enough shared memory or semaphores configured.
On UNIX, increase shared memory or semaphores. On Windows, repeat the operation.
If the condition persists, contact Technical Support.
This critical initialization error probably means that the UNIX kernel does not have enough shared memory or semaphores configured.
Increase shared memory or semaphores. If the condition persists, contact Technical Support.
You cannot load the indicated table because the DBA has not granted permission for you to do so.
Make sure that you have insert permissions on the table.
The record format specifies a simple large object or extended type, but no column from the query is mapped to the record field.
Map a column to the field, or remove the field from the record format.
User tried to run onpload on a host computer other than the one that has the target database.
Run onpload on the host specified in the error message.
Either an internal error occurred or a user sent onpload a termination signal.
If the signal is not SIGKILL, SIGTERM, or SIGQUIT, note the circumstances and contact Technical Support.
UNIX Only
The device array specifies that the file is a pipe (executable program) file, but it is not.
Change the type of the file in the device-array definition, or make sure that the file is an executable disk file. Pipes are only supported on UNIX.
The onpload utility requires that the special columns (simple large column and user-defined types) appear at the end of the select list. The onpload utility will reorder simple SELECT statements but is unable to re-order the select list because of expressions, aggregates, or both.
Reorder select columns manually as explained in error message. Alternatively, you can remove aggregates and expressions from the select list by selecting the columns into a temporary table and then unloading them from that table.
The unload query is extracting a simple large object or extended type column that is not mapped to the record field.
Modify the unload query so that it does not reference the simple large object or extended type column, or map it to a field in the record format.
The unload query does not a contain a SELECT statement.
Modify the query so that it contains a SELECT statement.
The record size exceeds the size of the onpload buffers (AIOBUFSIZE). This error can occur when a delimited record contains simple-large-objects or extended types, and a format specification for a field is missing, which causes a simple large object or an extended type to be treated as a regular field.
Increase the size of AIOBUFSIZE for this record, or check that the format specification for the field matches the input file.
An onpload/server interface error occurred.
Note the circumstances and contact Technical Support.
An internal error occurred when onpload accessed the onpload database.
For more information, use the finderr or Informix Error Messages utility.
The SQLBYTE simple large object or extended type data could not be converted to HEXASCII, or the SQLTEXT simple large object or extended type has invalid character data (characters not in the code set).
Remove the invalid characters from the input data.
A start record was specified for the load, but fewer records are in the input file than the indicated number of records to skip.
Specify the start-record number again.
The shared library was loaded successfully.
Check the path to verify that the correct library is being used. If the path is incorrect, edit the HPL_DYNAMIC_LIB_PATH configuration parameter in the plconfig file to supply the correct path.
After an express-mode load, a level-0 archive is needed to make the table available for update.
Perform a level-0 archive.
You attempted to use express mode to load a table that contains data for a simple large object. Express mode does not support this condition.
Perform the load in deluxe mode.
You attempted to use express mode to load a table that contains simple large object or extended type data. Express mode does not support this condition.
Perform the load in deluxe mode.
You attempted a no-conversion load on a table with simple large object or extended type columns. This action is not allowed.
Remove the no-conversion specification, and run the job again.
A tape header size is too large to fit into a memory buffer.
Increase AIOBUFSIZE in PLCONFIG to at least the value specified for tape I/O.
The device array specifies that the file is a tape device, but it is not.
Change the type of the file in the device-array definition, or make sure that the file is a tape device.
The specified column has a NOT NULL constraint, but in the definition of the load map, no field is mapped to the column.
Correct the load map or drop the NOT NULL constraint.
The GLS locale specified in CLIENT_LOCALE or DB_LOCALE cannot be loaded, or if these variables are not set, the GLS file cannot be loaded.
Check the $INFORMIXDIR/gls or %INFORMIXDIR%\gls directory to ensure that the locale files are present.
A SELECT statement contains a column name that might not be unique.
Modify the SELECT statement to contain a name for each column expression. For example:
SELECT Max(I) Mcol FROM table x
The onpload command-line option -Z enabled write to and read from the tape until the end of the device.
No action is required.
The write to tape is failing on a tape device due to lack of space.
Increase the space on the tape device or replace the device and restart the load or unload job.