DB2 FOR LUW / DB2FORLUW / A50 - DB2

When a stored procedure: ENV_GET_INSTANCE_CODE_LEVELS is called 
on 
Windows platform, it results in SQL0444N error. 
 
Here are the steps to reproduce the error: 
 
db2 SELECT * FROM TABLE (SYSPROC. 
ENV_GET_INSTANCE_CODE_LEVELS()) 
: 
SQL0444N  Routine "*E_LEVELS" (specific name 
"ENV_GET_INSTANCE_CODE_LEVELS") 
is implemented with code in library or path "*", function 
"env_get_rolling_update_status" which cannot be accessed. 
Reason code: 
"". 
SQLSTATE=42724 
 
Diag.log may contain the following error: 
 
2014-08-12-11.47.21.273000-420 I645871F1287 LEVEL: Severe 
PID : 10588 TID : 11236 PROC : db2syscs.exe 
INSTANCE: DB2 NODE : 000 DB : TEST 
APPHDL : 0-1157 APPID: *LOCAL.DB2.xxx 
AUTHID : xxxx HOSTNAME: xxx 
EDUID : 11236 EDUNAME: db2agent (TEST) 
FUNCTION: DB2 UDB, routine_infrastructure, 
sqlerRoutineResolveAddress, 
probe:10 
MESSAGE : ZRC=0xFFFFFE44=-444 
SQL0444N Routine "" (specific name "") is implemented with code 
in 
library or path "", function "" which cannot be accessed. Reason 
 
code: "". 
 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -444 sqlerrml: 70 
sqlerrmc: *E_LEVELS ENV_GET_INSTANCE_CODE_LEVELS * 
env_get_rolling_update_status 
sqlerrp : SQLERLIB 
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000 
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000 
sqlwarn : (1) (2) (3) (4) (5) (6) 
(7) (8) (9) (10) (11) 
sqlstate: 42724 
DATA #2 : String, 34 bytes 
env_get_rolling_update_status_v105 
DATA #3 : String, 16 bytes 
db2dbrouttrusted

**************************************************************** 
* USERS AFFECTED:                                              * 
* Windows                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.5 FP5 or higher                           * 
****************************************************************

First fixed in DB2 V10.5 FP5

not known / see Local fix

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

02.09.2014
18.03.2015
18.03.2015