Faileddatafile, Forcestaging, Faileddatafile forcestaging – HP Neoview Release 2.4 Software User Manual
Page 54
NOTE:
These values are advisory only. While this number can be considered a trigger for
shutting down a job, Transporter continues to process data already in progress to completion.
For this reason, there may be additional error records beyond the number specified.
•
For a job where the
option is “true”:
When the number of records written to the
file for the job reaches
number
, Transporter stops processing the job.
•
For a job where the
option is “false”:
When the number of records written to the
file for a job entry
reaches number, Transporter stops processing the job entry.
If number is zero, this option is disabled. Transporter does not stop processing a job or job entry
based on the number of failed records.
This option is ignored for extract operations.
faileddatafile
faileddatafile = filename
The default value is:
current-working-directory/failedrecord.dat
For a load operation, this option specifies where to put source records that have a valid format
but could not be written to the Neoview database. For example, a record that fails a data
conversion step or violates a uniqueness constraint.
Load records written to faileddatafile appear in the same format as the source file.
This option is ignored for extract operations.
forcestaging
forcestaging = "true" | "false"
The default is “false”.
For a file or named pipe load source, this option specifies whether rows should be written to
internally-managed staging tables on the Neoview system before populating target tables. If the
option is not “insert”, the forcestaging setting is ignored and the
option is implicitly set to “false”.
This option is ignored for extract operations.
This option is supported for table synonyms but not supported for views.
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
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
option for the job is “insert”, the
forcestaging
and
options cannot both be "true". If the
option is "true", the forcestaging option must be “false”, otherwise an error is
returned.
Because the operation is non-transactional, the
option is ignored.
When forcestaging is set to "true", SQL expressions and constant entries in the
section are not supported.
When staging tables are used for an “insert” operation:
54
Control File Options