HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide

[Contents][Glossary][Index][Back][Next]

3.3.10 Skipping import errors

If an error occurs during import processing, Datareplicator enables you to ignore the error and continue the import processing. This prevents interruption of import processing when errors that do not affect the import processing occur.

There are two types of error skipping during import processing:

Type Description
Using import suppression to skip errors
(skipping specified errors)
After an error occurs, this method specifies whether the error is to be skipped on the basis of the error information (update information identifiers).
This method is applicable to all errors, including SQL errors.
Skipping SQL errors This method uses SQLCODE to specify in advance the SQL errors that are to be skipped.
This method is applicable only to some SQL errors. For details about the applicable SQL errors, see the skip_sqlcode operand in 5.9 Import environment definition.
Organization of this subsection
(1) Using import suppression to skip errors
(2) Skipping SQL errors

(1) Using import suppression to skip errors

To ignore an error and continue import processing, specify the update information identifier# that is displayed as information in the error message. Use the import suppression list file to specify the update information identifiers.

For details about the message, see 10.1.3(4) Explanation of detail information.

#
You can also obtain the update information identifier by executing the hdsrefinfm command. For details, see hdsrefinfm in Chapter 7. Command Syntax.
(a) Prerequisites

The following table shows the Datareplicator versions that are capable of using import suppression to skip errors.

Table 3-1 Datareplicators capable of using import suppression to skip errors

Extraction product Version
HiRDB Datareplicator 04-00-/O or later
HiRDB Datareplicator Version 5.0 05-03-/D or later
HiRDB Datareplicator Version 6 06-01-/A or later
HiRDB Datareplicator Version 7 or later 07-00 or later
XDM/DS (TMS/4V) 07-01 or later
XDM/DS (other than TMS/4V) 08-03 or later
VOS3 Database Datareplicator 01-00 or later

Note
If you use the following system configuration, even a Datareplicator of the applicable version listed in Table 3-1 cannot use import suppress to skip errors:
  • The source system uses HiRDB Datareplicator Extension.
  • The hdssamqin command is used to input data to the target Datareplicator.
(b) Definition method

To specify use of import suppress, use an import suppression list file. The following table provides the details of an import suppression list file.

Table 3-2 Details of import suppression list file

Item Description
File name HDSPATH/reflect_pass_list_data-linkage-identifier#
Example: HDSPATH/reflect_pass_list_a1
File type UNIX regular file or Windows file
Attributes The user who executes the hdsstart command has the read privilege.

#
  • Specify the linkage identifier in lower-case letters.
  • For linkage identifiers 00 to 09, specify 0 to 9.
    For linkage identifiers 0a to 0f, specify a to f.

The following shows the specification format in the import suppression list file:

Specification format
 
control-code = Trn[:Pos][,Grp] #comment
    :
 
control-code
Specifies one of the following control codes, as appropriate to the operation:
Control code Description
SKIP_TYPE_ONLY Specifies normal import suppress.
This code suppresses the specified update information identifier.
SKIP_TYPE_UNTIL Specifies data linkage recovery.
Trn[:Pos][,Grp]
Specifies the update information identifier that is displayed as information in the error message. There can be no spaces or tabs between Trn, Pos, and Grp.
Specification Description
Trn ID of the transaction whose update information has been stored.
This is the hexadecimal value (24 digits) preceding the colon in Extract Id in the information portion of the error message.
Pos Storage position of the update information in the transaction indicated by Trn.
This is the decimal value (1 to 4294967295) following the colon in Extract Id in the information portion of the error message.
Grp Import group name specified in the group statement in the import definition.
The error to be suppressed by Grp specification depends on the method of import processing. Table 3-3 describes Grp suppression for each import method.

Table 3-3 Grp suppression for each import method

Import method Error to be suppressed by Grp specification
Grp specified Grp not specified
Table-based import method Suppresses Trn:Pos in the import group specified in Grp. Suppresses Trn:Pos in all import groups.
Transaction-based import method Suppresses Trn:Pos in all import groups (Grp specification is ignored). Suppresses Trn:Pos in all import groups.

Rules
  • Specify only one item per line.
  • Specify information from one control code through update identifier on the same line.
  • One line cannot exceed 512 bytes.
  • If a line contains a hash mark (#), the information following the hash mark is treated as a comment.

Example
This subsection presents an example of specifying an update information identifier.
This example assumes that the following message has been displayed during import processing by the table-based import method:
information portion of the message
 
Fri May 23 16:29:42 2003 process: hdssqle[trngroup](2032) function: hds_sqe_hexeis
errorcode: KFRB03033-E 02 a1 (hdssqle.exe[trngroup]) HiRDB data base EXECUTE error occurred, table name = "k896201"."R003", SQLCODE = -803.
information: "C1"=1
KFPA11803-E Duplicate key value in unique index id=196861
Additional Transaction Info = 3e681b95000000000000012f.
Extract Id = 3e681b95000000000000012f:1
 
To suppress import of only the transaction 3e681b95000000000000012f (storage position: 1) for the import group trngroup, this example is specified as follows:
Contents of the import suppression list file
 
SKIP_TYPE_ONLY=3e681b95000000000000012f:1,trngroup

(2) Skipping SQL errors

If an error with a predefined SQLCODE occurs, Datareplicator can ignore the error and continue import processing. With this method, you can skip only SQL errors, but it is easier than using import suppress because you can specify in advance the errors that are to be skipped.

If an SQLCODE error for which skip is specified occurs during import processing, you can ignore the error and continue import processing. You must specify the applicable SQLCODEs in the skip_sqlcode operand in the import environment definition. Note that Datareplicator ignores the skip specification for an SQLCODE corresponding to an SQL error that is subject to implicit rollback; in this case, import processing terminates.

For details about the skip specification for import SQL errors, see the skip_sqlcode operand in 5.9 Import environment definition.