RE: auditing code changes ?
- From: "Hostetter, Jay M" <JHostetter@xxxxxxxxxxxxxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 2 Oct 2008 14:18:51 -0400
This implict compilation also generates records in the database audit
trail (false positives) -- Which can leave a DBA scratching his head
when he knows that the user listed in the audit record doesn't have the
rights to issue DDL on the given view.
Jay
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Jared Still
Sent: Thursday, October 02, 2008 1:28 PM
To: dofreeman@xxxxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: auditing code changes ?
On Thu, Sep 25, 2008 at 5:48 AM, Freeman, Donald <dofreeman@xxxxxxxxxxx>
wrote:
I believe you can at least check dba_objects and see the
last_compile_time. Won't tell you who did it though.
Relying on LAST_DDL_TIME can be kind of tricky, as it can be
indirectly altered by a user other than the one that made the change.
Consider that a view is created on a table.
The table is then modified by adding a column.
The view is now invalidated, and the next time a user queries it
the view will be recompiled.
**DISCLAIMER
This e-mail message and any files transmitted with it are intended for the use
of the individual or entity to which they are addressed and may contain
information that is privileged, proprietary and confidential. If you are not
the intended recipient, you may not use, copy or disclose to anyone the message
or any information contained in the message. If you have received this
communication in error, please notify the sender and delete this e-mail
message. The contents do not represent the opinion of D&E except to the extent
that it relates to their official business.
Other related posts:
