home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC97283 Status: Closed

THE REBIND COMMAND FAILED WITH SQL0901N ERROR.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When an array type UDT is dropped and recreated and it is 
referred in a stored procedure, the rebind command against the 
package associated with the stored procedure might fail with 
SQL901N error. 
And dump files might be generated under ./sqllib/db2dump. 
 
Example of the error: 
 
$ db2 rebind package P1014268503 
SQL0901N  The SQL statement or command failed because of a 
database system 
error. (Reason "SQLNQ_FINDCAST 050".)  SQLSTATE=58004 
 
db2diag.log has the following kind of records. 
 
2013-10-29-05.05.09.146961-240 E947128A802          LEVEL: Error 
PID     : 38928442             TID : 2058           PROC : 
db2sysc 
INSTANCE: jl08183              NODE : 000           DB   : 
SAMPLE3 
APPHDL  : 0-7                  APPID: 
*LOCAL.jl08183.131029085927 
AUTHID  : JL08183              HOSTNAME: p6db2serv 
EDUID   : 2058                 EDUNAME: db2agent (SAMPLE3) 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:30 
MESSAGE : ADM14005E  The following error occurred: "AppErr". 
First Occurrence 
          Data Capture (FODC) has been invoked in the following 
mode: 
          "Automatic".  Diagnostic information has been recorded 
in the 
          directory named 
 
"/home/jl08183/sqllib/db2dump/FODC_AppErr_2013-10-29-05.05.09.14 
6048_ 
          38928442_2058_000/". 
 
<snip> 
 
2013-10-29-05.05.09.794481-240 E993349A1678         LEVEL: Info 
(Origin) 
PID     : 38928442             TID : 2058           PROC : 
db2sysc 
INSTANCE: jl08183              NODE : 000           DB   : 
SAMPLE3 
APPHDL  : 0-7                  APPID: 
*LOCAL.jl08183.131029085927 
AUTHID  : JL08183              HOSTNAME: p6db2serv 
EDUID   : 2058                 EDUNAME: db2agent (SAMPLE3) 
FUNCTION: DB2 UDB, SW- common services, sqlnn_cmpl, probe:650 
MESSAGE : ZRC=0x80040001=-2147221503=SQLD_NOREC "NO MORE RECORDS 
FOUND ON FETCH" 
          DIA8000C An unexpected end of file was reached "". 
DATA #1 : String, 62 bytes 
An unexpected error was detected during statement compilation. 
DATA #2 : Boolean, 1 bytes 
true 
DATA #3 : Boolean, 1 bytes 
false 
DATA #4 : Boolean, 1 bytes 
true 
DATA #5 : Boolean, 1 bytes 
false 
DATA #6 : Hex integer, 4 bytes 
0x00000000 
DATA #7 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 18 
 sqlerrmc: SQLNQ_FINDCAST 050 
 sqlerrp : SQLNQ25C 
 sqlerrd : (1) 0x801A006D      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0xFFFFFFCE      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
DATA #8 : Hex integer, 4 bytes 
0x00000040 
DATA #9 : String with size, 88 bytes 
set :HV00013  :HI00013  = CARDINALITY(CAST(:HV00008  :HI00008 
AS "JL08183"."INTARRAY")) 
DATA #10: String, 196 bytes 
Compiler error stack for rc = -2147221503: 
sqlnn_cmpl[300] 
sqlnp_main[250] 
sqlnp_parser[510] 
sqlnp_smactn[100] 
sqlnq_sem[2175] 
sqlnq_cast_non_marker[2183] 
sqlnq_convertNode[40] 
sqlnq_findCast[50]
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW users.                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V10.1 Fix Pack 4.                                 * 
****************************************************************
Local Fix:
Run the SYSPROC.ADMIN_REVALIDATE_DB_OBJECTS procedure before 
executing the rebind command.
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 10.1 Fix Pack 4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
29.10.2013
21.07.2014
21.07.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList