Disabling Access Logging | Teradata Vantage - 17.20 - Disabling Access Logging with the END LOGGING Statement - Analytics Database - Teradata Vantage

Teradata Vantage™ - Analytics Database Security Administration - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-03-07
dita:mapPath
hjo1628096075471.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
zuy1472246340572

You can use the END LOGGING statement to terminate access logging on any user, action, or object for which one or more logging rules are currently active.

An END LOGGING statement generates an error if a corresponding BEGIN LOGGING statement is not currently in effect for the database name specified in the END LOGGING statement.

Also consider the following END LOGGING characteristics:
  • You cannot omit the BY username clause to apply the END LOGGING to all users.
  • The END LOGGING statement terminates access logging on the database objects included in the statement. If the END LOGGING statement terminates all logging rules for a particular user, database, or object, the system deletes the row from DBC.AccLogRuleTbl.

To disable access logging:

  1. Query the DBC.AccLogRulesV view to display the list of BEGIN LOGGING statements currently in effect:
    SELECT * FROM DBC.AccLogRulesV;
  2. Submit an END LOGGING statement for each BEGIN LOGGING statement in the list that you want to end.
  3. Issue a DROP MACRO statement for DBC.AccLogRule macro if you are ending all logging.
    If you do not issue an END LOGGING statement for every rule in DBC.AccLogRules, access logging continues even if you drop the DBC.AccLogRule macro and reset the database.
  4. Run the tpareset command to set the change.

    For information on use of the tpareset command, see Teradata Vantage™ - Database Utilities, B035-1102.