HP Neoview Release 2.3 Software - Manual (Page 69)

• Static
— Extract source: Neoview SQL Text or Multi-Partition Set Table Extract
— Single Stream or Parallel Extract Streams
— Target information: name of file, named pipe or data source
— Indication if recovery operation was initiated by user
— Load target table name
— Text of DML query for load
• Dynamic
— Run status: scheduled, in progress, complete or error
— Exit status or error reason: Transporter exit error message
— Internal recovery attempt triggered due to tenacity setting: for example, 2 of 3
— Total rows extracted
— Extract statistics per stream basis
— Start time of the job entry
— Time for next retry operation if applicable
— End time of the job entry
Control File Metadata Tables
You can retrieve control file related data from these metadata tables on the Neoview platform:
• HP_TRANSPORTER.CONTROL_FILES — list of control files including the host name,
absolute path, and modification time. Use this list to locate a particular control file.
Example 9-2 Sample HP_TRANSPORTER_CONTROL_FILES File
| FILE_ID | FILE_HOST | FILE_ABS_PATH | FILE_ENCODING | FILE_VERSION | FILE_MODTIME |
| 17714284327823 | mynode.intranet.foo.bar.net | /mydir/control-files/control_info.txt | UTF-8 | 1 |
2008-02-13 16:47:18.0 |
| 17713711815864 | mynode.intranet.foo.bar.net | /mydir/control-files/control_ordr.txt | UTF-8 | 1 |
2008-02-13 16:47:27.0 |
• HP_TRANSPORTER.CONTROL_FILE_TEXT — the text of a particular control file
Example 9-3 Sample HP_TRANSPORTER_CONTROL_FILE_TEXT File
| FILE_ID | SEQ_NUM | FILE_TEXT |
| 17714284327823 | 1 | version 1.0; options { errors = 3 discards = 8, commitsize = 777, rowsetsize =
777 } ... |
| 17713711815864 | 1 | version 1.0; options { errors = 5, discards = 1, commitsize = 777, rowsetsize =
777 } ... |
NOTE: Password values have already been encrypted before control files are saved on the
Neoview platform.
Use these two metadata tables to find and examine the control file used to run a particular job
in the job statistics table. You can use the information from these tables to find and fix problems
that caused a job to fail.
Outdated information must be removed manually from these metadata tables.
CAUTION: Running jobs are actively using rows in the metadata tables. Do not delete these
rows or any other rows that might be needed for the recovery of failed jobs.
Using Transporter Metadata Tables
This section describes several scenarios, with examples, for statistics retrieval and metadata
maintenance.
Job Statistics on the Neoview Platform 69