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

CREATING A PACKAGE WHEN CONECTING FROM ISERIES TO A DB2 LUW DATABASE
FAILS WITH MESSAGE SQL9004

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When connected to a DB2 for Linux, Unix and Windows database 
V9.7 FP1, the iSeries client gets the error message SQL9004 
("Create of SQL package failed."). DDM trace of this scenario 
shows that the attempt to create a package failed because of a 
DRDA protocol error (sqlcode -30020) detected by the iSeries 
client while it was parsing the reply received from the DB2 LUW 
server.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* USERS CREATING A PACKAGE FROM ISERIES CLIENT TO A DB2        * 
* LUWSERVER                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When connected to a DB2 for Linux, Unix and                  * 
* WindowsdatabaseV9.7 FP1, the iSeries client gets the error   * 
* messageSQL9004("Create of SQL package failed."). DDM trace   * 
* of thisscenario shows that the attempt to create a package   * 
* failedbecause ofaDRDA protocol error (sqlcode -30020)        * 
* detected bythe iSeries client while it was parsing the reply * 
* receivedfrom the DB2LUWserver.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.7 fix pack 2                               * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem in DB2 v9.7 fix pack 1 and unfortunately no workaround. 
Upgrade to next fix pack release.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC66170 IC66171 IC66676 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.02.2010
10.06.2010
10.06.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP1,
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList