Migrating to Db2 13

Migration is the process of upgrading from Db2 12 to Db2 13.

  • The Db2 13 migration process uses a single catalog level. For more information about catalog levels in Db2 13, see Function levels and related levels in Db2 13.

  • Before you begin migration to Db2 13, read all information in Preparing your system to install or migrate to Db2 13.

  • Start of changeIf your Db2 environment contains PBR RPN table spaces, APAR PH61633 is an important PE fix that you must apply on all data sharing members before migrating to or activating function levels in Db2 13.
    Attention: If your Db2 environment contains PBR RPN table spaces, do not migrate any data sharing members to function level V13R1M100, or activate function level V13R1M500 or higher, until you apply the PTF for PH61633 on all data sharing members and complete all ++HOLD actions. For more information, see the 21 June 2024 Red Alert.
    End of change
Important: Start of changeBefore you can migrate a Db2 12 environment to Db2 13, you must complete premigration activities and activate function level 510 in Db2 12. For more information, see Activate function level 510 in Db2 12.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

Availability of new function and Db2 13 function levels

Continuous delivery in Db2 13

The availability of most new-function application capabilities in Db2 13 depends on the type of enhancement, the activated function level, and the application compatibility levels of each application. For a list of all available function levels that are currently available in Db2 13, see Db2 13 function levels.

Many new-function enhancements take effect at any function level when you apply a PTF in each Db2 subsystem or data sharing member. For more information, see New-function APARs for Db2 13.

Availability of virtual storage and optimization enhancements

Some virtual storage and optimization enhancements take effect in function level 100. Optimization enhancements become available after full prepare of the SQL statements, depending on the statement type:
  • For static SQL statements, after bind or rebind of the package.
  • For non-stabilized dynamic SQL statements, immediately, unless the statement is in the dynamic statement cache.
  • For stabilized dynamic SQL statements, after invalidation, free, or changed application compatibility level.

Application compatibility in Db2 13

After migration to Db2 13 is complete, you can resolve application incompatibilities before you rebind each application at the appropriate application compatibility, so they can use new SQL capabilities. You can do these steps for each application when you are ready and satisfied that your environment is stable on Db2 13. For more information see, APPLCOMPAT levels in Db2 13