Requirements for Logging Certain Operations and Objects in Combination

The following table is an alphabetical listing of operations that have limitations when specified in a BEGIN LOGGING statement.

Operations to Log	Limitations
ALL	Does not log the following operations, which refer to system level objects that do not support an ON clause: CREATE PROFILE CREATE ROLE DROP PROFILE DROP ROLE
CREATE DATABASE CREATE MACRO CREATE TABLE CREATE VIEW CREATE USER DROP DATABASE DROP USER	The ON clause can only specify a database or user.
DROP TABLE	The logging also includes ALTER TABLE, which requires the DROP table privilege.
DROP MACRO or DROP VIEW	Also includes logging of REPLACE for the specified object.
DROP, EXECUTE or GRANT	The only operations allowed if the ON clause specifies a macro or procedure.
DUMP, RESTORE or CHECKPOINT	Are not allowed if the ON clause specifies a VIEW.
The single keyword representation of multiple SQL privileges, for example: TABLE VIEW MACRO TRIGGER PROFILE USER PROCEDURE ROLE FUNCTION AUTHORIZATION GLOP	Logs all the privileges covered by the keyword. For example, specifying TABLE as the logging operation logs CREATE TABLE, ALTER TABLE, and DROP TABLE. For more information, see Granting Multiple Privileges with a Single Keyword.
CREATE FUNCTION, DROP FUNCTION, EXECUTE FUNCTION, ALTER FUNCTION, or GRANT	The only operations that can be specified if the ON clause specifies a FUNCTION (internal or external functions).
ALTER EXTERNAL PROCEDURE, EXECUTE PROCEDURE, and GRANT	The only operations allowed on external procedures.

Requirements for Logging Certain Operations and Objects in Combination - Teradata VantageCloud Lake