Oracle Consulting Oracle Training Oracle Support Development
Home
Catalog
Oracle Books
SQL Server Books
IT Books
Job Interview Books
eBooks
Rampant Horse Books
911 Series
Pedagogue Books

Oracle Software
image
Write for Rampant
Publish with Rampant
Rampant News
Rampant Authors
Rampant Staff
 Phone
 800-766-1884
Oracle News
Oracle Forum
Oracle Tips
Articles by our Authors
Press Releases
SQL Server Books
image
image

Oracle 11g Books

Oracle tuning

Oracle training

Oracle support

Remote Oracle

STATSPACK Viewer

Privacy Policy

 

   
 

Oracle Tips by Burleson

Chapter 8 General Oracle Auditing

  • Ideally, three months worth of audit data should be available. Therefore, every month, the oldest month should be archived and purged. For instance, on July 31st, the data for April should be archived and purged off. Data for May, June and July should be in aud$ table.
     

  • There will be a small period of inactivity.
     

  • The redo and undo generation should be minimal.
     

  • The archived data should be available for query on request. A small amount of time can be allowed between the request and the expectation for delivery of the data.
     

  • Existing reports based on the data dictionary views such as dba_audit_session are already built. The report should not have to be modified to query the archived data.

Design

These requirements seem reasonable for a security and accountability conscious database implementation. Next, we will see how to set this up.

  1. First we will decide on a naming convention for the tablespaces and tables. Since the purge and archival routine has to run every month, we will name tables with the month and year, e.g. AUD<yy><mm>, where <yy> is the two-digit year and <mm> is the two-digit month when the data is being archived. The routine run at the end of September 2003 will archive the data from June 2003 and therefore create a table named AUD0306 in tablespace AUD0306.
     

  2. Every month we create a new tablespace, which should be placed in a low throughput and low cost filesystem, say /u200.
     

  3. Next, we will create a table to hold the data from the table aud$ for the entire month 3 months ago, e.g. of June, if this is run in September. The table is created in NOLOGGING mode to regenerate minimal redo and undo. In this example this table is named AUD0306.


The above text is an excerpt from the bestselling book: Oracle Privacy Security Auditing It's only $39.95 and has an download of working security scripts:

 

This is the only authoritative book on Oracle Security, Oracle Privacy, and Oracle Auditing written by two of the world’s leading Oracle Security experts.

This indispensable book is only $39.95 and has an download of working security scripts:

 

http://rampant-books.com/book_2003_2_audit.htm

 


Download your Oracle scripts now:

www.oracle-script.com

The definitive Oracle Script collection for every Oracle professional DBA

 

Linux Oracle commands syntax poster

ION Oracle tuning software

Oracle data dictionary reference poster



Oracle Forum

BC Oracle consulting support training

BC remote Oracle DBA   

 

   

 Copyright © 1996 -2016 by Burleson. All rights reserved.


Oracle® is the registered trademark of Oracle Corporation. SQL Server® is the registered trademark of Microsoft Corporation. 
Many of the designations used by computer vendors to distinguish their products are claimed as Trademarks