The Catalog Synchronization facility (CatSync) enables you to synchronize the definitions of DB2 objects in a particular subsystem's catalog with their respective definitions in the CA Repository for z/OS.
This utility compares the catalog definitions with the repository definitions and performs INSERT, UPDATE, and DELETE actions as necessary to ensure that the repository definitions accurately reflect the DB2 catalog.
In instances where objects in the catalog have no analogous repository definition, CatSync automatically performs the INSERT actions necessary to define the objects to the repository. CA Repository for z/OS documents all actions executed during the catalog synchronization process in a Sync Report table. To review this information afterward, simply run the Sync Report using the CA Repository for z/OS Reports facility.
You can run CatSync directly or as part of another process. Some of the other Facilities that call CatSync are the Relational Translator and the interfaces with DB2 Utility products such as CA RC/MIGRATOR and BMC's CHANGE MANAGER.
When you run CatSync directly, you must start the process from the Edit windows of the repository entity types DATABASE, TBSPACE (table space), TABLE, VIEW and DATATYPE. CatSync modifies entities of these and any subordinate entity types as needed to correctly define the catalog object.
When processing a table space definition, for example, CatSync also processes all tables of different types defined as part of that table space, as well as any indexes, constraints, distinct data types, triggers, auxiliary tables, views, and synonyms that are linked to each of those tables.
Note: The LOB table space column and auxiliary table column require special consideration. They have no meaning without a base table containing a row identifier for each row, and an indicator column for each of their LOB columns, with LOB data stored in the corresponding auxiliary table.
Therefore, all three DB2 objects-the base table containing the LOB column's definition, its auxiliary table, and corresponding LOB table space-should be scanned as one undivided DB2 object. Otherwise, repository metadata information cannot be completed and the result may have no informational value.
To successfully execute the CatSync process, you must have DB2 SELECT authority for the DB2 Catalog tables and repository SELECT, INSERT, UPDATE, and DELETE authority for the entity types in the repository's DB2 dialog.
You can also run the CatSync utility in a test mode. This enables you to identify the activities required to synchronize a catalog without actually modifying repository data. As with standard catalog synchronization, CA Repository for z/OS records the activities in the SYNC report table, which you can review by running the SYNC report.
| Copyright © 2009 CA. All rights reserved. | Email CA about this topic |