ARC0: Cannot archive online log based on backup controlfile

無限追云

环境：

DB:  9.2.0.8
SID: wind        #一台主机上装了很多个数据库，wind数据量 206G
OS:  Redhat 4.5

生产库用Netbackup备份到磁带，周二和周六凌晨全备(也就是说4.24号凌晨做了次全备)。昨晚(4.24晚上)把数据

恢复到测试库。


我的操作：

1. 删除测试机上wind数据库
SQL > shutdown immediate
rm /orasys/oradata/wind/下的数据文件、归档日志文件、控制文件

2. 使用rman从磁带还原wind到测试库上

SQL > startup nomount;

rman>run {
ALLOCATE CHANNEL CH00 TYPE 'SBT_TAPE';
SEND 'NB_ORA_SERV=shabo,NB_ORA_CLIENT=aclgcl-036';
restore controlfile from 'ctl_WIND_4608_1_20120424';     #ctl_WIND_4608_1_20120424 是从生产库备份脚本log中得到的
RELEASE CHANNEL CH00;
}


SQL > shutdown immediate;
SQL > startup mount;

rman>run {
allocate channel ch00 type 'SBT_TAPE';
SEND 'NB_ORA_SERV=shabo,NB_ORA_CLIENT=aclgcl-036';
restore database;
recover database;
release channel ch00;
}

SQL> alter database open resetlogs;


数据库恢复成功，但是测试库的alert里记录了大量

ARC0: Cannot archive online log based on backup controlfile。

Google了下，文章说没什么影响

请刘总帮忙确认下

谢谢

無限追云

谢谢刘，我会和领导说明情况

Maclean Liu(刘相兵

这是 9.2的一个bug  使用 backup controlfile 或者 Data Guard standby时可能发生，对数据库不会产生危害，一般可以忽略

ODM FINDING:

'Cannot archive online log based on backup controlfile' Message In Physical Standby Alert Log

Applies to:
Oracle Server - Enterprise Edition - Version: 9.2.0.7 to 9.2.0.7
This problem can occur on any platform.
Symptoms

The DataGuard - Physical Standby alert log may shows below messages whenever there is a archive log switch.

<Physical Standby database alert log >

   ARC1: Cannot archive online log based on backup controlfile
Changes

You will see this messages only when you have :

1)  Applied 9.2.0.7 patchset

2) DataGuard Physical Standby running in Maximum Availability/Protection Mode with standby redo log files.

Note:

Customers not using DataGuard but having standby created using a backup controlfile will also see this messages on mount.
Cause

ARCH process is prodded to perform an online logfile archival. Since this is a standby database, the operation is not allowed.

It is a code problem issue currently being addressed in Bug 5158600 which will be fixed in future patchset releases.
Solution

This messages are absolutely harmless and should be ignored !

Running DataGuard mode in Maximum Performance   or  setting log_archive_start=FALSE in standby instance will stop giving this messages in the standby alert log.

Hdr: 5158600 9.2.0.7 RDBMS 9.2.0.7 DATAGUARD_PSBY PRODID-5 PORTID-215
Abstract: 'CANNOT ARCHIVE ONLINE LOG ..' IS OUTPUT IN STANDBY WHEN FINISH ARCHIVING LOG.


PROBLEM:
--------
The following message is output in standby when finish archiving log.

  ARC1: Cannot archive online log based on backup controlfile

This problem occurs after applying PSR9.2.0.7.
This problem did not occur on R9.2.0.4 in the customer site.

<Alert.log of Standby database>
======================================
Fri Dec 02 06:50:25 2005
ARC1: Completed archiving  log 13 thread 1 sequence 13017
ARC1: Cannot archive online log based on backup controlfile
======================================

DIAGNOSTIC ANALYSIS:
--------------------
This problem is reproduced in R9.2.0.7 if performing the steps
in "TEST CASE".

This problem occurs under the following conditions
in Physical Standby (DataGuard).

- R9.2.0.7
- Using MAXIMUM PROTECTION mode or MAXIMUM AVAILABILITY mode
  as protection mode.

As far as I have confirmed,
this problem does not occur under the following conditions.

- R9.2.0.6
- Using MAXIMUM PROTECTION mode or MAXIMUM AVAILABILITY mode
  as protection mode.
or
- R9.2.0.7
- Using MAXIMUM PERFORMANCE mode as protection mode.


WORKAROUND:
-----------
None.

RELATED BUGS:
-------------
None.

REPRODUCIBILITY:
----------------
This problem is also reproduced in house.

Rep?     Platform              RDBMS Ver.
-------  --------------------- ----------------
Y(100%)  215 Windows2003       9.2.0.7 <=== The CT site
N        215 Windows2003       9.2.0.4 <=== The CT site
Y(100%)  214 Linux Itanium     9.2.0.7
Y(100%)  212 AIX5L             9.2.0.7
N        197 HP-UX Itanium     9.2.0.6

TEST CASE:
----------
1. Construct R9.2.0.7 Data Guard (Physical Standby) environment.

2. Change protection mode.

   Eg.
   SQL> conn /as sysdba
   SQL> startup mount
   SQL> alter database set standby database to maximize protection;
   SQL> alter database open;

   SQL> select protection_mode from v$database;

   PROTECTION_MODE
   --------------------
   MAXIMUM PROTECTION

3. In primary database, performe log switch.

   Eg.
   SQL> alter system switch logfile;

==> In standby, Alert.log shows the following message.

------------
ARC1: Cannot archive online log based on backup controlfile

無限追云

这是测试库24号的的alert日志

[ 本帖最后由 無限追云 于 2012-4-25 10:25 编辑 ]