Unable to bring database online on 2nd node in FailSafe and MSCS config

Question

I have a two node cluster running Windows 2003 Server, MSCS, and Oracle Failsafe. I have been unable to bring the database online on Node2. All resources in Cluster Administrator fail over fine and come online except for the Database resource itself. The shared disks, listener, etc, are all online. All resources come online on Node1. When I failover to Node2, the Database Resource fails and posts this error in the Event Viewer:
Oracle Fail Safe encountered an error starting resource DISS.
ORA-01100: database already mounted
The database is not mounted and the database windows service is not running (is set to manual). I can manually start the database thru Windows Services and access it fine. But still unable to bring it online via Cluster Administrator or Oracle Fail Safe Manager.
Any help would be greatly appreciated.
Thanks in advance!

Answer 1

The only message in the event viewer is the ORA-01100 I originally posted.
ORACLE_HOME is set correctly.
Here are the contents of the alert.log:
Fri Sep 04 13:06:21 2009
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 11.1.0.7.0.
Using parameter settings in server-side spfile C:\ORACLE\PRODUCT\11.1.0\DB_1\DATABASE\SPFILEDISS.ORA
System parameters with non-default values:
processes = 150
memory_target = 820M
control_files = "O:\ORACLE\ORADATA\DISS\CONTROL01.CTL"
control_files = "O:\ORACLE\ORADATA\DISS\CONTROL02.CTL"
control_files = "O:\ORACLE\ORADATA\DISS\CONTROL03.CTL"
db_block_size = 8192
compatible = "11.1.0.0.0"
db_recovery_file_dest = "C:\Oracle\flash_recovery_area"
db_recovery_file_dest_size= 2G
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = ""
dispatchers = "(PROTOCOL=TCP) (SERVICE=DISSXDB)"
audit_file_dest = "C:\ORACLE\ADMIN\DISS\ADUMP"
audit_trail = "DB"
db_name = "DISS"
open_cursors = 300
diagnostic_dest = "C:\ORACLE"
Fri Sep 04 13:06:22 2009
PMON started with pid=2, OS id=2892
Fri Sep 04 13:06:22 2009
VKTM started with pid=3, OS id=3932 at elevated priority
VKTM running at (20)ms precision
Fri Sep 04 13:06:22 2009
DIAG started with pid=4, OS id=1280
Fri Sep 04 13:06:22 2009
DBRM started with pid=5, OS id=1084
Fri Sep 04 13:06:22 2009
PSP0 started with pid=6, OS id=648
Fri Sep 04 13:06:22 2009
DIA0 started with pid=7, OS id=1792
Fri Sep 04 13:06:22 2009
MMAN started with pid=8, OS id=3172
Fri Sep 04 13:06:22 2009
DBW0 started with pid=9, OS id=3740
Fri Sep 04 13:06:22 2009
LGWR started with pid=10, OS id=524
Fri Sep 04 13:06:22 2009
CKPT started with pid=11, OS id=2020
Fri Sep 04 13:06:22 2009
SMON started with pid=12, OS id=1068
Fri Sep 04 13:06:22 2009
RECO started with pid=13, OS id=3636
Fri Sep 04 13:06:22 2009
MMON started with pid=14, OS id=3512
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
ORACLE_BASE from environment = C:\Oracle
Fri Sep 04 13:06:22 2009
alter database mount exclusive
Fri Sep 04 13:06:22 2009
MMNL started with pid=15, OS id=2996
Setting recovery target incarnation to 2
Successful mount of redo thread 1, with mount id 739001231
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: alter database mount exclusive
alter database open
Beginning crash recovery of 1 threads
Started redo scan
Completed redo scan
295 redo blocks read, 99 data blocks need recovery
Started redo application at
Thread 1: logseq 134, block 176
Recovery of Online Redo Log: Thread 1 Group 2 Seq 134 Reading mem 0
Mem# 0: O:\ORACLE\ORADATA\DISS\REDO02.LOG
Completed redo application of 0.13MB
Completed crash recovery at
Thread 1: logseq 134, block 471, scn 3797812
99 data blocks read, 99 data blocks written, 295 redo blocks read
Thread 1 advanced to log sequence 135 (thread open)
Thread 1 opened at log sequence 135
Current log# 3 seq# 135 mem# 0: O:\ORACLE\ORADATA\DISS\REDO03.LOG
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
SMON: enabling cache recovery
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is WE8MSWIN1252
Opening with internal Resource Manager plan
Starting background process FBDA
Fri Sep 04 13:06:29 2009
FBDA started with pid=19, OS id=4004
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Fri Sep 04 13:06:29 2009
QMNC started with pid=20, OS id=1132
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Fri Sep 04 13:06:35 2009
Starting background process CJQ0
Fri Sep 04 13:06:35 2009
CJQ0 started with pid=21, OS id=2864
Fri Sep 04 13:06:35 2009
Completed: alter database open
Fri Sep 04 13:06:42 2009
Starting ORACLE instance (restrict)
alter database "DISS" mount exclusive
ORA-1100 signalled during: alter database "DISS" mount exclusive...
Stopping background process FBDA
Shutting down instance: further logons disabled
Stopping background process QMNC
Stopping background process CJQ0
Stopping background process MMNL
Stopping background process MMON
Shutting down instance (immediate)
License high water mark = 3
Waiting for dispatcher 'D000' to shutdown
All dispatchers and shared servers shutdown