DB2 - Problem description
Problem IC89101 | Status: Closed |
DB2UPDV97 MAY HANG IF DB2_COMPATIBILITY_VECTOR REGISTRY VARIABLE IS ENABLED. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem 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. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 8. * **************************************************************** | |
Local Fix: | |
Unset the DB2 registry variable DB2_COMPATIBILITY_VECTOR and restart the instance, db2start. Finally execute the db2updv97 command. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 Version 9.7 Fix Pack 8. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.12.2012 02.04.2013 02.04.2013 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP8 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.8 |