Is it necessary to recompile and/or rebind a program after doing a reorg
on a table that is used by the program to take advantage of the reorg?
QUESTION POSED ON: 01 FEB 2005
QUESTION ANSWERED BY:
Craig Mullins
No, it is not. But let me elaborate on that. Running a REORG will "clean up"
the DB2 table space (or index space) by re-clustering, resetting free space,
and generally putting the data in its proper place. So, any program that
accesses a table (or index) after it has been reorganized can possibly
become more efficient.
Simply rebinding after running a REORG will do absolutely nothing. However,
if you run RUNSTATS after a successful REORG then you can possibly improve
performance by rebinding. It all depends on when the program was initially
bound and whether things have changed that would change your access paths.
For example, if the program was initially bound when the data was
disorganized and the statistics showed that, then rebinding after a REORG is
a very, very good idea. But if the program was initially bound when the data
was organized well (and the statistics showed that) then rebinding is not
likely to change anything (unless significant changes have been made to the
data (that is, more data added, or a lot of data was deleted).
As a general high level rule of thumb though, it is a good idea to REORG
followed by RUNSTATS followed by REBIND as the data in your objects grows or
changes.
Related Topics:
Search Advice from more than 250 TechTarget Experts
Your question may have already been answered! Browse or search more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.
Browse our Expert Advice
ASSOCIATED RSS FEEDS
 |
|
Expert Answer Center: Expert Q&As |
|
View all RSS Feeds | RSS Info
|
|
|
