Application behavior when running in a mixed release environment

There are special application considerations when the Db2® Mirror nodes are running on different IBM® i operating system levels.

When the operating systems levels are different across the node pair, actions initiated from the node using the higher level operating system will fail if the replication action includes an enhancement which is unique to the higher level operating system. Operations and replication actions initiated from the node using the lower level system will not fail.

This means that if the mixed release environment consists of Node A (IBM i 7.4 or IBM i 7.5) and Node B (IBM i 7.5 or IBM i 7.6), replicated objects cannot use software enhancements that exist only on the higher level operating system release.

Consider the following example with one node on IBM i 7.4 and the other node on IBM i 7.5 or IBM i 7.6.

The database file named SALES is a replicated object. On the IBM i 7.5 or IBM i 7.6 node, the Database Engineer (DBE) decides to protect the SALES file from being accidentally dropped by using the RESTRICT ON DROP feature.

ALTER TABLE sales ADD RESTRICT ON DROP;

The attempt to execute this SQL statement will fail because the RESTRICT ON DROP support does not exist on IBM i 7.4 but does exist on releases beyond IBM i 7.4. The DBE must wait until both nodes are running with the release level of IBM i that established support for the software feature being used.

When the replication action is initiated from the higher level node and the action is disallowed because it includes a software enhancement unique to the node at the higher level, the operation fails as follows:

SQL statements fail with SQLCODE = -7061 and SQLSTATE = '55019' (reason code 1)
CL commands fail with either CPFC922 (reason code 1), and possibly also CPF32AF (reason code 1)