RE: Fw: OT - Getting fired for database oops

And protect/audit your login.sql and glogin.sql (on the oracle server side
in particular) otherwise some bad person might inject "grant dba to public"
into it without you noticing it :-)

Andre

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Jack van Zanen
Sent: zaterdag 23 mei 2009 12:14
To: tomdaytwo@xxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: Fw: OT - Getting fired for database oops

create a login.sql in the location of sqlpath variable

that I believe will be called whenever you do connect or login

Jack

2009/5/22 Thomas Day <tomdaytwo@xxxxxxxxx>:
> Thanks to all who replied.  I guess that I'll need to upgrade my client.
> None of the techniques offered worked and there doesn't seem to be a 
> login.sql (or one that I can find).
>
> I'll try to remember this when I do upgrade.



--
Jack van Zanen

-------------------------
This e-mail and any attachments may contain confidential material for the
sole use of the intended recipient. If you are not the intended recipient,
please be aware that any disclosure, copying, distribution or use of this
e-mail or any attachment is prohibited. If you have received this e-mail in
error, please contact the sender and delete all copies.
Thank you for your cooperation
--
http://www.freelists.org/webpage/oracle-l


--
http://www.freelists.org/webpage/oracle-l

Other related posts: