Falling back to Db2 11
If you encounter serious errors after tailoring the catalog and directory for Db2 12, you can return to Db2 11. Fallback to Db2 11 is only supported if Db2 12 is at function level 100.
Before you begin
Fallback to Db2 11 is not supported after activation of function level 500 in Db2 12.
Before you fall back to your previous Db2 version, consider the implications of doing so. For details, see Implications of falling back.
About this task
Fallback is the process of returning to Db2 11 after migrating the catalog and directory to Db2 12, as described in Migration step 19: Tailor Db2 12 catalog: DSNTIJTC. It is best to fall back only if you encounter severe errors while operating in Db2 12. After fallback, the catalog remains a Db2 12 catalog.
You cannot fall back to Db2 11 after you activate function level 500.
Remigrating is the process of returning to Db2 12 after falling back.
Procedure
To fall back to Db2 11, complete the following steps:
- Stop Db2 12.
- Run job DSNTIJFV to rename the cataloged procedures and reactivate Db2 11 code.
- Reconnect TSO, IMS, and CICS® to Db2 11.
- Start Db2 11.
- Run the Db2 11 installation verification jobs (DSNTEJxx).
What to do next
You can save your Db2 12 TSO logon procedures and JCL for remigration to Db2 12.