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 IT04963 Status: Geschlossen

RESTORE_DB audit event not generated for database level auditing.

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
The audit event generated for a database restore operation is 
RESTORE_DB.  It is captured when the SYSADMIN category is 
audited.  The SYSADMIN category can be audited at the instance 
level and at the database level.  However, given a database is 
not active during a database restore operation, it is not 
possible for DB2 to generate a RESTORE_DB event at the database 
level.  Hence, to capture a RESTORE_DB event, you will need to 
audit SYSADMIN category at the instance level. 
 
The defect is, the RESTORE_DB event is not being generated for 
the SYSADMIN category at the instance level either.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW Version 10.1 Fixpack 5 or Later.          * 
****************************************************************
Local-Fix:
Lösung
First Fixed in DB2 LUW Version 10.1 Fixpack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
16.10.2014
14.07.2015
14.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList