asked on

Database mount ID mismatch

There was some kind of hardware problem where the NAS switch failed. This was resolved, but when the standby was brought up again i'm getting these messages in the alert_log of primary.

Wed Dec 16 19:51:19 2009
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[71]: Assigned to RFS process 19204
RFS[71]: Database mount ID mismatch [0x9d030fd2:0x9d02cab6]
RFS[71]: Not using real application clusters
Wed Dec 16 19:51:19 2009
Errors in file /u01/app/oracle/admin/BB600/udump/bb60_rfs_19204.trc:
ORA-16009: remote archive log destination must be a STANDBY database
Wed Dec 16 19:56:19 2009
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[72]: Assigned to RFS process 19619
RFS[72]: Database mount ID mismatch [0x9d030fd2:0x9d02cab6]
RFS[72]: Not using real application clusters
Wed Dec 16 19:56:19 2009
Errors in file /u01/app/oracle/admin/BB600/udump/bb60_rfs_19619.trc:
ORA-16009: remote archive log destination must be a STANDBY database

What do i need to do to resolve these errors?
~

ASKER CERTIFIED SOLUTION

logictank

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

xoxomos

ASKER

Thanks. I saw something like that on google and i'm 100% certain that will work. If that was correct, and i need only change that parameter on standby, that would be much better. Right now i'm waiting on Oracle.
Seems like years later and they still may be '... stuck on this one'. I should have followed that post.
As I recall, i set the parameter that way for failover capability or whatever so that the standby, acting as primary, could send archives to whatever was acting as standby.

xoxomos

ASKER

Mil gracias :-)

xoxomos

ASKER

So far all Oracle is saying is '.... thank you for sending...please send again'. :-)