Call: +44 (0)1904 557620 Call

Pete Finnigan's Oracle Security Weblog

This is the weblog for Pete Finnigan. Pete works in the area of Oracle security and he specialises in auditing Oracle databases for security issues. This weblog is aimed squarely at those interested in the security of their Oracle databases.

[Previous entry: "CPU July 2005 and CPU October 2005 have problems!!"] [Next entry: "A sample package to manipulate LDAP"]

Nice post about LOG ERRORS potential performance issue

I saw Mark's post this evening titled - (broken link)Performance Issues with DML Error Logging and Conventional Path Inserts and read it with interest. The LOG ERRORS feature was added in 10g release 2 as a way to log error rows for most DML statements to a table called ERR$_{TABLE_NAME} in the background instead of the DML failing. I have not had a chance to look at this feature in detail yet but I have planned to do so as I see it as a useful feature for security in the area of auditing. When I first read about it i saw that it could have a use for critical tables to capture any error rows. In some few cases of SQL injection or malicious use of a database someone may be guessing structures of objects and attempting to update or insert data. This could be a useful way to correlate these types of actions. Anyway Marks post is quite useful and worth a read.