ARC0: Becoming the 'no FAL' ARCH ARC0: Thread not mounted

今天在alter.log日誌裡面發現了一個以前沒有見過的問題：
PMON started with pid=2
DIAG started with pid=3
LMON started with pid=4
LMD0 started with pid=5
LMS0 started with pid=6
LMS1 started with pid=7
DBW0 started with pid=8
LGWR started with pid=9
CKPT started with pid=10
SMON started with pid=11
RECO started with pid=12
CJQ0 started with pid=13
Wed Apr  8 04:36:40 2009
starting up 1 shared server(s) ...
starting up 0 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=ipc))'...
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=15
ARC0: Archival started
ARC1 started with pid=16
Wed Apr  8 04:36:40 2009
ARCH: STARTING ARCH PROCESSES COMPLETE
Wed Apr  8 04:36:40 2009
ARC1: Archival started
Wed Apr  8 04:36:40 2009
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no FAL' ARCHARC0: Thread not mounted
Wed Apr  8 04:36:40 2009
ARC1: Becoming the heartbeat ARCH
ARC1: Becoming the heartbeat ARCHARC1: Thread not mounted
Wed Apr  8 04:36:40 2009
ALTER DATABASE   MOUNT
Wed Apr  8 04:36:41 2009
lmon registered with NM - instance id 1 (internal mem no 0)
Wed Apr  8 04:36:42 2009
Reconfiguration started (old inc 0, new inc 4)
List of nodes:

    這個問題以前沒有注意過，不知道是錯誤，還是正常告警資訊，查了一下metalink，原因如下：
    APPLIES TO :
                 Oracle Server - Enterprise Edition - Version: 9.2.0.7 to 10.2
                 Oracle Server - Standard Edition - Version: 9.2.0.7 to 10.2.0.0
    CAUSE:
                 These are configuration messages newly introduced in 9.2.0.7 and 10g.
                 The messages are related to Data Guard.
                 This message is flagged to the alert log when an ARCH process starts and we have not yet started a
                 non-FAL process（about Data Guard process）, so need to start one. Because FAL Archiver processes
                  are only used on a Data Guard environment, non-FAL processes would be started on both Data Guard
                 and non-Data Guard environments.
                 Even if there is no Data Guard configuration, these informational messages are displayed at startup.
     SOLUTION:
                1. Ignore the messages.The messages do not relate to any problem.
                2.or you can show parameter about FAL and SAL, that's default value is null ,if not ,you can modified it 
                    to default value.

Subject:	NEW MESSAGES IN ALERT LOG RELATED TO ARCH PROCESS SINCE 9.2.0.7 PATCHSET
	:	342652.1	Type:	PROBLEM
	Modified Date :	05-DEC-2008	Status:	MODERATED

metalink reply:
ANSWER
=======
Per NOTE 342652.1 these messages are informational and can be ignored. It occurs in archive process
starts and no Data Guard non-FAL (Fetch Archive Log) process has started yet.

When first arc process starts it is automatically assigned to be 'no FAL' process
for Data Guard.

ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no FAL' ARCH ARC0: Thread not mounted

These messages do not occur in BIDB/BKDB instance because they are not running in archivelog mode and so archiver pro
cess does not start.
eos (end of section)