Disabling and re-enabling Db2 data sharing

Disabling Db2 data sharing is a complex procedure and is very disruptive. Do not attempt to disable Db2 data sharing without a thorough understanding of the process.

Do not make disabling Db2 data sharing part of your contingency plans for handling recovery situations. For temporary bypasses to data sharing problems, try moving to one-way data sharing, which involves stopping all but one member and having that member perform the work for the group. If one-way data sharing does not work, your data sharing problem might be resolved by performing a group restart.

The disabling procedure is included in this section for completeness, but it should rarely be used. Situations in which it might be necessary to disable Db2 data sharing are:
  • You made a strategic decision to move away from a data sharing environment.
  • One-way data sharing is not working.

After you disable Db2 data sharing, only one member of the data sharing group can access the previously shared data. That member is called the surviving member. Before you disable data sharing, all page sets must be converted to extended format. For details, see What to do before RBA or LRSN limits are reached.

If you plan to re-enable data sharing for a group, do not change any group-wide information in the BSDS of the surviving member. Group-wide information includes the catalog alias name and the database password. It also includes the DDF name and password information, even if you do not plan to use DDF when you re-enable Db2 data sharing. If you change any of this information, you need to change the information in every member's BSDS before you start the group.