Plan analyzer rulesets re-synchronization (RESYNC) to allow EXPLAIN to work between two releases.

Products

• SQL-Ease for DB2 for z/OS
• Plan Analyzer for DB2 for z/OS
• Database Management for DB2 for z/OS - Performance Suite
• Database Management for DB2 for z/OS - SQL Performance Suite

Issue/Introduction

Here is a Scenario for a two-way datasharing group DB0A with DB1A/DB2A members:
A:

1.      DB1A code gets upgraded to V12

2.      CATMAINT gets executed on DB1A

3.      Catalog level is V12R1M500, function level is V12R1M100

4.      DB2A remains at V11 NFM for a few hours/days.

5.      DB2A then gets upgraded to V12.

Scenario B:

1.      DB1A/DB2A runs V12

2.      Catalog level is V12R1M500, function level is V12R1M100

3.      DB1A is fallen back to V11 NFM for a few hours/days/weeks due to issues.

4.      DB2A is re-upgraded to DB2 V12.

What are the exact steps required for ensuring stability and operability of the CA DB2 tools. More specifically about:
 Plan analyzer rule set resynchronization (RESYNC) to allow EXPLAIN to work from either members at all time.

Environment

Release : 19.0

Component : CA Detector for DB2 for z/OS

Resolution

The RESYNC allows a rulesets to upgrade the rulesets release level from say Db211 to Db2 12, but doesn't support the ability to lower the rulesets release from a higher Db2 level down to lower Db2 level. In the  above described scenario you would need to maintain two distinct rulesets one defined using the DB2A SSID for V11 release level and the other DB1A SSID using the V12 release level. When the data-sharing group members are  at the V12 release level, the rulesets are at the V12 release level, the rulesets can be shared between members by defining the rulesets using the group name, but when the members are on different Db2 releases levels, they require their own rulesets.