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 IC96388 Status: Closed

DB2PD -REORG ON HADR STANDY TRAPS WHEN THE TABLE NAME OR SCHEMA HAS NOT
BEEN ALLOCATED WITHIN THE TCB

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
This trap can occur on an HADR standby machine, if DB2PD -reorg 
is run.  The issue is that, on a standby machine, the table name 
and schema name may not always be allocated within the TCB.  If 
this happens, the tcbCurrentName will be NULL and cannot be 
dereferenced, resulting in a trap of the DB2PD tool.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all users of db2pd                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2_v97 version 9.07.009                          * 
****************************************************************
Local Fix:
N/A
available fix packs:
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
Corrected and included in db2v97 version 9.07.009
Workaround
N/A
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC96431 IC96701 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.09.2013
17.12.2013
17.12.2013
Problem solved at the following versions (IBM BugInfos)
9.7.,
9.7.7.009
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.9 FixList
9.7.0.9 FixList