DB2 - Problem description
Problem IT20873 | Status: Closed |
"DB2PD -REORG" DOESN'T SHOW ONLINE REORG INFORMATION ON PURESCALE | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
In pureScale server, "db2pd -d <db> -reorg" cannot show reorg information after running online reorg against the same table second time. After deactivating/activating the database, "db2pd -d <db> -reorg" can show reorg information again. Case 1: db2 "reorg testtable inplace allow write access start" db2pd -d <db> -reorg -- reorg information shows in db2pd output db2 "reorg testtable inplace pause " db2pd -d <db> -reorg -- reorg information shows in db2pd output db2 "reorg testtable inplace allow write access resume " db2pd -d <db> -reorg -- no reorg information shows in db2pd output Case 2: db2 "reorg testtable inplace allow write access start" db2pd -d <db> -reorg -- reorg information shows in db2pd output db2 "reorg testtable inplace allow write access start" db2pd -d <db> -reorg -- no reorg information shows in db2pd output | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 11.1 Mod 2 Fix Pack 2 or higher * **************************************************************** | |
Local Fix: | |
Use db monitoring instead of db2pd. | |
available fix packs: | |
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 11.1 Mod 2 Fix Pack 2 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 05.06.2017 23.06.2017 23.06.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |