home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC76025 Status: Geschlossen

"AUD0022N THE AUDIT LOG FILE IS CORRUPTED" DUE TO RUNNING DB2SE T
FROM PRE-FIXPAK 2 AGAINST FIXPACK 2 OR HIGHER (OR VICE VERSA)

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
The audit log file can become corrupt if the pre-Fixpak 2 
version of db2set is ran against against an instance that is at 
Fixpack 2 or higher (or vice versa).  This also affects any 
other commands that happen to run db2set as part of it's 
processing (such as the db2ilist command). 
 
The following sequence of commands is an example of how the 
corruption may occur. 
1) Two instances on the same box. One is on Fixpak 2 or higher 
and one is at Fixpak 1 or lower. 
2) Configure the Fixpak 2 instance to do instance auditing on 
SYSADMIN category 
3) From the Fixpak 1 instance, set DB2INSTANCE to point to the 
Fixpak 2 instance 
4) From Fixpak 1, run db2set. Because DB2INSTANCE is pointing to 
the Fixpak 2 instance, db2set will read the audit config from 
Fixpak 2 and write to the audit log in Fixpak 2. Note the Fixpak 
1 db2set is running, not Fixpak 2 
5) The Fixpak 2 audit log will be corrupted as a result.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users that have multiple copies of v9.7 at different Fixpack * 
* levels                                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* "AUD0022N  THE AUDIT LOG FILE IS CORRUPTED" DUE TO RUNNING   * 
* DB2SET FROM PRE-FIXPAK 2 AGAINST FIXPACK 2 OR HIGHER (OR     * 
* VICE VERSA)                                                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.7 Fixpack 5                                * 
****************************************************************
Local-Fix:
Ensure the db2set command being ran is from the same Fixpack 
version as the instance to avoid corrupting the audit log.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 v9.7 Fixpack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
26.04.2011
19.01.2012
19.01.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP5
Problem behoben lt. FixList in der Version
9.7.0.5 FixList