Re: trace every SQL statement of a specific user
Date: Fri, 7 Mar 2008 01:42:48 -0800 (PST)
> She is not in the binaries directory when she initiates the
> connection. The login.sql needs to be in the directory where SHE
> calls the executable, not necessarily where the executable resides:
> Executables reside here (for example) => c:\myapp\bin
> User calls executable from here => c:\mydata
> The login.sql would then need to be in c:\mydata.
> David Fitzjarrell
the topic starts being quite esoteric:)
what about her doubleclicking the application exe in a file manager? that's what "she" does:).
is there a way to place the login.sql file globally in some location
on a machine so that
perhaps all programs using oracle client software might use/see it? Greetings
K Received on Fri Mar 07 2008 - 03:42:48 CST