Bulk Data Movement Guide

10.4.1
- 10.5.8
- 10.5.6
- 10.5.5
- 10.5.4
- 10.5.3
- 10.5.2
- 10.5.1
- 10.5
- 10.4.0 HotFix 1
- 10.4.0

Back Next

Creating Error Action Files for Customized Error Handling

You can customize fault tolerance behavior if you require a specific error handling strategy. However, this task is optional because PowerExchange provides a default list of recoverable and fatal error codes for each supported database.

Use the following procedure to customize PowerExchange behavior for certain database error codes.

To create error action files for customized error handling:

Create an error action file that defines all of the database error codes for which you want to customize PowerExchange handling of the error. You can use one of the sample error action files that PowerExchange provides as a template. To specify a fault tolerance option for an error code, use the following syntax:

error_code,option

Where:

error_code
is a database-specific code, such as a DB2 SQLSTATE code or an Oracle ORA-nnnnn
error code.

option
is either R
for recoverable or F
for fatal.

For example:

00017,R
00018,F

Specify the full path and file name of your customized error action file in the DBMOVER configuration file on the target system. Use the statement for your database, for example:

DB2_ERRORFILE=path_filename
ORA_ERRORFILE=path_filename
MSS_ERRORFILE=path_filename

After the error action file is defined, PowerExchange uses the customized error code specifications instead of its default error handling. PowerExchange processes any error codes that you do not specify in the error action file as recoverable errors.

Rename Saved Search

Table of Contents

Bulk Data Movement Guide

Bulk Data Movement Guide

Creating Error Action Files for Customized Error Handling

Creating Error Action Files for Customized Error Handling