Maintaining a mirrored database at a remote site

What is the best approach for maintaining a mirrored image of an Oracle database at a remote site, purely for disaster recovery? We need the ability to switch users to the remote site database (on the network) with a minimum of downtime. This is a TCP/IP network running Oracle 7.x under Solaris.

The approaches I see are using triggers to keep the two databases in synch, or using the Archive log files to apply changes at the remote site.

The trigger approach would require two-phase commit and would cause both databases to hang if the network fails.

The archive log mode would not be a "hot" mirror, but more of a "warm" mirror, because it would always be behind the other database by the size of an archive log file.

Any other approaches that I'm missing? Is anyone doing anything similar, that you'd like to share.

Thanks for your help.

-- 
Brian Fitzpatrick
bmf_at_dlogics.com