DB2 FOR LUW / DB2FORLUW / 970 - DB2

Some system functions that get created automatically by DB2, 
incorrectly have the instance userid set as the owner of these 
functions. 
It would be more appropriate to have SYSIBM as the owner. Other 
than this owner field, there is no impact of this owner as the 
instance user cannot modify the functions anyway. ( results in 
error ) 
 
To see which functions are affected, run  : 
 
db2 "select substr(owner,1,10) owner, substr(routinename,1,20) 
routinename , substr(ROUTINESCHEMA,1,10) ROUTINESCHEMA 
,ownertype,routinetype  from syscat.routines where ROUTINESCHEMA 
= 'SYSPROC' and owner <> 'SYSIBM' " ; 
 
OWNER      ROUTINENAME          ROUTINESCHEMA OWNERTYPE 
ROUTINETYPE 
---------- -------------------- ------------- --------- 
----------- 
DB2INST3   DB2SECURITYLABEL     SYSPROC       U         F 
 
DB2INST3   VARCHAR              SYSPROC       U         F 
 
DB2INST3   =                    SYSPROC       U         F 
 
DB2INST3   <                    SYSPROC       U         F 
 
DB2INST3   >                    SYSPROC       U         F 
 
DB2INST3   <=                   SYSPROC       U         F 
 
DB2INST3   >=                   SYSPROC       U         F 
 
DB2INST3   <>                   SYSPROC       U         F 
 
DB2INST3   DB2SQLSTATE          SYSPROC       U         F 
 
DB2INST3   CHAR                 SYSPROC       U         F 
 
DB2INST3   DB2SQLSTATE          SYSPROC       U         F 
 
DB2INST3   =                    SYSPROC       U         F 
 
DB2INST3   <                    SYSPROC       U         F 
 
DB2INST3   >                    SYSPROC       U         F 
 
DB2INST3   <=                   SYSPROC       U         F 
 
DB2INST3   >=                   SYSPROC       U         F 
 
DB2INST3   <>                   SYSPROC       U         F 
 
 
  17 record(s) selected. 
 
 
The fix for this apar will correct this for new databases. For 
existing databases the ownership of these functions will remain 
the same.

**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the DB2 server to V9.7 Fix Pack 10 or higher.        * 
****************************************************************

This problem was first fixed in V9.1 Fix Pack 10

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC99675 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

15.01.2014
05.01.2015
05.01.2015

9.1.FP10,
9.7.FP10