That sounds a lot like materialized views.
On Thu, 2003-08-28 at 08:14, Igor Neyman wrote:
It could be a combination of trigger/pooling.
Trigger writes changes locally into some kind queue table.
The second instance is pooling this queue table (using db link) at
it's own rate without
Hi listers,
=20
Assume that there are two instances in Oracle. Both
instances are on =
different machines and different Oracle versions.
There is a table on =
first instance. Any update on this table should
invoke stored procedures =
on the second instance. This should be real time
based.
For this AQ or possibly streams in 9i would be the best, but there is a
bit of work to get either set up and functioning the way you want. The big
benefit is done right you cant lose a message from one system to the
other.
This is fundamentally EAI integration without the messaging server.
You
It could be a combination of trigger/pooling.
Trigger writes changes locally into some kind queue table.
The second instance is pooling this queue table (using db link) at
it's own rate without affecting transactions against original table.
Also, in this case when network is down, original
