Table of Contents

Search

  1. Preface
  2. Introduction
  3. Servers
  4. Console Client
  5. Search Clients
  6. Table Loader
  7. Update Synchronizer
  8. Globalization
  9. Siebel Connector
  10. Web Services
  11. ASM Workbench
  12. Cluster Merge Rules
  13. Forced Link and Unlink
  14. System Backup and Restore
  15. Batch Utilities

Integrity Checking

Integrity Checking

The Update Synchronizer can be used to check the integrity of the IDT. When started with the
-i
switch, the Update Synchronizer compares the current contents of the User Source Tables against the current state of the IDT and report any differences. It can also check the integrity of the IDT vs IDXs.
This process does not take into account the following anomalies that might cause an incorrect error report:
  • unapplied transactions held in the Transaction Table
  • updates to the UST that have occurred while opening the cursors that reads it.
Therefore any errors reported may be transient. The best way to check is to run the Update Synchronizer to process all known updates and run the integrity checker a second time to see if the errors are transient.
The IDT vs IDX integrity check confirms that every IDT row has at least one IDX entry. If the IDX has been built with the
NO-NULL-KEY
option, some IDT rows may not have a corresponding row in the IDX as they generated NULL keys. The integrity checker flags this case as an error when in reality no error exists.

Syntax

The integrity checker is invoked with the
-i
switch:
-i[IDT[,IDX]]
If
-i
is specified without an IDT nor IDX name, it will check all IDTs within the System, and all IDXs against each IDT.
If an IDT name is provided, that specific IDT will be checked against all IDXs.
If an IDT and IDX name is provided, only that specific IDT/IDX combination will be checked.
The optional
-k
switch can be used to display detailed (field level information) for any erroneous records.

0 COMMENTS

We’d like to hear from you!