标签云
asm mount asm 恢复 asm恢复 bbed bootstrap$ dul eking 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 2662 ORA-600 3020 ORA-600 4000 ORA-600 4137 ORA-600 4193 ORA-600 4194 ORA-600 16703 ORA-15042 ORA-15196 ORACLE 12C oracle dul ORACLE PATCH Oracle Recovery Tools oracle加密恢复 oracle勒索 oracle异常恢复 ORACLE恢复 Oracle 恢复 ORACLE数据库恢复 oracle 比特币 OSD-04016 sql加密恢复 YOUR FILES ARE ENCRYPTED 勒索恢复 比特币 oracle 比特币加密文章分类
- Others (2)
- 中间件 (2)
- WebLogic (2)
- 操作系统 (91)
- 数据库 (1,419)
- DB2 (22)
- MySQL (58)
- Oracle (1,305)
- Data Guard (41)
- EXADATA (7)
- GoldenGate (20)
- ORA-xxxxx (150)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (12)
- ORACLE 21C (3)
- Oracle ASM (58)
- Oracle Bug (7)
- Oracle RAC (42)
- Oracle 安全 (6)
- Oracle 开发 (26)
- Oracle 监听 (26)
- Oracle备份恢复 (438)
- Oracle安装升级 (71)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (63)
- PostgreSQL (10)
- SQL Server (26)
- SQL Server恢复 (7)
- TimesTen (7)
- 达梦数据库 (2)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (24)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (7)
-
最近发表
- O/S-Error: (OS 23) 数据错误(循环冗余检查) 数据库恢复
- 数据库open报ORA-00959: tablespace ‘UNDOTBS1′ does not exist分析
- ASM删除表空间恢复
- ORA-12518 ORA-27302: 错误发生在: ssthrddcr
- plsql 插入blob
- 分享运气超级好的一次drop tablespace 数据恢复
- segment header异常对象删除处理
- Oracle 数据库(RDBMS)的版本支持状态摘要 (Doc ID 1674382.1)
- [back2023@proxy.tg].eking勒索数据库恢复
- ORA-600 ktbsdp2 处理
- win文件系统损坏oracle恢复
- asm disk 磁盘部分被清空恢复
- File #xxx found in data dictionary but not in controlfile. Creating OFFLINE file ‘MISSING00XXX’ in the controlfile
- commit_wait和commit_logging设置不当导致数据库无法正常启动
- ORA-00742 ORA-00312故障恢复
- 110T oracle故障恢复
- ora-600 kcratr_scan_lastbwr
- .asistchinadecryption扩展名勒索数据库恢复
- .[decrypt20@firemail.cc].eking 数据库勒索恢复
- ocr磁盘组掉盘故障处理
友情链接
标签归档:19c ORA-600 4194
Oracle 19c故障恢复
有客户找到我们,他们的oracle 19c数据库由于异常断电,导致启动异常,经过一系列恢复之后,依旧无法解决问题,请求我们给予支持.通过我们的Oracle数据库异常恢复检查脚本(Oracle Database Recovery Check),获取数据库当前信息如下:
数据库版本为19C并且安装了19.5.0.0.191015 (30125133)补丁
数据库使用pdb

