tkcrrsarc: (WARN) Failed to find ARCH for message

lovegigi1999

SQL> select version from v$instance;
 
VERSION
-----------------
10.2.0.3.0
查看数据库的时候发现在bdump下有个错误信息，具体内容如下：
--------------------------------------------------------------------------
*** SERVICE NAME:() 2011-02-01 13:58:33.761
*** SESSION ID:(331.1) 2011-02-01 13:58:33.761
tkcrrsarc: (WARN) Failed to find ARCH for message (message:0x1)
tkcrrpa: (WARN) Failed initial attempt to send ARCH message (message:0x1)
Maximum redo generation record size = 156160 bytes
Maximum redo generation change vector size = 150672 bytes
tkcrrsarc: (WARN) Failed to find ARCH for message (message:0x10)
tkcrrpa: (WARN) Failed initial attempt to send ARCH message (message:0x10
--------------------------------------------------------------------------

找到解决方案如下

(Warn) Failed To Find Arch For Message (Message:0x1)

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 11.1.0.6 - Release: 10.2 to 11.1

Information in this document applies to any platform.

***Checked for relevance on 04-Oct-2010***

Symptoms

- After starting the database receive the following errors in trace file:

> />>

tkcrrsarc: (WARN) Failed to find ARCH for message (message:0x1)

tkcrrpa: (WARN) Failed initial attempt to send ARCH message (message:0x1)

<<<

- After manual performing log switches the following messages occur in the alert.log:

> />>

Shutting down archive processes

Wed Oct 19 14:13:22 2005

ARCH shutting down

ARC2: Archival stopped

<<<

> />

> />

Cause

BUG 4704334 - ''TKCRRSARC: (WARN) FAILED TO FIND ARCH FOR MESSAGE (MESSAGE:0X1)''



These messages are warning messages and are a consequence of the internal archive process spawning and releasing.

There can be different reasons for this message to appear, but it is in fact related to internal work.

The BUG 4704334 has been closed as an duplicate of BUG 6074620 - fixed in 10.2.0.4.1, 10.2.0.5, 11.1.0.7 and 11.2 releases.

Solution

These are only diagnostic messages and can be safely ignored. 

However, there are three options:

Option 1

Ignore the messages.

Option 2

Increase the log_archive_max_processes equal to/or greater than 10

*Testing information about Option 2

log_archive_max_processes=2 may still cause messages, and 4 may cause less.

Recommended setting is 10 or higher as testing has verified that messages disappeared completely at this setting.

Option 3

Upgrade to an release where the BUG 6074620  has been fixed or check patch availability for your version and platform.

References

BUG:4704334 - ''TKCRRSARC: (WARN) FAILED TO FIND ARCH FOR MESSAGE (MESSAGE:0X1)''

采取方案：
SQL> alter system set log_archive_max_processes=4 scope=both;

System altered.
观察一段时间。