dg的alert日志出现Heartbeat failed to connect to standby 'primaryorcl'. Error is 16009

清疚 2022-08-10 15:38 165阅读 0赞

dg的alert日志出现Heartbeat failed to connect to standby 'primaryorcl'. Error is 16009  
主库：  
RFS\[80\]: Assigned to RFS process 25039  
RFS\[80\]: Database mount ID mismatch \[0x5261c3dd:0x52614808\] (1382138845:1382107144)  
RFS\[80\]: Client instance is standby database instead of primary  
Thu Jul 31 16:14:02 2014  
备库：  
RFS connections are allowed  
Thu Jul 31 17:15:56 2014  
alter database open  
AUDIT\_TRAIL initialization parameter is changed to OS, as DB is NOT compatible for database opened with read-only access  
Thu Jul 31 17:19:39 2014  
krsu\_upi\_rfs: kspgsp returned null string for db unique name  
PING\[ARC2\]: Heartbeat failed to connect to standby 'primaryorcl'. Error is 16009.  
Thu Jul 31 17:20:39 2014  
krsu\_upi\_rfs: kspgsp returned null string for db unique name  
PING\[ARC2\]: Heartbeat failed to connect to standby 'primaryorcl'. Error is 16009.  
krsu\_upi\_rfs: kspgsp returned null string for db unique name  
PING\[ARC2\]: Heartbeat failed to connect to standby 'primaryorcl'. Error is 16009.  
Thu Jul 31 17:21:33 2014  
Abort recovery for domain 0  
Errors in file /oracle/oracle/diag/rdbms/orcldg/orcl1/trace/orcl1\_ora\_4267.trc:  
主库  
SQL> show parameter log\_archive\_dest\_2  
  
NAME                                 TYPE  
\------------------------------------ ---------------------------------  
VALUE  
\------------------------------  
log\_archive\_dest\_2                   string  
service=STANDBYORCL valid\_for=  
(ALL\_LOGFILES,ALL\_ROLES) db\_un  
ique\_name=orcldg  
  
备库：  
SQL> show parameter log\_archive\_dest\_2  
  
NAME                                 TYPE       VALUE  
\------------------------------------ ---------- ------------------------------  
log\_archive\_dest\_2                   string     service=primaryorcl valid\_for=  
                                                (ALL\_LOGFILES,ALL\_ROLES) db\_un  
                                                ique\_name=orcl  
修改standby端：  
SQL> alter system set log\_archive\_dest\_state\_2=defer scope=both sid='\*'  
报错解决  
可以修改valid\_for来解决这个报错  
SQL> alter system set log\_archive\_dest\_2='service=standbydg arch sync valid\_for=(online\_logfiles,primary\_role) db\_unique\_name=orcldg' scope=both sid='\*'

System altered.

注：

<table style="color:rgb(0,61,91); font-family:Simsun; font-size:12px; text-align:left"> 
 <tbody> 
  <tr> 
   <td align="left"><span style="font-size:14px; text-align:right; color:black; padding:0px 6px 0px 0px; font-weight:bold"><br> Database mount ID mismatch ORA-16009: invalid redo transport destination (文档 ID 1450132.1)</span></td> 
  </tr> 
 </tbody> 
</table>

**In this Document**

<table style="color:rgb(0,0,0); font-family:Simsun; font-size:12px; text-align:left"> 
 <tbody> 
  <tr> 
   <td>&nbsp;</td> 
   <td><a href="https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=l0bsagkj_4&amp;_afrLoop=521384381503787#SYMPTOM" rel="nofollow">Symptoms</a></td> 
  </tr> 
 </tbody> 
</table>

<table style="color:rgb(0,0,0); font-family:Simsun; font-size:12px; text-align:left"> 
 <tbody> 
  <tr> 
   <td>&nbsp;</td> 
   <td><a href="https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=l0bsagkj_4&amp;_afrLoop=521384381503787#CAUSE" rel="nofollow">Cause</a></td> 
  </tr> 
 </tbody> 
</table>

