An initial understanding of Oracle fine-grained Audit (FGA) _oracle
Source: Internet
Author: User
Fine-grained audits (FGA), introduced in Oracle 9i, can record the SCN number and row-level changes to reconstruct old data, but they can only be used for SELECT statements, not for DML, such as update, Insert and DELETE statements. Therefore, for a previous version of Oracle database 10g, using triggers is not an attractive option for tracking user initial changes at the line level, but it is also the only reliable way
The enhancements to the FGA feature in oracle10g enable it to support not only select operations but also DML operations. In Oracle 10g,
The audit has grown from a mere "action recorder" to a "fact-logging mechanism" that captures the behavior of users at a very detailed level, which eliminates your need for manual, trigger-based audits. It also combines standard auditing with FGA tracking, which makes it easier to track database access without considering how it is generated
Through fine-grained audits we can record:
A table was visited between nine and six o'clock in the afternoon in the morning or in Saturday and Sunday
Use an IP address outside of the corporate network
Selected or updated a specific column
Use a specific value for this column
The audit is actually a session of the server process is doing some recursive SQL operations, rather than relying on some background processes, which can be observed from 10046 events.
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.