数据库启动成功后,一会就crash掉
2020-03-10T01:44:41.018032+08:00 Pluggable database RACBAK opened read write 2020-03-10T01:44:41.018996+08:00 Pluggable database RAC opened read write 2020-03-10T01:44:51.244050+08:00 Completed: ALTER PLUGGABLE DATABASE ALL OPEN Starting background process CJQ0 Completed: ALTER DATABASE OPEN 2020-03-10T01:44:51.317085+08:00 CJQ0 started with pid=224, OS id=32581 2020-03-10T01:44:56.067043+08:00 Errors in file /opt/oracle/diag/rdbms/XFF/XFF/trace/XFF_j001_32588.trc (incident=1095281) (PDBNAME=RAC): ORA-00600: internal error code, arguments: [4193], [27733], [27754], [], [], [], [], [], [], [], [], [] RAC(4):Incident details in: /opt/oracle/diag/rdbms/XFF/XFF/incident/incdir_1095281/XFF_j001_32588_i1095281.trc RAC(4):Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. 2020-03-10T01:44:56.073112+08:00 RAC(4):***************************************************************** RAC(4):An internal routine has requested a dump of selected redo. RAC(4):This usually happens following a specific internal error, when RAC(4):analysis of the redo logs will help Oracle Support with the RAC(4):diagnosis. RAC(4):It is recommended that you retain all the redo logs generated (by RAC(4):all the instances) during the past 12 hours, in case additional RAC(4):redo dumps are required to help with the diagnosis. RAC(4):***************************************************************** 2020-03-10T01:44:56.079228+08:00 Errors in file /opt/oracle/diag/rdbms/XFF/XFF/trace/XFF_j002_32590.trc (incident=1095289) (PDBNAME=RAC): ORA-00600: internal error code, arguments: [4193], [2633], [2638], [], [], [], [], [], [], [], [], [] RAC(4):Incident details in: /opt/oracle/diag/rdbms/XFF/XFF/incident/incdir_1095289/XFF_j002_32590_i1095289.trc RAC(4):Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. 2020-03-10T01:44:56.085068+08:00 RAC(4):***************************************************************** RAC(4):An internal routine has requested a dump of selected redo. RAC(4):This usually happens following a specific internal error, when RAC(4):analysis of the redo logs will help Oracle Support with the RAC(4):diagnosis. RAC(4):It is recommended that you retain all the redo logs generated (by RAC(4):all the instances) during the past 12 hours, in case additional RAC(4):redo dumps are required to help with the diagnosis. RAC(4):***************************************************************** 2020-03-10T01:44:56.115765+08:00 Errors in file /opt/oracle/diag/rdbms/XFF/XFF/trace/XFF_j004_32594.trc (incident=1095305) (PDBNAME=RAC): ORA-00600: internal error code, arguments: [4193], [63532], [63537], [], [], [], [], [], [], [], [], [] RAC(4):Incident details in: /opt/oracle/diag/rdbms/XFF/XFF/incident/incdir_1095305/XFF_j004_32594_i1095305.trc RAC(4):Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. 2020-03-10T01:46:48.202213+08:00 RAC(4):Recovery of Online Redo Log: Thread 1 Group 2 Seq 2 Reading mem 0 RAC(4): Mem# 0: /opt/oracle/oradata/XFF/redo02.log RAC(4):Block recovery completed at rba 0.0.0, scn 0x0000000d3675e48e RAC(4):DDE: Problem Key 'ORA 600 [4193]' was completely flood controlled (0x6) Further messages for this problem key will be suppressed for up to 10 minutes 2020-03-10T01:46:48.384040+08:00 Errors in file /opt/oracle/diag/rdbms/XFF/XFF/trace/XFF_clmn_31741.trc: ORA-00600: internal error code, arguments: [4193], [27733], [27754], [], [], [], [], [], [], [], [], [] Errors in file /opt/oracle/diag/rdbms/XFF/XFF/trace/XFF_clmn_31741.trc (incident=1093505) (PDBNAME=CDB$ROOT): ORA-501 [] [] [] [] [] [] [] [] [] [] [] [] Incident details in: /opt/oracle/diag/rdbms/XFF/XFF/incident/incdir_1093505/XFF_clmn_31741_i1093505.trc 2020-03-10T01:46:49.264624+08:00 USER (ospid: 31741): terminating the instance due to ORA error 501 2020-03-10T01:46:49.280664+08:00 System state dump requested by (instance=1, osid=31741 (CLMN)), summary=[abnormal instance termination]. System State dumped to trace file /opt/oracle/diag/rdbms/XFF/XFF/trace/XFF_diag_31759.trc 2020-03-10T01:46:53.156926+08:00 ORA-00501: CLMN process terminated with error 2020-03-10T01:46:53.157103+08:00 Errors in file /opt/oracle/diag/rdbms/XFF/XFF/trace/XFF_diag_31759.trc: ORA-00501: CLMN process terminated with error 2020-03-10T01:46:53.157211+08:00 Dumping diagnostic data in directory=[cdmp_20200310014649], requested by (instance=1, osid=31741 (CLMN)), summary=[abnormal instance termination].
通过报错信息判断,数据库open之后(特别是pdb 4 open之后),开始报ORA-600 4193错误.然后由于CLMN进程异常,最后数据库crash.对于这类故障,因为使用的pdb,而且是由于pdb的undo异常导致数据库启动之后crash,可以通过对于pdb进行特殊处理,从而实现数据库启动之后不再crash.