<table style="color:rgb(0,0,0); font-family:Simsun; font-size:12px; text-align:left"> 
 <tbody> 
  <tr> 
   <td>&nbsp;</td> 
   <td><a href="https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=l0bsagkj_4&amp;_afrLoop=521384381503787#FIX" rel="nofollow">Solution</a></td> 
  </tr> 
 </tbody> 
</table>

--------------------

## APPLIES TO: ##

Oracle Database - Enterprise Edition - Version 11.2.0.2 and later  
Information in this document applies to any platform.  
\*\*\*Checked for relevance on 20-SEPT-2013\*\*\*

## SYMPTOMS ##

Primary with one or more physical or logical standby databases  
All the databases involved in data guard configuration are correctly configured   
with log\_archive\_dest\_n and log\_archive\_config parameters  
There are no errors in the available standby database alertlogs when the below messages pop up in Primary alertlog  
  
\---- Primary alertlog ----   
  
Thu Apr 12 10:27:47 2012  
RFS\[1\]: Assigned to RFS process 23666  
RFS\[1\]: Database mount ID mismatch \[0x5d0945b9:0x5ce6c765\] (1560888761:1558628197)  
RFS\[1\]: Not using real application clusters  
Thu Apr 12 10:27:48 2012  
RFS\[2\]: Assigned to RFS process 23668  
RFS\[2\]: Database mount ID mismatch \[0x5d0945b9:0x5ce6c765\] (1560888761:1558628197)  
RFS\[2\]: Not using real application clusters  
Thu Apr 12 10:27:49 2012  
  
Thu Apr 12 18:54:39 2012  
ALTER SYSTEM SET log\_archive\_trace=8191 SCOPE=BOTH; <<<<-------- Enabling trace leaves ORA-16009  
Thu Apr 12 18:54:46 2012  
  
Thu Apr 12 19:14:26 2012  
Redo Shipping Client Connected as PUBLIC  
\-- Connected User is Valid  
RFS\[555\]: Assigned to RFS process 17392  
RFS\[555\]: Database mount ID mismatch \[0x5d0945b9:0x5ce6c765\] (1560888761:1558628197)  
RFS\[555\]: Not using real application clusters  
Errors in file /orahome/app/oracle/diag/rdbms/qd\_f4wp1/f4wp1/trace/f4wp1\_rfs\_17392.trc:  
ORA-16009: invalid redo transport destination  
Thu Apr 12 19:15:27 2012  
Redo Shipping Client Connected as PUBLIC  
\-- Connected User is Valid  
  
  
  
  
\-------- f4wp1\_rfs\_17392.trc ----------  
  
krsr\_rfs\_nfy: Startup received from ARCH pid 6366 <<< --------------------- This is the process of some read/write open database connected to this primary  
krsd\_init\_sdips: called from \[krsr.c:3189\] with function 2  
krso\_proc\_add: Detected dead process 16969; subsuming V$MANAGED\_STANDBY slot  
krso\_proc\_add: Using V$MANAGED\_STANDBY slot 0xca8a68420  
krsr\_rfs\_nfy: Identified 3 RFS client(s)  
\*\*\* 2012-04-12 19:14:26.262 879 krsr.c  
RFS message number 427 (RFSATTCH state:1 mode:1 flag:0x800002) start  
  
  
\*\*\* 2012-04-12 19:14:26.269 1799 krsa.c  
Completed  CFTXN 0x7fff2299ae50 (last PID:17392) \[krsr.c:4466\] IX-  
Resignalling exception 16009 \[krsr.c:4469\]  
ORA-16009: invalid redo transport destination  
\*\*\* 2012-04-12 19:14:26.370 883 krsv.c  
krsv\_dpga: Freeing krsrrx

## CAUSE ##

One of the existing standby databases was cloned without removing Data Guard Related Parameters  
that enables it to connect to original Primary when this standby takes Primary database role - Cloning open the database in read / write Mode

## SOLUTION ##

Ensure that there is no log\_archive\_dest\_n parameter that connects to original Primary and   
also remove any Data guard Related parameters from cloned database  
  
Example Parameters  
  
alter system set log\_archive\_dest\_n='' scope=both sid='\*';- one that points to original Primary  
alter system set fal\_server='' scope=both sid='\*';  
alter system set fal\_client='' scope=both sid='\*';