|
|
|
|
|
|
|
|
|
| Previous | Next | Contents | Index | Navigation | Glossary | Library |
Whenever you choose to audit the actions of users of the system you are deciding to keep the details of all the transactions that take place. This includes 'before' and 'after' details as well as the details of who made the change and when.
Turning Audit on has no noticeable effect on the performance of the system and users will not be aware of any extra delay in committing their transactions.
Attention: In normal use the auditing of data can soon generate large volumes of audit data, which even when stored in a compressed format will continue to grow in size until you reach the limits imposed by your environment. If you reach the limits during active use then users will be unable to use the system until you remedy the problem.
You are strongly advised to consider the scope of your audit activities and how you will use the data you accumulate. Also you should consider how often you will report on the audit data, and when you will archive and purge your audit data.
If you need more advice on this you should contact your Oracle Support representative.
The following tasks are the responsibility of your System Administrator.
If you have installed more than one Oracle Application you can audit across multiple installations. For Oracle Training Administration you should enable auditing for the OTA user and the APPLSYS user.
See: Audit Installations Window
With Oracle Applications you can define the level of detail you want to audit. You define the individual fields of each record that you want to audit.
See: Audit Tables Window
You can define one or more Audit Groups for your installation. You might find this useful if you have more than one Oracle Application installed.
See: Audit Groups Window
To start the AuditTrail activity you must submit the Activate AuditTrail Update Tables Process.
See: Submitting a Request
| Previous | Next | Contents | Index | Navigation | Glossary | Library |