Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: No future for DB2

Re: No future for DB2

From: Madison Pruet <mpruet_at_comcast.net>
Date: Wed, 3 Aug 2005 20:28:54 -0500
Message-ID: <XOSdnQdADcnB8mzfRVn-2w@comcast.com>

"Mark Malakanov" <markmal_at_rogers.com> wrote in message news:xLydnbH1n-Pl8GzfRVn-tQ_at_rogers.com...
>
> Madison Pruet wrote:
> > At a minimun the replication solution should be able to either prevent
> > triggers from firing on the target if it is populated by a replication
> > apply, with the assumption (and policing) that all of the tables
associated
> > with original transaction is replicated as part of that transaction.
>
> Yes, there is a function that should be called in an updateable MV
> target table trigger DBMS_MVIEW.I_AM_A_REFRESH. It returns FALSE if
> trigger is fired by local changes, and TRUE if trigger is fired by
> replication.
>
Received on Wed Aug 03 2005 - 20:28:54 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US