MRP进程报1111错误:Recovery Slave PR00 previously exited with exception 1111

查看dg报错 

select dest_name,status,error from v$archive_dest;
FACILITY                 SEVERITY      ERROR_CODE TIMESTAMP MESSAGE
------------------------ ------------- ---------- --------- --------------------------------------------------------------------------------
Log Transport Services   Informational          0 24-MAR-20 ARC0: Archival started
Log Transport Services   Informational          0 24-MAR-20 ARC1: Archival started
Log Transport Services   Informational          0 24-MAR-20 ARC2: Archival started
Log Transport Services   Informational          0 24-MAR-20 ARC1: Becoming the 'no FAL' ARCH
Log Transport Services   Informational          0 24-MAR-20 ARC2: Becoming the heartbeat ARCH
Log Transport Services   Informational          0 24-MAR-20 ARC2: Becoming the active heartbeat ARCH
Log Apply Services       Informational          0 24-MAR-20 Managed Standby Recovery starting Real Time Apply
Log Transport Services   Informational          0 24-MAR-20 ARC3: Archival started
Log Apply Services       Control                0 24-MAR-20 Attempt to start background Managed Standby Recovery process
Log Apply Services       Control                0 24-MAR-20 MRP0: Background Managed Standby Recovery process started
Log Apply Services       Informational          0 24-MAR-20 Managed Standby Recovery starting Real Time Apply

FACILITY                 SEVERITY      ERROR_CODE TIMESTAMP MESSAGE
------------------------ ------------- ---------- --------- --------------------------------------------------------------------------------
Log Apply Services       Error               1111 24-MAR-20 MRP0: Background Media Recovery terminated with error 1111
Log Apply Services       Informational          0 24-MAR-20 Managed Standby Recovery not using Real Time Apply
Log Apply Services       Control                0 24-MAR-20 MRP0: Background Media 
Recovery process shutdown

强制开启还是会宕 

SQL> recover managed standby database using current logfile disconnect from session;  
Media recovery complete.
SQL> select process,client_process,sequence#, THREAD# ,status from v$managed_standby;  

PROCESS   CLIENT_P  SEQUENCE#   ??STATUS
--------- -------- ---------- ----------
ARCH      ARCH          15894          2
ARCH      ARCH          14999          1
ARCH      ARCH              0          0
ARCH      ARCH          15000          1
RFS       UNKNOWN           0          0
RFS       UNKNOWN           0          0
RFS       UNKNOWN           0          0
RFS       UNKNOWN           0          0
RFS       UNKNOWN           0          0
RFS       LGWR          15001          1
RFS       LGWR          15895          2

PROCESS   CLIENT_P  SEQUENCE#   ??STATUS
--------- -------- ---------- ----------
RFS       UNKNOWN           0          0

12 rows selected.


alert日志报错 


Managed Standby Recovery starting Real Time Apply
MRP0: Background Media Recovery terminated with error 1111
Errors in file /u01/app/oracle/diag/rdbms/hisdg2/hisdb/trace/hisdb_pr00_7650.trc:
ORA-01111: name for data file 50 is unknown - rename to correct file
ORA-01110: data file 50: '/u01/app/oracle/product/11.2.0/db_1/dbs/UNNAMED00050'
ORA-01157: cannot identify/lock data file 50 - see DBWR trace file
ORA-01111: name for data file 50 is unknown - rename to correct file
ORA-01110: data file 50: '/u01/app/oracle/product/11.2.0/db_1/dbs/UNNAMED00050'
Managed Standby Recovery not using Real Time Apply
Recovery Slave PR00 previously exited with exception 1111
MRP0: Background Media Recovery process shutdown (hisdb)

mrp0进程宕 

SQL> select process,status,sequence# from v$managed_standby;

PROCESS   STATUS        SEQUENCE#
--------- ------------ ----------
ARCH      CONNECTED             0
ARCH      CONNECTED             0
ARCH      CONNECTED             0
ARCH      CLOSING           14997
RFS       IDLE                  0
RFS       IDLE                  0
RFS       WRITING           14999

