IBM Support

IT19926: THE DB2CHECKSD OPERATION MAY HANG WHEN RESTORING A 11.1.0.0 ESE BACKUP IMAGE TO 11.1.1.1 PURESCALE ENVIRONMENT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The documented procedure to restore an ESE backup image into a
    pureScale instance (as described in the Knowledge Center page
    titled "Restore from DB2 Enterprise Server Edition to DB2
    pureScale instance") describes performing a db2checkSD operation
    after the restore operation.
    
    When restoring a v11.1.0.0 (GA) ESE backup image into a
    v11.1.1.1 pureScale instance, the db2checkSD operation may hang.
    
    The db2diag.log will contain the following error message:
    
    2017-03-27-10.33.45.204689-240 I146748A817          LEVEL:
    Warning
    PID     : 55705820             TID : 50406          PROC :
    db2sysc 0
    INSTANCE: db2inst1             NODE : 000           DB   :
    SAMPLE
    APPHDL  : 0-58                 APPID: *N0.DB2.170327143345
    AUTHID  : DB2INST1              HOSTNAME: hotelaix14
    EDUID   : 50406                EDUNAME: db2agnti (SAMPLE) 0
    FUNCTION: DB2 UDB, base sys utilities,
    sqeLocalDatabase::SubsequentConnect, probe:12292
    RETCODE : ZRC=0xFFFFFBF5=-1035
              SQL1035N  The operation failed because the specified
    database cannot
              be connected to in the mode requested.
    
    A stack dump of the hanging agent will show the following
    functions:
    
    <Stack dump>
    WaitForCompletion
    DispatchIndependentDBAgent
    StartRqstHandler
    sqlraInvokeAutonomousRebind
    sqlra_find_pkg
    

Local fix

  • As a workaround, the v11.1.0.0 (GA) ESE backup image can instead
    be restored into a v11.1.0.0 (GA) pureScale instance followed by
    the upgrade of this pureScale instance to v11.1.1.1.
    Alternately, v11.1.0.0 (GA) ESE instance can be upgraded to
    v11.1.1.1 before the backup image is obtained, followed by
    restoring this backup image in the v11.1.1.1 pureScale instance.
    

Problem summary

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

Problem conclusion

  • First fixed in DB2 11.1 Mod 2 Fix Pack 2
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT19926

  • 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-03-28

  • Closed date

    2017-06-23

  • Last modified date

    2017-06-23

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

  • 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

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

Document Information

Modified date:
29 June 2020