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

WHEN SSL IS USED FOR HADR COMMUNICATION DB2HADRS EDU IS SPINNINGAFTER HADR
GRACEFUL TAKEOVER.

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
This problem only occurs when SSL is used for communication
between HADR primary and standby.  That is, when HADR_SSL_LABEL
database configuration parameter is set.

Users might observe that db2sysc takes much CPU time in new HADR
standby after graceful takeover. The db2pd -edu shows CPU time
for db2hadrs EDU keeps growing.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.5 Mod 4 Fixpack 0 or higher                *
****************************************************************
Local Fix:
Restart the HADR standby, like as below:
1. Login to the new HADR standby server as instance owner.
2. Stop and start the standby database via
db2 deactivate db 
db2 activate db
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.5 Mod 4 Fixpack 0 or higher                *
****************************************************************
Comment
First fixed in Db2 11.5 Mod 4 Fixpack 0
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.03.2021
11.03.2021
11.03.2021
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)