Home | Previous Page | Next Page   Appendix G. HPL Log-File and Pop-Up Messages >

Log-File Messages

Blob conversion error occurred on record record_num.
Explanation:

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).

User Response:

Remove the invalid characters from the input data.

Cannot access database table table_name: SQL error error_num.
Explanation:

The target database table cannot be accessed.

User Response:

For more information, use the finderr or Informix Error Messages utility.

Cannot allocate shared memory.
Explanation:

A memory allocation error occurred. Probably the system is out of virtual shared memory.

User Response:

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.

Cannot allocate TLI memory for operating_system structure.
Explanation:

System memory cannot be allocated for communications. This situation should only happen if all system resources are consumed.

User Response:

Note the circumstances and contact Technical Support.

Cannot bind socket connection: errno=operating-system_ error_num.
Explanation:

A TCP socket cannot be opened.

User Response:

See your errno.h file.

Cannot bind TLI connection: t_errno=t_error_num.
Explanation:

An error occurred when onpload attempted to open a TLI connection.

User Response:

Check that TLI services are installed on the operating system. See your tiuser.h file.

Platform:

UNIX Only

Cannot configure driver driver_name.
Explanation:

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.

User Response:

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.

Platform:

UNIX Only

Cannot connect to message server: Socket error=UNIX_error_num.
Explanation:

This message is generated by ipload when it cannot connect to the onpload socket service.

User Response:

See /usr/include/errno.h.

Platform:

UNIX Only

Cannot connect to message server: TLI error=t_error_num, TLI event=t_event_num, errno=error_num.
Explanation:

An error occurred when onpload attempted to open a TLI connection.

User Response:

Check that TLI services are installed on the operating system. See /usr/include/tiuser.h (t_error_num).

Platform:

UNIX Only

Cannot connect to server_name: SQL error error_num, ISAM error error_num.
Explanation:

The target database server cannot be opened.

User Response:

For more information, use the finderr or Informix Error Messages utility.

Cannot connect worker to server data stream.
Explanation:

A possible permissions problem exists for onpload or oninit.

User Response:

Note the circumstances and contact Technical Support.

Cannot disable table_name object constraints: SQL error error_num, ISAM error error_num.
Explanation:

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.

User Response:

For more information, use the finderr or Informix Error Messages utility.

Cannot disable primary-key constraint. Child-table references exist.
Explanation:

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.)

User Response:

Perform the load in deluxe mode or remove the constraint in question.

Cannot express load to logged table on HDR server server_name.
Explanation:

You attempted to use express mode to load an HDR replicated table. Express mode does not support this condition.

User Response:

Perform the load in deluxe mode.

Cannot filter indexes for table table_name: SQL error error_num, ISAM error error_num.
Explanation:

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.

User Response:

For more information, use the finderr or Informix Error Messages utility.

Cannot find the shared library path in the plconfig file.
Using the shared library from the default location library_location.
Explanation:

The ipldd09a.so shared library path is not set in the plconfig file.

User Response:

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.

Cannot find the user-defined function user_func_name in the shared library: error error_num.
Explanation:

The onpload process could not find the required user-defined function in the shared library.

User Response:

Restart the onpload load or unload with the correct shared library or function name in the pload job definition.

Cannot get systable info for table table_name: SQL error error_num, ISAM error error_num.
Explanation:

Cannot access the systable table to get dictionary information for the indicated table.

User Response:

For more information, use the finderr or Informix Error Messages utility.

Cannot initialize shared library handling.
Explanation:

The pload utility cannot start because it failed to initialize the shared library-handling functionality.

User Response:

Ensure that the computer has the proper resources and that the shared library has been built properly.

Cannot load code-set conversion file from -> file_name to -> file_name.
Explanation:

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.

User Response:

Check that the file exists. Check the file for permissions.

Cannot load mapping definitions.
Explanation:

