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 IC74235 Status: Geschlossen

POSSIBLE ABEND CALLING BACKUP AND SNAPSHOT APIS IN MULTITHREADED
APPLICATION

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
When a multithreaded application is using different db2 APIs 
e.g.db2Backup and db2GetSnapshot 
and they do not operate within separate contexts, then the 
application may possibly abend with a number of possible stack 
traces. 
 
e.g. 
csmSetCursorBuf 
sqlak_callbDrdaOutput 
sqlak_callbDrdaExecuteOutput 
sqljrParseExecuteReply 
sqljrParse 
sqljrDrdaArCall 
sqleproc 
sqlerInvokeKnownProcedure 
 
The recommendation to this is to use a separate context for each 
thread. This is documented under the 
"Concurrent transactions and multi-threaded database access in 
embedded SQL applications" 
topic in the Online DB2 documentation 
( 
http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm 
.db2.udb.apdv.embed.doc/doc/c0006107.htm 
)
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Client code failures when using snapshot api simultaneously  * 
* with backup api in a single process.                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.7 Fix Pack 5                               * 
****************************************************************
Local-Fix:
As per recommendation, use a separate context per application 
thread calling DB2 api functions ( or CLI functions )
verfügbare FixPacks:
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

Lösung
This problem has first been fixed in V9.7 Fix Pack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
01.02.2011
22.12.2011
22.12.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP5
Problem behoben lt. FixList in der Version
9.7.0.5 FixList