Re: Oracle direction on triggers

"Ed Stevens" <nospam_at_noway.nohow> wrote in message news:8qek5vs8psuifc57o8k14smlc8678f7eck_at_4ax.com...
> We have a developing situation I'd like some feedback on.
>
> A few months ago a new application went to production, using an Oracle
> 8.1.7 db on Win2k. This app is partly purchased product, partly
> custom code. Recently, another app, running on DB2 on the mainframe,
> needed to have a copy of the data on one of the tables in this system.
> We settled on using a trigger and the OTG to keep a DB2 table
> populated with changes from the Oracle table. The lead analyst on the
> Oracle app got upset over this approach, claiming it would wreck
> performance. He further stated that "Oracle apps have set a direction
> of moving away from the use of triggers because of performace." Since
> I don't keep up with Oracle Apps (we have none here) I couldn't refute
> it, but it sure sounded specious to me.

On the face of it this sounds pretty specious to me, too, but I confess am not familiar with OTG (I assume this is Oracle Transparent Gateway).

Is this replication synchronous? If so, then presumably the Oracle transaction has to wait for the DB2 transaction to be ready to commit before it can, so we have a 2-phase issue. It seems to me that this could be problematic.

On the other hand, if it's asychronous (i.e. the Oracle app can do its work and commit, leaving any DB2 updates to message queues and so forth), then I doubt if one would expect a problem in real life, unless we were dealing with an extremely high transaction rate.

Does this help?

Regards,
Paul Received on Mon Feb 24 2003 - 15:02:47 CST