DB2 - Problem description
Problem IC74235 | Status: Closed |
POSSIBLE ABEND CALLING BACKUP AND SNAPSHOT APIS IN MULTITHREADED | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
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 Summary: | |
**************************************************************** * 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 ) | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
This problem has first been fixed in V9.7 Fix Pack 5 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 01.02.2011 22.12.2011 22.12.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.5 |