RE: Sparky auth file

Yes and no. If I remember correctly (it's been a few months now), the lock on the trace file is probably a shareable write lock (RMS). So you can read/copy the file, but not open it for write/append. Changing the requested access on the open of the file may solve this. Someone correct me if I'm wrong...

Yes, some of do miss VMS, Mladen! :) <zipping up flame-proof suit>

Rich

Rich Jesse                           System/Database Administrator
rjesse_at_qtiworld.com                  Quad/Tech Inc, Sussex, WI USA

> -----Original Message-----
> From: Gudmundur Bjarni Josepsson [mailto:gbj_at_index.is]
> Sent: Tuesday, July 15, 2003 5:35 AM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Sparky auth file
>
>
> This was solved offline by examining the setup at one of my customers'
> site which has the same configuration of VMS, Oracle and Perl as Barb
> listed.
>
> Barb changed the setting of user_dump_dest to point to the actual
> directory that was defined in the hotsos.auth file. For some
> reason the
> logical was not resolved correctly. I am not proficient enough in VMS
> to explain that behaviour further.
>
> To save any future users of Sparky and VMS a few minutes of
> frustration
> I'd like to point out that you must remember to quit your
> session before
> Sparky can pull the trace file over to your PC. VMS does not release
> the file lock on the trace file even if you stop tracing.
Received on Tue Jul 15 2003 - 10:43:24 CDT