标签云
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,882)
- DB2 (22)
- MySQL (82)
- Oracle (1,707)
- 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备份恢复 (661)
- Oracle安装升级 (108)
- 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)
-
最近发表
- 断电引起ORA-600 3005故障处理
- 记录一次云存储资源到期之后引起的数据库恢复
- Firebird 损坏数据库数据抢救工具—firebirdext
- Oracle 19c 202610补丁(RUs+OJVM)-19.33
- 由于con$.con#值达到极限,触发数据库增加约束报ORA-600 12807错误
- 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
分类目录归档:数据库
ORA-600 kokasgi1故障处理(sys被重命名)
接到一个客户数据库无法启动的case请求,查看alert日志,发现错误是经典的ORA-600 kokasgi1
Fri Oct 17 21:56:48 2025 ALTER DATABASE OPEN Beginning crash recovery of 1 threads parallel recovery started with 7 processes Started redo scan Completed redo scan read 30 KB redo, 24 data blocks need recovery Started redo application at Thread 1: logseq 3749, block 2, scn 111907926 Recovery of Online Redo Log: Thread 1 Group 2 Seq 3749 Reading mem 0 Mem# 0: /u01/oradata/orcl/redo02.log Completed redo application of 0.02MB Completed crash recovery at Thread 1: logseq 3749, block 62, scn 111927984 24 data blocks read, 24 data blocks written, 30 redo k-bytes read Thread 1 advanced to log sequence 3750 (thread open) Thread 1 opened at log sequence 3750 Current log# 3 seq# 3750 mem# 0: /u01/oradata/orcl/redo03.log Successful open of redo thread 1 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set SMON: enabling cache recovery [2261] Successfully onlined Undo Tablespace 2. Undo initialization finished serial:0 start:4294684900 end:4294684970 diff:70 (0 seconds) Verifying file header compatibility for 11g tablespace encryption.. Verifying 11g file header compatibility for tablespace encryption completed SMON: enabling tx recovery Database Characterset is ZHS16GBK Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_2261.trc (incident=81755): ORA-00600: internal error code, arguments: [kokasgi1], [], [], [], [], [], [], [], [], [], [], [] Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl/incident/incdir_81755/orcl_ora_2261_i81755.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 /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_2261.trc: ORA-00600: internal error code, arguments: [kokasgi1], [], [], [], [], [], [], [], [], [], [], [] Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_2261.trc: ORA-00600: internal error code, arguments: [kokasgi1], [], [], [], [], [], [], [], [], [], [], [] Error 600 happened during db open, shutting down database USER (ospid: 2261): terminating the instance due to error 600 Instance terminated by USER, pid = 2261
尝试启动数据库确实报该错误
SQL> alter database open; alter database open * ERROR at line 1: ORA-01092: ORACLE instance terminated. Disconnection forced ORA-00600: internal error code, arguments: [kokasgi1], [], [], [], [], [], [],[], [], [], [], [] Process ID: 164830 Session ID: 688 Serial number: 169
这类错误恢复比较多:
ORA-600 kokasgi1故障恢复
win环境报ora-600 kokasgi1处理
再次遇到ORA-600 kokasgi1故障恢复
2022年恢复第一单ORA-600 kokasgi1
等保修改oracle SYS用户名要求的请注意—ORA-00600 kokasgi1
重命名sys用户引起数据库启动报ORA-01092 ORA-00600 kokasgi1错误
处理方法比较简单,就是在数据库启动的过程中绕过对SYS用户的检查,然后把user#=0的用户update为SYS(在后续数据库版本中,oracle可能发现了该问题,直接禁止用户级别对user$进行update操作update user$报ORA-01031错误),再重启库即可

SQL> update user$ set name='SYS' WHERE USER#=0;
1 row updated.
SQL> commit;
Commit complete.
SQL> select user#,name from user$ WHERE USER#=0;
USER# NAME
---------- ------------------------------
0 SYS
SQL> alter system checkpoint;
System altered.
SQL> shutdown abort;
ORACLE instance shut down.
[oracle@oracle ~]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.4.0 Production on Sat Oct 18 00:36:37 2025
Copyright (c) 1982, 2013, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 1286066176 bytes
Fixed Size 2252904 bytes
Variable Size 1157631896 bytes
Database Buffers 117440512 bytes
Redo Buffers 8740864 bytes
Database mounted.
SQL>
SQL>
SQL> recover database;
Media recovery complete.
SQL> alter database open;
Database altered.
完美处理ORA-600 kokasgi1故障,实现数据0丢失,业务快速恢复
ORA-600 2662错误处理-202510
一个朋友一个历史库,由于某种原因无法正常启动,尝试强制打开库报ORA-600 2662错误
[oracle@db01 check_db]$ sqlplus / as sysdba SQL*Plus: Release 11.2.0.4.0 Production on Fri Oct 10 22:08:31 2025 Copyright (c) 1982, 2013, Oracle. All rights reserved. Connected to an idle instance. SQL> startup mount pfile='/tmp/pfile' ORACLE instance started. Total System Global Area 2.0176E+10 bytes Fixed Size 2261928 bytes Variable Size 2818575448 bytes Database Buffers 1.7314E+10 bytes Redo Buffers 41463808 bytes Database mounted. SQL> alter database open resetlogs; alter database open resetlogs * ERROR at line 1: ORA-01092: ORACLE instance terminated. Disconnection forced ORA-00704: bootstrap process failure ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [2662], [4293], [1546030629], [4293], [1646742297], [4194545], [], [], [], [], [], [] Process ID: 12499 Session ID: 66 Serial number: 3
对应的alert日志报错如下
Fri Oct 10 22:08:41 2025 ALTER DATABASE MOUNT Set as converted control file due to db_unique_name mismatch Changing di2dbun from to xff Successful mount of redo thread 1, with mount id 92634729 Database mounted in Exclusive Mode Lost write protection disabled Completed: ALTER DATABASE MOUNT Fri Oct 10 22:08:58 2025 alter database open resetlogs RESETLOGS after complete recovery through change 18439840632350 Clearing online redo logfile 1 /u01/oradata/xff/redo01.log Clearing online log 1 of thread 1 sequence number 0 Clearing online redo logfile 1 complete Resetting resetlogs activation ID 90952602 (0x56bd39a) Online log /u01/oradata/xff/redo01.log: Thread 1 Group 1 was previously cleared Online log /u01/oradata/xff/redo02.log: Thread 1 Group 2 was previously cleared Online log /u01/oradata/xff/redo03.log: Thread 1 Group 3 was previously cleared Online log /u01/oradata/xff/redo04.log: Thread 1 Group 4 was previously cleared Online log /u01/oradata/xff/redo05.log: Thread 1 Group 5 was previously cleared Online log /u01/oradata/xff/redo06.log: Thread 1 Group 6 was previously cleared Online log /u01/oradata/xff/redo07.log: Thread 1 Group 7 was previously cleared Online log /u01/oradata/xff/redo08.log: Thread 1 Group 8 was previously cleared Fri Oct 10 22:08:59 2025 Setting recovery target incarnation to 2 Initializing SCN for created control file Database SCN compatibility initialized to 3 Warning - High Database SCN: Current SCN value is 18439840632353, threshold SCN value is 0 If you have not previously reported this warning on this database, please notify Oracle Support so that additional diagnosis can be performed. Fri Oct 10 22:08:59 2025 Assigning activation ID 92634729 (0x5857e69) Thread 1 opened at log sequence 1 Current log# 1 seq# 1 mem# 0: /u01/oradata/xff/redo01.log Successful open of redo thread 1 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Fri Oct 10 22:08:59 2025 SMON: enabling cache recovery Errors in file /u01/app/oracle/diag/rdbms/xff/xff/trace/xff_ora_12499.trc (incident=4961): ORA-00600: internal error code, arguments: [2662], [4293], [1546030629], [4293], [1646742297],[4194545] Incident details in: /u01/app/oracle/diag/rdbms/xff/xff/incident/incdir_4961/xff_ora_12499_i4961.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 /u01/app/oracle/diag/rdbms/xff/xff/trace/xff_ora_12499.trc: ORA-00704: bootstrap process failure ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [2662], [4293], [1546030629], [4293],[1646742297],[4194545] Errors in file /u01/app/oracle/diag/rdbms/xff/xff/trace/xff_ora_12499.trc: ORA-00704: bootstrap process failure ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [2662], [4293], [1546030629], [4293],[1646742297],[4194545] Error 704 happened during db open, shutting down database USER (ospid: 12499): terminating the instance due to error 704 Instance terminated by USER, pid = 12499 ORA-1092 signalled during: alter database open resetlogs... opiodr aborting process unknown ospid (12499) as a result of ORA-1092
这个错误算是在oracle 12c之前比较经典的一个错误,一般是由于文件头的SCN小于数据库在启动/运行过程中block的SCN,从而出现该问题,解决该问题的方法一般就是把文件头的SCN修改为更大值即可,对于这种情况,可以通过Patch_SCN小工具进行修改(Patch SCN一键解决ORA-600 2662故障),也可以反向找出来报错的block,把其SCN修改为更小的值,以前写过类似的文章:https://www.xifenfei.com/2011/12/%e4%bd%bf%e7%94%a8bbed%e8%a7%a3%e5%86%b3ora-006002662.html
通过调整之后,数据库正常打开
SQL> recover database;
Media recovery complete.
SQL> alter database open ;
Database altered.
SQL> select open_mode from v$database;
OPEN_MODE
--------------------
READ WRITE
SQL> select file#,status from v$datafile;
FILE# STATUS
---------- -------
1 SYSTEM
2 ONLINE
3 ONLINE
4 ONLINE
5 ONLINE
6 ONLINE
7 ONLINE
8 ONLINE
9 ONLINE
10 ONLINE
11 ONLINE
11 rows selected.
检测字典没有问题
SQL> @hcheck
HCheck Version 07MAY18 on 10-OCT-2025 22:31:36
----------------------------------------------
Catalog Version 11.2.0.4.0 (1102000400)
db_name: XFF
Catalog Fixed
Procedure Name Version Vs Release Timestamp
Result
------------------------------ ... ---------- -- ---------- --------------
------
.- LobNotInObj ... 1102000400 <= *All Rel* 10/10 22:31:36 PASS
.- MissingOIDOnObjCol ... 1102000400 <= *All Rel* 10/10 22:31:36 PASS
.- SourceNotInObj ... 1102000400 <= *All Rel* 10/10 22:31:36 PASS
.- OversizedFiles ... 1102000400 <= *All Rel* 10/10 22:31:36 PASS
.- PoorDefaultStorage ... 1102000400 <= *All Rel* 10/10 22:31:36 PASS
.- PoorStorage ... 1102000400 <= *All Rel* 10/10 22:31:36 PASS
.- TabPartCountMismatch ... 1102000400 <= *All Rel* 10/10 22:31:36 PASS
.- OrphanedTabComPart ... 1102000400 <= *All Rel* 10/10 22:31:36 PASS
.- MissingSum$ ... 1102000400 <= *All Rel* 10/10 22:31:36 PASS
.- MissingDir$ ... 1102000400 <= *All Rel* 10/10 22:31:36 PASS
.- DuplicateDataobj ... 1102000400 <= *All Rel* 10/10 22:31:36 PASS
.- ObjSynMissing ... 1102000400 <= *All Rel* 10/10 22:31:36 PASS
.- ObjSeqMissing ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- OrphanedUndo ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- OrphanedIndex ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- OrphanedIndexPartition ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- OrphanedIndexSubPartition ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- OrphanedTable ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- OrphanedTablePartition ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- OrphanedTableSubPartition ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- MissingPartCol ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- OrphanedSeg$ ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- OrphanedIndPartObj# ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- DuplicateBlockUse ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- FetUet ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- Uet0Check ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- SeglessUET ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- BadInd$ ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- BadTab$ ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- BadIcolDepCnt ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- ObjIndDobj ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- TrgAfterUpgrade ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- ObjType0 ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- BadOwner ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- StmtAuditOnCommit ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- BadPublicObjects ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- BadSegFreelist ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- BadDepends ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- CheckDual ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- ObjectNames ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- BadCboHiLo ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- ChkIotTs ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- NoSegmentIndex ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- BadNextObject ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- DroppedROTS ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- FilBlkZero ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- DbmsSchemaCopy ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- OrphanedObjError ... 1102000400 > 1102000000 10/10 22:31:37 PASS
.- ObjNotLob ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- MaxControlfSeq ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- SegNotInDeferredStg ... 1102000400 > 1102000000 10/10 22:31:37 PASS
.- SystemNotRfile1 ... 1102000400 > 902000000 10/10 22:31:37 PASS
.- DictOwnNonDefaultSYSTEM ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- OrphanTrigger ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
.- ObjNotTrigger ... 1102000400 <= *All Rel* 10/10 22:31:37 PASS
---------------------------------------
10-OCT-2025 22:31:37 Elapsed: 1 secs
---------------------------------------
Found 0 potential problem(s) and 0 warning(s)
PL/SQL procedure successfully completed.
Statement processed.
Complete output is in trace file:
/u01/app/oracle/diag/rdbms/xff/xff/trace/xff_ora_8794_HCHECK.trc
SQL>
system表空间丢失部分文件恢复
有客户因为system表空间有一个数据文件放在其他位置,当时没有正常拷贝出来(备份了oradata路径下面文件,遗漏了一个system文件),尝试启动库报ORA-01157 ORA-01147等错误
[oracle@xifenfei check_db]$ sqlplus / as sysdba SQL*Plus: Release 11.2.0.4.0 Production on Sun Oct 5 21:13:28 2025 Copyright (c) 1982, 2013, Oracle. All rights reserved. Connected to: 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> recover datafile 1; Media recovery complete. SQL> recover datafile 2,3,4,5,6,7,8,9,10; Media recovery complete. SQL> alter database open; alter database open * ERROR at line 1: ORA-01157: cannot identify/lock data file 11 - see DBWR trace file ORA-01110: data file 11: '/u01/app/oracle/product/11.2.0.4/db_1/dbs/path_to_datafile.dbf' SQL> alter database datafile 11 offline drop; Database altered. SQL> alter database open; alter database open * ERROR at line 1: ORA-01147: SYSTEM tablespace file 11 is offline ORA-01110: data file 11: '/u01/app/oracle/product/11.2.0.4/db_1/dbs/path_to_datafile.dbf'
alert日志报错信息
Sun Oct 05 22:35:01 2025 alter database open Sun Oct 05 22:35:01 2025 Errors in file /data/app/oracle/diag/rdbms/mtxdb1/mtxdb1/trace/mtxdb1_dbw0_5946.trc: ORA-01157: cannot identify/lock data file 11 - see DBWR trace file ORA-01110: data file 11: '/u01/app/oracle/product/11.2.0.4/db_1/dbs/path_to_datafile.dbf' ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: 3 Errors in file /data/app/oracle/diag/rdbms/mtxdb1/mtxdb1/trace/mtxdb1_ora_11264.trc: ORA-01157: cannot identify/lock data file 11 - see DBWR trace file ORA-01110: data file 11: '/u01/app/oracle/product/11.2.0.4/db_1/dbs/path_to_datafile.dbf' ORA-1157 signalled during: alter database open... Sun Oct 05 22:35:25 2025 alter database datafile 11 offline ORA-1145 signalled during: alter database datafile 11 offline ... alter database datafile 11 offline drop Completed: alter database datafile 11 offline drop alter database open Errors in file /data/app/oracle/diag/rdbms/mtxdb1/mtxdb1/trace/mtxdb1_ora_11264.trc: ORA-01147: SYSTEM tablespace file 11 is offline ORA-01110: data file 11: '/u01/app/oracle/product/11.2.0.4/db_1/dbs/path_to_datafile.dbf' ORA-1147 signalled during: alter database open...
由于11号文件是system表空间的一个数据文件,对于这种数据文件丢失无法offline该数据文件,然后open库(也就是说在open库的时候,system表空间的数据文件必须全部online,如果有部分文件offline就会报ORA-01147).对于这样的情况,以前有过类似恢复经历:bbed打开丢失部分system数据文件库,这次的编写了一个m_scn程序实现快速处理
[oracle@xifenfei tmp]$ cat 1.txt 1@/data/app/oracle/oradata/mtxdb1/system01.dbf 11@/tmp/11.dbf [oracle@xifenfei tmp]$ ./m_scn 1.txt -------------Is processing datafile:/tmp/11.dbf------------- 1+0 records in 1+0 records out 1048576 bytes (1.0 MB) copied, 0.000835728 s, 1.3 GB/s [oracle@xifenfei tmp]$ sqlplus / as sysdba SQL*Plus: Release 11.2.0.4.0 Production on Wed Oct 8 11:27:32 2025 Copyright (c) 1982, 2013, Oracle. All rights reserved. Connected to: 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> set numw 16 SQL> col CHECKPOINT_TIME for a40 SQL> set lines 150 SQL> set pages 1000 SQL> SELECT status, 2 to_char(checkpoint_time,'yyyy-mm-dd hh24:mi:ss') checkpoint_time,FUZZY,checkpoint_change#, 3 count(*) ROW_NUM 4 FROM v$datafile_header 5 GROUP BY status, checkpoint_change#, to_char(checkpoint_time,'yyyy-mm-dd hh24:mi:ss'),fuzzy 6 ORDER BY status, checkpoint_change#, checkpoint_time; STATUS CHECKPOINT_TIME FUZ CHECKPOINT_CHANGE# ROW_NUM ------- ---------------------------------------- --- ------------------ ---------------- OFFLINE 2025-10-02 06:50:06 NO 17328662858685 1 ONLINE 2025-10-02 06:50:06 NO 17328662858685 10 SQL> alter database datafile 11 online; Database altered.
然后查询11号文件中涉及的对象情况
SQL> select distinct owner,segment_name,segment_type from dba_extents where file_id=11; OWNER SEGMENT_NAME SEGMENT_TYPE ------------------------------ -------------------------------------- ------------------ SYS SYSTEM ROLLBACK SYS I_COL1 INDEX SYS AUD$ TABLE SQL> select owner,segment_name from dba_segments where HEADER_FILE=11; no rows selected
证明丢失的11号文件(system表空间文件),涉及的对象较少,而且不涉及核心字典,比如tab$,obj$,col$等非常核心对象,评估理论上应该不涉业务数据丢失,尝试直接expdp导出数据,但是很不幸,报ORA-00600: internal error code, arguments: [kdBlkCheckError], [11], [3], [18018]错误
. . exported "XFF020"."OTHERBILLDETAIL_DEL" 6.405 MB 126048 rows
. . exported "XFF020"."POSSOLDOUT" 7.784 MB 281413 rows
ORA-31693: Table data object "XFF020"."MATERIELTRAN" failed to load/unload and is being skipped due to error:
ORA-39068: invalid master table data in row with PROCESS_ORDER=159:1000001
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [kdBlkCheckError], [11], [3], [18018], [], [], [], [], [], [], [], []
ORA-06512: at "SYS.KUPF$FILE", line 3720
ORA-06512: at line 1
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_DATA [TABLE_DATA:"XFF020"."MATERIELTRAN"]
UPDATE "SYS"."SYS_EXPORT_FULL_01" SET processing_state = :1, processing_status = :2
WHERE process_order = :3 AND duplicate = 0
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [kdBlkCheckError], [11], [3], [18018], [], [], [], [], [], [], [], []
ORA-06512: at "SYS.KUPW$WORKER", line 7866
ORA-31693: Table data object "XFF020"."MATERIELTRAN" failed to load/unload and is being skipped due to error:
ORA-39068: invalid master table data in row with PROCESS_ORDER=159:1000001
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [kdBlkCheckError], [11], [3], [18018], [], [], [], [], [], [], [], []
ORA-06512: at "SYS.KUPF$FILE", line 3720
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.KUPW$WORKER", line 9721
----- PL/SQL Call Stack -----
object line object
handle number name
0xef2fc508 21979 package body SYS.KUPW$WORKER
0xef2fc508 9742 package body SYS.KUPW$WORKER
0xef2fc508 3437 package body SYS.KUPW$WORKER
0xef2fc508 10436 package body SYS.KUPW$WORKER
0xef2fc508 1824 package body SYS.KUPW$WORKER
0xef2feb20 2 anonymous block
ORA-39097: Data Pump job encountered unexpected error -607
ORA-39065: unexpected master process exception in DISPATCH
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [kdBlkCheckError], [11], [3], [18018], [], [], [], [], [], [], [], []
ORA-31693: Table data object "XFF020"."ANALYSEREPORT" failed to load/unload and is being skipped due to error:
ORA-39068: invalid master table data in row with PROCESS_ORDER=161:1000001
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [kdBlkCheckError], [11], [3], [18018], [], [], [], [], [], [], [], []
ORA-06512: at "SYS.KUPF$FILE", line 3720
ORA-06512: at line 1
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_DATA [TABLE_DATA:"XFF020"."ANALYSEREPORT"]
UPDATE "SYS"."SYS_EXPORT_FULL_01" SET processing_state = :1, processing_status = :2
WHERE process_order = :3 AND duplicate = 0
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [kdBlkCheckError], [11], [3], [18018], [], [], [], [], [], [], [], []
ORA-06512: at "SYS.KUPW$WORKER", line 7866
ORA-31693: Table data object "XFF020"."ANALYSEREPORT" failed to load/unload and is being skipped due to error:
ORA-39068: invalid master table data in row with PROCESS_ORDER=161:1000001
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [kdBlkCheckError], [11], [3], [18018], [], [], [], [], [], [], [], []
ORA-06512: at "SYS.KUPF$FILE", line 3720
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.KUPW$WORKER", line 9721
----- PL/SQL Call Stack -----
object line object
handle number name
0xef2fc508 21979 package body SYS.KUPW$WORKER
0xef2fc508 9742 package body SYS.KUPW$WORKER
0xef2fc508 3437 package body SYS.KUPW$WORKER
0xef2fc508 10436 package body SYS.KUPW$WORKER
0xef2fc508 1824 package body SYS.KUPW$WORKER
0xef2feb20 2 anonymous block
ORA-31693: Table data object "XFF020CW"."MATERIELTRAN" failed to load/unload and is being skipped due to error:
ORA-39068: invalid master table data in row with PROCESS_ORDER=160:1000001
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [kdBlkCheckError], [11], [3], [18018], [], [], [], [], [], [], [], []
ORA-06512: at "SYS.KUPF$FILE", line 3720
ORA-06512: at line 1
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_DATA [TABLE_DATA:"XFF020CW"."MATERIELTRAN"]
UPDATE "SYS"."SYS_EXPORT_FULL_01" SET processing_state = :1, processing_status = :2
WHERE process_order = :3 AND duplicate = 0
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [kdBlkCheckError], [11], [3], [18018], [], [], [], [], [], [], [], []
ORA-06512: at "SYS.KUPW$WORKER", line 7866
ORA-31693: Table data object "XFF020CW"."MATERIELTRAN" failed to load/unload and is being skipped due to error:
ORA-39068: invalid master table data in row with PROCESS_ORDER=160:1000001
ORA-00607: Internal error occurred while making a change to a data block
ORA-00600: internal error code, arguments: [kdBlkCheckError], [11], [3], [18018], [], [], [], [], [], [], [], []
ORA-06512: at "SYS.KUPF$FILE", line 3720
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.KUPW$WORKER", line 9721
----- PL/SQL Call Stack -----
object line object
handle number name
0xef2fc508 21979 package body SYS.KUPW$WORKER
0xef2fc508 9742 package body SYS.KUPW$WORKER
0xef2fc508 3437 package body SYS.KUPW$WORKER
0xef2fc508 10436 package body SYS.KUPW$WORKER
0xef2fc508 1824 package body SYS.KUPW$WORKER
0xef2feb20 2 anonymous block
Job "SYS"."SYS_EXPORT_FULL_01" stopped due to fatal error at Wed Oct 8 11:59:29 2025 elapsed 0 00:18:48
对ORA-600 kdBlkCheckError进行分析分析(11表示文件号,3表示block),是由于导出生成的master表写入在system表空间,而system表空间中的file# 11是人工构造出来的,block 3 是位图分配信息(该信息和实际字典中存储信息不匹配),所以导致出现该错误,对于这个问题解决方法为expdp写master表不在system表空间即可,通过该操作,顺利导出数据,完成本次恢复任务



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

