IT21927: BLOCK DROPPING OF CF DURING ROLLING UPGRADE

Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 6 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 5 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 7 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• In a pureScale environment it is possible to drop a CF in the
  middle of Rolling Upgrade (that is, Rolling Upgrade has started
  but not completed and members are at different fix pack levels).
  Once that occurs a CF cannot be added back as the following
  SQLCODE is returned:
  
  SQL1648N  The SQL statement or command cannot be processed
  because of the state of a DB2 member in a DB2 pureScale
  environment. Member = "129". Reason code = "10".  SQLSTATE=57061
  
  Further, rolling upgrade cannot be cancelled as two CF's are
  required:
  
     Minimum 2 CFs are required to perform online fixpack updates
      DBI20135E  The online fix pack update has halted because the
  secondary CF is not in PEER state.
  
  Thus during Rolling Upgrade the dropping of a CF is now blocked.
  

Local fix

• Complete the rolling upgrade before dropping a CF
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ALL                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to Db2 11.1 Mod 3 Fix Pack 3 or higher               *
  ****************************************************************
  

Problem conclusion

• First fixed in Db2 11.1 Mod 3 Fix Pack 3
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  IT21413

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  DB2 FOR LUW

• Fixed component ID

  DB2FORLUW

Applicable component levels

• RB10 PSN

     UP