Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Recovery Manager for Db2 13.1.

Data sharing considerations

If you are making contingency plans for the disaster recovery of a Db2 data sharing object set, you must set up and install a data sharing object set at the recovery site that is identical to the local site by using the same subsystem IDs and member names.

Each member must have all system resources restored before application recovery can begin.

Note

  • BMC AMI Recovery Manager enables you to generate JCL for the situation in which all members exist on a single LPAR at the remote site even if they are on multiple LPARs at the local site.
  • ARMBSRR supports data sharing when the data sharing object set includes members with different IBM Db2 version levels. In these cases, you should execute ARMBSRR to connect to the member with the higher version level. For example, if a data sharing object set has both Db2 Version 11 members and Db2 Version 12 members, you should execute ARMBSRR to connect to a Db2 Version 12 member.

We recommend that you read the following information in the appropriate Db2 planning and administration guide:

  • Discussions of the prerequisites for disaster recovery
  • How to avoid using object set naming conventions that conflict with the coupling facility (XCF) object set names for disaster recovery

Permanently quiesced subsystems

It is possible for your data sharing system to have one or more permanently quiesced members that are no longer in use and do not need to be recovered even in the event of a system-wide disaster.

The ARMBSRR program allows you to enter the system IDs of such quiesced subsystems in order to exclude them from a disaster recovery.

In the event that you need to start Db2 with a permanently quiesced member, you may receive the following error message:

 DSNR020I csect-name START MEMBERmember, OR REPLY 'NO' OR 'QUIESCED'

Respond QUIESCED to tell Db2 that the member is quiesced.

A second message might appear:

 DSNR030I csect-name WILL CONTINUE WITHOUT THE
member MEMBER'S LOG, REPLY 'YES' OR 'NO'

Respond YES to continue without the quiesced member’s log.

Warning

You must ensure that none of the logs of the quiesced members are needed for recovery.


Related topics

Basic-information

Preparing-system-resources-for-recovery



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*