Required maintenance for Db2 13 installation or migration

In addition to ensuring that you have required hardware and software products installed, you must ensure that required service changes for Db2 13 have been applied.

Start of changeSome examples include the PTFs for the following important APARs, but you must check for others:
  • APAR PH37108 is the fallback SPE for migrating to Db2 13. You must apply the APAR on every Db2 12 subsystem or data sharing member, and stop and restart each one before starting your migration to Db2 13.
  • APAR PH42656 is the ERLY code for migration to Db2 13. You must apply the PTF for this APAR if you plan to use the Db2 12 ERLY code with Db2 13 subsystems.
  • APAR PH43770 enhances IRLM to support various new capabilities in Db2 13.
End of change
Tip: Start of changeAfter you apply the PTF for APAR PH50072 in Db2 12, you can get a migration readiness report in the DSN7100I message by issuing DISPLAY GROUP command with the DETAIL keyword. The report includes a reason if your environment is not ready for migration to Db2 13. See Check readiness for migration to Db2 13.End of change

FIXCATs for migrating to Db2 13

To help you identify the required service, z/OS® provides enhanced HOLDDATA. Enhanced HOLDDATA categories (FIXCATs) provide a simplified, automated method of identifying and applying missing PTFs that are required for installation or migration or to support specific product functions. For installation and migration to Db2 13, use the following FIXCATs:

Fix category (FIXCAT) Keyword
IBM.Migrate-Fallback.DB2.V13 DB2MIGV13/K
IBM.Coexistence.DB2.SYSPLEXDataSharing DB2COEXIST/K

You can use this automated process instead of manually reviewing Preventive Service Planning (PSP) buckets, identifying service that is already installed, and applying missing PTFs.

For more information about enhanced HOLDDATA and available FIXCATs, see the following pages:

New function and service APARs for Db2 12

Changes from many Db2 12 APARs are built-in when you migrate to Db2 13:
  • Enhancements from many new-function APARs in Db2 12 are built-in when you migrate to Db2 13. If you do not apply the PTFs for such APARs in Db2 12, plan for these changes to take effect when you migrate to Db2 13. See the APARs with availability dates earlier than 2022-06 in New-function APARs for Db2 12.
  • Also check for other Db2 12 service-stream APARs for Db2 12 that were available before general availability of Db2 13. If you did not already complete any required actions that are described in ++HOLD data for these APARs, make plans to do so before migration to Db2 13.