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

PRIMARY MAY ENCOUNTER "UNEXPECTED NETWORK ERROR" WHEN STANDBY HIT DISK
FULL ISSUE.

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
On Standby :

2016-09-20-01.17.43.562556+420 I934960A581          LEVEL:
Warning
PID     : 25034904             TID : 5400           PROC :
db2sysc 0
INSTANCE: DB2INST1             NODE : 000           DB   :
SAMPLE
HOSTNAME: MACHINE01
EDUID   : 5400                 EDUNAME: db2logalloc.0 (SAMPLE) 0
FUNCTION: DB2 UDB, data protection services,
sqpLogAllocEdu::sqlpAttemptToClearDiskFull, probe:210
DATA #1 : 
Disk Full state after all shipped logs have been replayed. Not
shutting down due to blk_log_dsk_ful enabled. Performing
disconnect/reconnect to unblock the Primary.

On Primary :

2016-09-20-01.17.43.564635+420 I148319A440          LEVEL: Error
PID     : 35193076             TID : 11054          PROC :
db2sysc 0
INSTANCE: DB2INST1             NODE : 000           DB   :
SAMPLE
HOSTNAME: MACHINE01
EDUID   : 11054                EDUNAME: db2hadrp.0.1 (SAMPLE) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrTcpIpRecv, probe:11810
MESSAGE : Zero bytes received. Remote end may have closed
connection

2016-09-20-01.17.43.564953+420 I148760A501          LEVEL: Error
PID     : 35193076             TID : 11054          PROC :
db2sysc 0
INSTANCE: DB2INST1             NODE : 000           DB   :
SAMPLE
HOSTNAME: MACHINE01
EDUID   : 11054                EDUNAME: db2hadrp.0.1 (SAMPLE) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrRecvMsgP, probe:30048
MESSAGE : HADR primary recv error:
DATA #1 : Hexdump, 4 bytes
0x0A000000057F3B50 : 0000 0001
....

2016-09-20-01.17.43.565297+420 I149262A487          LEVEL:
Severe
PID     : 35193076             TID : 11054          PROC :
db2sysc 0
INSTANCE: DB2INST1             NODE : 000           DB   :
SAMPLE
HOSTNAME: MACHINE01
EDUID   : 11054                EDUNAME: db2hadrp.0.1 (SAMPLE) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrEduAcceptEvent, probe:20215
MESSAGE : ZRC=0x8280001B=-2105540581=HDR_ZRC_COMM_CLOSED
          "Communication with HADR partner was lost"

2016-09-20-01.17.57.186824+420 I151991A588          LEVEL: Error
PID     : 35193076             TID : 11054          PROC :
db2sysc 0
INSTANCE: DB2INST1             NODE : 000           DB   :
SAMPLE
HOSTNAME: MACHINE01
EDUID   : 11054                EDUNAME: db2hadrp.0.1 (SAMPLE) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrGetTcpMessage, probe:36530
MESSAGE : ZRC=0x8780013D=-2021654211=HDR_ZRC_GENERIC_ERROR
          "generic HADR error code"
DATA #1 : 
Unexpected network error.  This may indicate a problem with the
network or the HADR partner.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* HADR                                                         *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* See workaround                                               *
****************************************************************
Local Fix:
The temp solution for this issue is to set DB config,
BLK_LOG_DSK_FUL to default value "NO" .
As when encounter disk full issue again, standby will be brought
down and primary will not be blocked.
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.10.2016
21.06.2018
21.06.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)