Oracle DataGuard Standby database ID mismatch错误

| | Comments (0)

故障现象:

Oracle 9208 DataGuard日志应用正常,但是在standby alter log文件里老是提示下面错误:

 

RFS: Possible network disconnect with primary database
standby database ID mismatch [0x99bb1983:0x8d17262b]

 

Metalink的解释:

Symptoms

Standby alert log reports "RFS: Possible network disconnect with primary database"

At the standby DB side I get this error every minute.
RFS: Possible network disconnect with primary database
Standby database ID mismatch [0xAAAA:0xBBBBB]

Archive log transfer/apply works O.K.

Cause

The (error) message may be triggered by another database that  has log_archive_dest_2 pointing to standby instance of (error) message .

RFS process tries to communicate with the instance.

Solution

Check if you have DB with mismatched ID and its  log_archive_dest_X parameter value.
If found one but not in primary/standby config, disable log_archive_dest_2 to the instance, ie

From the error message of "Standby database ID mismatch [0xAAAA:0xBBBBB]"

Convert the hex number of first argument, 0xAAAA to decimal value using calculator

Then search db with the dbid.
SQL> select dbid from v$database;

SQL> alter system set log_archive_dest_2_state=defer;

 

 

 

按照上述说明,果然在primary database所在主机上,找到了另外一个实例,其参数log_archive_dest_2的设置也是:

 

log_archive_dest_2                   string      SERVICE=standby

 

log_archive_dest_2参数defer后,即可解决问题。

 

关于log_archive_dest_n参数的设置说明:

说明: 指定相应的归档日志目标参数 ( LOG_ARCHIVE_DEST_3) 的可用性状态。如果启用,

 

日志目标将被归档。如果延迟, 该目标将被排除在归档操作之外直至重新启用。

 

值范围: ENABLE | DEFER

 

Categories

留言 (0)

发表留言:



Remember Me?
(输入验证码后方可评论,谢谢支持)


About this Entry

This page contains a single entry by Dodd published on February 4, 2008 9:46 AM.

有钱没钱回家过年 was the previous entry in this blog.

ORA-03113错误解决一例 is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.

Powered by Movable Type 4.0