Re: CLOB
From: <phil_herring_at_yahoo.com.au>
Date: Tue, 25 May 2010 17:00:10 -0700 (PDT)
Message-ID: <6b1d90ce-2c5c-4ae2-8e01-6b79740cc98b_at_u20g2000pru.googlegroups.com>
On May 26, 1:30 am, The Magnet <a..._at_unsu.com> wrote:
Date: Tue, 25 May 2010 17:00:10 -0700 (PDT)
Message-ID: <6b1d90ce-2c5c-4ae2-8e01-6b79740cc98b_at_u20g2000pru.googlegroups.com>
On May 26, 1:30 am, The Magnet <a..._at_unsu.com> wrote:
> Problem is that we are using a source table with a trigger that will
> update another table on a remote database over a DB link. So, if you
> cannot update, how is this task to be accomplished?
So you have a *trigger* that is going to update a *remote table*. And you're going to write a CLOB.
Maybe you should consider using queues for this. Your trigger can write the change data to a queue in that DB; set up a queue on the remote DB that subscribes to the first queue, and run a batch that reads that queue and applies the change.
- Phil