DB2 - Problem description
Problem IC96431 | 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 / A50 - 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_v105 version 10.05.003 * **************************************************************** | |
Local Fix: | |
N/A | |
available fix packs: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
Solution | |
Corrected and included in db2v105 version 10.05.003 | |
Workaround | |
N/A | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 27.09.2013 08.04.2014 08.04.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.4 |