16.10 - Rules Validation - Teradata Database

Teradata Database Administration

Product
Teradata Database
Release Number
16.10
Published
April 2018
Language
English (United States)
Last Update
2018-04-26
dita:mapPath
qjg1509413559832.ditamap
dita:ditavalPath
changebar_rev_16_10_exclude_audience_ie.ditaval
dita:id
ujp1472240543947

The following table lists the rules DBQL validates when DBQL logging begins. DBQL checks against the application name, user name, and account string to validate rules.

IF a… THEN DBQL …
user logs on to start a session checks the username, account string, application name, and zone ID (in secure-zoned systems) in the rules cache and also looks for this in the dictionary table.
match is found in the rules cache logs according to any options in the rules table.
match is not found in the rules cache searches for a matching user or account in the Data Dictionary.
match is found in the Data Dictionary creates an entry in the rules cache and logs according to any options in the rules table.
match is not found in the Data Dictionary creates a “do not log” rule in the rules cache but does not perform logging.
“WITH NONE” rule is found creates a “do not log” rule in the rules cache but does not perform logging.
If the account string of a session is changed via the SET SESSION ACCOUNT statement, the system ensures that any rules associated with the user and account string applies when the next query is issued from that session.