A memory-allocation error or database-integrity error occurred when onpload accessed the onpload database.

User Response:

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.

Cannot load the shared library library_location.
Shared library load failed with error message error_message.
Explanation:

The onpload utility could not load the shared library from the library_location path and failed with error_message.

User Response:

For more information, use the finderr or Informix Error Messages utility. Correct the problem and reload the shared library.

Cannot locate delimiter in data file.
Explanation:

No delimiter is found when onpload scans for an end-of-record delimiter in the load data.

User Response:

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.

Cannot open.
Explanation:

An internal error occurred when onpload attempted to open the load or unload file.

User Response:

Note the circumstances and contact Technical Support.

Cannot open simple large object file:file_name, simple large object not loaded.
Explanation:

The record references a filename that should contain a simple large object, but the file cannot be located.

User Response:

Check that the simple-large-object file exists.

Cannot open database database_name: SQL error error_num, ISAM error error_num.
Explanation:

The target database cannot be opened.

User Response:

For more information, use the finderr or Informix Error Messages utility.

Cannot open file file_name: error number operating-system_ error_num.
Explanation:

The file cannot be opened.

User Response:

See your errno.h file.

Cannot open TCP connection for server_name: errno operating-system_error_num.
Explanation:

A TCP socket cannot be opened.

User Response:

See your errno.h file.

Cannot perform express mode load on table with pseudo rowid.
Explanation:

The load table is fragmented by row ID. Express mode does not support this condition.

User Response:

Perform the load in deluxe mode.

Cannot perform express-mode load with rowsize=row_length > page_size.
Explanation:

The table-row size exceeds page size. Express mode does not support this condition.

User Response:

Perform the load in deluxe mode.

Cannot read file file_name: AIO error code operating-system_ error_num.
Explanation:

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.

User Response:

See your errno.h file.

Cannot re-enable all objects: num_violations violations detected. Check for violations in violations table table_name and diagnostics table table_name.
Explanation:

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.

User Response:

Review the information in the violations and diagnostics tables.

Cannot re-order query statement to align simple large objects or Ext Types.
Explanation:

The unload query does not contain a FROM clause.

User Response:

Rewrite the query so that it contains a FROM clause.

Cannot re-order query statement to align blobs.
Explanation:

The unload query does not contain a FROM clause.

User Response:

Rewrite the query so that it contains a FROM clause.

Cannot set mode of table_name objects from current_mode to final_mode mode: SQL error error_num, ISAM error error_num.
Explanation:

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.

User Response:

For more information, use the finderr or Informix Error Messages utility.

Cannot start violations table for table_name: SQL error error_num, ISAM error error_num.
Explanation:

An error occurred when onpload attempted to set up the violations table for the load table.

User Response:

For more information, use the finderr or Informix Error Messages utility.

Cannot stop violations table for table_name: SQL error error_num, ISAM error error_num.
Explanation:

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.

User Response:

For more information, use the finderr or Informix Error Messages utility.

Cannot unload to multiple devices when the given query cannot be executed in parallel.
Explanation:

The server determined that the query cannot be executed in parallel.

User Response:

Remove non-parallel aspects of the query, such as non-parallel UDRs, or unload to a single device.

Cannot write file file_name: AIO error code operating-system_ error_num.
Explanation:

The unload file cannot be accessed.

User Response:

See your errno.h file.

Code-set conversion overflow.
Explanation:

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.

User Response:

To unload this data, use a delimited format.

Conversion of onpload database failed due to error error_num.
Explanation:

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.

User Response:

For more information, use the finderr or Informix Error Messages utility. Resolve this before you rerun onpload.

Conversion of onpload database failed due to error error_num, run as user informix.
Explanation:

Database conversion fails because the current user running onpload does not have sufficient privileges to convert the onpload database.

User Response:

Run the onpload job as user informix once.

Custom conversion function function_name not found in shared library.
Explanation:

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.

User Response:

