HiRDB Dataextractor Version 8 Description, User's Guide and Operator's Guide
This section describes the procedures for handling errors that occur while extracting data from a HiRDB and importing it into another HiRDB. Table 7-1 shows the HiRDB Dataextractor error handling procedures.
Table 7-1 HiRDB Dataextractor error handling procedures
| Error | HiRDB Dataextractor processing | User's action |
|---|---|---|
| Insufficient memory |
|
Re-execute when sufficient memory becomes available. |
| Internal conflict |
|
Contact the customer engineer. |
| System call error |
|
Eliminate the cause of the error and re-execute. |
| Line error or disconnection from remote system |
|
|
| Access error during data import into HiRDB |
|
Eliminate the cause of the error and re-execute. If data was extracted from a HiRDB and an error occurred during data import into another HiRDB, HiRDB Dataextractor outputs the JXU7010E message to the data source system. If this is the case, eliminate the cause of the error on the basis of the message output to the error log file that was created by the data import process. |
| Access error during data extraction from HiRDB |
|
Eliminate the cause of the error and re-execute. If the PDCLTPATH environment variable has been specified, HiRDB's SQL trace information is output to the SQL trace file. Eliminate the cause of the error on the basis of this information. |
| Access error during data extraction from ORACLE |
|
In the case of an SQL analysis error, check the values specified in the column name specification file, table expression specification file, and lock information file, eliminate the cause of the error, and then re-execute. |
| HiRDB Dataextractor operating environment setup error |
|
Check the HiRDB environment (such as variables), eliminate the cause of the error, and then re-execute. |
| HiRDB Dataextractor abnormal termination |
|
Contact the customer engineer. |
All rights reserved. Copyright (C) 2007, Hitachi, Ltd.