beautypg.com

Multipart – HP Neoview Release 2.3 Software User Manual

Page 50

background image

This option can be specified at the global level or for individual file or pipe sources that are part
of a load operation. When the

“parallel” (page 52)

option is set to "true" for a given job, all

sources within the job must have the same forcestaging setting.

For a load source where the

“operation” (page 52)

option for the job is “insert”, the

forcestaging

and

“noaudit” (page 51)

options cannot both be "true". If the

“noaudit”

(page 51)

option is "true", the forcestaging option must be “false”, otherwise an error is

returned.

Because the operation is non-transactional, the

“commitsize” (page 47)

option is ignored.

When staging tables are used for an “insert” operation:

Each target table has its own staging table.

The names of staging tables are generated by Transporter and written to the Transporter
log.

Source rows are first written to staging tables. When all source rows for a given target table
have been written to the staging table, Transporter populates the target table.

Jobs using staging tables cannot be recovered if the failure occurs during the staging table
to target table row transfer.

multipart

multipart = "true" | "false"

The default is “false”.

For an extract operation when this option is set to “false”:

Transporter uses the value of

“parallelstreams” (page 52)

to determine how many internal

data streams to manage and records from all internal streams are merged into a single target
file or pipe.

Rows in the target file or pipe do not appear in any particular order. If the extract source is
a Neoview SQL query containing an ORDER BY clause, the specified ordering is not
maintained.

If the extract target is of type file and parallelstreams is greater than one, Transporter
first writes records to a collection of intermediate files and then merges these files into the
single target file.

The number of intermediate files is determined by the parallelstreams option. The
names of the intermediates files are:

name-of-target-file.NNNN

Where NNNN is a zero-padded four digit integer.

For example, if the specified target file is “extractData” and the value of
parallelstreams

is 4, the following intermediate files are used:

extractData.0001
extractData.0002
extractData.0003
extractData.0004

For an extract operation when this option is set to “true”:

Target file or pipe names in the control file are interpreted as a prefix only.

If the extract source is a Neoview SQL query containing an ORDER BY clause, each target
file or pipe is ordered accordingly. However, there is no guaranteed ordering relationship
among the different targets. For example, if the ORDER BY list is a single integer column,
values for the ordering column might be [1,3,5] in one target and [2,4,6] in another.

Transporter generates a unique suffix for each actual target file or pipe. The number of actual
targets is determined by the parallelstreams option.

The suffix is:

50

Control File Options