Neoview Messages Manual (R2.2)

error is the value of the errno variable returned by TCP/IP.
Cause Failed to receive reply from a gelserver on the Neoview platform. Possibly:
• The gelserver process on the Neoview platform terminated before sending the reply. In
this event, check the gelserver Neoview task instance log.
• Problems occurred in the network between the Neoview and Linux systems.
Recovery Contact the GMCSC for analysis of accompanying error and warning messages.
Control Message could not be sent to the loader.
Cause Failed to send a message to the gelserver on the Neoview platform. Possibly:
• The gelserver process on the Neoview platform terminated.
• Problems occurred in the network between the Neoview platform and Linux system.
Recovery Contact the GMCSC for analysis of accompanying error and warning messages.
ODBC/MX FastPath has been enabled.
Cause The gelserver is configured to use the FastPath interface for the HP ODBC driver.
Recovery This is an informational message only. No corrective action is needed.
Compression failed
Cause The server was unable to perform the requested data compression.
Recovery Retry the operation. If the problem persists, contact the GMCSC for analysis of
accompanying error and warning messages.
Error resetting compression routines.
Cause The server was unable to perform the resetting function for the compression routines.
Recovery This is an internal software error. Contact the GMCSC for analysis of accompanying
error and warning messages.
Record rejected by SQL. (SQLCODE number, Bad Record number).
SQLCODE number
is the value of the SQLCODE error number that occurred during
the data loading operation into the SQL object.
Bad Record number
is the record number in the “.sql” bad file.
Cause The insert or update failed with the provided SQLCODE error information.
Recovery Check the value of the SQLCODE error number. To find the cause of failure for
this particular SQLCODE, see Chapter 22 (page 397). Correct the problem and retry the task.
Record rejected by SQL. (Bad Rec number).
Bad Rec number
is the record number in the “.sql” bad file.
Cause If the operation attempted is UPDATE, the record does not exist in the target table.
For all other cases, the load for this record failed, and no error number was provided by SQL.
Recovery In the case of an UPDATE operation, the record to be updated did not exist, so
the error resulted. No corrective action is required. However, if the operation attempted was
other than UPDATE, contact the GMCSC for analysis of accompanying errors and warnings.
Status array acknowledgement could not be sent to the loader.
Cause The gelserver was unable to send a status array acknowledgement message to the
gelserver on the Neoview platform, indicating a TCP/IP problem. Previous errors in the log
provide details about the error.
Recovery Contact the GMCSC for analysis of accompanying errors and warnings.
Reflexive update cannot be applied to non-numeric field (field-name).
384 Neoview Loader