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

The "num_sessions" value passed by DB2 to the vendor API
SQLUVINT() with the LOAD WITH COPY YES command is always "0"

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When trying to setup a backup vendor product for DB2 backups, 
the "NUM_SESSIONS" value passed by DB2 to the vendor API 
SQLUVINT() with the "LOAD WITH COPY YES" command is always "0" 
regardless of number of sessions passed. 
 
Example of a LOAD command with 3 sessions to be used with the 
vendor product: 
db2 load from .\test.dat of DEL insert into Table1 copy yes LOAD 
"c:\temp\libnsrdb2.dll" open 3 sessions 
 
However when checking the number of sessions passed by DB2 to 
the vendor API, the output shows 0 for the "num_sessions" 
parameter: 
 
num_sessions=0
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users using Load Vendor API for copy target.             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 Fixpack 5 or higher.                    * 
****************************************************************
Local Fix:
Solution
Firstly fixed in DB2 V10.1 Fixpack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.04.2015
14.07.2015
14.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList