IBM Support

IZ68673: BACKUP MAY HANG DUE TO DB2VEND NOT BEING INITIALIZED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A backup process may hang under Solaris operating system because
    one of the child db2vend process may be waiting to acquire an
    AIO lock. This will only affect the backup processing. You can
    identify this issue if the backup seems not to respond and by
    running "db2ptree". The db2ptree will show some db2vend
    processes started and others being db2sysc at the same tree
    level
    as highlighted with "<<<<<<<<<<<<<" in the output below:
    
    
    5844  db2wdog 0
    
       5845  db2sysc 0
    
          5846  db2ckpwd 0
    
          5847  db2ckpwd 0
    
          5848  db2ckpwd 0
    
          26338  db2vend (db2med - 1067 (ECA))
    
          26339  db2vend (db2med - 1069 (ECA))
    
          26340  db2vend (db2med - 1068 (ECA))
    
          26341  db2vend (db2med - 1070 (ECA))
    
          26342  db2vend (db2med - 1072 (ECA))
    
          26343  db2sysc 0       <<<<<<<<<<<<<<<
    
          26344  db2vend (db2med - 1071 (ECA))
    
          26345  db2sysc 0      <<<<<<<<<<<<<<<
    
       5933  db2acd 0
    
       7506  db2fmp (C) 0
    
       7720  db2fmp (idle) 0
    

Local fix

  • Cancel the backup and retry might circumvent the issue.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All under Solaris operating system                           *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * A backup process may hang under Solaris operating system     *
    * because one of the child db2vend process may be waiting      *
    * to acquire an AIO lock. This will only affect the backup     *
    * processing. You can identify this issue if the backup seems  *
    * not to respond and by running "db2ptree". The db2ptree       *
    * will show some db2vend processes started and others being    *
    * db2sysc at the same tree level as highlighted with           *
    * "<<<<<<<<<<<<<" in the output below:                         *
    *                                                              *
    * 5844  db2wdog 0                                              *
    * 5845  db2sysc 0                                              *
    * 5846  db2ckpwd 0                                             *
    * 5847  db2ckpwd 0                                             *
    * 5848  db2ckpwd 0                                             *
    * 26338  db2vend (db2med - 1067 (ECA))                         *
    * 26339  db2vend (db2med - 1069 (ECA))                         *
    * 26340  db2vend (db2med - 1068 (ECA))                         *
    * 26341  db2vend (db2med - 1070 (ECA))                         *
    * 26342  db2vend (db2med - 1072 (ECA))                         *
    * 26343  db2sysc 0      <<<<<<<<<<<<<<<                        *
    * 26344  db2vend (db2med - 1071 (ECA))                         *
    * 26345  db2sysc 0      <<<<<<<<<<<<<<<                        *
    * 5933  db2acd 0                                               *
    * 7506  db2fmp (C) 0                                           *
    * 7720  db2fmp (idle) 0                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 version 9.5 FP6 or above.                     *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 version 9.5 FP6.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IZ68673

  • Reported component name

    DB2 UDB ESE SOL

  • Reported component ID

    5765F4102

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-01-25

  • Closed date

    2010-03-26

  • Last modified date

    2010-03-26

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

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

    IC65806 IC65807 IC67368

Fix information

  • Fixed component name

    DB2 UDB ESE SOL

  • Fixed component ID

    5765F4102

Applicable component levels

  • R950 PSY

       UP

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"950"}]

Document Information

Modified date:
06 October 2021