Using the Catalog Synchronization Utility › Implementation Considerations

Implementation Considerations

Before you begin synchronizing the DB2 catalog with CA Top Secret Option for DB2, you must determine the following:

• Why you are synchronizing? Are you synchronizing so that products, such as QMF, can utilize information in the catalog?
• What users and resources must be synchronized?
  • Do only table resources need to be synchronized?
  • Do only a subset of tables need to be synchronized?
• Which method should you use for synchronization, selective or incremental?
• Are parts of your DB2 catalog and CA Top Secret Option for DB2 already in synch-If so, run an incremental synchronization to keep the catalogs in synch when changes occur to CA Top Secret Option for DB2

Finally, there are several factors in your DB2 or CA Top Secret Option for DB2 set‑up that can affect the processing or the output of the CA Top Secret Option for DB2 Catalog Synchronization Utility. Before you run this utility, read through the sections on familiarizing yourself with each of the synchronization processes. Each process provides pertinent information that you should be aware of before you begin. Once you are familiar with each process, read through the remaining sections and consider carefully whether any of the mentioned conditions exist at your site and the impact, if any, that they might have on the results of your synchronization.

Note: You should establish a synchronization policy. If you are a new CA Top Secret Option for DB2 user, you should determine your policy before you activate CA Top Secret Option for DB2.

The following topics are discussed in this section:

• Familiarizing yourself with a selective synchronization
• Familiarizing yourself with an incremental synchronization
• Methods of streamlining the synchronization
• Affects of the synchronization process on certain DB2 attributes and functions
• Affects of the synchronization process on certain CA Top Secret attributes and functions