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
The DB2 for LUW Audit Policy Editor opens.
Note: Click New 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.
Specifies the name of the audit policy.
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.
Specifies whether or not to generate DDL for this object during Forward Engineering.
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.
Sets all categories to the same status.
Other supported categories include:
The DB2 for LUW Audit Policy Editor closes.
Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |