I wrote/revamped an article yesterday called Auditing in Oracle 10g Database Release 2. Most of the information was already present on the site, but it was spread across several articles including an 8i article and several new features articles for 9i and 10g. Rather than write a small article on the XML audit trail in Oracle 10g Release 2, I thought I would bring the whole lot up to date.
One point I spotted was an unusual change in the AUDIT_TRAIL parameter. In 10g Release 1 there was an allowed value of DB_EXTENDED, which indicates that the audit records should go to the DB audit trail and the SQL_TEXT and SQL_BIND columns should be populated. In Release 2 this has been changed to DB,EXTENDED. Can’t see the point in this change myself. Personally, I would not have been offended by XML_EXTENDED, rather than XML,EXTENDED… 🙂
Whatever…
Cheers
Tim…
