Reorgchk, Reorg, Runstats not having any effect after completion. Anyone know why this can be? Any solution?

Hi all,
I am very surprised to see that after doing a Reorgchk followed by reorg of selected tables and concluding with a runstats of the reorged tables, all of the tables continue to be identified and selected as reorg candidates in subsequent/followup reorgchk.

Has anyone had this experience? Can you share with me what you may have found out to the the reason and if possible what are the possible solutions to correct the situation?

This is very important to us to get this tables to their optimal state and I'll greatly appreciate a solution to this issue.

Thanks
EnudaAsked:
Who is Participating?
 
Kent OlsenData Warehouse Architect / DBACommented:
Hi Enuda,

This isn't a page-size issue.  :(

I'd read that when a reorg leaves a table appearing that another reorg is required, running with the CLEANUP ONLY flag will perform a quick condensing of the index and can solve the problem.

CLEANUP attempts to physically restructure the index pages without scanning the source table and rebuilding them.  It physically deletes index entries that are marked as logically deleted, when it encounters (or generates) an index page with no entries it returns the page to the free pool, and where possible, it merges partial pages to reduce the total number of index pages.

This actually clearing the reorg check needed flag on one table/index is a good thing.  It would have been nice if it had gotten them all, but it did indicate that the issue with reorgchk is minor.

Let me study a bit....

Kent
0
 
Kent OlsenData Warehouse Architect / DBACommented:
Hi Eduda,

My guess is that you're not using the CLEANUP option an the REORG INDEX statements.  That should solve this.

It's annoying to have DB2 suggest that a REORG is still needed, but it shouldn't really affect performance.


Good Luck,
Kent
0
 
EnudaAuthor Commented:
Kdo,
Ok thanks. I'l try that and see...
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
EnudaAuthor Commented:
Kdo,
I have tried CLEANUP ONLY ALL and all but one table/index is left still indicating a need for reorg. Can you suggest what might be the problem here?
I will like to dig further and find out why. Could it be that the page size is not the right page size for the table? Just a thought.

Another question. CLEANUP ONLY says indexes are not rebuilt. What does that really mean? Isn't rebuilding indexes just the whole idea behing reorg indexes? You would think IBM could have made REORG do all CLEANUP tasks without being told or is there a reason for not doing so?

So far so god and thanks again
0
 
Kent OlsenData Warehouse Architect / DBACommented:

Did you run the reorgs in exclusive mode?
0
 
MurpheyApplication ConsultantCommented:
Hi Enuda,

Did you check the manual about reorganisation of indexes?
http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/topic/com.ibm.db29.doc.ugref/db2z_utl_reorgindex.htm

Special the part "Concurrency and compatibility for REORG INDEX" (told me some new stuff :)
http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/topic/com.ibm.db29.doc.ugref/db2z_concurrencyreorgindex.htm

Good Luck,
Murph
0
 
EnudaAuthor Commented:
Kdo, No I did not run in exclusive mode. I allowed READ WRITE access during reorg. Is that what you mean?

murphey2, thanks for the links. I'll read thru them tonight and see what I can learn from it.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.