Start of change

Switching to previous access paths

You can save information about the previous access paths when you use a REBIND command to rebind your packages. When a new access path results in a performance regression, you can switch back to the previous access path.

About this task

When you specify a plan management policy, DB2® saves access path information for SQL statements when you issue a REBIND PACKAGE or REBIND TRIGGER PACKAGE command to rebind. When an access path change results in a performance regression, you can specify the SWITCH option and rebind the package again to revert to the previous access paths.

Start of changeThe use of plan management polices is recommend whenever you rebind packages with the APCOMPARE(WARN) option. This approach enables you to revert the package to use the previous access paths when you detect access path changes that you do not want.End of change

Parent topic: Managing and preventing access path change
Related tasks:
Reusing and comparing access paths at bind and rebind
Related reference:
REBIND PACKAGE (DSN)
REBIND TRIGGER PACKAGE (DSN)
BIND and REBIND options for packages and plans
End of change