Re: tracing oracle filesystem access

  • From: Charlotte Hammond <charlottejanehammond@xxxxxxxxx>
  • To: "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
  • Date: Thu, 12 Jan 2006 02:52:37 -0800 (PST)

Hi Max,

I agree with Niall, at least if it's possible to
change the code.

One thing that you might also want to consider whilst
checking dependencies is to cross-reference these with
the timestamps of files changed on your server. 
Depending on the application and how much other
activity is happening on your server, unix "find" may
not produce too much noise to manually sift through. 
Otherwise you could consider using something like
tripwire.

Charlotte

>What version are you on? If you can I'd strongly
suggest you move to using directory objects and then
set utl_file_dir to null.
>
>As for auditing I like the dependency idea suggested
elsewhere. It might be a good time to ensure that each
source code file gets a header detailing prupose,
dependencies and so on...
>
>
>
>--
>Niall Litchfield
>Oracle DBA
>http://www.niall.litchfield.dial.pipex.com

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
--
//www.freelists.org/webpage/oracle-l


Other related posts: