DG:RFS[8]: No standby redo logfiles created for thread 2
环境:两节点的RAC在线搭建DG,处理报错
现象:RFS[8]: No standby redo logfiles created for thread 2 ,thread2 没有建立redo
Tue Aug 24 09:51:58 2021
Primary database is in MAXIMUM PERFORMANCE mode
RFS[8]: Assigned to RFS process 4994
RFS[8]: No standby redo logfiles created for thread 2
RFS[8]: Opened log for thread 2 sequence 54 dbid 1608598914 branch 1080818180
当前备库redo文件V$STANDBY_LOG视图:
SQL> select group#,thread#,sequence#,bytes/1024/1024 mb,archived,status from V$STANDBY_LOG;
GROUP# THREAD# SEQUENCE# MB ARC STATUS
---------- ---------- ---------- ---------- --- ----------
11 1 73 50 YES ACTIVE
12 1 0 50 YES UNASSIGNED
13 1 0 50 YES UNASSIGNED
14 1 0 50 YES UNASSIGNED
15 1 0 50 YES UNASSIGNED
v$log视图:
SQL> select group#,thread#,bytes/1024/1024,archived,status,members from v$log;
GROUP# THREAD# BYTES/1024/1024 ARC STATUS MEMBERS
---------- ---------- --------------- --- ---------------- ----------
1 1 50 YES CURRENT 1
2 1 50 YES CLEARING 1
3 2 50 YES CLEARING 1
4 2 50 YES CURRENT 1
当前mrp进程状态:
SQL> select process, status, thread#,sequence#, block#, blocks from v$managed_standby; PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
--------- ------------ ---------- ---------- ---------- ----------
ARCH CLOSING 1 72 1 708
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CLOSING 1 71 2048 1272
RFS IDLE 0 0 0 0
RFS IDLE 0 0 0 0
RFS IDLE 0 0 0 0
RFS IDLE 1 73 3037 1
RFS IDLE 0 0 0 0
RFS IDLE 0 0 0 0
RFS IDLE 2 54 5408 1 PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
--------- ------------ ---------- ---------- ---------- ----------
MRP0 WAIT_FOR_LOG 2 54 0 0 12 rows selected.
取消实时应用:
SQL> alter database recover managed standby database cancel; Database altered.
重建redo:
SQL> alter database drop logfile group 11;
alter database drop logfile group 12;
alter database drop logfile group 13;
alter database drop logfile group 14;
alter database drop logfile group 15;alter database drop logfile group 11
*
ERROR at line 1:
ORA-00261: log 11 of thread 1 is being archived or modified
ORA-00312: online log 11 thread 1:
'/u1/db/oracle/product/11.2.0/db_1/dbs/std_redo11.log' SQL>
Database altered. SQL>
Database altered. SQL>
Database altered. SQL> Database altered.
SQL> alter database add standby logfile thread 1 group 11 '/u1/db/oracle/product/11.2.0/db_1/dbs/std_redo11.log' size 50M;
alter database add standby logfile thread 1 group 16 '/u1/db/oracle/product/11.2.0/db_1/dbs/std_redo16.log' size 50M;
alter database add standby logfile thread 1 group 17 '/u1/db/oracle/product/11.2.0/db_1/dbs/std_redo17.log' size 50M;
alter database add standby logfile thread 2 group 18 '/u1/db/oracle/product/11.2.0/db_1/dbs/std_redo18.log' size 50M;
alter database add standby logfile thread 2 group 19 '/u1/db/oracle/product/11.2.0/db_1/dbs/std_redo19.log' size 50M;alter database add standby logfile thread 1 group 11 '/u1/db/oracle/product/11.2.0/db_1/dbs/std_redo11.log' size 50M
*
ERROR at line 1:
ORA-01184: logfile group 11 already exists SQL>
Database altered. SQL> Database altered. SQL> Database altered. SQL> Database altered.
主库切换归档:
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination +CRSDG
Oldest online log sequence 73
Next log sequence to archive 74
Current log sequence 74
SQL>
SQL>
SQL>
SQL> alter system switch logfile; System altered. SQL> / System altered. SQL> / System altered.
备库mrp状态,可以正常APPLYING_LOG
SQL> r
1* select process, status, thread#,sequence#, block#, blocks from v$managed_standby PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
--------- ------------ ---------- ---------- ---------- ----------
ARCH CLOSING 1 74 1 50
ARCH CLOSING 1 75 1 5
ARCH CONNECTED 0 0 0 0
ARCH CLOSING 1 76 1 1
RFS IDLE 0 0 0 0
RFS IDLE 0 0 0 0
RFS IDLE 0 0 0 0
RFS IDLE 1 77 1293 1
RFS IDLE 0 0 0 0
RFS IDLE 0 0 0 0
RFS IDLE 2 55 526 1 PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
--------- ------------ ---------- ---------- ---------- ----------
MRP0 APPLYING_LOG 2 55 526 102400 12 rows selected.
备库standby alert日志,可以正常应用
RFS[8]: Selected log 18 for thread 2 sequence 55 dbid 1608598914 branch 1080818180
Tue Aug 24 10:04:10 2021
Media Recovery Log /arch/2_54_1080818180.dbf
Media Recovery Log /arch/1_73_1080818180.dbf
Media Recovery Log /arch/1_74_1080818180.dbf
Media Recovery Log /arch/1_75_1080818180.dbf
Media Recovery Log /arch/1_76_1080818180.dbf
Media Recovery Waiting for thread 1 sequence 77 (in transit)
Recovery of Online Redo Log: Thread 1 Group 11 Seq 77 Reading mem 0
Mem# 0: /u1/db/oracle/product/11.2.0/db_1/dbs/std_redo11.log
Media Recovery Waiting for thread 2 sequence 55 (in transit)
Recovery of Online Redo Log: Thread 2 Group 18 Seq 55 Reading mem 0
Mem# 0: /u1/db/oracle/product/11.2.0/db_1/dbs/std_redo18.log
Tue Aug 24 10:10:05 2021
Successfully added datafile 7 to media recovery
Datafile #7: '/u1/db/oracle/product/11.2.0/db_1/dbs/ORCL_STB/datafile/o1_mf_smart_jl8o7x0o_.dbf'
DG:RFS[8]: No standby redo logfiles created for thread 2的更多相关文章
- 转 Alert.log shows No Standby Redo Logfiles Of Size 153600 Blocks Available
http://blog.itpub.net/23135684/viewspace-703620/ Alert.log shows No Standby Redo Logfiles Of Size 15 ...
- STANDBY REDO LOG
SRL Introduce 从">ORACLE9i开始,出现了Standby Redo Logs(SRL),9.1开始只有">physical standby支持SRL ...
- Standby Redo Logs的前世今生与最佳实践
编辑手记:使用过Data Guard的人应该对于Standby Redo Logs都不陌生,在配置了 Standby Redo Logs的standby中,能够进行日志的实时应用,同时Standby ...
- Oracle Dataguard Standby Redo Log的两个实验
在Data Guard环境中,Standby Redo Log是一个比较特殊的日志类型.从最新的DG安装指导中,都推荐在Primary和Standby端,都配置Standby Redo Log. 简单 ...
- dataguard 下主备 online redo 与 standby redo log resize 重建
环境说明: 本实验环境是一个节点的rac + 单节点 asm dg database 与 grid 版本是 11.2.0.4 .提别提醒 如果是多节点集群,操作时需要特别注意 thread . ...
- Standby Redo Log 的设定原则、创建、删除、查看、归档位置
设定: 1.每个standby redo log file 至少要和primary database的redo log 一样大,为了方便管理,Oracle 建议主备库的redo log 设置成一样的大 ...
- 配置standby redo log
Data Guard在最大保护和最高可用性模式下,Standby数据库必须配置standby redo log,通过下面的实验展示创建的原则和过程. 1.原则1).standby redo log的文 ...
- eclipse:Workspace in use or cannot be created
打开eclipse出现:Workspace in use or cannot be created, choose a different one 原因:出现这种情况一般是workspace的配置文件 ...
- 晚上打开eclipse时碰到这个问题 :Workspace in use or cannot be created, choose a different one.
晚上打开eclipse时碰到这个问题 :Workspace in use or cannot be created, choose a different one. 网上看到这方面的解决方式: 原因: ...
- 【spring data jpa】使用spring data jpa 的删除操作,需要加注解@Modifying @Transactional 否则报错如下: No EntityManager with actual transaction available for current thread - cannot reliably process 'remove' call
使用spring data jpa 的删除操作,需要加注解@Modifying @Transactional 否则报错如下: No EntityManager with actual tran ...
随机推荐
- redis部署集群时出现的问题(redis 版本 6.2.5)
配置 redis 集群时(redis 版本 6.2.5),我使用了同一个 server 端运行3个不同的配置文件. 配置文件中只修改了端口号并打开了 cluster-enable. 脚本运行后什么提示 ...
- 阿里云Linux服务器安装Maven实战教程
下载地址 https://maven.apache.org/download.cgi 文件上传 把下载的文件上传到阿里云服务器 /usr/local/software 的目录(使用工具) window ...
- 基础实验之访问控制列表ACL应用
要求: 1,PC1,PC2,PC3互通 2,配置ACL限制PC2不能访问PC3 1,首先规划好IP,配置如上图 SW2配置 # vlan batch 10 20 # interface Vlanif ...
- 转发:前端组件化之Monorepo方案实战
前言 在上一篇的前端组件化方案探究中,我们研究了什么是组件化以及我们为什么需要组件化.也调研和测试了一些开源项目,并且在使用.学习.研究.对比之后最终确定了以 pnpm + workspace + c ...
- MySQL 分组排序,取第一条
select t1.* from coal_installed_capacity t1where NOT EXISTS (select * from coal_installed_capacity t ...
- Sleuth 使用
sleuth是spring cloud中日志链(调用链解决方案),自动添加traceId,spanId. sleuth包也可单独引入,和其它藕合度小.sleuth + zipkin 实现APM管理. ...
- 《MySQL是怎样运行的》第四章小结
- 接口自动化之request几种常见请求及响应方法
request 的几种常见方法 1.request.get() 发送get请求 2.request.post() 发送post请求 3.request.delete() 发送delete请求 4.re ...
- AI智能问答助手 AI智能批量文章生成器 网站优化SEO批量内容生成工具 原创文章生成软件
<AI智能问答助手> 软件基于当下热门的OpenAI的ChatGPT技术,导入问题列表就可以批量生成对应的内容,内容质量高.原创度高.适合对内容生成需求量大的场景,如网站优化.广告文案 ...
- odoo ORM API学习总结兼orm学习教程
环境 odoo-14.0.post20221212.tar ORM API学习总结/学习教程 模型(Model) Model字段被定义为model自身的属性 from odoo import mode ...