home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT02471 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users in A50                                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 7 or higher.            * 
****************************************************************
Local-Fix:
Lösung
Firstly fixed in DB2 Version 10.5 Fix Pack 7.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
11.06.2014
20.01.2016
20.01.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList