标签云
asm恢复 bbed bootstrap$ dul kcbzib_kcrsds_1 kccpb_sanity_check_2 kcratr_nab_less_than_odr MySQL恢复 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-600 kdsgrp1 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)
- 操作系统 (112)
- 数据库 (1,855)
- DB2 (22)
- MySQL (82)
- Oracle (1,682)
- 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 (71)
- Oracle Bug (8)
- Oracle RAC (56)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (29)
- Oracle备份恢复 (640)
- Oracle安装升级 (106)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (90)
- PostgreSQL (37)
- pdu工具 (7)
- PostgreSQL恢复 (13)
- SQL Server (34)
- SQL Server恢复 (14)
- TimesTen (7)
- 达梦数据库 (4)
- 达梦恢复 (2)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (48)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (31)
-
最近发表
- 硬件故障后数据文件大小不对故障处理—Oracle碎片扫描恢复
- 1.5T MySQL数据库完美恢复
- WARNING: detected duplicate paths to the same disk导致crs无法正常启动故障解决
- asm dd 10M导致system文件部分坏块修复
- Oracle 19c 202604补丁(RUs+OJVM)-19.31
- Oracle故障第一现场被恢复混乱的数据库恢复
- impdp报ORA-39083 ORA-14102错误处理
- 一次断电引起的Oracle故障恢复-ora-600 2662故障
- OraScan(Oracle 碎片扫描工具) 使用说明
- .[xueyuanjie@onionmail.org].AIR勒索加密数据库恢复
- oracleasm createdisk破坏的acfs文件系统恢复
- 先offline数据文件,再resetlogs导致恢复复杂的故障处理
- exp dmp导入报IMP-00098: INTERNAL ERROR: impgst2故障处理
- Oracle 19c Grid Infrastructure Release Update-202604(19.31)
- Oracle Database 19c Release Update-202604(19.31)
- aix环境rac 私网直连导致haip启动异常
- 又一例TRIM导致asm磁盘数据丢失的故障
- 一次运气好的ORA-600 kcratr_nab_less_than_odr故障处理
- OraFHR快速open被勒索加密破坏的Oracle数据库
- obet一键恢复offline数据文件
标签归档:ORA-07445[kdxlin]
一次幸运的ORA-07445 kdxlin故障恢复
一个oracle 19.3版本数据库异常关机之后直接启动数据库报ORA-07445 [kdxlin()+4824]相关错误
alter database open 2025-09-27T13:45:25.877298+08:00 Ping without log force is disabled: instance mounted in exclusive mode. 2025-09-27T13:45:25.924174+08:00 Beginning crash recovery of 1 threads parallel recovery started with 11 processes Thread 1: Recovery starting at checkpoint rba (logseq 2188 block 62125), scn 0 2025-09-27T13:45:26.049176+08:00 Started redo scan 2025-09-27T13:45:26.174177+08:00 Completed redo scan read 1070 KB redo, 536 data blocks need recovery 2025-09-27T13:45:26.465482+08:00 Started redo application at Thread 1: logseq 2188, block 62125, offset 0 2025-09-27T13:45:26.481107+08:00 Recovery of Online Redo Log: Thread 1 Group 1 Seq 2188 Reading mem 0 Mem# 0: D:\APP\ADMINISTRATOR\ORADATA\Nxff\REDO01.LOG 2025-09-27T13:45:26.496732+08:00 Completed redo application of 0.58MB 2025-09-27T13:45:26.699860+08:00 Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0xC] [PC:0x7FF77DBBF2F8, kdxlin()+4824] Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\xff\xff\trace\xff_p003_4996.trc (incident=131272): ORA-07445: 出现异常错误: 核心转储 [kdxlin()+4824][ACCESS_VIOLATION][ADDR:0xC][PC:0x7FF77DBBF2F8][UNABLE_TO_READ][] Incident details in: D:\APP\ADMINISTRATOR\diag\rdbms\xff\xff\incident\incdir_131272\xff_p003_4996_i131272.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. 2025-09-27T13:45:30.776913+08:00 Slave encountered ORA-10388 exception during crash recovery 2025-09-27T13:45:30.776913+08:00 Slave encountered ORA-10388 exception during crash recovery 2025-09-27T13:45:30.776913+08:00 Slave encountered ORA-10388 exception during crash recovery 2025-09-27T13:45:30.776913+08:00 Slave encountered ORA-10388 exception during crash recovery 2025-09-27T13:45:30.776913+08:00 Slave encountered ORA-10388 exception during crash recovery 2025-09-27T13:45:30.792538+08:00 Slave encountered ORA-10388 exception during crash recovery 2025-09-27T13:45:30.792538+08:00 Slave encountered ORA-10388 exception during crash recovery 2025-09-27T13:45:31.792552+08:00 Slave encountered ORA-10388 exception during crash recovery 2025-09-27T13:45:32.802610+08:00 Slave encountered ORA-10388 exception during crash recovery 2025-09-27T13:45:33.818250+08:00 Slave encountered ORA-10388 exception during crash recovery 2025-09-27T13:45:33.833875+08:00 Aborting crash recovery due to slave death, attempting serial crash recovery 2025-09-27T13:45:33.833875+08:00 Beginning crash recovery of 1 threads Thread 1: Recovery starting at checkpoint rba (logseq 2188 block 62125), scn 0 2025-09-27T13:45:33.865126+08:00 Started redo scan 2025-09-27T13:45:33.912001+08:00 Completed redo scan read 1070 KB redo, 536 data blocks need recovery 2025-09-27T13:45:33.912001+08:00 Started redo application at Thread 1: logseq 2188, block 62125, offset 0 2025-09-27T13:45:33.927627+08:00 Recovery of Online Redo Log: Thread 1 Group 1 Seq 2188 Reading mem 0 Mem# 0: D:\APP\ADMINISTRATOR\ORADATA\Nxff\REDO01.LOG Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0xC] [PC:0x7FF77DBBF2F8, kdxlin()+4824] Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\xff\xff\trace\xff_ora_4880.trc (incident=131240): ORA-07445: ??????: ???? [kdxlin()+4824] [ACCESS_VIOLATION] [ADDR:0xC] [PC:0x7FF77DBBF2F8] [UNABLE_TO_READ] [] Incident details in: D:\APP\ADMINISTRATOR\diag\rdbms\xff\xff\incident\incdir_131240\xff_ora_4880_i131240.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. 2025-09-27T13:45:36.386177+08:00 Dumping diagnostic data in directory=[cdmp_20250927134536],requested by(instance=1,osid=4880),summary=[incident=131240] 2025-09-27T13:45:39.745686+08:00 PMON (ospid: ): terminating the instance due to ORA error 2025-09-27T13:45:39.745686+08:00 Cause - 'Instance is being terminated due to fatal process death (pid: 33, ospid: 4880, )' 2025-09-27T13:45:39.745686+08:00 System state dump requested by (instance=1, osid=4652 (PMON)), summary=[abnormal instance termination]. System State dumped to trace file D:\APP\ADMINISTRATOR\diag\rdbms\xff\xff\trace\xff_diag_4696.trc 2025-09-27T13:45:44.013452+08:00 Instance terminated by PMON, pid = 4652
这次运气爆棚,直接尝试recover database,然后open库成功,完成数据库恢复任务

检查数据库没有发现其他问题,完成本次恢复业务

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

