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

LOAD FROM CURSOR WITH DATABASE CLAUSE GENERATES BENIGN ERROR MESSAGE IN
DB2DIAG.LOG

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The Load utility, when invoked with from CURSOR filetype where 
the cursor is defined using 
the DATABASE keyword (known internally as a 'remote fetch 
Load'), will generate a benign error 
message in the db2diag.log, similar to this: 
 
2009-04-09-02.35.35.980658-240 I10731A470         LEVEL: Error 
PID     : 1802342              TID  : 1           PROC : 
db2lueff 
INSTANCE: hidehy               NODE : 000 
APPID   : *LOCAL.hidehy.090409063535 
EDUID   : 1 
FUNCTION: DB2 UDB, database utilities, 
sqluffGenerateFetchQueries, probe:3534 
DATA #1 : String, 0 bytes 
Object not dumped: Address: 0x0000000000000000 Size: 0 Reason: 
Address is NULL 
MESSAGE : Query 
DATA #2 : String, 23 bytes 
 SELECT * FROM user1.t1 
 
The intent of this message is simply to describe the select 
statement 
used.  It will made a WARNING message instead.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of LOAD FROM CURSOR                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Users of LOAD FROM CURSOR with a DATABASE name defined will  * 
* sometimes see an Error in db2diag.log.                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 FP1                                      * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Solution
Fixed in DB2 V9.7 FP1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.11.2009
22.02.2010
22.02.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList