Troubleshooting
Problem
The error "SQL0572N Package "NULLID.SQLC2K26" is inoperative" and rebind issues after an update from DB2 10 .5 Fix Pack 7 to Fix Pack 8.
Symptom
Following a DB2 FixPack update from 10.5 FP7 to 10.5 FP8, the erroor SQL0572N is returned for any query using CLP, for instance: db2 "select * from syscat.tables with ur"
SQL0572N Package "NULLID.SQLC2K26" is inoperative. SQLSTATE=51028
Cause
There are a couple factors that might cause an inoperative package in this scenario:
Running db2updv105 following a DB2 FixPack update, will execute CREATE OR REPLACE statements to update some system routines, as result couple system packages will be invalidated including a few CLP packages.
In this scenario, the inoperative packages will be implicitly rebind successfully if the database configuration parameter auto_reval is not set to DISABLED. However, if auto_reval is DISABLED, the inoperative packages cannot implicitly be rebind - they can only rebind explicitly (resolve any).
If auto_reval is set to DEFERRED than an implicit rebind will be successful.
Running "db2 BIND...ACTION ADD" does not replace an existing package, even if the package is inoperative. The ACTION ADD option is recommended in general because you do not want to waste time binding packages that already exist - but it will not replace inoperative or invalid packages. In cases where auto_reval is disabled, the default ACTION REPLACE should be used.
Running db2rbind can rebound the package successfully - if the "-r any" option is in fact specified.
Without "-r any" it will not attempt to rebind inoperative packages.
Using the "-r any" is the same as issuing a db2 rebind package
Diagnosing The Problem
After a DB2 10.5 FixPack update on a database having the auto_reval parameter disabled and running db2updv105 can cause certain system packages including CLP to be inoperative resulting in SQL0572N.
Resolving The Problem
You can use one of the flowing options to avoid the inoperative package issue and ensure the rebinding the packages is successful:
1) Changing to auto_reval deferred (or immediate)
2) Running db2rbind using the "-r any" option
3) Rebinding the inoperative package explicitly using: db2 "rebind package NULLID.SQLC2K26".
4) Binding the system packages using ACTION REPLACE rather than ACTION ADD
Related Information
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21993607