解决办法:

设置db_file_name_convert,将原有的未加入的转换加入

alter system set db_file_name_convert='+DATA/hisdb3/','/oradata/hisdb/hisDB/datafile/','+DATA/hisdb/hgoa/','/oradata/hisdb/hisDB/datafile/hgoa/','+DATA/hisdb/hisdata/','/oradata/hisdb/hisDB/datafile/hisdata/','+DATA/hisdb/hisdatabi/','/oradata/hisdb/hisDB/datafile/hisdatabi/','+DATA/hisdb/hissms/','/oradata/hisdb/hisDB/datafile/hissms/' ,'+DATA/hisdb/datafile/','/oradata/hisdb/hisDB/datafile/' scope=spfile;

 

设备手动
ALTER SYSTEM SET standby_file_management='MANUAL' SCOPE=MEMORY;

将转换失败文件手工创建
SQL> alter database create datafile '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/UNNAMED00050' as '/oradata/hisdb/hisDB/datafile/undotbs2_03191.dbf';

Database altered.

SQL> alter database create datafile '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/UNNAMED00051' as '/oradata/hisdb/hisDB/datafile/undotbs2_031951.dbf';

Database altered.


设置DG成自动

SQL>  ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=AUTO scope=both;

System altered.
开启应用

SQL> alter database recover managed standby database using current logfile disconnect;

Database altered.
完成解决

SQL> SELECT PROCESS, STATUS, THREAD#, SEQUENCE#,BLOCK#,BLOCKS,PID FROM V$MANAGED_STANDBY;

PROCESS   STATUS          THREAD#  SEQUENCE#     BLOCK#     BLOCKS        PID
--------- ------------ ---------- ---------- ---------- ---------- ----------
ARCH      CLOSING               1      15002      67584       1668      23285
ARCH      CLOSING               1      15003          1        218      23287
ARCH      CONNECTED             0          0          0          0      23289
ARCH      CLOSING               2      15897          1        119      23291
RFS       IDLE                  0          0          0          0      23296
RFS       IDLE                  0          0          0          0      23298
RFS       IDLE                  0          0          0          0      23300
RFS       IDLE                  0          0          0          0      23302
RFS       WRITING               2      15898       8416          1      23304
RFS       IDLE                  0          0          0          0      23306
RFS       WRITING               1      15004       8254          5      23308

PROCESS   STATUS          THREAD#  SEQUENCE#     BLOCK#     BLOCKS        PID
--------- ------------ ---------- ---------- ---------- ---------- ----------
RFS       IDLE                  0          0          0          0      23311
MRP0      APPLYING_LOG          1      13792     381294     822544      23318

13 rows selected.

 

 

 

 

 

 

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
引用\[1\]中提到了一个选项字符串,其中包含了一些参数和值。这个字符串可能是用于配置数据库的复制设置的。引用\[2\]中的日志记录显示了一些关于从库的错误和警告信息,包括从库SQL线程被终止的情况。引用\[3\]中列出了一些与数据库性能相关的事件和等待时间。根据这些引用内容,可以推断出readMode和subscriptionMode是用于配置数据库复制的模式。 回答: 根据提供的引用内容,readMode和subscriptionMode可能是用于配置数据库复制的模式。readMode可能是指定从库的读取模式,而subscriptionMode可能是指定从库的订阅模式。然而,具体的含义和配置方式需要根据上下文和数据库系统的文档来确定。 #### 引用[.reference_title] - *1* *2* [Error reading relay log event: slave SQL thread was killed](https://blog.csdn.net/shaochenshuo/article/details/50312777)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v91^control_2,239^v3^insert_chatgpt"}} ] [.reference_item] - *3* [Waits for: "PX Deq: Slave Session Stats](https://blog.csdn.net/u013012406/article/details/80278943)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v91^control_2,239^v3^insert_chatgpt"}} ] [.reference_item] [ .reference_list ]

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值