For information on how to configure the custom function library, see Appendix E. Custom-Conversion Functions.

Platform:

UNIX Only

Discarded num_bytes null bytes from end of tape device device_name.
Explanation:

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.

User Response:

If necessary, manually enter the discarded data.

Environment variable variable_name expansion would overflow string.
Explanation:

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.

User Response:

Use a shorter default value, or expand the length of the column.

Error accepting socket connection: errno=operating-system_ error_num.
Explanation:

A TCP socket cannot be accessed.

User Response:

See your errno.h file.

Error accessing file_name.
Explanation:

An error occurred when onpload attempted to open the load or unload file.

User Response:

Check that the file exists. Check the file for permissions.

Error accessing format: SQL error error_num, ISAM error error_num.
Explanation:

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.

User Response:

For more information, use the finderr or Informix Error Messages utility.

Error accessing map map_name: SQL error error_num, ISAMerror error_num.
Explanation:

The requested map for the load or unload does not exist, or a problem exists with the onpload database.

User Response:

For more information, use the finderr or Informix Error Messages utility.

Error accessing sysmaster: SQL error error_num, ISAMerror error_num.
Explanation:

An access error occurred on the sysmaster database on the target server where onpload attempted to perform the load or unload job.

User Response:

For more information, use the finderr or Informix Error Messages utility.

Error accessing table table_name: SQL error error_num, ISAM error error_num.
Explanation:

The target database table cannot be accessed.

User Response:

For more information, use the finderr or Informix Error Messages utility.

Error:AIO buffer size buffer_size is less than required minimum size size.
Explanation:

AIO buffer size is less than required size.

User Response:

Increase the specified buffer size in the PLCONFIG file.

Error error_num closing current database.
Explanation:

A server error occurred when onpload closed the onpload or target database.

User Response:

For more information, use the finderr or Informix Error Messages utility.

Error operating-system_error_num closing file file_name.
Explanation:

An error occurred when onpload closed the load or unload file.

User Response:

See your errno.h file

Error error_num converting record field field_name to column column_name.
Explanation:

A conversion error occurred when onpload attempted to convert the record data to the database column type.

User Response:

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.

Error declaring cursor: could not get table info.
Explanation:

Cannot access information about the load table.

User Response:

Check the validity of the table in the target database.

Error declaring cursor: SQL error error_num, ISAM error error_num.
Explanation:

The onpload utility is unable to use the autogenerated formats and maps to create entries in a table in the onpload database.

User Response:

For more information, use the finderr or Informix Error Messages utility.

Error describing unload query query_name: SQL error error_num, ISAM error error_num.
Explanation:

The unload query cannot be processed.

User Response:

For more information, use the finderr or Informix Error Messages utility.

Error error_num initializing backend connection.
Explanation:

An internal error occurred in onpload. Probably the server went down.

User Response:

Note the circumstances and contact Technical Support.

Error inserting into table table_name: SQL error error_num, ISAM error error_num.
Explanation:

The onpload utility is unable to use the autogenerated formats and maps to create entries in a table in the onpload database.

User Response:

For more information, use the finderr or Informix Error Messages utility.

Error listening for socket connection: t_errno=t_error_num errno=operating-system_error_num.
Explanation:

An error occurred listening on a Socket connection.

User Response:

See your errno.h file.

Error listening for TLI connection: t_errno=t_error_num errno=UNIX_error_num.
Explanation:

An error occurred listening on a TLI connection.

User Response:

See /usr/include/tiuser.h (t_error_num).

Platform:

UNIX Only

Error error_num on record record_num converting column column_name to record field field_name.
Explanation:

A conversion error occurred when onpload attempted to convert the column data to the record field type.

User Response:

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.

Error occurred on record %d reading pipe %s.
Explanation:

A conversion error occurred in a record.

User Response:

No action is required.

Error on close of server load session: SQL error error_num, ISAM error error_num.
Explanation:

