There are no performance issues regarding the actual OAV product as this is stored on our Rackspace servers. However, the Collection Agent and the Collectors are stored on your system. The Collectors are associated to each source database and they read the audit data generated by the auditing mechanisms configured. Because the collectors run on the source host the additional work will impact the load on your database machines.
Oracle stated numbers for the additional overload using 100 Audit records per second are:
- 2% CPU overhead for DBAUD collector type.
- 3% CPU overhead for OASUD collector type.
- 6% CPU overhead for REDO collector type.
We can set-up your database auditing requirements using our 'Audit 'Policies' template that will ensure that you are maximizing your performance and not wasting any of your valuable CPU resources.
Please contact us for more information on how we can help you accomplish your Database Auditing goals!