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

--
Message posted via DBMonster.com
http://www.dbmonster.com/Uwe/Forums....m-db2/200806/1