Software Owner's manual

Considerations for Job Recovery

Transporter jobs can be recovered, with these considerations:

• Only load jobs with file sources can be recovered. Job recovery is not supported for named

pipes or JMS Trickle Feed.

• Job recovery is not supported for extract operations.

• Only jobs started using the -recover command line option can be recovered.

The -recover Command Line Option

To recover a job, use the —recover option on the command line, and provide the name of the

original control file for the load. The Transporter client determines whether there are job

definitions in the control file that can be recovered. If recoverable jobs are found, Transporter

starts these jobs again from the last point of failure. Non-recoverable jobs are ignored. If all jobs

are non-recoverable, Transporter logs an error message and exits.

CAUTION:

• You must use the original control file to recover load jobs. If the control file has changed,

Transporter reports an error and exits.

• The original and unmodified data files must be available to Transporter during recovery.

• Do not attempt to recover a job that is still running.

• Do not attempt to recover a job that is already in the recovery process.

Job Statistics on the Neoview Platform

Job statistics on the Neoview platform are used by Transporter to facilitate job recovery. The job

statistics table, HP_TRANSPORTER.BASE_JOB_STATS, maintains this information for every

job:

• job name

• job progress and status

• source and target for each job entry

• start and end time for each job entry

Each row in the BASE_JOB_STATS table represents a job entry instance. The ROWS_PROCESSED

column reflects the number of rows processed for a particular job entry instance, including

discarded and failed records. The number of rows logged in this table is not cumulative. For

example, if you must run several instances of a control file because of errors in a job entry, you

must add together the number of rows processed from all instances to get the total number of

rows processed for that job entry.

Example 9-1 Sample HP_TRANSPORTER_BASE_JOB_STATS File

TRANSACTION_SIZE | ROW_LEN | END_TIME | SQL_TEXT |

| 17714284327823 | load1 | src1 | tgt1 | 2008-02-13 16:50:44.503 | 7 | 2406 | 777 | 342 | 2008-02-13 16:50:46.284

| INSERT INTO NEO.SALES.INFORMATION (FIRST_NAME,LAST_NAME,ADDRESS,ZIP,PHONE,SSN,INFO2) VALUES (?,?,?,?,?,?,?)

| 17713711815864 | load1 | src1 | tgt1 | 2008-02-13 16:50:53.56 | 33 | 3452 | 777 | 120 | 2008-02-13 16:50:55.61

| INSERT INTO NEO.SALES.ORDERS

(O_ORDERDATE,O_ORDERKEY,O_CUSTKEY,O_SHIPPRIORITY,O_TOTALPRICE,O_ORDERSTATUS,O_ORDERPRIORITY,O_CLERK,O_COMMENT)

VALUES (?,?,?,?,?,?,?,?,?) |

You can use a simple Neoview SQL query to retrieve all of the statistics for a particular Neoview

platform:

SELECT * FROM HP_TRANSPORTER.BASE_JOB_STATS

These are the static and dynamic statics that you can retrieve:

68 Troubleshooting