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

Synchronization Considerations

Synchronization Considerations

In general, synchronization of a cloned target database is not possible without reloading the IDT/IDXs. There are many problems including:
  • Triggers on the source database will continue creating transactions for a specific database number (example, IDS_01). If the new target database’s connection string specifies a different database number, it will be unable to see those transactions.
  • There are now multiple consumers of trigger transactions (databases A and A’), but only one transaction will be created, which is insufficient to synchronize both databases. In other words, the cloned system does not have any triggers defined for it, and must not process the transactions created for the original system.
  • The
    IDS_2PC
    table contains the name (connection string) of the original target database. This may be changed to the new target database by using the
    -z
    switch in combination with the
    -o
    and
    -n
    switches. That is,
    ssachdb
    will connect to the database specified with
    -n
    and update the
    IDS_2PC
    table, replacing the
    OldName
    with the
    NewName
    .

0 COMMENTS

We’d like to hear from you!