I have related questions regarding Oracle software and Oracle executables (e.g., Pro*C) install in the following...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
environments: A. Compaq Tru64 UNIX v4.0F B. 2-node ASE cluster v1.6 C. RA8000 shared SCSI (AdvFS; several RAIDed disks) D. normal operation: Oracle7 and Oracle8 databases and Pro*C apps running on primary node E. OPS not used
I thought you might be able to comment on/answer a few questions or know a colleague who has had Oracle/ASE Failover-Clustering/RAID experience. The shared disks are attached to only one server/node at a time. Oracle database files reside on shared disks. At failover, via configured STOP and START scripts, the databases are shut down and disks re-mount on backup node; and databases re-started on backup node. Also, Pro*C apps are stopped on primary node and re-started on backup node by the same failover STOP and START scripts. Failover and the single Disk Service that causes the failover is fairly straightforward if Oracle software (e.g., Oracle7, Oracle8, Oracle Developer v6.0) are installed on each node separately; i.e., on local disks--and I tend to want to install Oracle software (Oracle7, Oracle8, Oracle Developer, etc.) on each set of local/private disks per each node. Am I correct in thinking that for a single install of all required Oracle software on the shared disks; failover of databases and apps will not function without special configuration; e.g., multiple ASE services, multiple Oracle Homes on the shared disks, etc.?
It sounds like you've developed quite the custom configuration. This type of architecture can sure test one's mettle.
To my knowledge, Oracle Corp. does not officially support shared disks for both the RDBMS software and the database files. There have been many instances where one has gotten the whole thing to work. So I know that your current direction is plausible and can be accomplished. But keep in mind that Oracle may not support certain technical issues should you run into problems. Their first response may be something like "We do not support that feature. Please change your configuration."
Installing the Oracle software on shared storage will be more complicated. It is easier to install separately on each of the two systems.
The only writeable file in the ORACLE_HOME subdirectory that is updated when running an Oracle database is the sgadef
Now all of this assumes that you are not trying to start both database instances against the same datafiles at the same time. Unless you run Oracle Parallel Server, you will not be able to run multiple instances against the same database.
Again, others have gotten this to work on shared or networked drives. But Oracle does not support this configuration. Your best bet would be to install them locally.
For More Information
- What do you think about this answer? E-mail us at editor@searchDatabase.com with your feedback.
- The Best Oracle Web Links: tips, tutorials, scripts, and more.
- Have an Oracle tip to offer your fellow DBA's and developers? The best tips submitted will receive a cool prize--submit your tip today!
- Ask your technical Oracle questions--or help out your peers by answering them--in our live discussion forums.
- Ask the Experts yourself: Our Oracle guru is waiting to answer your toughest questions.
Dig Deeper on Oracle database design and architecture
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.