home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC75111 Status: Closed

ERROR LOG MESSAGE WAS DUMPED INTO DB2DIAG.LOG WHEN THE EVENT MON ITOR NAME
DOES NOTEXIST ON DROP EVENT MONITOR

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
following Error log message is dumped into db2diag.log when  the 
event monitor 
name does not exist on drop event monitor.  In this case the 
event monitor 
name is  '@@@@@@1@__DWDPE$' 
 
---------------------------------------------------------------- 
 
2010-11-19-02.33.54.389316-480 I100673A614      LEVEL: Error 
PID     : 421994              TID  : 44723      PROC : db2sysc0 
INSTANCE: db2inst1            NODE : 000        DB   : SAMPLE 
APPHDL  : 0-5374              APPID: x.x.x.x.58916.101119103401 
AUTHID  : DB2ADMIN 
EDUID   : 44723               EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, database monitor, sqm_evmon_mgr::dropEvmon, 
          probe:10 
CALLED  : DB2 UDB, catalog services, sqlrlGetEvmonDesc 
RETCODE : ZRC=0x801A006D=-2145779603=SQLZ_CA_BUILT 
          "SQLCA has already been built" 
DATA #1 : String with size, 16 bytes 
          @@@@@@1@__DWDPE$ 
 
 
2010-11-19-02.33.54.389490-480 I101288A861     LEVEL: Error 
PID     : 421994              TID  : 44723    PROC : db2sysc0 
INSTANCE: db2inst1            NODE : 000      DB   : SAMPLE 
APPHDL  : 0-5374              APPID: x.x.x.x.58916.101119103401 
AUTHID  : DB2ADMIN 
EDUID   : 44723               EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary 
          logging func, probe:0 
 DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -204   sqlerrml: 16 
 sqlerrmc: @@@@@@1@__DWDPE$ 
 sqlerrp : SQLRL0AF 
 sqlerrd : (1) 0x801A006D  (2) 0x00000000  (3) 0x00000000 
           (4) 0x00000000  (5) 0xFFFFFFEC  (6) 0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)       (11) 
 sqlstate: 
 
 
2010-11-19-02.33.54.482105-480 I102150A745    LEVEL: Warning 
PID     : 421994               TID  : 12456   PROC : db2sysc0 
INSTANCE: db2inst1             NODE : 000     DB   : SAMPLE 
APPHDL  : 0-5387               APPID: *N0.DB2.101119103417 
AUTHID  : DB2ADMIN 
EDUID   : 12456                EDUNAME: db2evmti (DB2STATISTICS) 
FUNCTION: DB2 UDB, database monitor, 
          sqm_evmon_ttarget::get_table_info, 
          probe:70 
CALLED  : DB2 UDB, data management, sqldGetTableData 
RETCODE : ZRC=0x80040003=-2147221501=SQLD_INTRP "USER INTERRUPT 
DETECTED" 
          DIA8003C The interrupt  has been received. 
DATA #1 : String, 118 bytes 
          Event Monitor Name: DB2STATISTICS; 
          TableName: HISTOGRAMBIN_DB2STATISTICS; 
          Unable to get information about the Table! 
 
----------------------------------------------------------------
Problem Summary:
following Error log message is dumped into db2diag.log when  the 
event monitor  name does not exist on drop event monitor.  In 
this case the  event monitor  name is  '@@@@@@1@__DWDPE$' 
 
 
---------------------------------------------------------------- 
 
2010-11-19-02.33.54.389316-480 I100673A614      LEVEL: Error 
PID    : 421994              TID  : 44723      PROC : db2sysc0 
INSTANCE: db2inst1            NODE : 000        DB  : SAMPLE 
APPHDL  : 0-5374              APPID: x.x.x.x.58916.101119103401 
AUTHID  : DB2ADMIN 
EDUID  : 44723              EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, database monitor, sqm_evmon_mgr::dropEvmon, 
          probe:10 
CALLED  : DB2 UDB, catalog services, sqlrlGetEvmonDesc 
RETCODE : ZRC=0x801A006D=-2145779603=SQLZ_CA_BUILT 
          "SQLCA has already been built" 
DATA #1 : String with size, 16 bytes 
          @@@@@@1@__DWDPE$ 
 
 
2010-11-19-02.33.54.389490-480 I101288A861    LEVEL: Error 
PID    : 421994              TID  : 44723    PROC : db2sysc0 
INSTANCE: db2inst1            NODE : 000      DB  : SAMPLE 
APPHDL  : 0-5374              APPID: x.x.x.x.58916.101119103401 
AUTHID  : DB2ADMIN 
EDUID  : 44723              EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, trace services, sqlt_logerr_data (secondary 
          logging func, probe:0 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
sqlcaid : SQLCA    sqlcabc: 136  sqlcode: -204  sqlerrml: 16 
sqlerrmc: @@@@@@1@__DWDPE$ 
sqlerrp : SQLRL0AF 
sqlerrd : (1) 0x801A006D  (2) 0x00000000  (3) 0x00000000 
          (4) 0x00000000  (5) 0xFFFFFFEC  (6) 0x00000000 
sqlwarn : (1)      (2)      (3)      (4)        (5)      (6) 
          (7)      (8)      (9)      (10)      (11) 
sqlstate: 
 
 
2010-11-19-02.33.54.482105-480 I102150A745    LEVEL: Warning 
PID    : 421994              TID  : 12456  PROC : db2sysc0 
INSTANCE: db2inst1            NODE : 000    DB  : SAMPLE 
APPHDL  : 0-5387              APPID: *N0.DB2.101119103417 
AUTHID  : DB2ADMIN 
EDUID  : 12456                EDUNAME: db2evmti (DB2STATISTICS) 
FUNCTION: DB2 UDB, database monitor, 
          sqm_evmon_ttarget::get_table_info, 
          probe:70 
CALLED  : DB2 UDB, data management, sqldGetTableData 
RETCODE : ZRC=0x80040003=-2147221501=SQLD_INTRP "USER INTERRUPT 
DETECTED" 
          DIA8003C The interrupt  has been received. 
DATA #1 : String, 118 bytes 
          Event Monitor Name: DB2STATISTICS; 
          TableName: HISTOGRAMBIN_DB2STATISTICS; 
          Unable to get information about the Table! 
 
----------------------------------------------------------------
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 9.7 Fix Pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.03.2011
09.12.2011
09.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList