Planning for release coexistence in Db2 13

In release coexistence, applications can continue to access Db2 data while you migrate data sharing members or distributed subsystems. However, you must weigh the benefit of continuous availability against the operational costs of running in coexistence. Most new capabilities and enhancements in Db2 13 remain unavailable during coexistence, and additional system management considerations apply.

Db2 13 supports release coexistence with Db2 12 in data sharing and distributed environments, as long as function level 500 or higher has not been activated on any Db2 13 member or subsystem.

Important: Do not issue the ACTIVATE command or run job DSNTIJAF for activation of Db2 13 until you are certain that the subsystem or data sharing group can proceed on Db2 13, without the possibility of falling back to or coexistence with Db2 12. In data sharing, the ACTIVATE command has group scope. Fallback and coexistence become impossible with the successful activation of function level 500 or higher.

For more information about release coexistence in Db2 data sharing, see Release coexistence in Db2 data sharing.