Re: hot to limit sqlldr ?

"Stefan" <stefan_at_dragolov.com> wrote in message news:<1113402433.811868.295760_at_f14g2000cwb.googlegroups.com>...
> ideally you are correct - however, I am hosting an application which
> requires that the application level user have the same username and
> password as the database level user, AND the database level user has to
> have insert/update/delete in order to be able to use the application's
> front end....
> I know it's a horrible design, but that's the way it is....
>
> so the only thing I've been able to think of so far is to create a
> LOGON trigger which kills sessions unless they are made via the
> appropriate client application...
>
> was wondering if there are any other ideas out there...

Simply do not install sqlldr on the clients pc. Easy

--
Sybrand Bakker
Senior Oracle DBA