科室反应业务不能使用，工程师重启数据库及应用程序问题解决，收集日志查看日志发现如下信息，数据库版本为10.2.0.1.

/home/oracle/orabase/admin/ORACLE/bdump/oracle_lgwr_29650.trc

Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production

With the Partitioning, OLAP and Data Mining options

ORACLE_HOME = /home/oracle/orahome

System name:Linux

Node name:pacsserver-b

Release:2.6.18-194.el5

Version:#1 SMP Tue Mar 16 21:57:01 EDT 2010

Machine:ia64

Instance name: ORACLE

Redo thread mounted by this instance: 1

Oracle process number: 6

Unix process pid: 29650, p_w_picpath: oracle@pacsserver-b (LGWR)


*** SERVICE NAME:() 2012-09-18 18:13:02.855

*** SESSION ID:(551.1) 2012-09-18 18:13:02.855

LGWR: Archivelog for thread 1 sequence 2728 will NOT be compressed

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 = 150676 bytes

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

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

*** 2012-09-18 22:00:14.010

LGWR: Archivelog for thread 1 sequence 2729 will NOT be compressed

*** 2012-09-18 23:13:08.915

LGWR: Archivelog for thread 1 sequence 2730 will NOT be compressed

*** 2012-09-19 03:00:05.449

LGWR: Archivelog for thread 1 sequence 2731 will NOT be compressed

*** 2012-09-19 03:01:19.097

LGWR: Archivelog for thread 1 sequence 2732 will NOT be compressed

*** 2012-09-19 08:19:26.483

LGWR: Archivelog for thread 1 sequence 2733 will NOT be compressed


查看官方资料解释如下

(Warn) Failed To Find Arch For Message (Message:0x1) (文档 ID 375229.1)


In this Document

Symptoms

Cause

Solution

References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

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 14-Jun-2012***

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.


For a detailed list of fixed versions, please refer to:

Note 6074620.8 - Bug 6074620 - LGWR unconditionally writes to trace file


REFERENCES


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

NOTE:6074620.8 - Bug 6074620 - LGWR unconditionally writes to trace file