Re: Running with _system_trig_enabled set to false

From: Paul Brewer <paul_at_paul.brewers.org.uk>
Date: Tue, 28 Jan 2003 21:03:38 -0000
Message-ID: <3e36fcee_1@mk-nntp-1.news.uk.worldonline.com>

"Mark D Powell" <Mark.Powell_at_eds.com> wrote in message news:2687bb95.0301280730.2f50b15e_at_posting.google.com...
>
> Joe, if you have metalink support look up the following documents:
> (bug no) 2187432, Doc Id 143639.1, 222467.1, and 2670738.1.
>
> The bug appears to match your problem since it appears to relate to
> JAVA code.
>
> As far as turning off database event triggers goes: This is a feature
> of Oracle that you do not have to use and if your shop does not now or
> intend to use the feature then turning it off should be fine.
>

I would be very wary of running in this mode.

We are on 8.7.1.4 and have a THIRD_PARTY three-tier application. All the developers know the Oracle Username/Password which the application server uses to connect to the database - and it would be useless to change it.

All the business rules are in the app. There are no constraints in the database (other than primary keys) and I have *no* influence here.

The best I've been able to do so far is to restrict that Oracle username to logging in from named terminals (i.e. the application servers), using an after_event logon trigger owned by SYSTEM.

Any suggestions would be welcomed.

Regards,
Paul Received on Tue Jan 28 2003 - 15:03:38 CST