IBM Support

Guardium - zDB2 not logging database name for ALTER events captured

How To


Summary

The reporting of 'blank' database name for some events in Guardium STAP for Db2 is normal as it is a software limitation.

The database name is not reported(captured) for Db2 Command, Set Current SQLID, operations involving a global temporary table, and CREATE <object> where <object> is a PROCEDURE, FUNCTION, and object types because in Db2, these events are not associated with a database.
When reviewing the excel report, the events with blank database name are expected.

Similar to CREATE <object> and DROP <object> events, the Database Name is not collected for ALTER <object>.
It is expected that the Database Name would be empty or blank for the ALTER events.

The following is an abbreviated list that contains some of the more common statements with unavailable database names:

SET: CURRENT/SCHEMA/PATH/etc.,
UTILITY: CHECK, COPY, DIAGNOSE REPAIR, QUISCE, RUNSTATSDB2 COMMANDs: BIND, REBIND, DISPLAY, STA, STO, ACCESS, TERM.
COMMIT
REVOKE
GRANT

Any event from a GLOBAL TEMP TABLE
Any event completing with a negative SQLCODE.

BIND
REBIND
CREATE <object>
DROP <object>
ALTER <object>

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"ARM Category":[{"code":"a8m0z0000000CdpAAE","label":"z\\OS"}],"ARM Case Number":"TS007290480","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"All Versions"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
17 November 2021

UID

ibm16517078

Page Feedback