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. System Backup and Restore
  13. Batch Utilities

Restarting

Restarting

Checkpoints

The Table Loader takes checkpoints after the following major points in its processing:
  • Creation of IDT
  • Opening data source and creation of triggers (if necessary)
  • Source data extraction and key generation
  • Load of IDT
  • Creation of indexes on IDT
  • Analysis of IDT
  • Creation, loading and analysis of each IDX

Failures that can be recovered

The Table Loader can be restarted from the last successful checkpoint after a failure, as long as the reason for the failure has been corrected and it does not change the workflow performed by the Table Loader. For example, if the Table Loader:
  • ran out of room in the database and more space has been added, or
  • the process was cancelled.
the Table loader can be restarted after the last successful checkpoint.
However, anything that changes the workflow performed, or the output generated by the Table Loader invalidates the checkpoint information. For example, if you change
  • the data source, or
  • Key-Logic and/or options, or
  • the number of indexes, or
  • Loader options such as Load-All-Indexes, Re-Index, IDT-Only, etc., or
  • Sync-level,
the previous checkpoints are invalid and you must not restart the load.
The
Load
button in the System Editor deletes all restart information. Do not edit a System when a restart is pending.

How to Restart

The IIR Console keeps track of the Table Loader’s status. When you click
System
Load IDT
, the console will offer to restart a load if it failed last time.
To re-start, click
Yes
. If you wish to restart from the beginning, the partially loaded IDT and IDX must first be deleted by running
System
Refresh
, followed by running
System
Load IDT
.

0 COMMENTS

We’d like to hear from you!