Ok, this goes to the heart of Q1 and Q2: (Caveat: I have been running the
index reorgs since 12noon today and I am not done as of 4pm.)
Output from Reorgchk_tb_stats
REORG TABLE DB2ADMIN.ALERTS_PART;
REORG TABLE DB2ADMIN.CASE_CLOSURE_DETAILS;
REORG TABLE DB2ADMIN.CASE_PART_STAT;
REORG TABLE DB2ADMIN.INVS_BCKGRND_SUMRY;
REORG TABLE DB2ADMIN.MPHONE_FRST;
REORG TABLE DB2ADMIN.MPHONE_LST;
REORG TABLE DB2ADMIN.NICKNAME;
REORG TABLE DB2ADMIN.PROVIDER_CHAR;
REORG TABLE DB2ADMIN.SCRTY_GRP_PRFL;
REORG TABLE DB2ADMIN.SCRTY_PRFL_RSRC;
Observe that few tables are reported for reorg versus many more indexes as
shown below. For, example, for ACCESS_REPORT, there are two indexes that
reorgchk says should be reorge'd hence two REORG INDEXES for ACCESS_REPORT. I
want to REORG ALL for a table once...
Output from Reorgchk_ix_stats:
REORG INDEXES ALL FOR TABLE DB2ADMIN.ACCESS_REPORT ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.ACCESS_REPORT ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.ADDRESS ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.ADDRESS ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.ALERTS ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.APPROVAL ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.APPROVAL ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.ASSIGNMENT ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.ASSIGNMENT ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.ASSIGNMENT ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.CASE_CLOSURE ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.CASE_CLOSURE_DETAILS ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.CASE_MASTER ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.CASE_OTHR_CNTCT ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.CASE_PART ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.CASE_PART ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.CASE_PART ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.CASE_PART ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.CA_MAIN ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.COUNTY_PROVIDER_CROSS_REF ALLOW WRITE
ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.DOC_NARRATIVE ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.DOC_NARRATIVE ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.EPISODE ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.EPISODE ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.EPISODE ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.EPISODE ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.EPISODE ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.EPISODE ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.EPISODE ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.EPISODE ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.EPISODE ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.EPISODE ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.EPISODE ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.INTAKE_PART ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.INVESTIGATION ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.INVESTIGATION ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.INVESTIGATION_CNTC ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.INVESTIGATION_CNTC ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.INVESTIGATION_CNTC ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.MEDICAL_PROFILE ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.MEDICATIONS ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.MENTAL_HEALTH_PROFILE ALLOW WRITE
ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.MPHONE_FRST ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.MPHONE_FRST ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.MPHONE_LST ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.ONCALL_SCHEDULE ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.ORG_WORKER_ROLE ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.PAN_TEXT_EVENT ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.PAN_TEXT_EVENT ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.PERSON_AKA ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.PROVIDER_ORG ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.PROVIDER_ORG ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.PROVIDER_ORG ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.PROVIDER_PART ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.PROVIDER_PART_STAT ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.RELATIONSHIP ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.RELATIONSHIP ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.TICKLER ALLOW WRITE ACCESS;
REORG INDEXES ALL FOR TABLE DB2ADMIN.TICKLER ALLOW WRITE ACCESS;
The index reorgs is taking way too long because VERY LARGE tables are being
reorg'd many times and I need to find another way of doing indexes or
eliminating multiple reorgs of the same table because of multiple indexes
being reported for the same table. Am I making sense?
Some of the tables are in the millions of rows in the index section. What can
I do for relief? I am researching hard for options and the documentation that
I have reviewed don't say nothing about this. In fact, I have learned more
from this runnig thread than from the books - they tell you the code but no
reasoning behind it or why it done so...anyway, that is where I am stuck.
I appreciate some more help to resolve this...
Thanks
Ian wrote:
>(1) 2 Tables are identified as needing reorg both before and after runstats
was done on them. Reorg is then performed on the two tables and another
runstats done on these tables.
What puzzles me is that both tables still show that Reorg is needed. How can
that be?
Let's see the output from reorgchk for the tables that you're concerned
about.
--
Message posted via
http://www.dbmonster.com