RE: Fw: OT - Getting fired for database oops

From: Andre van Winssen <>
Date: Sat, 23 May 2009 19:42:21 +0200
Message-ID: <002301c9dbcd$d35d8570$7a189050$_at_com>

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 :-)


-----Original Message-----
From: [] On Behalf Of Jack van Zanen
Sent: zaterdag 23 mei 2009 12:14
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


2009/5/22 Thomas Day <>:
> 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

Received on Sat May 23 2009 - 12:42:21 CDT

Original text of this message