问题说明

客户环境主库4节点RAC11.2.0.4,单实例DG环境,DG由于空间不足,导致同步中断,由于DG备库未应用的归档主库都再,本次恢复的方式,是开启dg mrp进程,自动同步追上主库。

以下遇到的问题,都在此过程中,遇到的报错。

一 dg环境遇到

ORA-00353 ORA-00334  如果主库还存在归档日志,则可以mv ,rm删除备库有问题的归档,让dg产生gap,主库会再次像备库传输归档日志
另一种方法,就是如果主库无法自动像备库传输日志,可以从主库scp归档至备库dg,注册归档后,解决问题。
其次,本次通过主库,dg alert排除存在异常现象,也就是说再本次问题前,alert日志中并未出现日志块损坏现象!
ORA-354 ORA-353 Corrupt Redo Log Block Header against online redolog using EMC/Cisco SANTap Service (Doc ID 779711.1)
ORA-354 ORA-353 and ORA-312 on Redo Log Group members (Doc ID 332672.1)
hu Nov  ::
Media Recovery Log /oradata/newora901dg/archivelog/NEWORA901DG/archivelog/2019_11_21/o1_mf_4_31416_gxf6v6p0_.arc
Incomplete read from log member '/oradata/newora901dg/archivelog/NEWORA901DG/archivelog/2019_11_21/o1_mf_1_46650_gxc023sj_.arc'.
Trying next member.
Errors in file /u01/app/oracle/diag/rdbms/newora901dg/ora901/trace/ora901_pr00_9153.trc (incident=):
ORA-: log corruption near block change time // ::
ORA-: archived log: '/oradata/newora901dg/archivelog/NEWORA901DG/archivelog/2019_11_21/o1_mf_1_46650_gxc023sj_.arc'
Incident details in: /u01/app/oracle/diag/rdbms/newora901dg/ora901/incident/incdir_192300/ora901_pr00_9153_i192300.trc
Errors with log /oradata/newora901dg/archivelog/NEWORA901DG/archivelog/2019_11_21/o1_mf_4_31416_gxf6v6p0_.arc
MRP0: Background Media Recovery terminated with error
Errors in file /u01/app/oracle/diag/rdbms/newora901dg/ora901/trace/ora901_pr00_9153.trc:
ORA-: corrupt redo log block header
ORA-: log corruption near block change time // ::
ORA-: archived log: '/oradata/newora901dg/archivelog/NEWORA901DG/archivelog/2019_11_21/o1_mf_1_46650_gxc023sj_.arc'
Thu Nov ::
Dumping diagnostic data in directory=[cdmp_20191121221305], requested by (instance=, osid= (PR00)), summary=[incident=].
Recovery interrupted!
Recovered data files to a consistent state at change
Thu Nov ::
MRP0: Background Media Recovery process shutdown (ora901)
Thu Nov ::
Sweep [inc][]: completed
Sweep [inc][]: completed
Sweep [inc2][]: completed
Sweep [inc2][]: completed
MRP0: Background Media Recovery process shutdown (ora901) 操作:
dg环境
mv 有问题的归档 xxx.bak 后,dg备库启动Mrp进程

SQL> recover managed standby database disconnect from session;

 
Thu Nov  ::
ALTER DATABASE RECOVER managed standby database disconnect from session
Attempt to start background Managed Standby Recovery process (ora901)
Thu Nov ::
MRP0 started with pid=, OS id=
MRP0: Background Managed Standby Recovery process started (ora901)
started logmerger process
Thu Nov ::
Managed Standby Recovery not using Real Time Apply
Parallel Media Recovery started with slaves
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Media Recovery Log /oradata/newora901dg/archivelog/NEWORA901DG/archivelog/2019_11_21/o1_mf_2_47491_gxf6t3v7_.arc
Media Recovery Log /oradata/newora901dg/archivelog/NEWORA901DG/archivelog/2019_11_21/o1_mf_1_46650_gxc023sj_.arc
Error opening /oradata/newora901dg/archivelog/NEWORA901DG/archivelog/2019_11_21/o1_mf_1_46650_gxc023sj_.arc
Attempting refetch
Media Recovery Waiting for thread sequence
Fetching gap sequence in thread , gap sequence -
Thu Nov ::
RFS[]: Allowing overwrite of partial archivelog for thread sequence
RFS[]: Opened log for thread sequence dbid - branch
Archived Log entry added for thread sequence rlc ID 0x948808ac dest :
Completed: ALTER DATABASE RECOVER managed standby database disconnect from session
Thu Nov ::
Media Recovery Log /oradata/newora901dg/archivelog/NEWORA901DG/archivelog/2019_11_21/o1_mf_1_46650_gxf7ctdd_.arc
Media Recovery Log /oradata/newora901dg/archivelog/NEWORA901DG/archivelog/2019_11_21/o1_mf_3_31565_gxbzzfxk_.arc
Media Recovery Log /oradata/newora901dg/archivelog/NEWORA901DG/archivelog/2019_11_21/o1_mf_4_31416_gxf6v6p0_.arc
Media Recovery Log /oradata/newora901dg/archivelog/NEWORA901DG/archivelog/2019_11_21/o1_mf_4_31417_gxbzvr69_.arc
Media Recovery Log /oradata/newora901dg/archivelog/NEWORA901DG/archivelog/2019_11_21/o1_mf_1_46651_gxc023sz_.arc

