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 IC89114 Status: Closed

SQL0901N "ERROR LOADING TYPE PD (SQLRL_FTC_TYPEPD)" FOR EXPLICIT
REBIND OF A PACKAGE IN DPF

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
In DPF environments, an explicit rebind of a package for a 
stored procedure hits -901, if the procedure uses UDT and the 
UDT was previously dropped. 
 
The following is reported in the db2diag.log 
 
2012-11-03-11.30.58.248415-240 I1330148E863        LEVEL: Severe 
PID     : 14392                TID  : 46916985416000PROC : 
db2sysc 1 
INSTANCE: db2inst1             NODE : 001          DB   : SAMPLE 
APPHDL  : 1-38882              APPID: *N1.db2inst1.121103153005 
AUTHID  : DB2INST1 
EDUID   : 939                  EDUNAME: db2agent (CAPO) 1 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, 
probe:300 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 40 
 sqlerrmc: Error loading type pd (sqlrl_ftc_typepd) 
 sqlerrp : SQLNN0C9 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFFF9C      (6) 
0x00000001 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
 
 
The relevant stack file indicates that the error occurred in 
sqlnnCheckNestedTypeInDPF.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to v9.7 Fixpack 10                                    * 
****************************************************************
Local Fix:
Recreate the UDT and revalidate the corresponding routine during 
next access or call sysproc.admin_revalidate_db_objects, instead 
of rebinding the package.
Solution
First fixed in v9.7 Fixpack 10
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC97839 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.12.2012
11.08.2014
11.08.2014
Problem solved at the following versions (IBM BugInfos)
9.7.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.10 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.