DB2 FOR LUW / DB2FORLUW / A50 - DB2

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.

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

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

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.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

06.03.2017
27.09.2017
27.09.2017