Restoring the legacy system workload manager objects

Prerequisites

The legacy workload manager environment uses a different set of system workload manager objects (built-in service classes, thresholds, work actions, etc) than the adaptive workload manager. Before the legacy workload manager can be enabled on a database, you must migrate the system workload manager objects. This migration step only needs to be performed once per database.

Installations of IBM Integrated Analytics System, Db2 Warehouse and Db2 Warehouse on Cloud permanently run adaptive workload manager and are unable to migrate away from it.

To disable the adaptive workload manager and restore the system workload manager objects to their legacy configuration (2 service subclasses, default concurrency threshold) perform the following steps:
  1. Using a connection that has DBADM or WLMADM authority or was granted the ability to execute the stored procedure, invoke the adaptive workload manager migration stored procedure as follows:
    CALL WLM_ENABLE_ADMISSION_CTRL(‘no’)

    This prepares the database for migration from an adaptive workload manager environment; however, no changes are made to the active database at this time.

  2. Deactivate and then reactivate the database. Upon reactivation, the database has new objects created, some old objects deleted and the database configuration parameter wlm_admission_ctrl set to NO putting the database into the Version 11.5 default workload manager environment. Please see Default query concurrency management.

If any workload objects were pointing to any service subclasses of SYSDEAULTUSERCLASS before migration, they will be changed to point SYSDEAULTUSERCLASS during migration.

Note: Migration to and from an adaptive workload manager environment is fully supported in an HADR environment.