suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT22615 Status: Closed

OWNER / QUALFIER OF STORED PROCEDURE CHANGED TO SYSIBM

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Due to a code issue, after customer execute db2upv105 to update
fixpack, certain user defined stored procedure now owned and
qualified by SYSIBM (i.e. owner and qualifier field in the
catalog => SYSIBM)
Conditions:
1. the db cfg value auto_reval set to immediate (default is
DEFERRED)
2. where the user defined stored procedure has a call to a
SYSPROC procedure that was update/changed in that fixpack.

You can confirm if this is the case with following command :
please change  to your own schema

db2 "select substr(ROUTINESCHEMA,1,10),
substr(ROUTINENAME,1,50),
substr(OWNER,1,10),substr(QUALIFIER,1,10) from syscat.routines
where ROUTINESCHEMA='' and QUALIFIER='SYSIBM'"
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to v11.1 FP2 or later                                *
****************************************************************
Local Fix:
db2 update db cfg for  using auto_reval deferred
db2 terminate
run the db2updv105 tool
db2 update db cfg for  using auto_reval immediate
db2 terminate
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT19141 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.10.2017
13.10.2017
13.10.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)