IT21915: 'START HADR AS STANDBY' OPERATION MAY FAIL WITH SQL1776N RC=7 DURING REINTEGRATION IN PURESCALE

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

APAR status

• Closed as program error.

Error description

• In a pureScale and HADR enviornment, after a forced takeover,
  when reintegrating the old primary database to make it a new
  standby database using the "START HADR ON DATABASE
  <db_name> AS STANDBY" operation, an SQL1776N RC=7 error
  might occur.  This is due to having other applications
  attempting
  to connect to this old primary database, and these connection
  attempts are interfering with the START HADR command, causing
  it to incorrectly return SQL1776N error.
  

Local fix

• If this problem persists, then you can attempt to block
  applications from connecting to the database until the hadr
  reintegration completes.
  For information on how to block incoming database connections,
  see technote:
  http://www-01.ibm.com/support/docview.wss?uid=swg21673436
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * pureScale                                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Fixed in Fix Pack inclusive of this APAR                     *
  ****************************************************************
  

Problem conclusion

• After Fix Pack inclusive of this APAR is applied, a START HADR
  AS STANDBY will not fail following a TAKEOVER HADR BY FORCE with
  SQL1776N RC=7.
  

Temporary fix

Comments

APAR Information

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

  IT19560

• 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

• RA50 PSY

     UP

• RB10 PSY

     UP