Neoview Database Administrator's Guide (R2.2)

-gs server1 -tn NEO-CMSERVER \
-it FILE \
-ii /opt/testdata/WISC-INSERT \
-ot TABLE -oi CAT.SCH.WISC \
-un user1 -pw mypassword \
-of N
Running a Recovery-Enabled Task
To start a recovery-enabled task, use the START_TASK request, the same request you use to start
a task with recovery disabled.
This is an example of a task start request with recovery enabled:
gcmd -rt START_TASK -tk TASK_1 -un user1 -pw mypassword
Stopping a Recovery Enabled Task
To stop a recovery-enabled task, use the STOP_TASK request, the same request you use to start
a task with recovery disabled.
This is an example of task stop request with recovery enabled:
gcmd -rt STOP_TASK -tk TASK_1 -un user1 -pw mypassword
Recovering a Recovery-Enabled Task
You can now recover the task, using one of these scenarios:
• The task instance run was interrupted, that is, the task was stopped using the STOP_TASK
request.
• The task instance run failed with an error.
In both of these cases you can choose to recover the failed task by resubmitting the original start
task request. With recovery enabled, the gelserver data-load process obtains recovery information;
that is, the point of the last the successful commit from the Neoview platform. It then reads and
loads data from that point onwards.
Recovery Files
The .rcvy file on the Linux Loader platform stores this information:
• Linux Loader gelserver Reader thread number
• Offset value of the last bad record (if any) read from the input file corresponding to that
reader thread
This information is used by the gelserver data-load process to avoid writing duplicate records,
if possible, to the .input.bad file during a recovery run. This file contains data in binary format.
This file is stored in a file named .task-name.task-identifier.rcvy in the load directory
on the Loader system. Note that the file name starts with a dot ('.'). To see this file, you must use
ls -all when listing the directory.
For the example above, recovery information for reporting bad records would be stored in a file
named .LOAD_TASK1.214235476634543.rcvy.
Do not delete this file. Deleting it could result in duplicate records being reported to the
.input.bad file for the associated load task. The Linux gelserver process automatically deletes
the .rcvy file once the task instance run completes successfully.
Sample Recovery Scenario
This example configures a recovery-enabled task named TASK_RECOVERY_ENABLED that uses
this command:
Recovery 117