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

ACTIVATE COMMAND UNABLE TO START HADR DUE TO CLIENT CONNECT SESSION
TERMINATED

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Steps to reproduce:

1) suspend connect using db2trc

 2) on one window, issue CONNECT (was suspended )

 3) on another window issue ACTIVATE ( was suspended)

 4) db2trc off; force application(CONNECT's APPHDL)


All the connect and activate window received the SQL1768N reason
code 10.

Another test just using START HADR command replace ACTIVATE
command on our last test, when application force, the connect
window received the SQL1768N reason code 10, but the START HADR
command can run successful.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* linux/aix                                                    *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to db2 version 11.1.4.6                              *
****************************************************************
Local Fix:
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* linux/aix                                                    *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to db2 version 11.1.4.6                              *
****************************************************************
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.11.2020
14.03.2021
14.03.2021
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)