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

Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 6 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 5 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 4 Fix Pack 7 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error 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.
  

Local fix

• Archive to disk instead of using userexit program
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ALL                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Problem Description above.                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to DB2 Version 11.1.3 Fix Pack 3                     *
  ****************************************************************
  

Problem conclusion

• First fixed in DB2 Version 11.1.3 Fix Pack 3
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  IT22504

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  DB2 FOR LUW

• Fixed component ID

  DB2FORLUW

Applicable component levels

• RB10 PSN

     UP