HP Neoview Release 2.5 Software - Manual (Page 20)

Table 3-1 Exception Tables: Columns Generated by Transporter
Column Type Column Name
INTEGER DEFAULT NULL _excp_err_num
VARCHAR(776) DEFAULT NULL _excp_object_name
CHAR(35) DEFAULT NULL _excp_partn_name
INTEGER DEFAULT NULL _excp_file_num
LARGEINT DEFAULT NULL _excp_rec_num
LARGEINT DEFAULT NULL _excp_load_id
NOTE: Transporter creates exception tables automatically. You cannot create exception tables
with other applications because the additional columns are not correctly configured for use with
Transporter.
Rows logged to the exception table contain a copy of the table row for which an error has been
detected. If the error is detected but the row is unavailable, a NULL is inserted into the exception
table as a placeholder.
Error Threshold With EIL
The error threshold for an Enhanced Initial Load differs from that of a conventional Transporter
load operation. The threshold value for EIL is the number of tolerable errors (errors control
file option) across all streams divided by the number of parallel streams (parallelstreams
control file option). This means that an average number of errors across all streams is the error
threshold for each individual stream. If one stream has few errors, but another has many errors,
the threshold might be reached even if a stream has no errors at all.
Restrictions for EIL
These restrictions exist:
• The current restrictions for a “noaudit” (page 61) load apply to EIL, except that sorting the
data is not required.
• Do not set these control file options for EIL:
— forcestaging
— noaudit
— norollback
• The table being loaded cannot have dependent objects such as indexes, constraints,
materialized views, or triggers defined on it.
• The row length of the target table cannot exceed 31000 bytes. If it does, the EIL option is not
available.
Staging Tables
A staging table is a Neoview SQL table used as an intermediate place for data before it is processed
and moved to the target table on a Neoview platform. Transporter creates the staging table in
the same schema as the target table, names it, uses it during the load operation, and deletes it
when the load operation is complete.
You cannot use staging tables for extract operations.
Use the “forcestaging” (page 59) option in the control file to control the use of staging tables.
Staging tables increase performance for load operations. However, if the operation fails:
20 Functions and Features