The following figure shows the Catalog object definition syntax used in the WHERE clause of the LOGSCAN statement. Use this syntax to select log records based on the type of DB2 catalog object that is affected by the activity reflected in the log record.
For example, you can select all log records that affect storage groups or all log records that affect indexes. Besides the commonly used objects, such as tables and columns, you can also select log records that affect other objects defined in the DB2 catalog, such as plans, packages, collections, and buffer pools.
Use the catalog object definition when you are generating a data definition language (DDL) output file or Catalog Activity report; it is not valid if your log scan specifies any other type of output. By defining a filter that includes catalog activity and generating a Catalog Activity report, you can select information about changes to the DB2 catalog, including changes to DB2 security.
Catalog object definition syntax diagram
To select log records based on a type of DB2 catalog object, Log Master must perform completion processing on DB2 catalog log records. Because of the large number of log records related to the catalog, this processing can cause your job to run longer and require more resources than a job that does not read the DB2 catalog. If you frequently operate on objects stored in the catalog, you can improve performance by creating more frequent image copies of the catalog, or by defining tables in the DB2 catalog with Data Capture Changes (DCC).
| Option | Description |
|---|
| catalogObject | Specifies the type of object in the DB2 catalog. The available objects are as follows: | Object | Description |
|---|
| ALIAS | Selects log records based on whether they reflect changes that affect aliases. | | BUFFERPOOL | Selects log records based on whether they reflect changes that affect buffer pools. | | COLLECTION | Selects log records based on whether they reflect changes that affect collections. | | COLUMN | Selects log records based on whether they reflect changes that affect columns. | | CONTEXT | Selects log records based on whether they reflect changes that affect contexts. | | DATABASE | Selects log records based on whether they reflect changes that affect databases. | | DISTINCT TYPE | Selects log records based on whether they reflect changes that affect distinct types. | | FUNCTION | Selects log records based on whether they reflect changes that affect functions. | | GLOBAL TABLE | Selects log records based on whether they reflect changes that affect global tables. | | INDEX | Selects log records based on whether they reflect changes that affect indexes. | | MASK | Selects log records based on whether they reflect changes that affect column masks. | | PACKAGE | Selects log records based on whether they reflect changes that affect packages. | | PERMISSION | Selects log records based on whether they reflect changes that affect row permissions. | | PLAN | Selects log records based on whether they reflect changes that affect application plans. | | PROCEDURE | Selects log records based on whether they reflect changes that affect procedures. | | ROLE | Selects log records based on whether they reflect changes that affect roles. | | SCHEMA | Selects log records based on whether they reflect changes that affect schemas. | | SEQUENCE | Selects log records based on whether they reflect changes that affect sequences. | | STORAGE GROUP | Selects log records based on whether they reflect changes that affect storage groups. | | SYNONYM | Selects log records based on whether they reflect changes that affect synonyms. | | SYSPRIV | Selects log records based on whether they reflect changes in system privileges. | | TABLE | Selects log records based on whether they reflect changes that affect tables. | | TABLESPACE | Selects log records based on whether they reflect changes that affect table spaces. | | TRIGGER | Selects log records based on whether they reflect changes that affect triggers. | | VIEW | Selects log records based on whether they reflect changes that affect views. |
|
|---|
| IN (catalogObject) | Log Master can select log records based on whether they reflect changes that affect a single type of DB2 object or a set of DB2 objects. The IN keyword indicates a set of objects. Enclose the set of DB2 objects within parentheses, and separate multiple objects with commas. |
|---|
| NOT | Specifies that log records are selected when the DB2 object that they affect does not match any member of a set of DB2 objects. |
|---|
Comments