Weird behaviour during DB2 REORG for some Jazz Tables
Hi all,
the REORG Operation seems to take for ever for the following tables: REORG TABLE DB2INST1.CONNHEADER_JAZZ_DEADLOCKS; For each one of the REORG db2 sleeps: the db2sync process doesn't show anymore in the top window (Linux), the iostat show that nothing happens on the database. the most amazing thing is that for example the DB2INST1.CONNHEADER_JAZZ_DEADLOCKS table had only 101 records. the REORG hanged for about two hours and when we decided to stop it, the db2diag.log actually logged that the process was interrupted by the user, like if he was still running it. 2009-06-12-20.42.43.625018-240 I7609830G572 LEVEL: Warning Does anyone shares the same experience or have some advices regarding that issue? Are the DEADLOCK related tables important tables to index? Thanks, |
One answer
Hi all,
I did open WI 86744 https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=86744 for RTC and here's the response I got from IBM support on that issue: Hi Adil, we do not reorg the DEADLOCK related tables. Attaching a sample of the reorganization, which we do in the dev lab as best practice. https://jazz.net/jazz/service/com.ibm.team.workitem.service.internal.rest.IAttachmentRestService/repo/csid/Attachment/RTCDB2TablesWithReorg.txt?itemId=_H1axsGWDEd6HZLaaq4FsDg&id=26643 Thanks for you all for your time! |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.