Operations Guide

10.5
- 10.5 HotFix 2
- 10.5 HotFix 1
- 10.2 HotFix 1
- 10.2
- 10.1 HotFix 1
- 10.1
- 10.0 HotFix 1
- 10.0

Back Next

Fault Tolerance - Data Errors

The Table Loader will terminate with an error if the DBMS Load utility reports any errors while loading the IDT or IDXs. This may be undesirable if the failure is caused by a small number of data errors in the source rows.

The

DATABASE-OPTIONS=IDTERR

is used to specify the maximum number of data errors that can occur before the Table Loader will report a fatal error. The default value is zero.

Allowing data errors may produce integrity errors in the IDT and/or IDXs. The exact nature of the integrity error is database dependent:

Oracle’s SQL*Loader and UDB’s LOAD utility reject erroneous rows and writes them to an error file, so they will be missing from the IDT. However, these rows will still be present in the IDX, since IDX rows are stored in binary form and are only interpreted by MDM-RE.

UDB’s Import utility does not reject rows. Instead, the rows are loaded to the IDT with the incorrect column values set to NULL.

Correcting Errors

The source data should be corrected and the IDT/IDXs reloaded. If the System is synchronized the Update Synchronizer will automatically correct the IDT and IDXs while processing UST updates. Therefore it is unnecessary to reload the tables.

Rename Saved Search

Table of Contents

Operations Guide

Operations Guide

Fault Tolerance - Data Errors

Fault Tolerance - Data Errors

Correcting Errors