Oracle failsafe on MSCS

Question

I'm not sure where but I think I missed a configuration somewhere. This is my first time installing and working with all this so I'm sure there is an easy answer I just don't have it.
I am running:
Windows 2008 R2 64bit
Oracle 11g R2 64bit
Failsafe 3.4.2
I have everything installed and "mostly" working.
Everything on the primary node seems to work fine. Everything went fairly smoothly and I was able to create the database and the listener and all that work perfectly on the primary node.
The problem is:
When I fail over to the secondary node the database seems to work and the applications can connect but sqlplus and EM don't. I get the typical:
ORA-12560: TNS:protocol adapter error
What configuration did I miss?
Glenn

Answer 1

How to Configure the 10.2 DB Control in a Failsafe Environment
ID: 452305.1
HOWTO:  PUBLISHED 17-OCT-2008
In this Document
Goal
Solution
References
Applies to:
Enterprise Manager Grid Control - Version: 10.2.0.1 to 10.2.0.3
Information in this document applies to any platform.
Goal
The goal of the document is to provide the steps to configure the DB Console in an Oracle Failsafe environment.
Please note that the solution offered in this document is not certified by Oracle. It's only provided as a workaround for customers who wish to use this setup for the Database Control Console in a failsafe environment. Support for the procedure outlined in this document will be provided on a 'best efforts' approach.
As an alternative to this approach you can use Grid Control Agents to monitor a database in a failsafe environment. For more details please see:
Note 396659.1  How To Setup Grid Control Central Agent Manually in Oracle Failsafe Environment
We assume the following:
- the database binaries are installed on each node on the local disk
- you already have a failsafe group with the database, the listener, disk resource, and virtual
ip/hostname
Note: This is specific for Windows environments using Oracle Failsafe. For setting up the DB Console in Active/Passive clusters on UNIX please use the following note instead:
Note 362524.1 Configure DB Control 10.2 for use in Active/Passive High Availability Environments
Solution
1. Drop the DB Control repository and configuration files on the active node:
<ORACLE_HOME>/bin/emca -deconfig dbcontrol db -repos drop
2. Recreate the DB Control using the virtual hostname:
- in a command window do the following:
set oracle_sid=<your_sid>
set oracle_home=<your_oracle_home>
set oracle_hostname=<virtual_hostname>
cd %oracle_home%\bin
emca -config dbcontrol db -repos create
-- make sure that the virtual host name was picked up by emca (it will display a summary screen
before continuing)
3. Verify that the DB Console works fine and can be accessed using the virtual host name in the URL
4. Stop the DB Console
5. Create a directory path on the group disk resource similar to your oracle home path on the local disk.
For example:
If the oracle home on the local disk is C:\oracle\product\10.2.0\db_1 and the shared disk is D:
then create the following path: D:\oracle\product\10.2.0\db_1
Copy C:\oracle\product\10.2.0\db_1\<hostname_sid> and
C:\oracle\product\10.2.0\db_1\oc4j\j2ee\OC4J_DBConsole_<hostname_sid>
to D:\oracle\product\10.2.0\db_1\<hostname_sid> and respectively
D:\oracle\product\10.2.0\db_1\oc4j\j2ee\OC4J_DBConsole_<hostname_sid>
Remember to change the values enclosed in <> with those in your environment.
6. Delete the following directories from the local disk
C:\oracle\product\10.2.0\db_1\<hostname_sid>
C:\oracle\product\10.2.0\db_1\oc4j\j2ee\OC4J_DBConsole_<hostname_sid>
7. Create NTFS junction points from the local disk to the shared disk (these work like symbolic
links on UNIX) . It is your responsibility to create these.
You can find a brief guide as well as some tools that will help you create them at:
http://en.wikipedia.org/wiki/NTFS_junction_point
http://www.microsoft.com/technet ... dDisk/Junction.mspx
Important: Please note that this functionality is not certified nor supported by Oracle. Make sure you understand the
implications. Especially don't delete the junction points from Windows Explorer !!
In the end you should have the junction points on the local disk (with the same names as the
original directories) that would point to the directories you copied on the shared disk.
8. Start the DB Console service and verify that everything is still working fine.
9. Stop the DB Console service.
10. Move the Fail Safe group to the 2nd node.
11. Once the database is started, create the DB Console configuration files on the 2nd node:
<ORACLE_HOME>/bin/emca -config dbcontrol db
12. Stop the DB Console
13. Delete the created configuration files from the local disk:
C:\oracle\product\10.2.0\db_1\<hostname_sid>
C:\oracle\product\10.2.0\db_1\oc4j\j2ee\OC4J_DBConsole_<hostname_sid>
14. Create junction points from the local disk to the directories already located on the shared
disk.
15. Start the DB Console service and verify that is working fine.
16. Add the DB Console service as a resource to the fail safe group and put dependencies on the
database and listener services.
17. Perform a fail over and see if everything works fine.
References
Note 298238.1 - Oracle10g Grid Control with Oracle Fail Safe
Note 362524.1 - Configure DB Control 10.2, 11g for use in Active/Passive High Availability Environments
Note 396659.1 - How To Setup Grid Control Central Agent Manually in Oracle Failsafe Environment
Keywords
EMCA ; DB~CONTROL ; FAILSAFE ; DBCONTROL ; ENTERPRISE~MANAGER ;