Versions Compared

Version Old Version 1 New Version Current
Changes made by

Sidney Chen

Ben

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Scroll ignore
scroll-viewporttrue
scroll-pdftrue
scroll-officetrue
scroll-chmtrue
scroll-docbooktrue
scroll-eclipsehelptrue
scroll-htmltrue
scroll-epubtrue

Open in new tab

About Collectors

Insert excerpt
Collector Method
Collector Method
nameabout

...

  • The DB2 user that the collector will be using must have select access to the following tables

    1. syscat.tables

    2. syscat.views

    3. syscat.columns

    4. syscat.procedures

    5. syscat.functions

    6. syscat.roleauth

    7. syscat.tableauth

    8. sysibm.sqlforeignkeys

Enabling DB2 Audit

To capture usage information audit needs to be enabled in db2.

See https://www.ibm.com/docs/en/db2/11.1?topic=facility-audit-policies

KADA audit policy guidelines

  1. KADA recommending to start using the WITHOUT DATA directive to limit logging. However if dynamic sql is used WITH DATA may need to be enabled.

  2. KADA only requires the successful EXECUTE events

Code Block
CREATE AUDIT POLICY KADA CATEGORIES EXECUTE WITHOUT DATA STATUS SUCCESS ERROR TYPE NORMAL COMMIT
AUDIT DATABASE USING POLICY KADA COMMIT

After the logs are captured they need to decoded and loaded into db2 tables. KADA will extract the usage information from the audit tables. Follow the guide https://www.ibm.com/docs/en/db2/11.1?topic=logs-creating-tables-db2-audit-data

...

Step 2: Create the Source in K

...