About Database Alert Log
The Database Alert Log makes it possible for system administrators and installation
technicians to trace different activities in the database.
Contents
The Database Alert Log uses database triggers, Oracle Audit trails and a Scheduled
Task to transfer data between Audit trail and Database Alert Log.
There are three different ways to write to the Database Alert Log:
- Direct from a PL/SQL Package, usually as an Autonomous transaction.
- From a PL/SQL Package via a database trigger that catches what to log.
- Through Oracle Audit Trail (that holds data in AUD$ table), and is transferred
to Database Alert Log through a Scheduled Task.
Note: Using database triggers and Oracle Audit trail may generate some
overhead.
Essentially, the functionality exists to make trouble shooting and logging easier
if necessary.
It is possible to turn on or off every Database Alert Log Category independent
of each other.
There exists 1 more categories that should be
added.
- Server Errors
This category logs every error that occurs in the database.
Could be used to find errors that occur infrequently.
Uses database trigger.
- DDL Audit
Logs all DDL changes in the database.
- SQL Injection
Logs code that has been trapped as SQL Injection.
Built in as functions in database server code.
- Event Errors
Logs any error that occur when Events are
triggered.
- Alert Log Errors
Logs errors from Oracle Database Alert.
- Intrusions
Logs every failed logon attempt to the database.
Uses Oracle's Audit Trail and Scheduled Task to move data.
- Deployment
Logs timing over installation and upgrades of IFS Applications.
Built in as functions in deployment code.
- Debug
Logs specific occurrences for Debugging purpose.
- In-Memory
Logs what indexes that are removed when removing
analytical indexes for tables loaded to In-Memory.
Links