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

CONNECT/ACTIVATE SPM DATABASE SHOULD NOT INCREMENT THE COUNTER OF HOW MANY
DATABASE IS ACTIVATED.

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
The SPM is externalized as a fake database only as a means to 
support a few commands as well as heuristically commit or 
rollback of indoubt transactions it is maintaining. In addition, 
SPM is also used for mapping XA connections to 2 phase commit 
connections when going against DB2 for zOS. 
 
Therefore, connect or activate SPM DB <SPM_NAME> should not 
increment the counter of how many databases are currently 
activated 
 
Per example: 
 
If DBM CFG has the following settings: 
 
NUMDB=2                    <---  Max number of concurrently 
active databases allowed 
TM_DATABASE=1ST_CONN 
SPM_NAME=SPMDB 
 
And only 2 databases are defined (TESTDB1, TESTDB2) - no others 
databases are defined. This means SPMDB is not defined as such 
as it is the Sync Point Manager. 
 
- db2 activate db testdb1 ==> OK 
- db2 activate db testdb2 ==> OK 
- db2 connect to SPMDB  ==> SQL1041N  The maximum number of 
concurrent databases have already been started.  SQLSTATE=57032 
 
 
In the above case the connect or activate <SPM_NAME> should have 
been successful and show: 
 
- db2 activate db testdb1 ==> OK 
- db2 activate db testdb2 ==> OK 
- db2 connect to SPMDB  ==> OK
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Apar restricted to V9.1 users.                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See error descrition                                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.1 FP10                                         * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Solution
First fixed in V9.1 FP10
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.09.2010
28.06.2011
28.06.2011
Problem solved at the following versions (IBM BugInfos)
9.1.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.10 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.