With a standby database, either physical or logical (Oracle 9i) you get
a failower machine, typically much smaller then the original one. The
problem
is that there isn't much else you can do on that machine. In case of a
logical
standby, you can use it as a report server, but then again, you are
See comments below
RF
Robert G. Freeman
Consultant - TUSC
www.tusc.com
One browser to rule them all, one browser to find them,
One browser to bring them all and into the darkness bind them
In the land of Redmond where the shadows lie.
-Original Message-
To: Multiple recipients
If this is to be a web server kind of application then another possibility
to consider: Transparent Application Failover (TAF)
I think this works well with web applications where the data in the
database(s) isn't constantly changing at a high rate. You have two or more
independent databases
This application will need to tie into Sun one portal, the key items are
web central to provide unit to create content, change pages..etc
undergrades site for class registration, staff pages do other stuff.
Joan
Stephen Lee wrote:
If this is to be a web server kind of application then another
The TAF thing was just another option to consider. I think it works best
when you have a web app over here and databases over there and over there
etc. Sqlnet handles the dirty work of connection and failover management.
And *YOU* handle the dirty work of data management between the multiple
Thanks Robert, Malden and stephen. I am just wondering does master
replication is an option too? As I mentioned earlier, the application
is sun one portal, content based.
Joan
Freeman Robert - IL wrote:
See comments below
RF
Robert G. Freeman
Consultant - TUSC
www.tusc.com
One
CAVEAT: With all the banging around Oracle has done with replication, I
think my knowledge of replication is quickly getting outdated. Keeping that
in mind: In my limited experience with simple snapshot replication, about
the only time you run into difficulties is when you need to replicate at
