Authorization problems

DB2 performance can be affected by plans and packages that are waiting for authorization checks or by failures because the authorization cache is full.

Compare the number of authorization checks made for authorized plans (PLAN-AUTH SUCC) with the number of checks made that did not use the DB2 catalog (PLAN-AUTH SUCC-W/O CATALOG). A wide difference could indicate a first use of any plan by a given user ID after DB2 was started. Set the CACHESIZE parameter to a value greater than zero for all plans where EXECUTE privilege is not granted to public.

If the number of package authorization failures (AUTH UNSUCC-PKG-CACHE) is not zero, or close to zero, use the ZPARM ZPAC to increase the size of the package cache.