Oracle Database Audit

Sawmill plug-ins allow Sawmill to read ASCII text based logs that are saved to a folder Sawmill can read locally (including mapped/mounted filesystems) or available remotely via (S)FTP and HTTP. Additionally an ODBC connection to an Oracle or MSSQL instance is possible. Alternately (or for advanced users) there is a command line option that allows a script or program to feed data into the Sawmill processing engine.

This plug-in provides analysis support within Sawmill for the above named log format. Using this plug-in Sawmill will be able to read and interpret log files in their original format and perform analysis, reporting and alerting based on the data contained within them. If Sawmill does not perform quite as expected it is possible the original vendor has changed the logging specification. Contact providing details and a sample of the log file.

During importing of log data the following fields are stored in the Sawmill database for subsequent processing and report generation:

Back to All Formats List

Numeric Fields

  • events

Non-Numeric Fields

  • date/time
  • session ID
  • entry ID
  • statement
  • user ID
  • terminal
  • action
  • return code
  • comment_text
  • object creator
  • object name
  • session actions
  • session thread ID
  • OS user ID
  • audit file
  • oracle release
  • JServer release
  • oracle home
  • system name
  • node name
  • release
  • version
  • machine
  • instance name
  • redo thread
  • oracle process ID
  • unix process ID
  • image
  • database user ID
  • privilege
  • status