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

现象：

10.2.0.1

在lgwr的trc文件中发现大量如下信息：

*** SESSION ID:(1101.1) 2012-05-07 22:27:36.132
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)
*** 2012-05-08 07:28:10.101
LGWR: Archivelog for thread 1 sequence 284 will NOT be compressed
*** 2012-05-08 14:58:57.894
LGWR: Archivelog for thread 1 sequence 285 will NOT be compressed
*** 2012-05-09 06:42:27.459
LGWR: Archivelog for thread 1 sequence 286 will NOT be compressed
*** 2012-05-09 06:43:08.138
LGWR: Archivelog for thread 1 sequence 287 will NOT be compressed
*** 2012-05-10 06:46:54.713
LGWR: Archivelog for thread 1 sequence 288 will NOT be compressed
*** 2012-05-10 06:47:51.328
LGWR: Archivelog for thread 1 sequence 289 will NOT be compressed
*** 2012-05-11 06:42:34.825

参考1：

http://blog.chinaunix.net/uid-8003850-id-2035172.html

(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)''

参考2：

http://www.eygle.com/archives/2005/12/07/

在LGWR的trace文件中看到大量如下信息:

*** 2005-08-30 17:49:05.751
LGWR: Archivelog for thread 1 sequence 5068 will NOT be compressed
*** 2005-08-30 18:03:25.576
LGWR: Archivelog for thread 1 sequence 5069 will NOT be compressed
*** 2005-08-30 18:04:29.776
LGWR: Archivelog for thread 1 sequence 5070 will NOT be compressed
*** 2005-08-30 18:05:26.771
LGWR: Archivelog for thread 1 sequence 5071 will NOT be compressed
*** 2005-08-30 18:06:24.778
LGWR: Archivelog for thread 1 sequence 5072 will NOT be compressed
*** 2005-08-30 18:07:20.655
LGWR: Archivelog for thread 1 sequence 5073 will NOT be compressed
*** 2005-08-30 18:08:29.228
LGWR: Archivelog for thread 1 sequence 5074 will NOT be compressed
...

Oracle给出的解释是:

These informational messages do not indicate any problem and are reported 
in 10.1.0.X regardless of database configuration and specific settings.

在Oracle10.1.0.X中，这些信息不表明任何故障及数据库设置问题。

Archivelog compression is not available in 10gR1.

解决：

因为我的版本为10gR2，所以主要按照参考1来做。