DB2 FOR LUW / DB2FORLUW / A50 - DB2

When trying to drop or remove an audit policy one of several 
errors may be returned. 
 
For example: 
 
connect to sample; 
 
CREATE AUDIT POLICY DB_POLICY1 
CATEGORIES AUDIT STATUS BOTH, 
CHECKING STATUS BOTH , 
CONTEXT STATUS BOTH, 
EXECUTE STATUS NONE, 
OBJMAINT STATUS BOTH, 
SECMAINT STATUS BOTH, 
SYSADMIN STATUS BOTH, 
VALIDATE STATUS BOTH 
ERROR TYPE AUDIT; 
 
AUDIT DATABASE REPLACE POLICY DB_POLICY1; 
 
drop audit policy db_policy1; 
 
The 'drop audit policy' command may fail with any of: 
 
DB21034E  The command was processed as an SQL statement because 
it was not a valid Command Line Processor command.  During SQL 
processing it returned: 
 
SQL0478N  DROP, ALTER, TRANSFER OWNERSHIP, REVOKE, or CREATE OR 
REPLACE on object type "AUDIT POLICY" cannot be processed 
because there 
is an object  "SAMPLE", of type "DATABASE", which depends on it. 
SQLSTATE=42893 
 
 
DB21034E  The command was processed as an SQL statement because 
it was not a valid Command Line Processor command.  During SQL 
processing it returned: 
 
SQL1409N  An audit policy is not associated with the object 
"SAMPLE" of type "DATABASE".  SQLSTATE=5U042

**************************************************************** 
* USERS AFFECTED:                                              * 
* db2audit                                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* This is server side fix.  Upgrade to DB2 version 10.5        * 
* Fixpack 7                                                    * 
****************************************************************

1) Alter the policy so it will not perform any auditing: 
 
alter audit policy db_policy1 categories all status none; 
 
2) IBM can provide a tool to fix the INCORRECT OBJECTNAME issue. 
Please open a PMR with DB2 Support to get the tool. 
 
Use the new tool to replace OBJECTNAME with "CURRENT SERVER" 
 
> ./db2UpdateAuditUse -d trt -a AUDIT5 
Auditpolicyid=100 
DB2UPDATEAUDITUSE completed successfully for database 'trt'. 
 
db2 "select * from SYSIBM.SYSAUDITUSE" 
 
OBJECTNAME     OBJECTTYPE SUBOBJECTTYPE AUDITPOLICYID 
AUDITEXCEPTIONENABLED 
-------------- ---------- ------------- ------------- 
--------------------- 
CURRENT SERVER                                    100 N 
DBADM                   g                         100 N 
SECADM                  g                         100 N 
 
  3 record(s) selected. 
 
 
db2 audit database remove policy 
DB20000I  The SQL command completed successfully.

First fixed in version 10.5 Fixpack 7

SEE LOCAL FIX.

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

04.03.2015
20.01.2016
20.01.2016