标签云
asm恢复 bbed bootstrap$ dul In Memory kcbzib_kcrsds_1 kccpb_sanity_check_2 kfed MySQL恢复 ORA-00312 ORA-00607 ORA-00704 ORA-01110 ORA-01555 ORA-01578 ORA-08103 ORA-600 2131 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-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 勒索恢复 比特币加密文章分类
- Others (2)
- 中间件 (2)
- WebLogic (2)
- 操作系统 (102)
- 数据库 (1,682)
- DB2 (22)
- MySQL (73)
- Oracle (1,544)
- Data Guard (52)
- EXADATA (8)
- GoldenGate (24)
- ORA-xxxxx (159)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (15)
- ORACLE 21C (3)
- Oracle 23ai (7)
- Oracle ASM (67)
- Oracle Bug (8)
- Oracle RAC (53)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (28)
- Oracle备份恢复 (565)
- Oracle安装升级 (92)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (79)
- PostgreSQL (18)
- PostgreSQL恢复 (6)
- SQL Server (27)
- SQL Server恢复 (8)
- TimesTen (7)
- 达梦数据库 (2)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (37)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (20)
-
最近发表
- 断电引起的ORA-08102: 未找到索引关键字, 对象号 39故障处理
- ORA-00227: corrupt block detected in control file
- 手工删除19c rac
- 解决oracle数据文件路径有回车故障
- .wstop扩展名勒索数据库恢复
- Oracle Recovery Tools工具一键解决ORA-00376 ORA-01110故障(文件offline)
- OGG-02771 Input trail file format RELEASE 19.1 is different from previous trail file form at RELEASE 11.2.
- OGG-02246 Source redo compatibility level 19.0.0 requires trail FORMAT 12.2 or higher
- GoldenGate 19安装和打patch
- dd破坏asm磁盘头恢复
- 删除asmlib磁盘导致磁盘组故障恢复
- Kylin Linux 安装19c
- ORA-600 krse_arc_complete.4
- Oracle 19c 202410补丁(RUs+OJVM)
- ntfs MFT损坏(ntfs文件系统故障)导致oracle异常恢复
- .mkp扩展名oracle数据文件加密恢复
- 清空redo,导致ORA-27048: skgfifi: file header information is invalid
- A_H_README_TO_RECOVER勒索恢复
- 通过alert日志分析客户自行对一个数据库恢复的来龙去脉和点评
- ORA-12514: TNS: 监听进程不能解析在连接描述符中给出的SERVICE_NAME
分类目录归档:Data Guard
ORA-10485: Real-Time Query cannot be enabled while applying migration redo.
对于数据库打psu和jvm patch之后,dg备库同步会出现类似ORA-10485: Real-Time Query cannot be enabled while applying migration redo.异常
Tue Aug 15 18:48:18 2023 ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION Attempt to start background Managed Standby Recovery process (orcl) Tue Aug 15 18:48:18 2023 MRP0 started with pid=33, OS id=15486 MRP0: Background Managed Standby Recovery process started (orcl) started logmerger process Tue Aug 15 18:48:23 2023 Managed Standby Recovery starting Real Time Apply Parallel Media Recovery started with 80 slaves Waiting for all non-current ORLs to be archived... All non-current ORLs have been archived. Recovery of Online Redo Log: Thread 1 Group 10 Seq 106115 Reading mem 0 Mem# 0: /u01/app/oracle/oradata/orcl/std_redo10.log Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION Tue Aug 15 18:49:50 2023 RFS[1]: Assigned to RFS process 16049 RFS[1]: Opened log for thread 1 sequence 106117 dbid 1490144467 branch 962363734 Tue Aug 15 18:49:50 2023 RFS[2]: Assigned to RFS process 16051 RFS[2]: Selected log 10 for thread 1 sequence 106115 dbid 1490144467 branch 962363734 Tue Aug 15 18:49:50 2023 RFS[3]: Assigned to RFS process 16053 RFS[3]: Opened log for thread 1 sequence 106116 dbid 1490144467 branch 962363734 Archived Log entry 106102 added for thread 1 sequence 106116 rlc 962363734 ID 0x58d223d3 dest 2: RFS[3]: Opened log for thread 1 sequence 106118 dbid 1490144467 branch 962363734 RFS[2]: Opened log for thread 1 sequence 106119 dbid 1490144467 branch 962363734 Tue Aug 15 18:49:50 2023 Archived Log entry 106103 added for thread 1 sequence 106115 ID 0x58d223d3 dest 1: Tue Aug 15 18:49:50 2023 Media Recovery Log /u01/app/oracle/fast_recovery_area/ORCLDG/archivelog/2023_08_15/o1_mf_1_106116_lfpp2ghc_.arc Errors with log /u01/app/oracle/fast_recovery_area/ORCLDG/archivelog/2023_08_15/o1_mf_1_106116_lfpp2ghc_.arc MRP0: Background Media Recovery terminated with error 10485 Errors in file /u01/app/oracle/diag/rdbms/orcldg/orcl/trace/orcl_pr00_15488.trc: ORA-10485: Real-Time Query cannot be enabled while applying migration redo. Managed Standby Recovery not using Real Time Apply Recovery interrupted! Tue Aug 15 18:49:50 2023 MRP0: Background Media Recovery process shutdown (orcl)
这种情况,是由于数据库在upgrade模式下产生日志无法正常被adg实时应用,我一般是临时rman应用备库日志解决,官方解决方案:MRP process getting terminated with error ORA-10485 (Doc ID 1618485.1)
11g CASE --------- 1> Stop DG broker (if used) i.e., on primary and standby SQL> alter system set dg_broker_start = false scope = both sid = '*' ; 2> Stop managed recovery in the standby, shutdown the standby and startup mount. start managed recovery without real time apply. SQL> alter database recover managed standby database disconnect ; 3> Wait until all the redo is applied to the standby and the standby is in sync. Do a couple of log switches on the primary, all instances if RAC, and let them apply to the standby. 4> Shutdown the standby and startup mount start managed recovery with real time apply. SQL> alter database recover managed standby database using current logfile disconnect ; 5> Restart broker(if used). on primary and standby SQL> alter system set dg_broker_start = true scope = both sid = '*' ; 12c CASE ---------- In 12c and later, start Archived log apply using below command with ARCHIVED LOGFILE option: SQL> alter database recover managed standby database using archived logfile disconnect; Wait until all the redo is applied to the standby and the standby is in sync. Do a couple of log switches on the primary, all instances if RAC, and let them apply to the standby. To stop Redo Apply, Issue the following SQL statement: SQL> alter database recover managed standby database cancel; start managed recovery with real time apply, Issue the following SQL statement SQL> alter database recover managed standby database disconnect;
RMAN-06214: Archivelog错误
有一个客户他是linux到win环境dg,alert日志报清除fra中日志失败
un Jun 25 10:50:14 2023 Media Recovery Waiting for thread 1 sequence 196437 (in transit) Sun Jun 25 10:50:26 2023 WARNING: Cannot delete Oracle managed file /u01/oracle/fast_recovery_area/XFFDG/archivelog/2023_05_28/o1_mf_1_192078_l74s4m2l_.arc Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\XFFwin\XFF\trace\XFF_rfs_1100.trc: ORA-01265: 无法删除 ARCHIVED LOG /u01/oracle/fast_recovery_area/XFFDG/archivelog/2023_05_28/o1_mf_1_192078_l74s4m2l_.arc ORA-27056: 无法删除文件 OSD-04029: 无法获取文件属性 O/S-Error: (OS 3) 系统找不到指定的路径。
尝试人工rman删除日志,报RMAN-06214错误
RMAN-06214: Archivelog /u01/oracle/fast_recovery_area/XFFDG/archivelog/2023_05_29/o1_mf_1_192575_l78zobv0_.arc RMAN-06214: Archivelog /u01/oracle/fast_recovery_area/XFFDG/archivelog/2023_05_29/o1_mf_1_192576_l791fo3j_.arc RMAN-06214: Archivelog /u01/oracle/fast_recovery_area/XFFDG/archivelog/2023_05_29/o1_mf_1_192577_l7935w3d_.arc RMAN-06214: Archivelog /u01/oracle/fast_recovery_area/XFFDG/archivelog/2023_05_29/o1_mf_1_192578_l794y5bc_.arc RMAN-06214: Archivelog /u01/oracle/fast_recovery_area/XFFDG/archivelog/2023_05_29/o1_mf_1_192579_l795cngq_.arc RMAN-06214: Archivelog /u01/oracle/fast_recovery_area/XFFDG/archivelog/2023_05_29/o1_mf_1_192580_l795con4_.arc RMAN-06214: Archivelog /u01/oracle/fast_recovery_area/XFFDG/archivelog/2023_05_29/o1_mf_1_192581_l795jtxk_.arc RMAN-06214: Archivelog /u01/oracle/fast_recovery_area/XFFDG/archivelog/2023_05_29/o1_mf_1_192582_l795k97z_.arc RMAN-06214: Archivelog /u01/oracle/fast_recovery_area/XFFDG/archivelog/2023_05_29/o1_mf_1_192583_l795noy1_.arc RMAN-06214: Archivelog /u01/oracle/fast_recovery_area/XFFDG/archivelog/2023_05_29/o1_mf_1_192584_l795vvjg_.arc RMAN-06214: Archivelog /u01/oracle/fast_recovery_area/XFFDG/archivelog/2023_05_29/o1_mf_1_192585_l796y9o2_.arc RMAN-06214: Archivelog /u01/oracle/fast_recovery_area/XFFDG/archivelog/2023_05_29/o1_mf_1_192586_l798pk99_.arc RMAN-06214: Archivelog /u01/oracle/fast_recovery_area/XFFDG/archivelog/2023_05_29/o1_mf_1_192587_l79bgx33_.arc RMAN-06214: Archivelog /u01/oracle/fast_recovery_area/XFFDG/archivelog/2023_05_29/o1_mf_1_192588_l79bm1wf_.arc RMAN-06214: Archivelog /u01/oracle/fast_recovery_area/XFFDG/archivelog/2023_05_29/o1_mf_1_192589_l79bm2tn_.arc
crosscheck报ORA-19633错
RMAN> CROSSCHECK ARCHIVELOG ALL; 释放的通道: ORA_DISK_1 释放的通道: ORA_DISK_2 释放的通道: ORA_DISK_3 释放的通道: ORA_DISK_4 分配的通道: ORA_DISK_1 通道 ORA_DISK_1: SID=1717 设备类型=DISK 分配的通道: ORA_DISK_2 通道 ORA_DISK_2: SID=13 设备类型=DISK 分配的通道: ORA_DISK_3 通道 ORA_DISK_3: SID=579 设备类型=DISK 分配的通道: ORA_DISK_4 通道 ORA_DISK_4: SID=1148 设备类型=DISK 对归档日志的验证成功 归档日志文件名=D:\APP\ADMINISTRATOR\FAST_RECOVERY_AREA\XFFWIN\ARCHIVELOG\2023_06_25\O1_MF_1_196451_L9HC90MS_.ARC REC ID=35113 STAMP=1140433431 对归档日志的验证成功 归档日志文件名=D:\APP\ADMINISTRATOR\FAST_RECOVERY_AREA\XFFWIN\ARCHIVELOG\2023_06_25\O1_MF_1_196452_L9HC9271_.ARC REC ID=35112 STAMP=1140433425 已交叉检验的 2 对象 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: crosscheck 命令 (ORA_DISK_4 通道上, 在 06/25/2023 11:04:30 上) 失败 ORA-19633: 控制文件记录 30322 与恢复目录不同步
常规方法无法删除归档日志,只能通过dbms包强制删除归档日志
C:\Users\Administrator>sqlplus / as sysdba SQL*Plus: Release 11.2.0.4.0 Production on 星期日 6月 25 11:05:15 2023 Copyright (c) 1982, 2013, Oracle. All rights reserved. 连接到: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> execute sys.dbms_backup_restore.resetCfileSection( 11); PL/SQL 过程已成功完成。
ORA-600 kcbr_apply_change_11
客户active dataguard应用日志报ORA-600 kcbr_apply_change_11错误
Sun Jun 25 10:31:25 2023 ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION Sun Jun 25 10:31:25 2023 MRP0 started with pid=32, OS id=6380 started logmerger process Sun Jun 25 10:31:30 2023 Managed Standby Recovery starting Real Time Apply Parallel Media Recovery started with 4 slaves Waiting for all non-current ORLs to be archived... All non-current ORLs have been archived. Media Recovery Log D:\APP\ADMINISTRATOR\FAST_RECOVERY_AREA\xffWIN\ARCHIVELOG\2023_06_23\O1_MF_1_196319_L99NQQSN_.ARC Sun Jun 25 10:31:31 2023 Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\xffwin\xff\trace\xff_pr03_1540.trc (incident=180300): ORA-00600: 内部错误代码, 参数: [kcbr_apply_change_11], [], [], [], [], [], [], [], [], [], [], [] Incident details in: D:\APP\ADMINISTRATOR\diag\rdbms\xffwin\xff\incident\incdir_180300\xff_pr03_1540_i180300.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION Sun Jun 25 10:31:32 2023 Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\xffwin\xff\trace\xff_pr02_752.trc (incident=180292): ORA-00600: 内部错误代码, 参数: [kcbr_apply_change_11], [], [], [], [], [], [], [], [], [], [], [] Incident details in: D:\APP\ADMINISTRATOR\diag\rdbms\xffwin\xff\incident\incdir_180292\xff_pr02_752_i180292.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\xffwin\xff\trace\xff_rfs_6032.trc: ORA-01265: 无法删除 ARCHIVED LOG /u01/oracle/fast_recovery_area/xffDG/archivelog/2023_05_28/o1_mf_1_192064_l74rj3jz_.arc ORA-27056: 无法删除文件 OSD-04029: 无法获取文件属性 O/S-Error: (OS 3) 系统找不到指定的路径。 Archived Log entry 35084 added for thread 1 sequence 196424 rlc 1013082900 ID 0xe513780f dest 3: RFS[7]: Opened log for thread 1 sequence 196430 dbid -451738353 branch 1013082900 Slave exiting with ORA-600 exception Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\xffwin\xff\trace\xff_pr02_752.trc: ORA-00600: 内部错误代码, 参数: [kcbr_apply_change_11], [], [], [], [], [], [], [], [], [], [], [] Sun Jun 25 10:31:41 2023 Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\xffwin\xff\trace\xff_pr04_3696.trc (incident=180308): ORA-00600: 内部错误代码, 参数: [kcbr_apply_change_11], [], [], [], [], [], [], [], [], [], [], [] Incident details in: D:\APP\ADMINISTRATOR\diag\rdbms\xffwin\xff\incident\incdir_180308\xff_pr04_3696_i180308.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Sun Jun 25 10:31:41 2023 Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\xffwin\xff\trace\xff_mrp0_6380.trc (incident=180268): ORA-00600: 内部错误代码, 参数: [kcbr_apply_change_11], [], [], [], [], [], [], [], [], [], [], [] Incident details in: D:\APP\ADMINISTRATOR\diag\rdbms\xffwin\xff\incident\incdir_180268\xff_mrp0_6380_i180268.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Recovery Slave PR02 previously exited with exception 600 Sun Jun 25 10:31:41 2023 MRP0: Background Media Recovery terminated with error 448 Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\xffwin\xff\trace\xff_pr00_7812.trc: ORA-00448: 后台进程正常结束 Managed Standby Recovery not using Real Time Apply Sun Jun 25 10:31:41 2023 Slave exiting with ORA-600 exception Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\xffwin\xff\trace\xff_pr03_1540.trc: ORA-00600: 内部错误代码, 参数: [kcbr_apply_change_11], [], [], [], [], [], [], [], [], [], [], [] Sun Jun 25 10:31:43 2023 Sweep [inc][180308]: completed Sweep [inc][180300]: completed Sweep [inc][180292]: completed Sweep [inc][180268]: completed Sweep [inc2][180300]: completed Sweep [inc2][180292]: completed Sweep [inc2][180268]: completed Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\xffwin\xff\trace\xff_pr04_3696.trc: ORA-00448: 后台进程正常结束 ORA-00600: 内部错误代码, 参数: [kcbr_apply_change_11], [], [], [], [], [], [], [], [], [], [], [] Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\xffwin\xff\trace\xff_pr04_3696.trc: ORA-00339: 归档日志未包含任何重做 ORA-00334: 归档日志: 'D:\APP\ADMINISTRATOR\ORADATA\xff\REDO02.LOG' ORA-00600: 内部错误代码, 参数: [kcbr_apply_change_11], [], [], [], [], [], [], [], [], [], [], [] Slave exiting with ORA-600 exception Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\xffwin\xff\trace\xff_pr04_3696.trc: ORA-00600: 内部错误代码, 参数: [kcbr_apply_change_11], [], [], [], [], [], [], [], [], [], [], []
通过分析可能为:Bug 31104809 – ORA-600: [kcbr_apply_change_11] during adg recovery (Doc ID 31104809.8)
官方WORKAROUND:
In ADG, mount the database (do not open it) and restart media recovery; once
the affected redo log sequence is applied, open the ADG in read only mode.