|
Problem IT34352
|
Status: Closed |
DURING START DB2DIAG.LOG MAY BE FLOODED WITH "NO HADR RESOURCE DEFINED" INFO MESSAGES IN AN ACTIVE-PASSIVE TOPOLOGY
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
In an active-passive topology, the db2diag.log may be flooded
with "No HADR resource defined" info messages when starting. The
following is an example of one of the logs you may see
repeating:
2020-09-12-21.19.43.242940+480 I9188735A564 LEVEL: Info
PID : 14024942 TID : 27565 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 0-50210 APPID: GA103324.A1F4.225342134743
AUTHID : HOSTNAME: sampledb2host
EDUID : 27565 EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, high avail services,
sqlhaIsHADRAutomationEnabled, probe:4100
MESSAGE : No HADR resource defined.
DATA #1 : String, 11 bytes
_SAMPLE-rs
DATA #2 : String, 4 bytes
udbp |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Db2 11.1 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade Db2 server to 11.1.4.6 *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Db2 11.1 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade Db2 server to 11.1.4.6 *
**************************************************************** |
| Comment |
DURING START DB2DIAG.LOG MAY BE FLOODED WITH "NO HADR RESOURCE
DEFINED" INFO MESSAGES IN AN ACTIVE-PASSIVE TOPOLOGY |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.09.2020
15.03.2021
15.03.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
