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

DB2 LOAD INTO PARTITIONED TABLE THAT CONTAINS AN XML COLUMN MAY FAIL WITH
SQL0901N - "MAX PSEUDO RID REACHED"

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Loading a large number of records into a partitioned table that 
contains an XML column may fail with a SQL0901N error. 
 
The LOAD aborts with SQL0901N error and the following is logged 
in db2diag.log: 
 
2012-07-11-23.09.58.209812+120 I3853A817          LEVEL: Severe 
PID     : 7667800              TID  : 7198        PROC : db2sysc 
0 
INSTANCE: ddddd               NODE : 000         DB   : SAMPLE 
APPHDL  : 0-2207               APPID: *LOCAL.ddddd.120711210625 
AUTHID  : DDDDD 
EDUID   : 7198                 EDUNAME: db2lfrm0 0 
FUNCTION: DB2 UDB, database utilities, 
sqluXmlGeneratePseudoRIDForThisRow, probe:4887 
MESSAGE : ZRC=0x82150001=-2112552959=SQLU_GENERIC_ERROR 
"Internal Error" 
          DIA8532C An internal processing error has occurred. 
DATA #1 : LOADID, PD_TYPE_LOADID, 56 bytes 
LOADID: 11793.2012-07-11-23.06.25.021180.0 (65530;32769) 
DATA #2 : String, 22 bytes 
Max pseudo RID reached 
DATA #3 : unsigned integer, 8 bytes 
1 
DATA #4 : unsigned integer, 8 bytes 
1 
DATA #5 : unsigned integer, 8 bytes 
65536
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 3.                      * 
****************************************************************
Local Fix:
Split the LOAD files in smaller chunks when possible. 
 
Reduce the DATA BUFFER value used by the LOAD. This buffer needs 
to be specified explicitly in the LOAD command otherwise LOAD 
will 
use around 25% of free memory in the DB2 utility heap.
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 10.1 Fix Pack 3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.04.2013
08.10.2013
08.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList