IBM Support

IC89101: DB2UPDV97 MAY HANG IF DB2_COMPATIBILITY_VECTOR REGISTRY VARIABLE IS ENABLED.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Problem description:
    
    Following a fix pack upgrade db2updv97 should be executed to
    update the database system catalog tables. In this case
    execution of db2updv97 does not complete and instead may run for
    hours.
    
    In DB2 Version 9.7 Fix Pack 6 the following messages will be
    reported in the diagnostic log, db2diag.log:
    
    2012-11-16-20.55.58.523858-420 I3739A330          LEVEL: Warning
    PID     : 2805854              TID  : 1           PROC :
    db2updv97
    INSTANCE: db2inst             NODE : 000
    EDUID   : 1
    FUNCTION: DB2 UDB, Common Trace API, sqlrl_db2updv, probe:568
    DATA #1 : String, 54 bytes
    db2updv97 processing starting for database 'SAMPLE'.
    
    2012-11-16-20.55.58.604574-420 I4070A472          LEVEL: Warning
    PID     : 2965754              TID  : 14138       PROC : db2sysc
    0
    INSTANCE: db2inst             NODE : 000         DB   : SAMPLE
    APPHDL  : 0-1503               APPID:
    *LOCAL.db2inst.121117035558
    AUTHID  : DB2INST
    EDUID   : 14138                EDUNAME: db2agent (SAMPLE) 0
    FUNCTION: DB2 UDB, relation data serv, sqlrr_db_diagnose,
    probe:150
    MESSAGE : WARNING: Diagnostic request received (Type = 2)
    
    2012-11-16-20.56.12.169123-420 E4543A712          LEVEL: Info
    (Origin)
    PID     : 2965754              TID  : 14138       PROC : db2sysc
    0
    INSTANCE: db2inst             NODE : 000         DB   : SAMPLE
    APPHDL  : 0-1503               APPID:
    *LOCAL.db2inst.121117035558
    AUTHID  : DB2INST
    EDUID   : 14138                EDUNAME: db2agent (SAMPLE) 0
    FUNCTION: DB2 UDB, SW- common services, sqlnn_regen_function,
    probe:1
    DATA #1 : String, 0 bytes
    Object not dumped: Address: 0x0000000000000000 Size: 0 Reason:
    Address is NULL
    DATA #2 : String, 0 bytes
    Object not dumped: Address: 0x0000000000000000 Size: 0 Reason:
    Address is NULL
    DATA #3 : String, 9 bytes
    SYSIBMADM
    DATA #4 : String, 16 bytes
    DBMS_LOB_COMPARE
    
    2012-11-16-20.56.12.528382-420 E5256A714          LEVEL: Info
    (Origin)
    PID     : 2965754              TID  : 14138       PROC : db2sysc
    0
    INSTANCE: db2inst             NODE : 000         DB   : SAMPLE
    APPHDL  : 0-1503               APPID:
    *LOCAL.db2inst.121117035558
    AUTHID  : DB2INST
    EDUID   : 14138                EDUNAME: db2agent (SAMPLE) 0
    FUNCTION: DB2 UDB, SW- common services, sqlnn_regen_function,
    probe:1
    DATA #1 : String, 0 bytes
    Object not dumped: Address: 0x0000000000000000 Size: 0 Reason:
    Address is NULL
    DATA #2 : String, 0 bytes
    Object not dumped: Address: 0x0000000000000000 Size: 0 Reason:
    Address is NULL
    DATA #3 : String, 9 bytes
    SYSIBMADM
    DATA #4 : String, 18 bytes
    DBMS_LOB_COMPARE_5
    
    In addition an application snapshot for application handle 1503
    will show the following SQL statement being executed
    
    SELECT COUNT(*) FROM SYSIBM.SYSTABLES WHERE CREATOR =
    'SYSIBMADM' AND NAME = 'DBA_TAB_COLUMNS'
    
    In this particular case the table SYSIBMADM.DBA_TAB_COLUMNS does
    not exist. This table, along with other views and tables, is
    created when the DB2 registry variable
    DB2_COMPATIBILITY_VECTOR=ORA is set and then the database is
    created.
    
    To resolve the issue unset the DB2 registry variable
    DB2_COMPATIBILITY_VECTOR and restart the instance, db2start.
    Finally execute the db2updv97 command.
    

Local fix

  • Unset the DB2 registry variable DB2_COMPATIBILITY_VECTOR and
    restart the instance, db2start. Finally execute the db2updv97
    command.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 9.7 Fix Pack 8.                       *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 Version 9.7 Fix Pack 8.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC89101

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-12-13

  • Closed date

    2013-04-02

  • Last modified date

    2013-04-02

  • 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

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC89101

Modified date: 02 April 2013