#备选方案,如果是10G环境,备库产生gap,但是主库很可能并不会再次将归档传输到备库,因此需要手工scp归档日志传输至备库。
SQL> select name,thread# from v$archived_log where sequence#=46650;
NAME
------------------------------------------------------------------------
+FRA/newora901/archivelog/2019_11_19/thread_1_seq_46650.4973.1024753747
ASMCMD> cp thread_1_seq_46650.4973.1024753747 /home/grid/thread_1_seq_46650.arc
copying +FRA/newora901/archivelog/2019_11_19/thread_1_seq_46650.4973.1024753747 -> /home/grid/thread_1_seq_46650.arc
scp 传输归档到备库

SQL> ALTER DATABASE REGISTER LOGFILE '/zz/xxx.arc';

二 DG同步遇到如下ORA 600报错,MOS并未找到相关文档

本次通过将报错的上一个归档日志,进行mv 移除后,再次开启mrp进程,dg产生gap,主库重传报错归档解决问题。

Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Media Recovery Log /oradata/newora901dg/archivelog/NEWORA901DG/archivelog/2019_11_21/o1_mf_2_47745_gxc193wj_.arc
Errors in file /u01/app/oracle/diag/rdbms/newora901dg/ora901/trace/ora901_pr00_17446.trc (incident=):
ORA-: internal error code, arguments: [], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/newora901dg/ora901/incident/incdir_208045/ora901_pr00_17446_i208045.trc
Completed: ALTER DATABASE RECOVER managed standby database disconnect from session
Thu Nov ::
Dumping diagnostic data in directory=[cdmp_20191121231430], requested by (instance=, osid= (PR00)),
summary=[incident=].
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors with log /oradata/newora901dg/archivelog/NEWORA901DG/archivelog/2019_11_21/o1_mf_2_47745_gxc193wj_.arc
MRP0: Background Media Recovery terminated with error
Errors in file /u01/app/oracle/diag/rdbms/newora901dg/ora901/trace/ora901_pr00_17446.trc:
ORA-: internal error code, arguments: [], [], [], [], [], [], [], [], [], [], [], []
Recovery interrupted!
Errors in file /u01/app/oracle/diag/rdbms/newora901dg/ora901/trace/ora901_pr00_17446.trc:
ORA-: internal error code, arguments: [], [], [], [], [], [], [], [], [], [], [], []
MRP0: Background Media Recovery process shutdown (ora901)
SQL> host mv /oradata/newora901dg/archivelog/NEWORA901DG/archivelog/2019_11_21/o1_mf_2_47745_gxc193wj_.arc
/oradata/newora901dg/archivelog/NEWORA901DG/archivelog/2019_11_21/o1_mf_2_47745_gxc193wj_.arc_20191121.bak

