This content has been marked as final. Show 14 replies
Please see these docs/links for details.
Understanding Data Auditing in Oracle Application Tables [ID 69660.1]
FAQ (Audit Trail) [ID 107330.1]
Setup & Usage (Audit Trail) [ID 105630.1]
Troubleshooting (Audit Trail) [ID 105624.1]
I Know what's oracle do for Audit , my question is how can i make the audit just for delete operations .What do you mean by standard solution? Please elaborate more.
I have a solution but I want the standard one , I can go to the database and disable the triggers related to add and update.
I want a standard solution
ok. when you want to enable the audit trail
you have to do this
1- go to the audit group , create a new group that hold all tables that you want to do the audit for
2- you enable the owner of your application to be audited from the install window
3- go to the audit table window then select your columns that you want to audit for each table you select
4- run the audit table request
after you run this request oracle creates
1- shadow tables for your selected tables
2 -in non hr table create 3 triggers one for insert , one for update on for delete
3- function and procedure that oracle will use it for the audit reports and triggers
in this way you cant decide the operation that you want to do audit for
I mean you cant just chose delete , or just update , there is no screen or window to chose between the operations.
Really I'm looking for this window or screen , for me using oracle application window is the standard solution.
I dont want to go to the database and disable the insert or update or delete trigger that oracle creates when you ran the audit request
Really I would like to thank you for you attention, but I have read the notes and the system administrator user guide.
The note in the Oracle Metalink just explain what happened in the update operation , just for example to understand the process , it did not mention how can I just do the audit for the update or delete or insert only.
so still I did not have the answer if there is a standard solution for my question .
Employee information meaning the Person or Assignment record?
Date-track is what makes AOL auditing data difficult to interpret. A delete on a table row is quite different to a date-track operation. As part of, say, a 'Delete Next Change', 'Replace Future Changes' or 'Purge', the date-track operation will update or delete multiple table rows. So if you use AOL auditing it is very difficult to interpret a bunch of table operations into actions that users have taken.
Payroll have solved this for you in standard Oracle HRMS through the Payroll Event Model and a set of APIs called the 'Interpreter'. These are used by proration and retropay, as well as other areas across HRMS.
You don't need to be running payroll to use this functionality but you might need to enable the triggers and functional areas if they're not already running.
Once the triggers are capturing events you can then create an Event Group to register your interest in business-level events, such as 'Date-Track Purge' rather than delete row and use the APIs in Pay_Interpreter_pkg to pull back changes in your Event Group.
The payroll User Guides provide all sorts of information on enabling triggers and setting up Event Groups.
If you're looking for a little more background, check out:
HRMS DEVELOPMENT WHITE PAPER - Continuous Calculation (Doc ID 188154.1)
It's written for a payroll process (Continuous Calc) but offers an excellent introduction to the Event Model and Interpreter.