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

DB2 INVOKED THE USEREXIT TOO EARLY (USEREXIT WAS COPYING THE SOURCE LOG
WHILE LOGGW WAS STILL WRITING NEW LOG DATA TO IT)

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
This APAR applies if a database is configured to use a userexit
program to archive logs.

In very rare cases, IBM Db2's log writing EDU may still be
writing to a log file as Db2 invokes the userexit program.  No
warning or error message is produced.  Instead, the log file is
archived as a corrupt log file.

To detect such a case, IBM recommends users add code to their
userexit programs to verify the log archived, with the db2cklog
utility.  If the db2cklog responds with:

DBT7087W  The db2cklog utility found information in the current
log file which indicates that the log file might be active.

then Db2 has hit this APAR and the archived log file is corrupt.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to DB2 Version 10.5 Fix Pack 10                      *
****************************************************************
Local Fix:
Archive to disk instead of using userexit program
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : 
follow-up : IT23791 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.09.2017
18.07.2018
18.07.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)