An internal error occurred in onpload. Probably the server went down.

User Response:

Note the circumstances and contact Technical Support.

Error opening cursor: SQL Error error_num.
Explanation:

An error occurred when onpload attempted to set up an insert cursor on the load table.

User Response:

For more information, use the finderr or Informix Error Messages utility.

Error preparing query: SQL error error_num.
Explanation:

The unload query cannot be processed.

User Response:

For more information, use the finderr or Informix Error Messages utility.

Error preparing statement statement_name: SQL error error_num, ISAM error error_num.
Explanation:

An internal error occurred when onpload attempted to access the onpload database.

User Response:

For more information, use the finderr or Informix Error Messages utility.

Error preparing unload query query_name: SQL error error_num, ISAM error error_num.
Explanation:

The unload query cannot be processed.

User Response:

For more information, use the finderr or Informix Error Messages utility.

Error error_num reading message queue.
Explanation:

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.

User Response:

On UNIX, increase shared memory or semaphores. On Windows, repeat the operation.

If the condition persists, contact Technical Support.

Error operating-system_error_num reading TLI/socket connection.
Explanation:

An error occurred reading a socket or TLI connection, based on the type of connection specified in ONCONFIG file.

User Response:

See your errno.h file.

Error error_num setting isolation level.
Explanation:

An access error occurred when onpload attempted to set the isolation level for an unload job.

User Response:

For more information, use the finderr or Informix Error Messages utility.

Error error_num writing message on message queue.
Explanation:

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.

User Response:

On UNIX, increase shared memory or semaphores. On Windows, repeat the operation.

If the condition persists, contact Technical Support.

Error operating-system_error_num writing TLI/socket connection.
Explanation:

An error occurred writing a socket or TLI connection, based on the type of connection specified in ONCONFIG file.

User Response:

See your errno.h file.

Error:Stream buffer size buffer_size is less than required minimum size size.
Explanation:

Stream buffer size is less than required size.

User Response:

Increase the specified buffer size in the PLCONFIG file.

Exhausted all attempts to allocate shared-memory key.
Explanation:

All the shared-memory keys in the key range tried by onpload are currently allocated.

User Response:

Wait until another onpload session finishes. If the problem persists, contact Technical Support.

Fatal error: cannot execute pipe_name.
Explanation:

An attempt to execute the PIPE type device in the device array failed.

User Response:

Make sure the PIPE entry in the device array is a valid, executable program. Pipes are only supported on UNIX.

Fatal error - cannot load X resource
Explanation:

This is an internal error.

Fatal error creating server load session: error error_num.
Explanation:

Cannot start the load session with the server.

User Response:

Note the circumstances and contact Technical Support.

Fatal error getting stream buffer from server.
Explanation:

An internal error occurred in onpload. Probably the server went down.

User Response:

Note the circumstances and contact Technical Support.

Fatal error in server row processing: SQL error error_num, ISAM error error_num.
Explanation:

An internal communication problem exists between the server and onpload.

User Response:

Note the circumstances and contact Technical Support.

File type device file file_name is not a regular (disk) file.
Explanation:

The device array specifies that the file is a disk file, but it is not.

User Response:

Change the type of the file in the device-array definition, or make sure that the file is a disk file.

Got Interrupt: Shutting down.
Explanation:

An internal error occurred, or a user sent an interrupt to onpload.

User Response:

If a user did not generate this interrupt, contact Technical Support.

Internal error: cannot initialize AIO library.
Explanation:

This critical initialization error probably means that the UNIX kernel does not have enough shared memory or semaphores configured.

User Response:

Increase shared memory or semaphores. If the condition persists, contact Technical Support.

Internal error: cannot send message.
Explanation:

An internal error occurred in onpload. The most likely cause is a lack of shared memory.

User Response:

Note the circumstances and contact Technical Support.

Internal error: error_num. Contact Tech Support.
Explanation:

