If you distribute catalogs to end-users, there will be occasions when you need to send out updates to that catalog.
There are multiple ways to accomplish this:
- If you do not distribute the Relativity DBA, the end-user cannot modify your catalog; therefore, you just send an updated
catalog and replace the end-user's existing catalog.
- If you do allow your end-user access to the Relativity DBA, then you may wish to preserve changes made by the end-user when
you distribute an updated catalog.
The Catalog Merge capability, distributed with the Relativity DBA, generally takes any changes made by the DBA and merges
them into a new catalog, preserving Users, Privileges, and Connections modified and added by the end-user. For procedures
on using Catalog Merge, see
Merging a Catalog.
Note: Both the existing and modified catalogs must have owners in order to run this merge process.