Preparing for Db2 13 migration in Db2 data sharing
When planning the migration of data sharing members to Db2 13 it is best to take certain actions to reduce or avoid unnecessary operation complexity.
Procedure
To prepare for migration to Db2 13 in data sharing, complete the following steps:
-
Ensure that all required maintenance, including the Db2 13 fallback SPE, is applied on every member.
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.
-
After
all members have migrated to Db2 13, do not
activate new function until your data sharing group has processed a full range of typical work. The
amount of time that a data sharing group needs before new function is activated depends on the size
of the data sharing group and the complexity of its typical work.
Important: Do not issue the ACTIVATE command or run job DSNTIJAF for activation of Db2 13 until you are certain that the subsystem or data sharing group can proceed on Db2 13, without the possibility of falling back to or coexistence with Db2 12. In data sharing, the ACTIVATE command has group scope. Fallback and coexistence become impossible with the successful activation of function level 500 or higher.
-
Before you migrate to Db2 13, read the
information about release incompatibilities and make any necessary changes.
For more information, see Incompatible changes in Db2 13.
-
Plan to minimize the amount of time that Db2 13 operates in release coexistence with members on
Db2 12.
For more information about release coexistence in Db2 data sharing, see Release coexistence in Db2 data sharing.
- Start only one Db2 member for migration processing. During the migration, other group members can be active. However, other active group members may experience delays or timeouts if they attempt to access catalog objects that are locked by migration processing. After migration completes on the first member, you can migrate the other data sharing group members.
- To prepare for possible fallback from Db2 13, keep the subsystem parameter load module that is used by Db2 12.