ORA-01105: mount is incompatible with mounts by other instances ORA-19808: recovery destination parameter mismatch

Please check both db_recovery_file_dest and  db_recovery_file_dest_size parameters . In my case db_recovery_file_dest_size is different . See the below details



[oracle@XXXXXXXX02 ~]$ srvctl start instance -d XXXXX  -i XXXXX2

PRCR-1013 : Failed to start resource ora.XXXXt.db
PRCR-1064 : Failed to start resource ora.XXXX.db on node XXXXXXXX02
CRS-5017: The resource action "ora.XXXX.db start" encountered the following error:
ORA-01105: mount is incompatible with mounts by other instances
ORA-19808: recovery destination parameter mismatch  For details refer to "(:CLSN00107:)" in "/u01/app/grid/11gR2/log/XXXXXXXX02/agent/crsd/oraagent_oracle/oraagent_oracle.log".
CRS-2674: Start of 'ora.XXXXX.db' on 'XXXXXXX02' failed

-- Then I tried to Start Instance through Sqlplus

SQL> startup mount
ORACLE instance started.

Total System Global Area 2.1379E+10 bytes
Fixed Size                  2237776 bytes
Variable Size            1.1341E+10 bytes
Database Buffers         9999220736 bytes
Redo Buffers               36098048 bytes
ORA-01105: mount is incompatible with mounts by other instances
ORA-19808: recovery destination parameter mismatch

-- Still No luck 

-- Let check

1)Instance 1


SQL> show parameter recovery

NAME                                        TYPE       VALUE
-------------- ---------------------- ----------- ------------------------------
db_recovery_file_dest                      string    
db_recovery_file_dest_size                 big integer  32G

2)Instance 2


SQL> show parameter recovery

NAME                                        TYPE       VALUE
-------------- ---------------------- ----------- ------------------------------
db_recovery_file_dest                      string    
db_recovery_file_dest_size                 big integer  32G


-- Found the Problem . When I changed db_recovery_file_dest  to unset  the Second instance is down. Due to when Another instance is up you cant start up the another instance. So we need to stop and start database it will fix the issues.

Terminal> srvctl stop instance -d DBname -i Instance_name


Then again i tried to start first instance and it is successfully started.

Terminal>srvctl start instance -d DBname -i Instance_name


-- Check Status

 srvctl status database -d XXXXX
Instance  XXXXX1 is running on node  XXXXXXXXX01
Instance  XXXXX2 is  running on node  XXXXXXXXX02