Implications of enabling Db2 data sharing

You must plan a naming convention before enabling data sharing on the first member (the originating member) of the group.

Because names in the Parallel Sysplex® and names in the data sharing group must be unique, you must have a naming convention before you create the group. Not only must shared data objects have unique names, but you must create a unique name for every group resource.

The Db2 catalog of the originating member becomes the catalog for all the members of the data sharing group. You add additional members to the group as new installations, and those members use the originating member's Db2 catalog.

If you have data from existing Db2 subsystems that you want the group to share, you must merge the catalog definitions for that data into the group catalog. You must also ensure that all members of the group can access the data. Db2 does not provide a way to merge members' catalogs automatically.

Important: If the RBA for a non data sharing Db2 subsystem reaches or exceeds the hard or soft limit, you must either convert all table spaces and indexes to the 10-byte format or use the RBA reset procedure. Enabling data sharing is not sufficient to resolve the problem.