标签云
asm恢复 bbed bootstrap$ dul kcbzib_kcrsds_1 kccpb_sanity_check_2 kcratr_nab_less_than_odr MySQL恢复 obet ORA-00312 ORA-00704 ORA-00742 ORA-01110 ORA-01200 ORA-01555 ORA-01578 ORA-01595 ORA-600 2662 ORA-600 2663 ORA-600 3020 ORA-600 4000 ORA-600 4137 ORA-600 4193 ORA-600 4194 ORA-600 16703 ORA-600 kcbzib_kcrsds_1 ORA-600 KCLCHKBLK_4 ORA-600 kcratr_nab_less_than_odr ORA-15042 ORA-15196 ORACLE 12C oracle dul ORACLE PATCH Oracle Recovery Tools oracle加密恢复 oracle勒索 oracle勒索恢复 oracle异常恢复 ORACLE恢复 Oracle 恢复 ORACLE数据库恢复 oracle碎片 OSD-04016 YOUR FILES ARE ENCRYPTED 比特币加密文章分类
- MongoDB (1)
- MongoDB恢复 (1)
- Others (2)
- 中间件 (2)
- WebLogic (2)
- 操作系统 (112)
- 数据库 (1,877)
- DB2 (22)
- MySQL (82)
- Oracle (1,703)
- Data Guard (53)
- EXADATA (8)
- GoldenGate (24)
- ORA-xxxxx (168)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (15)
- ORACLE 21C (3)
- Oracle 23ai (8)
- Oracle ASM (72)
- Oracle Bug (8)
- Oracle RAC (56)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (29)
- Oracle备份恢复 (659)
- Oracle安装升级 (107)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (91)
- PostgreSQL (37)
- pdu工具 (7)
- PostgreSQL恢复 (13)
- SQL Server (34)
- SQL Server恢复 (14)
- TimesTen (7)
- 达梦数据库 (5)
- 达梦恢复 (3)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (51)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (34)
- MongoDB (1)
-
最近发表
- MongoDB 离线提取工具—mongoext
- .bres勒索病毒加密数据库dmp文件可恢复
- ORA-600 krsm_mrp_rebuild_lf_list.lno_mismatch
- 记录一次0丢失的ORA-00354: 损坏重做日志块标头故障恢复
- 不当数据库恢复操作导致一个月数据丢失
- obet快速修复oracle 位图损坏块
- 不太常见的10.2.0.1的oracle redo损坏恢复
- obet forcecopy功能抢救硬件故障中的数据文件
- kcratr_nab_less_than_odr和system坏块故障处理
- 通过obet 恢复system坏块,打开数据库
- obet dbv功能完整说明
- 分享一例运行在aix上的sap系统数据库恢复过程
- OBET-Oracle Block Editor Tool使用说明
- 几乎动用了所有手段的Oracle故障恢复
- Oracle Block Edit Tool (obet) 功能增强–2026.07
- Oracle 19c 202607补丁(RUs+OJVM)-19.32
- Patch_SCN快速修复ORA-01555数据库open故障
- 快速处理 ORA-01210: data file header is media corrupt 故障
- ORA-00314: log 3 of thread 1, expected sequence# N doesn’t match 0
- 记录block 0损坏,数据文件大量坏块,使用不当数据库版本恢复等各种操作之后的故障处理
标签归档:No SRLs available for T-1
log_archive_dest_1配置不当,当时standby redo无法归档引起adg不能实时同步
oracle database dataguard无法利用standby redo实时同步
2025-08-12T18:41:57.474031+08:00 PR00 (PID:245113): Media Recovery Log /u01/app/oracle/fast_recovery_area/……/2025_08_12/o1_mf_1_34206_n9p6mmkb_.arc PR00 (PID:245113): Media Recovery Waiting for T-1.S-34207 (in transit)
clear standby redo之后,实时同步一会儿,又无法实时同步
2025-08-12T18:43:28.183908+08:00 PR00 (PID:245113): MRP0: Background Media Recovery cancelled with status 16037 2025-08-12T18:43:28.184131+08:00 Errors in file /u01/app/oracle/diag/rdbms/dclhrdg2/DCLHR/trace/DCLHR_pr00_245113.trc: ORA-16037: user requested cancel of managed recovery operation PR00 (PID:245113): Managed Standby Recovery not using Real Time Apply Recovery interrupted! Stopping change tracking 2025-08-12T18:43:28.356862+08:00 Errors in file /u01/app/oracle/diag/rdbms/dclhrdg2/DCLHR/trace/DCLHR_pr00_245113.trc: ORA-16037: user requested cancel of managed recovery operation 2025-08-12T18:43:28.482234+08:00 Background Media Recovery process shutdown (DCLHR) 2025-08-12T18:43:29.178708+08:00 Managed Standby Recovery Canceled (DCLHR) 2025-08-12T18:43:44.724806+08:00 Clearing online log 11 of thread 1 sequence number 34111 2025-08-12T18:44:00.545234+08:00 Clearing online log 12 of thread 1 sequence number 34112 2025-08-12T18:44:10.770626+08:00 Clearing online log 13 of thread 1 sequence number 34113 2025-08-12T18:44:31.911565+08:00 Clearing online log 14 of thread 1 sequence number 34114 2025-08-12T18:44:42.111444+08:00 Clearing online log 15 of thread 1 sequence number 34108 2025-08-12T18:45:06.031673+08:00 Warning: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE has been deprecated. Warning: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE has been deprecated. 2025-08-12T18:45:06.047722+08:00 Attempt to start background Managed Standby Recovery process (DCLHR) Starting background process MRP0 2025-08-12T18:45:06.062512+08:00 MRP0 started with pid=219, OS id=245503 2025-08-12T18:45:06.064300+08:00 Background Managed Standby Recovery process started (DCLHR) 2025-08-12T18:45:11.086271+08:00 Started logmerger process 2025-08-12T18:45:11.100434+08:00 IM on ADG: Start of Empty Journal IM on ADG: End of Empty Journal PR00 (PID:245509): Managed Standby Recovery starting Real Time Apply max_pdb is 3 2025-08-12T18:45:13.275444+08:00 Parallel Media Recovery started with 80 slaves 2025-08-12T18:45:13.392342+08:00 Stopping change tracking PR00 (PID:245509): Media Recovery Waiting for T-1.S-34207 (in transit) 2025-08-12T18:46:22.717320+08:00 rfs (PID:245728): krsr_rfs_atc: Identified database type as 'PHYSICAL STANDBY': Client is Foreground (PID:15566) 2025-08-12T18:46:31.950359+08:00 rfs (PID:244324): Archived Log entry 99 added for B-1149239150.T-1.S-34207 ID 0x57544f44 LAD:32 2025-08-12T18:46:32.185391+08:00 rfs (PID:245735): krsr_rfs_atc: Identified database type as 'PHYSICAL STANDBY': Client is ASYNC (PID:3334853) rfs (PID:245735): Primary database is in MAXIMUM PERFORMANCE mode 2025-08-12T18:46:32.331928+08:00 rfs (PID:245735): Selected LNO:11 for T-1.S-34208 dbid 1299764411 branch 1149239150 2025-08-12T18:46:32.885400+08:00 PR00 (PID:245509): Media Recovery Log /u01/app/oracle/fast_recovery_area/……/2025_08_12/o1_mf_1_34207_n9p6mo8f_.arc PR00 (PID:245509): Media Recovery Waiting for T-1.S-34208 (in transit) 2025-08-12T18:46:33.669769+08:00 Recovery of Online Redo Log: Thread 1 Group 11 Seq 34208 Reading mem 0 Mem# 0: /u01/app/oracle/oradata/DCLHR/std_redo11.log 2025-08-12T18:50:03.011923+08:00 Expanded controlfile section 28 from 141 to 282 records Requested to grow by 141 records; added 2 blocks of records 2025-08-12T19:16:29.515866+08:00 rfs (PID:245735): Selected LNO:12 for T-1.S-34209 dbid 1299764411 branch 1149239150 2025-08-12T19:16:29.515943+08:00 PR00 (PID:245509): Media Recovery Waiting for T-1.S-34209 (in transit) 2025-08-12T19:16:30.522048+08:00 Recovery of Online Redo Log: Thread 1 Group 12 Seq 34209 Reading mem 0 Mem# 0: /u01/app/oracle/oradata/DCLHR/std_redo12.log 2025-08-12T19:46:29.852369+08:00 rfs (PID:245735): Selected LNO:13 for T-1.S-34210 dbid 1299764411 branch 1149239150 2025-08-12T19:46:29.852443+08:00 PR00 (PID:245509): Media Recovery Waiting for T-1.S-34210 (in transit) 2025-08-12T19:46:30.858423+08:00 Recovery of Online Redo Log: Thread 1 Group 13 Seq 34210 Reading mem 0 Mem# 0: /u01/app/oracle/oradata/DCLHR/std_redo13.log 2025-08-12T20:16:29.978563+08:00 rfs (PID:245735): Selected LNO:14 for T-1.S-34211 dbid 1299764411 branch 1149239150 2025-08-12T20:16:30.012723+08:00 PR00 (PID:245509): Media Recovery Waiting for T-1.S-34211 (in transit) 2025-08-12T20:16:30.013045+08:00 Recovery of Online Redo Log: Thread 1 Group 14 Seq 34211 Reading mem 0 Mem# 0: /u01/app/oracle/oradata/DCLHR/std_redo14.log 2025-08-12T20:46:30.307116+08:00 rfs (PID:245735): Selected LNO:15 for T-1.S-34212 dbid 1299764411 branch 1149239150 2025-08-12T20:46:30.339601+08:00 PR00 (PID:245509): Media Recovery Waiting for T-1.S-34212 (in transit) 2025-08-12T20:46:30.339893+08:00 Recovery of Online Redo Log: Thread 1 Group 15 Seq 34212 Reading mem 0 Mem# 0: /u01/app/oracle/oradata/DCLHR/std_redo15.log 2025-08-12T21:16:27.517565+08:00 rfs (PID:245735): No SRLs available for T-1 2025-08-12T21:16:27.560282+08:00 PR00 (PID:245509): Media Recovery Waiting for T-1.S-34213 (in transit) 2025-08-12T21:16:27.615513+08:00 rfs (PID:245735): Opened log for T-1.S-34213 dbid 1299764411 branch 1149239150 2025-08-12T21:46:27.633777+08:00 rfs (PID:245735): Archived Log entry 100 added for B-1149239150.T-1.S-34213 ID 0x57544f44 LAD:32 rfs (PID:245735): No SRLs available for T-1 2025-08-12T21:46:27.787746+08:00 rfs (PID:245735): Opened log for T-1.S-34214 dbid 1299764411 branch 1149239150 2025-08-12T21:46:28.439910+08:00 PR00 (PID:245509): Media Recovery Log /u01/app/oracle/fast_recovery_area/……/2025_08_12/o1_mf_1_34213_n9phockd_.arc 2025-08-12T21:46:32.804540+08:00 PR00 (PID:245509): Media Recovery Waiting for T-1.S-34214 (in transit) 2025-08-12T22:16:27.968668+08:00 rfs (PID:245735): Archived Log entry 101 added for B-1149239150.T-1.S-34214 ID 0x57544f44 LAD:32 rfs (PID:245735): No SRLs available for T-1
从报错信息看是由于无可用的standby redo导致(No SRLs available for T-1),查询standby redo状态
[oracle@db03 trace]$ ss
SQL*Plus: Release 19.0.0.0.0 - Production on Wed Aug 13 15:58:46 2025
Version 19.20.0.0.0
Copyright (c) 1982, 2022, Oracle. All rights reserved.
s
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.20.0.0.0
SQL> elect group#,status from v$standby_log;
GROUP# STATUS
---------- ----------
11 ACTIVE
12 ACTIVE
13 ACTIVE
14 ACTIVE
15 ACTIVE
所有的standby redo都是active状态,导致无可用standby redo,出现该问题的原因,初步怀疑是standby redo无法归档导致,引起该问题的原因怀疑是由于该备库的log_archive_dest_N参数设置不当导致,检查相关参数
*.db_unique_name='DCLHRDG2' *.fal_client='DCLHRDG2' *.fal_server='DCLHRDG','DCLHR' *.log_archive_config='dg_config=(DCLHR,DCLHRDG,DCLHRDG2)' *.log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST valid_for=(all_logfiles,all_roles) db_unique_name=DCLHRDG' *.log_archive_dest_2='service=DCLHR lgwr async valid_for=(online_logfiles,primary_role) db_unique_name=DCLHR' *.log_archive_dest_3='service=DCLHRDG2 lgwr async valid_for=(online_logfiles,primary_role) db_unique_name=DCLHRDG2'
比较明显由于log_archive_dest_1和log_archive_dest_3的相关参数配置不对导致standby redo无法通过log_archive_dest_1进行归档导致,正确的配置方式为
*.log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST valid_for=(all_logfiles,all_roles) db_unique_name=DCLHRDG' *.log_archive_dest_3='service=DCLHRDG lgwr async valid_for=(online_logfiles,primary_role) db_unique_name=DCLHRDG'
这样配置之后,该dg库同步日志正常.

加我微信(17813235971)
加我QQ(107644445)

