DB2 - Problem description
Problem IC89709 | Status: Closed |
APPLICATION MAY RECEIVE SQLCODE -1307 RC 11 DURING DB2AUDIT ARCHIVE PROCESS DUE TIMING HOLE IN AUDIT RECORD I/O | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
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. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v10.1 Fixpack 3 * **************************************************************** | |
Local Fix: | |
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 | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 v10.1 Fixpack 3 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.01.2013 03.10.2013 03.10.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.3 | |
10.1.0.3 |