Re: replication via trigger?

Alerts are blocking mechanisms.
If you fire alertX for updates to tableX, then all updates to tableX will queue on the first update to tableX waiting for it to commit.

--

Jonathan Lewis
Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk

Olaf Naumann wrote in message <88j5qr$oh6$1_at_news.netcologne.de>...
>
>oops that sound a bit complex, since triggers are synchnous. what may help
>is using alerts, since they are asynchronous. idea: define a trigger that
>fires an alert. write a procedure that listens to alerts and copies the
data
>to this other database. (for alerts use the dbms_alert package)
>
>olaf
>
>-----Ursprüngliche Nachricht-----
>Von: chrisstarck_at_my-deja.com [mailto:chrisstarck_at_my-deja.com]
>Gesendet am: Donnerstag, 17. Februar 2000 14:59
>An: comp_database_oracle_server-list_at_news2mail.com
>Betreff: replication via trigger?
>
>I want to replicate a database through trigger to
>have all time a equal database on an hot-stand-by-
>system. Is there a possibility to programm
>a "smart trigger" in the case the hot-stand-by-
>system fails, that the trigger not block the main
>system but give an alert?
>
>That would help me a lot! Thanks in advance!
>Christian S
>
>
>Sent via Deja.com http://www.deja.com/
>Before you buy.
>
>
>
Received on Fri Feb 18 2000 - 12:14:17 CST