PLANMGMT bind option

The PLANMGMT option retains, during a rebind operation, all relevant package information (such as metadata, query text, dependencies, authorizations, and access paths) in catalog tables and in the directory.

PLANMGMT
  • ( OFF )
  • ( BASIC )
  • ( EXTENDED )
On: REBIND PACKAGE and REBIND TRIGGER PACKAGE

If performance regression occurs, you can direct DB2® to fall back to the older copy of a package. Over time, a package can have multiple copies that exist on disk storage, but only one of those copies is the active or current copy. All other copies are inactive.

( OFF )
If none of the following options are changed, the current access path is removed and replaced with the incoming copy, and any previous or original copies are unaffected.
  • OWNER
  • QUALIFIER
  • ENABLE
  • DISABLE
  • PATH
  • PATHDEFAULT
  • IMMEDWRITE

If any of the previously listed options are changed, all package copies (current, previous, and original) are purged.

( BASIC )
Discard the previous copy of a package. The current copy becomes the previous copy, and the incoming copy becomes the current copy. If an original copy of a package exists, it remains available.

Start of changeIf the PLANMGMT option is specified explicitly and you change any of the following options, DB2 issues an error message:End of change

  • OWNER
  • QUALIFIER
  • ENABLE
  • DISABLE
  • PATH
  • PATHDEFAULT
  • IMMEDWRITE
(EXTENDED)
Discard the previous copy of a package. The current copy becomes the previous copy, and the original copy is managed as follows:
  • If no original copy exists, the current copy is cloned to become the original.
  • If an original copy exists, it is retained as the original.

In each case, the incoming copy of a package becomes the new current copy.

Start of changeIf the PLANMGMT option is specified explicitly and you change any of the following options, DB2 issues an error message:End of change

  • OWNER
  • QUALIFIER
  • ENABLE
  • DISABLE
  • PATH
  • PATHDEFAULT
  • IMMEDWRITE
Note: Start of changeIf the PLANMGMT setting is inherited from the value of the PLANMGMT subsystem parameter and the value of one of the previously listed options changes, DB2 internally turns off the PLANMGMT option. As a result, DB2 purges the prior copies of a package. However, if one of the previously listed options is specified but the value does not change, DB2 processes the command as if the option were not specified. If none of the previously listed options has a change in value, an error message is not issued, and the PLANMGMT option is not turned off.End of change

Pattern-matching characters: PLANMGMT settings remain valid when pattern-matching characters (*) are used in the REBIND syntax. When you use REBIND PACKAGE to rebind more than one package, DB2 retains previous and original copies for each package separately.

Defaults:

Process Default value
BIND PLAN N/A
BIND PACKAGE N/A
REBIND PLAN N/A
REBIND PACKAGE Value of subsystem parameter PLANMGMT
REBIND TRIGGER PACKAGE Value of subsystem parameter PLANMGMT

Start of changeCatalog record: Column PLANMGMT of table SYSPACKAGE.End of change