Migrating an existing data sharing group to Db2 13

If you have a Db2 12 Db2 data sharing group, and you want a Db2 13 data sharing group, you can migrate to the newer release.

Before you begin

Prepare your data sharing group for migration, as described in Preparing for Db2 13 migration in Db2 data sharing.

During the migration to Db2 13, other group members can be active, but they might experience delays or timeouts if they attempt to access catalog objects that are being updated or that are locked by migration processing. Before beginning the migration process, confirm that Db2 12 is at the proper service level. Also, check your coupling facilities to ensure that the appropriate service levels are installed. Having the wrong service levels installed can result in data corruption. No specific service level requirements exist for CFLEVELs other than 12, but CF levels 13 and 14 are recommended for additional function. Use the z/OS® D CF command to display the service levels for IBM® coupling facilities.

Important: Migration to Db2 13 is only supported from Db2 12.
Important: If you are migrating the source, proxy, and target data sharing groups in a GDPS Continuous Availability with zero data loss environment to Db2 13, see Upgrading a Db2 12 GDPS Continuous Availability with zero data loss environment to a Db2 13 environment for the order in which you need to perform the migrations.
Important: Apply the for fallback SPE (APAR PH37108) and stop and restart Db2 12 for every subsystem or data sharing member that you plan to migrate to Db2 13. For data sharing, every member must be started in Db2 12 after the fallback SPE is applied. Inactive members that never started with the fallback SPE applied in Db2 12 cannot start in Db2 13 or Db2 12 after migration to Db2 13 and activation of function level 500 on any other member. See Required maintenance for Db2 13 installation or migration.
Before you start to migrate your data sharing group:

To migrate an existing data sharing group to Db2 13: