Valid in: SQL, ESQL
The Disable Security_Audit statement enables the security administrator to turn off security logging for the specified type of security event. To turn security logging on, use the enable security_audit statement.
The Disable Security_Audit statement has the following format:
[EXEC SQL] DISABLE SECURITY_AUDIT audit_type | ALL;
Specifies the type of information to log, as follows:
Disables logging of all security events generated by create security_alarm statements issued on tables.
Disables logging of all types of access by all users to all database objects, including use of the ckpdb, rollforwarddb, and auditdb utilities.
Disables logging of all create dbevent, raise dbevent, register dbevent, remove dbevent, and drop dbevent statements.
Disables logging of all access to location objects (create location, alter location and drop location statements) by all users.
Disables logging of all access to database procedures (create procedure and drop procedure statements and procedure execution) by all users.
Disables logging of role events (set role statement with -r flag)
Disables logging of rule events (create rule, drop rule, and firing of rules)
Disables logging of all types of access by all users to all security-related objects.
Disables logging of all types of access by all users to all tables.
Disables logging of all changes to user and group information, including runtime verification of user and group names.
Disables logging of all types of access by all users to all views.
Disables logging of all types of access by all users to all events that dominate specific security audit labels.
Disables logging of all types of access by all users to all row-level events.
Disables logging of all types of access by all users to all the detail information for querytext events.
Disables logging of all types of access by all users to violations of resource limits.
Disables logging of all types of security events.
After disabling security logging, the DBMS Server continues to log security events for users that have the AUDIT_ALL privilege. (To disable auditing for users that are assigned the AUDIT_ALL privilege, use Ingres configuration tools, described in the System Administrator Guide.)
You cannot use host language variables in an embedded Disable Security_Audit statement.
You must have the maintain_audit privilege and be working in a session that is connected to the iidbdb.
The Disable Security_Audit statement locks pages in the iisecuritystate system catalog.
The following example turns off logging of database events:
disable security_audit dbevent;