IBM Support

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

Subscribe

You can track all active APARs for this component.

 

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

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 number

    IT21915

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-08-09

  • Closed date

    2018-03-15

  • Last modified date

    2018-03-15

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 March 2018