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

HADR STANDBY LOG FILES ACCUMULATING IN THE DATABASE LOG PATH.

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
The HADR standby will start to accumulate log files and
eventually can run out of disk space.  The problem originates on
the primary, and may be detected by checking the db2diag.log:

2021-09-05-22.55.29.098022-300 I3613422A1471    LEVEL: Error
PID   : 27722452       TID : 94326     PROC : db2sysc 0
INSTANCE: db2         NODE : 000      DB  : DB2C
APPHDL : 0-38477       APPID: 30.9.193.205.53816.210906034950
AUTHID : authid        HOSTNAME: hostname
EDUID  : 94326        EDUNAME: db2agent (Db2C) 0
FUNCTION: DB2 UDB, data protection services, sqlpxreg, probe:440
MESSAGE : ZRC=0x80100027=-2146435033=SQLP_PROTO
     "Transaction manager function called in wrong context."
     DIA8039C XA error with request type of "". XA protocol
error.
DATA #1 : String, 55 bytes
Incorrect transaction state. (tentryState / tid / xid):
DATA #2 : sqlpTranState, PD_TYPE_SQLP_TRAN_STATE, 8 bytes
2: SQLP_TWRITE
DATA #3 : SQLP_TID8, PD_TYPE_SQLP_TID8, 8 bytes
000000029CE5FD1F

If this problem is hit, the customer needs to take a new
database
backup on the HADR primary and use this to re-initialize the
HADR standby.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Apply Db2 Version 11.5.7.0                                   *
****************************************************************
Local Fix:
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* All                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Apply Db2 Version 11.5.7.0                                   *
****************************************************************
Comment
Apply Db2 Version 11.5.7.0
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.09.2021
06.11.2021
06.11.2021
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)