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

LOAD USING AN EXCEPTION TABLE FAILS WITH "SQL3012C A SYSTEM ERROR
OCCURRED."

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Load using an exception table may fail with "SQL3012C A system 
error occurred." 
 
You will see the following DB2 trace probe points where 
sqluCompareTables returned -3012 
 
For example: 
 
<flow> 
 
50410       | | | | | | | sqlacall data [probe 40] 
50411       | | | | | | | sqlacall exit 
50412       | | | | | | | sqlastop entry 
50413       | | | | | | | | sqloxult_app entry 
50414       | | | | | | | | sqloxult_app exit 
50415       | | | | | | | sqlastop exit 
50416       | | | | | | sqluCompareTables exit [rc = 0xFFFFF43C 
= -3012] 
 
<format> 
 
50416   exit DB2 UDB database utilities sqluCompareTables cei 
(2.3.21.169.2) 
        pid 16906 tid 182957779104 cpid 4678 node 0 
        rc = 0xFFFFF43C = -3012 
 
The problem is due to the base table which was created with an 
extra space character padded at the end.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users doing LOAD with an exception table.                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Without this APAR, customer is exposed to the issue as       * 
* described in the "ERROR DESCRIPTION" section.                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7, Fixpack 4.                       * 
****************************************************************
Local Fix:
The workaround is to recreate the base table without any 
trailing space.
available fix packs:
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 9.7, Fixpack 4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.10.2009
30.04.2011
30.04.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList