Disadvantages
There are certain disadvantages to using a single large plan for all transactions.
- The complete plan must be rebound for any DB2 program modification.
- BIND can be time-consuming for large plans.
- The BIND process cannot take place while the plan is in use. The plan is likely to be in use in a production system most of the time due to normal activity. In a test environment, the transaction rate is normally low, but programmers can use debugging tools that make the response times longer with conversational programs. This can effectively keep the thread and plan busy.
- DB2-invoked REBIND (due to plan invalidation) allows no DB2 transactions to execute this plan.
- There is no real information value in messages and statistics pointing out the plan name, because there is only one plan.
- EDMPOOL must be large enough to cope with DBDs, SKCTs, and CTs
and must allow some fragmentation. Remember that the plan segmentation
feature allows DB2 to load into CTs only parts of the application
plans being executed. Nevertheless, the header and directory parts
of an application plan are loaded in their entirety into the SKCT
(if not already loaded), then copied from the SKCT to CTs. This
happens
at thread creation time.
Because the application plan directory size is directly dependent on the number of segments in the plan, using a large plan influences the EDMPOOL size and the number of I/O operations needed to control it.