Preparing for Db2 12 migration in Db2 data sharing

When planning the migration of data sharing members to Db2 12 it is best to take certain actions to reduce or avoid unnecessary operation complexity.

Procedure

To prepare for migration to Db2 12 in data sharing, complete the following steps:

  • Start of change Ensure that all required maintenance, including the Db2 12 fallback SPE, is applied on every member.
    Important: Inactive members that never started in Db2 11 with the fallback SPE (APAR PI33871) applied cannot start after the first data sharing member is migrated to Db2 12 at function level 100.
    End of change
  • Start of change After all members have migrated to Db2 12, 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 12 until you are certain that the subsystem or data sharing group can proceed on Db2 12, without the possibility of falling back to or coexistence with Db2 11. In data sharing, the ACTIVATE command has group scope. Fallback and coexistence become impossible with the successful activation of function level 500 or higher.
    End of change
  • Before you migrate to Db2 12, read the information about release incompatibilities and make any necessary changes.
    For more information, see Incompatible changes for Db2 12 migration or function level activation.
  • Plan to minimize the amount of time that Db2 12 operates in release coexistence with members on Db2 11.
    For more information about release coexistence in Db2 data sharing, see Release coexistence in Db2 data sharing.
  • Start of change 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. For more information, see Migrating an existing data sharing group to Db2 12. End of change
  • Start of change To prepare for possible fallback from Db2 12, keep the subsystem parameter load module that is used by Db2 11. End of change