A critical internal error occurred.

User Response:

Note the circumstances and contact Technical Support.

Internal error: invalid message type error_num.
Explanation:

A critical internal error occurred.

User Response:

Note the circumstances and contact Technical Support.

Internal error error_num reading queue.
Explanation:

This critical initialization error probably means that the operating system kernel does not have enough shared memory or semaphores configured.

User Response:

On UNIX, increase shared memory or semaphores. On Windows, repeat the operation.

If the condition persists, contact Technical Support.

Invalid count detected, may be due to abnormal BE shutdown.
Explanation:

The count of rows being loaded became corrupt. This message can appear if a deluxe load job aborts with an error.

User Response:

Contact IBM Technical Support.

Invalid code-set character: cannot convert.
Explanation:

The data being loaded or unloaded has invalid character data.

User Response:

Make sure that you specified the correct data type on the format definition.

Invalid HEXASCII simple large object or extended type representation on record record_num.
Explanation:

The simple large object or extended type field being loaded was classed as HEXASCII, but the data contains a non-HEXASCII character.

User Response:

Fix the data.

Invalid HEXASCII simple large object representation in fieldname, record record_num.
Explanation:

The simple large object data field being loaded was classed as HEXASCII, but the data contains a non-HEXASCII character.

User Response:

Fix the data.

Invalid project name project_name entered.
Explanation:

Incorrect project name was specified for onpload.

User Response:

Check the given project name and restart onpload.

Invalid reject count detected, may be due to abnormal BE shutdown. Using last known reject count and proceeding.
Explanation:

The count of rows being loaded became corrupt. This message can appear if a deluxe load job aborts with an error.

User Response:

Contact IBM Technical Support.

Invalid session ID id_number.
Explanation:

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.

User Response:

Make sure the session ID on the command line matches the correct session ID in the session table.

Invalid Tape Header Expecting -> tape_name.
Explanation:

Incorrect tape was mounted.

User Response:

Mount the correct tape.

Map map_name type is not a load map.
Explanation:

Incorrect map was specified to onpload. You must use a load map for a load job and an unload map for an unload job.

User Response:

Verify that you are using the correct map type.

Method not supported by current driver.
Explanation:

An internal error occurred in onpload.

User Response:

Note the circumstances and contact Technical Support.

MT cannot bind to vpid.
Explanation:

This critical initialization error probably means that the operating system kernel does not have enough shared memory or semaphores configured.

User Response:

On UNIX, increase shared memory or semaphores. On Windows, repeat the operation.

If the condition persists, contact Technical Support.

MT internal failure.
Explanation:

This critical initialization error probably means that the operating system kernel does not have enough shared memory or semaphores configured.

User Response:

On UNIX, increase shared memory or semaphores. On Windows, repeat the operation.

If the condition persists, contact Technical Support.

MT failure putting CPU online.
Explanation:

This critical initialization error probably means that the UNIX kernel does not have enough shared memory or semaphores configured.

User Response:

Increase shared memory or semaphores. If the condition persists, contact Technical Support.

No insert permission on table table_name.
Explanation:

You cannot load the indicated table because the DBA has not granted permission for you to do so.

User Response:

Make sure that you have insert permissions on the table.

No mapping to simple large object field field_name.
Explanation:

The record format specifies a simple large object or extended type, but no column from the query is mapped to the record field.

User Response:

Map a column to the field, or remove the field from the record format.

onpload must run on the host host_name that contains the target database.
Explanation:

User tried to run onpload on a host computer other than the one that has the target database.

User Response:

Run onpload on the host specified in the error message.

onpload terminated by signal.
Explanation:

Either an internal error occurred or a user sent onpload a termination signal.

User Response:

If the signal is not SIGKILL, SIGTERM, or SIGQUIT, note the circumstances and contact Technical Support.

Platform:

UNIX Only

Pipe type device file file_name is not a regular file.
Explanation:

