![]() You can designate a different tablespace, including one that is encrypted, by using the DBMS_AUDIT_MGMT.SET_AUDIT_TRAIL_LOCATION procedure. ![]() In contrast, changes to schema object audit options become immediately effective for current sessions.īy default, audit trail records are written to the AUDSYS schema in the SYSAUX tablespace. However, any modifications (with respect to the statement audit option, privilege audit option, and audit conditions) to the existing unified audit policy definition using ALTER AUDIT POLICY statement will take effect in the subsequent sessions of the users on whom that policy is enabled. This holds true even when the unified audit policy gets disabled as well. When an unified audit policy is created and enabled, it will take effect immediately in the on-going session of the user on whom that policy is enabled without requiring that user to restart the database session. Statement and privilege audit options from unified audit policies that are in effect at the time a database user connects to the database remain in effect for the duration of the session. That is, even if a user transaction is rolled back, the audit trail record remains committed. The generation and insertion of an audit trail record is independent of the user transaction being committed. If the database version does not support partitioning, then the internal table is a regular, non-partitioned table. The partitioned version of this table is based on the EVENT_TIMESTAMP timestamp as a partition key with a default partition interval of one month. In this case, you can modify the partition interval of the table by using the DBMS_AUDIT_MGMT.ALTER_PARTITION_INTERVAL procedure. If the version of the database that you are using supports partitioned tables, then this internal table is a partitioned table. If you had migrated to unified auditing in Oracle Database 12 c release 1 (12.1), then you can manually transfer the unified audit records from the SecureFile LOBS to this internal table. In the previous release, the unified audit records were written to SecureFile LOBs. To improve read performance of the unified audit trail, the unified audit records are written immediately to disk to an internal relational table in the AUDSYS schema. Oracle Database individually audits SQL statements inside PL/SQL program units, as necessary, when the program unit is run. You can disable unified auditing from the container database (CDB) root only, not for individual pluggable databases (PDBs). You can include the unified audit trail in Oracle Database Pump export and import dump files.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |