home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IT41316 Status: Closed

TOO MANY LOG FILES IN ACTIVE LOG PATH ON HADR STANDBY AND ALSM ENABLED

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
Starting from Db2 Version 11.5 Mod Pack 7, with Advanced Log
Space Management enabled, it is possible for first active log
file to fall behind on the HADR standby database compared to the
HADR primary database.

In the following example, there is no gap in replay on the
standby database, and both the primary and standby database are
currently on log file 17942 as shown in the following output:

> db2pd -hadr -db testdb
...
            PRIMARY_LOG_FILE,PAGE,POS = S0017942.LOG, 1,
349580090
            STANDBY_LOG_FILE,PAGE,POS = S0017942.LOG, 1,
349580090
                  HADR_LOG_GAP(bytes) = 0
     STANDBY_REPLAY_LOG_FILE,PAGE,POS = S0017942.LOG, 1,
349580090
...

But the database configuration on the primary database states
first active log is:
 First active log file                                   =
S0017934.LOG

And on the standby database, first active log is significantly
behind:
 First active log file                                   =
S0017887.LOG

Note this large gap in first active logs between the HADR pair
will result in many more log files on disk for the standby
database.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* STANDBY TOO MANY ACTIVE LOGS                                 *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to the latest fix pack.                              *
****************************************************************
Local Fix:


Solution




Workaround


****************************************************************
* USERS AFFECTED:                                              *
* STANDBY TOO MANY ACTIVE LOGS                                 *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to the latest fix pack.                              *
****************************************************************


Comment


First fixed in 11.5.8.0.


Timestamps


Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

23.06.2022
03.10.2022
03.10.2022


Problem solved at the following versions (IBM BugInfos)




Problem solved according to the fixlist(s) of the following version(s)