IBM Support

IT21781: MEMBER COULD NOT BE ACTIVATED AFTER IT WAS STOPPED IN PURESCALE.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A member could not be activated with the following kind of error
    in pureScale environment.
    
    2016-07-15-21.51.25.454631+540 I130101438A751       LEVEL:
    Severe
    PID     : 27394228             TID : 22922          PROC :
    db2sysc 0
    INSTANCE: db2inst1             NODE : 000           DB   :
    DBNAME
    APPHDL  : 0-53                 APPID: *N0.DB2.192168000002
    HOSTNAME: HOST
    EDUID   : 22922                EDUNAME: db2redom (DBNAME) 0
    FUNCTION: DB2 UDB, recovery manager, sqlpPRecReadLog, probe:1275
    MESSAGE : ZRC=0x8710001D=-2028994531=SQLP_LERR "Fatal Logic
    Error"
              DIA8526C A fatal error occurred in data protection
    services.
    DATA #1 : String, 65 bytes
    Unexpected end of logs.  Recovery expects a log record to
    replay.
    DATA #2 : String, 25 bytes
    expectedFirstLsnToReplay:
    DATA #3 : SQLP_LSN8, PD_TYPE_SQLP_LSN8, 8 bytes
    000000004DE5FBBE
    
    In db2stop prior getting this error, the following kind of
    warning was found in db2diag.log.
    
    2016-07-14-00.05.10.171963+540 E10747538A528        LEVEL:
    Warning
    PID     : 1114404              TID : 43084          PROC :
    db2sysc 0
    INSTANCE: db2inst1             NODE : 000           DB   :
    DBNAME
    HOSTNAME: HOST
    EDUID   : 43084                EDUNAME: db2loggr (DBNAME) 0
    FUNCTION: DB2 UDB, data protection services, sqlpghck,
    probe:1880
    MESSAGE : DIA2030W In-doubt transaction(s) exists at database
    shutdown time on
              log stream "0". Crash recovery will be performed on
    the next database
              connection.
    

Local fix

  • Once deactivate the database at all members at the same
    time and activate the database again.
    It will trigger group crash recovery which will resolve this
    error.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * pureScale feature user.                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Version 11.1 Mod 2 Fix Pack 2.                    *
    ****************************************************************
    

Problem conclusion

  • This problem is first fixed in Version 11.1 Mod 2 Fix Pack 2.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT21781

  • 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-04

  • Closed date

    2017-11-03

  • Last modified date

    2017-11-03

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

    IT17470

  • 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

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"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:
03 November 2017