Neoview Messages Manual (R2.2)

Recovery Contact the GMCSC for analysis of accompanying error and warning messages.
Failed to initialize partition driver(s).
Cause Various reasons can cause failure of the initialization of partition drivers. Previous
errors in the log provide details about the error.
Recovery Contact the GMCSC for analysis of accompanying error and warning messages.
Failed to delete recovery file.
Cause The gelserver failed to delete the recovery file. Possible reasons are:
• The user deleted the file manually between the time the gelserver detected the presence
of the file and attempted to delete it.
• The user running the load task does not have permission to delete the recovery file.
Recovery Check if the recovery file exists and check the file permissions on the file. The
recovery file has the name .task-name.task-instance-name.rcvy and is in the directory
/opt/tandem/genus/gel/log/load. This file is a hidden file, and the leading dot must
be supplied when checking the file permissions.
Failed to create recovery file.
Cause The gelserver failed to create the recovery file. Possibly the user does not have
permission to create files in the log directory for load tasks.
Recovery Contact the GMCSC for analysis of accompanying error and warning messages.
Input file provided is empty. No processing required.
Cause The only input file provided by the user for the data load is empty, so the gelserver
gracefully stops execution.
Recovery This is an informational message only. No corrective action is needed.
Starting Threads.
Cause The gelserver is starting the worker threads.
Recovery This is an informational message only. No corrective action is needed.
Threads Started.
Cause The gelserver has successfully started the worker threads.
Recovery This is an informational message only. No corrective action is needed.
Threads completed with success.
Effect The gelserver worker threads have successfully completed.
Recovery This is an informational message only. No corrective action is needed.
Execution completed with warnings. Bad records rejected on both source
and target.
Cause The task completed with warnings—records were rejected at the source when the
data was being read from either a file, name pipe, or JMS queue and also at the target where
the data was being loaded.
Recovery This is an informational message only. No corrective action is needed. Details of
the rejected records can be found in the Linux task instance log. The source rejected records
are in file with a name in this format:
task_name.task_instance_name.input.bad
Also, the records rejected by SQL are in a file with a name in this format:
task_name.task_instance_name.sql.bad
376 Neoview Loader