Neoview Database Administrator's Guide (R2.2)

Rejected Data Records
If a data-load task encounters invalid data, it writes the data to a .bad file. There are two sources
of rejected records:
• The gelserver data-load process’ input validation
• The target system’s write process, where records can be rejected by SQL
Records that fail input validation are written to a file named
task-name.task-instance-name.input.bad located in the log directory specified at the
time of installation (typically /opt/tandem/genus/gel/log).
Records that are rejected by SQL are written to a file named task-name.task-instance
name.sql.bad located in the same directory. For each record rejected by SQL on the Neoview
platform an entry will be reported in the task instance log in this format:
[21:19:11] WRITER_19> WARNING : WRT_19 Record rejected by SQL. (SQLCODE
-8102, Bad Rec #853).
SQLCODE is the error code returned by SQL and the Bad Rec # is the record number in the SQL
.bad file on the Loader system.
For the example above, any records rejected by SQL would be stored in a file named
LOAD_TASK1.LOAD_TASK1_RUN1.sql.bad and any records rejected by the Neoview gelserver
process would be stored in a file named LOAD_TASK1.LOAD_TASK1_RUN1.input.bad.
You should periodically remove old .bad files because they can become full. They will be
recreated the next time you start a load task.
Example 8-1 (page 95) shows a task instance log file for a task that completed with warnings.
JMS Log
The JMS log file records information for tasks where the input is from one or more JMS queues.
The name of the JMS log file on the Linux system is:
task-name.task-instance-name.jms.log.
Recovery
The Recovery feature allows you to restart a failed or stopped task and complete it as if it had
run without pause. When the Neoview Loader runs a failed or stopped task instance in recovery
mode, it continues to commit data from the point of the last successful commit.
If you stop a task instance using the STOP_TASK request, or if the task instance terminates
unexpectedly, you can rerun the task in recovery mode, assuming that the task was configured
with recovery enabled.
You can recover a failed task instance if the following conditions are met:
• The task was configured with recovery enabled.
• The input type for the load task was set to FILE. Recovery is not supported for named pipes
or JMS queues (input types PIPE or QUEUE.)
Configuring A Recovery-Enabled Task
There are two ways to configure a task to use the recovery feature:
• By default, the system is installed with recovery enabled. You can check this by looking at
the gelserver.config.xml file. In this case, all tasks will run with recovery enabled unless you
set recoveryFlag (-rf) to N.
• Set the recovery flag, -rf, to Y when you configure a load task.
This is an example of a task configuration request with recovery enabled:
gcmd -rt CONFIG_TASK_LOAD \
-tk TASK_1 -rf Y \
116 Using the Neoview Loader