Real-time replication

Oracle is running ads claiming the ability to do "real-time replication". This is supposedly keeping a copy of a database at a remote site, synchronously updated. But in the event of a system or communication failure, all transactions are stored locally and then forwarded after the problem is fixed.

Is this a real current feature, and if so, how is it done? From the manuals, the only way I can see to do this is to create triggers on every table that send all updates to remote tables. Handling multiple updates and storeing them in the event of failures would seem to make this a very complex and messy (and probably inefficient) approach.

The correct solution to this problem is integrated into the logging and recovery mechanisms.

Can anyone explain what Oracle is talking about here? Thanks.

-- 
Jonathan Edwards				edwards_at_intranet.com
IntraNet, Inc					617-527-7020