The device array specifies that the file is a pipe (executable program) file, but it is not.

User Response:

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.

Pload cannot reorder queries having expressions/aggregates and blobs/udts in the same select list. Please reorder the select list in the query in the following order:
1. non-blob non-udt columns
2. inrow udts in the case of fixed format
3. other blob/udt columns
Explanation:

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.

User Response:

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.

Query contains unmapped simple large object column column_name: cannot proceed.
Explanation:

The unload query is extracting a simple large object or extended type column that is not mapped to the record field.

User Response:

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.

Query for unload is not a select query.
Explanation:

The unload query does not a contain a SELECT statement.

User Response:

Modify the query so that it contains a SELECT statement.

Record is too long to process: recnum record_num, length record_length, bufsize buffer_size.
Explanation:

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.

User Response:

Increase the size of AIOBUFSIZE for this record, or check that the format specification for the field matches the input file.

Server interface error; expected num_input but got num_received instead.
Explanation:

An onpload/server interface error occurred.

User Response:

Note the circumstances and contact Technical Support.

SQL error error_num executing statement statement_name.
Explanation:

An internal error occurred when onpload accessed the onpload database.

User Response:

For more information, use the finderr or Informix Error Messages utility.

Simple large object or extended type conversion error occurred on record record_num.
Explanation:

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).

User Response:

Remove the invalid characters from the input data.

Start record record_num is greater than number of records total_num read from input file_name.
Explanation:

A start record was specified for the load, but fewer records are in the input file than the indicated number of records to skip.

User Response:

Specify the start-record number again.

Successfully loaded the shared library library_location.
Explanation:

The shared library was loaded successfully.

User Response:

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.

Table table_name will be read-only until level-0 archive.
Explanation:

After an express-mode load, a level-0 archive is needed to make the table available for update.

User Response:

Perform a level-0 archive.

Tables with BLOBS cannot be loaded in High Performance Mode.
Explanation:

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.

User Response:

Perform the load in deluxe mode.

Tables with BLOBS or extended types cannot be loaded in Express mode.
Explanation:

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.

User Response:

Perform the load in deluxe mode.

Tables with simple large objects or extended types cannot be processed with no conversion (-fn).
Explanation:

You attempted a no-conversion load on a table with simple large object or extended type columns. This action is not allowed.

User Response:

Remove the no-conversion specification, and run the job again.

Tape header is larger than I/O buffer: tape header_length, I/O buffer_size.
Explanation:

A tape header size is too large to fit into a memory buffer.

User Response:

Increase AIOBUFSIZE in PLCONFIG to at least the value specified for tape I/O.

Tape type device file file_name is not a character-special or block-special file.
Explanation:

The device array specifies that the file is a tape device, but it is not.

User Response:

Change the type of the file in the device-array definition, or make sure that the file is a tape device.

There is no mapping to column column_name, which cannot accept null values.
Explanation:

The specified column has a NOT NULL constraint, but in the definition of the load map, no field is mapped to the column.

User Response:

Correct the load map or drop the NOT NULL constraint.

Unable to load locale categories for locale locale_name: error error_num.
Explanation:

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.

User Response:

Check the $INFORMIXDIR/gls or %INFORMIXDIR%\gls directory to ensure that the locale files are present.

Unload query select item for the query_item expression needs to be assigned a name.
Explanation:

A SELECT statement contains a column name that might not be unique.

User Response:

Modify the SELECT statement to contain a name for each column expression. For example:

SELECT Max(I) Mcol FROM table x

Write/read to/from tape until end of device.
Explanation:

The onpload command-line option -Z enabled write to and read from the tape until the end of the device.

User Response:

No action is required.

Write to device (tape or pipe) device_name failed; no space left on device. AIO error error_num.
Explanation:

The write to tape is failing on a tape device due to lack of space.

User Response:

Increase the space on the tape device or replace the device and restart the load or unload job.

Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]