The following table is an alphabetical listing of certain operations that have limitations when specified in a BEGIN LOGGING statement.
|When specifying logging of this operation||These conditions apply|
|ALL||Does not include logging of the following operations, because they refer to system level objects that do not support an ON clause:
||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, DROP PROCEDURE, 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:
||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 a list of keywords that represent multiple privileges, see Teradata Vantage™ - SQL Data Control Language, B035-1149.
|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).|
|UDTMETHOD or UDTTYPE||The ON clause must specify DATABASE or USER, and the database or user must be the SYSUDTLIB database.|
|UDTUSAGE||The ON clause must specify one of the following:
|ALTER EXTERNAL PROCEDURE, DROP PROCEDURE, EXECUTE PROCEDURE, and GRANT||The only operations allowed on external procedures.|