标签云
asm恢复 bbed bootstrap$ dul In Memory kcbzib_kcrsds_1 kccpb_sanity_check_2 MySQL恢复 ORA-00312 ORA-00607 ORA-00704 ORA-00742 ORA-01110 ORA-01555 ORA-01578 ORA-01595 ORA-08103 ORA-600 2131 ORA-600 2662 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)
- 操作系统 (103)
- 数据库 (1,739)
- DB2 (22)
- MySQL (75)
- Oracle (1,589)
- Data Guard (52)
- EXADATA (8)
- GoldenGate (24)
- ORA-xxxxx (160)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (15)
- ORACLE 21C (3)
- Oracle 23ai (8)
- Oracle ASM (68)
- Oracle Bug (8)
- Oracle RAC (54)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (28)
- Oracle备份恢复 (582)
- Oracle安装升级 (95)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (84)
- PostgreSQL (27)
- pdu工具 (5)
- PostgreSQL恢复 (9)
- SQL Server (29)
- SQL Server恢复 (10)
- TimesTen (7)
- 达梦数据库 (2)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (37)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (20)
-
最近发表
- VMware勒索加密恢复(vmdk勒索恢复)
- ORA-39773: parse of metadata stream failed故障处理
- sql数据库备份失败—失败: 23(数据错误(循环冗余检查)
- vmdk文件被加密恢复(虚拟机文件加密)
- 差点被误操作的ORA-600 kcratr_nab_less_than_odr故障
- win平台19c 打patch遭遇2个小问题汇总
- pg单个数据库目录恢复-pdu恢复单个数据库目录数据
- pg删除数据恢复—pdu恢复pg delete数据
- .[OnlyBuy@cyberfear.com].REVRAC勒索mysql恢复
- 表dml操作权限授权给public,导致只读用户失效
- 21c数据库恢复遭遇ora-600 ktugct: corruption detected
- pg_control丢失/损坏处理
- 当前主流数据库版本服务支持周期-202503
- pg启动报invalid checkpoint record处理
- 删除redo导致ORA-00313 ORA-00312故障处理
- Navicat连接postgresql时出现column “datlastsysoid” does not exist错误解决
- aix磁盘损坏oracle数据库恢复
- pg误删除数据恢复(PostgreSQL delete数据恢复)
- PostgreSQL表文件损坏恢复—pdu恢复损坏的表文件
- linux rm -rf 删除数据文件恢复
标签归档:Control file mount id mismatch
Control file mount id mismatch!故障处理
通过沟通确认客户由于存储双活异常,业务运行在主存储上,另外一套存储修复之后,进行存储双活同步,结果在这个过程中由于遭遇Control file mount id mismatch! 导致数据库crash了
2023-05-03T20:21:07.446873+08:00 Archived Log entry 491897 added for T-1.S-246903 ID 0x97d92f0b LAD:1 2023-05-03T20:47:53.902701+08:00 Error: 2141 Control file mount id mismatch! fhmid: 2592441863, SGA mid: 2624617448 Requesting DIAG on each RAC instance to dump the control file header block 2023-05-03T20:47:55.906490+08:00 Errors in file /opt/rac/oracle/diag/rdbms/xff/xff1/trace/xff1_rms0_20989.trc: 2023-05-03T20:47:56.521500+08:00 RMS0 (ospid: 20989): terminating the instance 2023-05-03T20:47:56.610656+08:00 System state dump requested by (instance=1, osid=20989 (RMS0)), summary=[abnormal instance termination]. System State dumped to trace file /opt/rac/oracle/diag/rdbms/xff/xff1/trace/xff1_diag_20912_20230503204756.trc 2023-05-03T20:47:58.480397+08:00 License high water mark = 395 2023-05-03T20:48:02.600203+08:00 Instance terminated by RMS0, pid = 20989 2023-05-03T20:48:02.601563+08:00 Warning: 2 processes are still attach to shmid 393226: (size: 28672 bytes, creator pid: 19941, last attach/detach pid: 20912) 2023-05-03T20:48:03.481726+08:00 USER (ospid: 967): terminating the instance 2023-05-03T20:48:03.483351+08:00 Instance terminated by USER, pid = 967
节点自动重启报错ORA-600 kccsbck_first
2023-05-03T20:48:34.870435+08:00 NOTE: ASMB mounting group 2 (FRA) NOTE: ASM background process initiating disk discovery for grp 2 (reqid:0) NOTE: Assigning number (2,1) to disk (/dev/asm_data0g) NOTE: Assigning number (2,0) to disk (/dev/asm_data0f) SUCCESS: mounted group 2 (FRA) NOTE: grp 2 disk 1: FRA_0001 path:/dev/asm_data0g NOTE: grp 2 disk 0: FRA_0000 path:/dev/asm_data0f 2023-05-03T20:48:34.919965+08:00 NOTE: dependency between database xff and diskgroup resource ora.FRA.dg is established 2023-05-03T20:48:38.983416+08:00 Errors in file /opt/rac/oracle/diag/rdbms/xff/xff1/trace/xff1_ora_2436.trc (incident=1333249): ORA-00600: ??????, ??: [kccsbck_first], [1], [2624617448], [], [], [], [], [], [], [], [], [] Incident details in: /opt/rac/oracle/diag/rdbms/xff/xff1/incident/incdir_1333249/xff1_ora_2436_i1333249.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. ORA-600 signalled during: ALTER DATABASE MOUNT /* db agent *//* {0:8:116} */...
再次重启数据库报错ORA-00742 ORA-00312
2023-05-04T08:18:59.635790+08:00 Aborting crash recovery due to error 742 2023-05-04T08:18:59.635897+08:00 Errors in file /opt/rac/oracle/diag/rdbms/xff/xff1/trace/xff1_ora_80855.trc: ORA-00742: ??????? 2 ?? 244996 ? 8262 ?????????? ORA-00312: ???? 7 ?? 2: '+FRA/xff/ONLINELOG/group_7.446.1059323695' ORA-00312: ???? 7 ?? 2: '+DATA/xff/ONLINELOG/group_7.272.1059323695' Abort recovery for domain 0, flags 4 2023-05-04T08:18:59.647994+08:00 Errors in file /opt/rac/oracle/diag/rdbms/xff/xff1/trace/xff1_ora_80855.trc: ORA-00742: ??????? 2 ?? 244996 ? 8262 ?????????? ORA-00312: ???? 7 ?? 2: '+FRA/xff/ONLINELOG/group_7.446.1059323695' ORA-00312: ???? 7 ?? 2: '+DATA/xff/ONLINELOG/group_7.272.1059323695' ORA-742 signalled during: ALTER DATABASE OPEN /* db agent *//* {2:37368:2} */... 2023-05-04T08:19:00.820708+08:00 License high water mark = 33 2023-05-04T08:19:00.820936+08:00 USER (ospid: 82788): terminating the instance 2023-05-04T08:19:01.827132+08:00 Instance terminated by USER, pid = 82788
明显数据库在启动的时候做实例恢复,发现redo写丢失,从而引起数据库无法正常open,对于此类故障,处理比较多
ORA-00742 ORA-00312 故障恢复-1
ORA-00742 ORA-00312故障恢复-2
ORA-00742: 日志读取在线程 %d 序列 %d 块 %d 中检测到写入丢失情况