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.
Important: 
Before 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 Verify Db2 13 premigration activities and activate function level 510 in Db2 12.
Before 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 Verify Db2 13 premigration activities and activate function level 510 in Db2 12.Tip: After 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.
After 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.Availability of new function and Db2 13 function levels
The availability of new function in Db2 13 depends on the type of enhancement, the activated function level, and the application compatibility levels of the applications. For a list of all available function levels in Db2 13, see Db2 13 function levels.
- Function level 100
- Db2 starts at function level 100 (V13R1M100) during migration to Db2 13, and fallback and coexistence with Db2 12 in data sharing remain possible. Many new capabilities in Db2 13 remain unavailable. For more information, see Function level 100 (for migrating to Db2 13 - May 2022).
- Function level 500
- Activating function level 500 (V13R1M500) prevents coexistence with and fallback to Db2 12. Function level 500 is also the first opportunity for applications to use many of the new capabilities in Db2 13. However, new capabilities that depend on Db2 13 catalog changes remain unavailable. For more information, see Function level 500 (for migrating to Db2 13 - May 2022).
- Function level 501
- Function level 501 (V13R1M501) is the first opportunity after migration to Db2 13 for applications to use new features and capabilities that depend on catalog changes in Db2 13. For more information, see Function level 501 (Db2 13 installation or migration - May 2022).
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 applications at the appropriate application compatibility, so that they can use new SQL capabilities. You can do these steps when you are ready and satisfied that your environment is stable on Db2 13. For details see, Application compatibility levels in Db2 13