Results 1 to 2 of 2

Thread: DB2 Audit Issue

  1. #1
    Join Date
    Oct 2015
    Posts
    4

    Unanswered: DB2 Audit Issue

    We have an audit configuration setup at an instance level (no audit policies defined at database level) as shown below since version 9.5 and we are currently at version10.1.5.
    An incident was discovered recently while ALTERS on a specific table didn't display expected extracts in objmaint.del

    My question below:
    1. To see any ALTER,CREATE,DROP activity on objects (at table level), is it mandatory to have an OBJMAINT policy setup at a database level?
    or
    2. Would the OBJMAINT configured at instance level be applicable to TABLE level audits across all databases under that instance?

    Here are our settings at instance level

    db2audit configure scope audit status success;
    db2audit configure scope objmaint status success;
    db2audit configure scope secmaint status failure;
    db2audit configure scope sysadmin status both;
    db2audit configure scope context status none;
    db2audit configure scope checking status none;
    db2audit configure scope validate status none;

    Thanks
    Mani

  2. #2
    Join Date
    Jul 2013
    Location
    Moscow, Russia
    Posts
    666
    Provided Answers: 55
    Q1: To see any ALTER,CREATE,DROP activity on objects (at table level), is it mandatory to have an OBJMAINT policy setup at a database level?
    A1: Yes

    Q2: Would the OBJMAINT configured at instance level be applicable to TABLE level audits across all databases under that instance?
    A2: Objects at the instance level for the OBJMAINT events are databases and not tables. So, you can see the DROP/CREATE DATABASE events, but not the ALTER/DROP/CREATE TABLE events. May be the object types for the instance level events can be some other, but I've never seen them in these logs.
    Regards,
    Mark.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •