RMAN-06820: WARNING: failed to archive current log at primary database

12C dataguard备库备份archivelog出现报错
 
Problem Description
---------------------------------------------------
SQL> select * from product_component_version ;
 
PRODUCT                                  VERSION    STATUS
---------------------------------------- ---------- ----------------------------------------
NLSRTL                                   12.1.0.2.0 Production
Oracle Database 12c Enterprise Edition   12.1.0.2.0 64bit Production
PL/SQL                                   12.1.0.2.0 Production
TNS for Linux:                           12.1.0.2.0 Production
 
备库的状态
SQL> select OPEN_MODE,PROTECTION_MODE,DATABASE_ROLE from v$database;
 
OPEN_MODE            PROTECTION_MODE      DATABASE_ROLE
-------------------- -------------------- ----------------
READ ONLY WITH APPLY MAXIMUM PERFORMANCE  PHYSICAL STANDBY
 
SQL> select THREAD# ,SEQUENCE#,APPLIED from  v$archived_log where APPLIED=‘NO‘ ;
 
no rows selected
 
在standby(备库)备份archivelog时会报RMAN-06820,ORA-17629,ORA-17627的错,但是最后归档还是备份成功了。
 
[[email protected] ~]$rman target /
 
RMAN> backup archivelog all;
 
Starting backup at 02-OCT-15
using target database control file instead of recovery catalog
RMAN-06820: WARNING: failed to archive current log at primary database
ORACLE error from target database:  
ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-00942: table or view does not exist
 
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=1156 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=2 sequence=132 RECID=135 STAMP=891367439
input archived log thread=1 sequence=172 RECID=134 STAMP=891367438
......
piece
handle=/opt/oracle/oradata/MXCNSTB/backupset/2015_10_02/o1_mf_annnn_TAG20151002T144942_c0wbbdw1_.bkp
tag=TAG20151002T144942 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07
Finished backup at 02-OCT-15

解决方法:

在备库上以sys用户登录

rman target sys/password

可以参考以下文档:

RMAN-06820 ORA-17629 ORA-17627 ORA-01034 ORA-27101 During Backup of a Standby Database ( Doc ID 2042148.1  )

RMAN-06820 ORA-17629 During Backup at Standby Site ( Doc ID 1616074.1  )

RMAN-06820 ORA-17629 ORA-12154 During Backup of a Standby Database ( Doc ID 2025142.1  )

时间: 2024-10-12 15:15:17

RMAN-06820: WARNING: failed to archive current log at primary database的相关文章

ALERT.LOG for ASM Shows "WARNING: failed to online diskgroup resource ora.GI.dg (unable to communica

APPLIES TO: OracleDatabase - Enterprise Edition - Version 11.2.0.1 to 12.1.0.1 [Release 11.2 to12.1] Informationin this document applies to any platform. ***Checked for relevance on 03-Jul-2013*** SYMPTOMS If OCR is located on ASM diskgroup, followin

DG环境RMAN删除归档报错RMAN-08137: archived log not deleted

Oracle 12C DG环境,备库归档目录告警,查看crontab脚本,发现有删除操作,保持两天的,后手动执行,查看具体报错原因: RMAN> delete noprompt expired archivelog all; released channel: ORA_DISK_1allocated channel: ORA_DISK_1channel ORA_DISK_1: SID=5408 device type=DISKspecification does not match any ar

【MongoDB】2014-07-25T11:00:48.634+0800 warning: Failed to connect to 127.0.0.1:27017, reason: errno:10061 由于目标计算机积极拒绝,无法连接。

1:启动MongoDB 2014-07-25T11:00:48.634+0800 warning: Failed to connect to 127.0.0.1:27017, reason: errno:10061 由于目标计算机积极拒绝,无法连接. 2:添加一配置文件 ##数据文件 dbpath=E:\ruanjian\MongoDB\data ##日志文件 logpath=E:\ruanjian\MongoDB\log\mongo.log 添加相应目录和文件,如下图所示 3: C:\User

PHP: configure: error: mysql configure failed. Please check config.log for more information.

为php增加mysql模块时报错 configure: error: mysql configure failed. Please check config.log for more information. 解决方法: ./configure --prefix=/usr/local/php --with-config-file-path=/usr/local/php/etc --with-mysql-dir=/usr --with- mysqli=/usr/bin/mysql_config -

ERROR 1872 (HY000): Slave failed to initialize relay log info structure from the repository

该问题的一般是由relay log没有在配置文件定义所致. 1.问题描述: mysql> start slave; mysql> system perror 1872 MySQL error code 1872 (ER_SLAVE_RLI_INIT_REPOSITORY): Slave failed to initialize relay log info structure from the repository 2.处理办法2.1.修改配置文件 诸如在my.cnf配置文件中添加如下项: r

断重启从库故障:电Last_Error: Slave failed to initialize relay log info structure from the repository

断电重启故障 2017-11-10T21:27:52.791849+08:00 0 [ERROR] Error in Log_event::read_log_event(): 'read error', data_len: 68, event_type: 22017-11-10T21:27:52.791889+08:00 0 [Warning] Error reading GTIDs from relaylog: -12017-11-10T21:27:52.793147+08:00 0 [Not

【故障处理】ERROR 1872 (HY000): Slave failed to initialize relay log info structure from the repository

今天在使用冷备份文件重做从库时遇到一个报错,值得研究一下. 版本:MySQL5.6.27 一.报错现象 dba:(none)> start slave; ERROR 1872 (HY000): Slave failed to initialize relay log info structure from the repository 这个时候查看error.log: 2017-07-17 16:19:02 9022 [ERROR] Failed to open the relay log '.

Oracle Alert日志出现Incremental checkpoint up to RBA [0x5d02.5e5b.0], current log tail at RBA [0x5d02.7b8b.0]

可能新巡检某台Oracle数据库服务器alert日志会忽然发现有如下输出: Wed Nov 21 05:46:04 2018 Incremental checkpoint up to RBA [0x5d02.5e5b.0], current log tail at RBA [0x5d02.7b8b.0] Wed Nov 21 06:06:05 2018 Incremental checkpoint up to RBA [0x5d02.dfe7.0], current log tail at RB

Slave failed to initialize relay log info structure from the repository

前几天做主从同步的时候没什么问题,今天做双机热备的时候出现了问题,问题如下:Slave failed to initialize relay log info structure from the repository(服务器未能从存储库初始化中继日志信息结构)可能是某些记录的存在导致的把,所以就尝试的用mysql自带的还原给还原了一下,成功了,具体如下:我是在从库做的主库的数据同步,所以在linux中的从库中进行的mysql命令,先停止从库同步操作,再做还原mysql> stop slave;