HP Neoview Release 2.3 Software - Manual (Page 60)

CAUTION: If multipart = false, and parallelstreams is enabled, Transporter still
moves data off the Neoview platform in multiple streams. However, all the streams merge
into one file or named pipe. Ordering is not maintained if the files are merged for an ORDER
BY query. See
“multipart” (page 50) for details.
You provide a base filename for the targets and Transporter creates the specified number of files
or pipes with an incremental extension, (myfile.0001, myfile.0002, myfile.0003), up to
the number of parallel streams.
NOTE: If you specified ORDER BY for a query extract operation, each parallel data stream is
ordered, even is there is only one stream. However, ordering is not guaranteed among the
different streams. For example, if the ORDER BY list is a single integer column, values for the
ordering column could be 1,3,5 in one stream and 2,4,6 in another.
Transaction Modes for Load Jobs
When a load job runs and the table operation is INSERT, Transporter selects one of two transaction
modes, depending on the values for the options
“forcestaging” (page 49) and “noaudit” (page 51) .
If the “parallel” (page 52) option is set to true, the entire job runs under one transaction mode.
If individual job entries have settings that prevent them from running under the selected
transaction mode, Transporter reports an error.
The transaction mode determines whether Transporter uses transactional database operations
and whether a Transporter load job can be recovered. For information about transactional database
operations, refer to the HP Neoview SQL Reference Manual.
Table 7-3 Transaction Modes for Load Jobs
Non-transactional Mode Transactional Mode
Either forcestaging or noaudit must be true.
If forcestaging is true, the operation uses staging
tables.
NOTE: Transporter returns an error if both are true.
forcestaging is false and
noaudit is false.
Staging tables cannot be used in this mode.
commitsize is ignored. commitsize determines the number of source rows in
a transaction.
Transporter uses non-transactional database operations. Transporter manages internal transactions.
If forcestaging is true, and failure occurs during
transfer from a staging table to the target row, the job
cannot be recovered, it must be restarted.
When recovery is possible, all source rows are recovered,
because the load process starts from the beginning of the
job.
A failed job can be recovered. Only source rows not
successfully inserted are involved in the recovery.
Recovery resumes the load process from the last point of
failure.
Also used for UPDATE, UPSERT, or for a reflexive update
operation. (A reflexive update operation in a map
implicitly changes an INSERT to UPSERT.)
Loading Data With JMS Trickle Feed
This section discusses the requirements for using JMS Trickle Feed and the differences between
JMS Trickle Feed and other types of load jobs.
60 Load and Extract Operations