DG环境恢复同步遇到报错ORA-00353ORA-00334以及ORA-00600[2619], [47745]的更多相关文章

  1. ORA-15025 搭建DG环境,restore controlfile报错,提示oracle无法使用ASM存储

    环境说明: #主库RAC环境 #备库RAC环境,操作系统AIX 6.1 数据库版本11.2.0.3 报错说明: #主库备份控制文件,传输至备库,备库restore 报错 本篇文档,分为两大阶段:第一阶 ...

  2. git同步遇到报错

    git同步遇到报错 “fatal: unable to access ‘https://github.com/ruanwenwu/newp.git/‘: Peer reports incompatib ...

  3. mysql5.7同步复制报错1060故障处理

    mysql5.7同步复制报错故障处理 # 报错 1060,具体如下Last_Errno: 1060Last_Error: Coordinator stopped because there were ...

  4. git同步遇到报错“fatal: unable to access 'https://github.com/lizhong24/mysite2.git/': Peer reports incompatible or unsupported protocol version.”

    git同步遇到报错“fatal: unable to access 'https://github.com/lizhong24/mysite2.git/': Peer reports incompat ...

  5. MRP进程起不来, 报错:ORA-00600: internal error code, arguments: [2619], [227424], [], [], [], [], [], [], [], [], [], []

    问题背景:客户数据库服务架构为一主一备,某日备库操作系统意外重启,重启后Oracle MRP进程起不来,报错:ORA-00600: internal error code, arguments: [2 ...

  6. ORA-16019搭建DG设置归档线程参数报错

    #操作描述:搭建DG,主库修改参数log_archive_dest_1线程路径报错 ORA-16019: cannot use LOG_ARCHIVE_DEST_1 with LOG_ARCHIVE_ ...

  7. 转:CentOS上安装LAMP之第三步:MySQL环境及安装过程报错解决方案(纯净系统环境)

    这是AMP运行环境中最后配置的环境: 惯例传送门: 1.编译安装MySQL cd /home/zhangatle/tar tar zxvf mysql-.tar.gz cd mysql- cmake ...

  8. Dynamics AX 2012 R2 切换环境后项目导入报错

        Reinhard重装了服务器.重装后,导入项目A报错,错误提示如下: A table, Extended Data Type, Base Enum or class called ???? a ...

  9. GG同步sqlserver报错一个案例 Invalid date format

    在里面Oracle表同步sqlserver时间,在sqlserver当应用程序数据的结束.您可能会遇到这个错误. 2014-05-17 17:20:24 WARNING OGG-01154 SQL e ...

随机推荐

  1. Android智能手机上的音频浅析【转】

    本文转载自:https://blog.csdn.net/david_tym/article/details/80903385 手机可以说是现在人日常生活中最离不开的电子设备了.它自诞生以来,从模拟的发 ...

  2. form表单文件上传提交且接口回调显示提交成功

    前端: <form method="post" enctype="multipart/form-data" id="formSubmit&quo ...

  3. nginx报警:nginx: [warn] could not build optimal server_names_hash, you should increase either server_names_hash_max_size: 512 or server_names_hash_bucket_size: 64; ignoring server_names_hash_bucket_size

    date: 2019-08-12   16:33:05 author: headsen chen notice :个人原创 告警现象:   解决办法:在http的部分添加hash缓冲值 测试:如下图, ...

  4. PHP 对象接口

    对象接口 (interface) 使用接口(interface),可以指定某个类必须实现哪些方法,但不需要定义这些方法的具体内容. 接口是通过 interface 关键字来定义的,就像定义一个标准的类 ...

  5. 谷歌官方 构建您的第一个应用 Kotlin版

    https://developer.android.google.cn/training/basics/firstapp MainActivity.kt package com.example.myf ...

  6. ansible常用的方法小结

    一.批量安装zabbix客户端 .拷贝sh脚本和.conf到远程服务器(也可以全量拷贝客户端) ansible all -m copy -a "src=/usr/local/zabbix_a ...

  7. Tekla 导出ifc并浏览

    Tekla导出IFC

  8. PAT 甲级 1070 Mooncake (25 分)(结构体排序,贪心,简单)

    1070 Mooncake (25 分)   Mooncake is a Chinese bakery product traditionally eaten during the Mid-Autum ...

  9. [ kvm ] 学习笔记 2:虚拟化基础

    1. 虚拟化概念 什么是虚拟化 虚拟化是使用所谓虚拟机管理程序从一台物理机上创建若干个虚拟机的过程.虚拟机的行为和运转方式与物理机一样,但它们会使用物理机的计算资源,如 CPU .内存和存储.虚拟机管 ...

  10. APT攻击与银行

    APT与传统攻击 APT:团队作战,拥有自研工具集,意图明确,技术高超,拥有政府或商业背景,潜伏期多达数年. 传统攻击:脚本小子,水平参差不齐,短期攻击,直接获取利益为目标. 攻击目标 APT攻击链 ...