I've been around lots of failover clusters like these and one of the
challenges that I've seen in these environments is scheduling routine
scheduled tasks. Often, crontab is used to start backups and in a
failover cluster (especially when all nodes are treated equally instead
of having a "primary" and "backup" node) and this poses a problem since
crontab isn't "cluster-aware". This is a great time to get familiar
with the DBMS_SCHEDULER interface that allows you to kick off shell
scripts. That way, you'll always ensure that the backup script will run
on the same node where the DB instance runs since the instance starts
its own backup. Other than that little tidbit, there shouldn't be anything else that would be dramatically different. Just make sure that you put all the pieces of the database on the proper storage locations (locations that will either be failed over or that are available to all nodes). I'd also recommend scheduling a failover test at least a couple times every year just to make sure that you aren't surprised by a non-starting instance during a failover time. Dan DIANNA GIBBS wrote: -- //www.freelists.org/webpage/oracle-l |