DB2 FOR LUW / DB2FORLUW / A10 - DB2

When the ERROR TYPE is set to AUDIT in the instance level 
configuration or database level policy, an application may fail 
with -1307 because of a timing hole in the audit record I/O 
which allows an audit archive operation to archive the active 
audit log file that has already been opened for audit record 
I/O.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1 Fixpack 3                               * 
****************************************************************

If you are not concerned about tracking DB2 audit failures, 
which might result in lost of audit records, then setting ERROR 
TYPE to NORMAL in the instance level audit configuration and 
database level audit policies will result in DB2 ignoring all 
errors encountered by the DB2 audit facility.  This will allow 
an application to continue in the event this -1307 error occurs. 
 
For more information on the errortype setting, please read more 
at the following link: 
http://pic.dhe.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2. 
luw.admin.cmd.doc/doc/r0002072.html

DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

First fixed in DB2 v10.1 Fixpack 3

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

22.01.2013
03.10.2013
03.10.2013