Previous Topic: Support for Security Features in DB2 LUWNext Topic: Define DB2 LUW Security Label Components


Define a DB2 LUW Audit Policy

You can create an audit policy to determine what categories you want to be audited; you can apply the policy to other database objects monitor the use of those objects.

Note: This topic applies to DB2 for LUW versions 9.5 and 9.7 only.

To define a DB2 LUW audit policy

  1. Right-click an Audit Policy in the Model Explorer and select Properties.

    The DB2 for LUW Audit Policy Editor opens.

  2. Select an audit policy and work with the following options:

    Note: Click New New icon in property editors to create a new object on the toolbar to create an audit policy. Use the Enter filter text text box to filter a large list of names to locate the one you want to work with.

    Name

    Specifies the name of the audit policy.

    Error Type

    Specifies the error type: Normal or Audit.

    Normal - Errors generated by the audit are ignored and only SQLCODEs for the errors are returned.

    Audit - All errors are returned.

    Generate

    Specifies whether or not to generate DDL for this object during Forward Engineering.

  3. Specify options for audit policy categories on the General tab.

    You can specify a status for each category as follows:

    Both - Successful and failed events are audited.

    Failure - Only failed events are audited.

    None - No events in this category are audited.

    Success - Only successful events are audited.

    All Categories Status (ALL)

    Sets all categories to the same status.

    Other supported categories include:

    • Audit Status (AUDIT)
    • Checking Status (CHECKING)
    • Context Status (CONTEXT)
    • Execute Status (EXECUTE)
    • Execute With Data [check box]
    • Object Maintenance Status (OBJMAINT)
    • Security Maintenance Status (SECMAINT)
    • System Admin Status (SYSADMIN)
    • Validate Status (VALIDATE)
  4. Click the Comment tab and enter any comments you want to associate with the audit policy.
  5. Click the Where Used tab to view where an audit policy is used in the model.
  6. Click the UDP tab to work with user-defined properties for the audit policy.
  7. Click the Notes tab to view history information and view or edit user notes.
  8. Click Close.

    The DB2 for LUW Audit Policy Editor closes.

More information:

Add a Comment in a Property Editor

Add a UDP in a Physical Property Editor