-
加我公众号(orasos)
加我微信(17813235971)
加我QQ(107644445)
标签云
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,884)
- DB2 (22)
- MySQL (82)
- Oracle (1,709)
- 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 (73)
- Oracle Bug (8)
- Oracle RAC (56)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (29)
- Oracle备份恢复 (662)
- 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)
-
最近发表
- 记录19c ASM磁盘掉线触发ORA-59048故障处理
- aix平台Oracle数据库由于断电无法启动故障处理
- 断电引起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使用说明
标签归档：ORA-600 2662
Oracle断电故障处理
异常断电导致数据库异常恢复文件报ORA-00283 ORA-00742 ORA-00312
D:\check_db>sqlplus / as sysdba SQL*Plus: Release 11.2.0.4.0 Production on 星期二 5月 31 00:38:42 2022 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> recover datafile 1; ORA-00283: 恢复会话因错误而取消 ORA-00742: 日志读取在线程 %d 序列 %d 块 %d 中检测到写入丢失情况 ORA-00312: 联机日志 3 线程 1: 'D:\APP\ADMINISTRATOR\FAST_RECOVERY_AREA\ORCL\ONLINELOG\O1_MF_3_HJ32KJD5_.LOG'
这个错误比较明显是由于异常断电引起的写丢失导致.而且这种故障在没有备份的情况下，没有什么好处理方法,只能屏蔽一致性强制拉库,尝试强制拉库报错如下
SQL> startup mount pfile='d:/pfile.txt'
ORACLE 例程已经启动。
Total System Global Area 2.0310E+10 bytes
Fixed Size 2290000 bytes
Variable Size 3690991280 bytes
Database Buffers 1.6576E+10 bytes
Redo Buffers 40837120 bytes
数据库装载完毕。
SQL> recover database until cancel;
ORA-00279: 更改 18755939194213 (在 生成) 对于线程 1 是必需的
指定日志: {<RET>=suggested | filename | AUTO | CANCEL}
D:\APP\ADMINISTRATOR\FAST_RECOVERY_AREA\ORCL\ONLINELOG\O1_MF_3_HJ32KJD5_.LOG
ORA-00600: internal error code, arguments: [3020], [2], [78824], [8467432], [],
[], [], [], [], [], [], []
ORA-10567: Redo is inconsistent with data block (file# 2, block# 78824, file
offset is 645726208 bytes)
ORA-10564: tablespace SYSAUX
ORA-01110: data file 2: 'D:\ORADATA\ORCL\SYSAUX01.DBF'
ORA-10561: block type 'TRANSACTION MANAGED INDEX BLOCK', data object# 80834
ORA-01112: 未启动介质恢复
SQL> alter database open resetlogs;
alter database open resetlogs
*
第 1 行出现错误:
ORA-00600: 内部错误代码, 参数: [krsi_al_hdr_update.15], [4294967295], [], [],[], [], [], [], [], [], [], []
ORA-600 krsi_al_hdr_update.15错误,主要是由于redo异常导致无法resetlogs成功,具体参考：Alter Database Open Resetlogs returns error ORA-00600: [krsi_al_hdr_update.15], (Doc ID 2026541.1)描述,处理这个问题之后,再次resetlogs库，报ORA-600 2662错误
SQL> alter database open resetlogs; alter database open resetlogs * 第 1 行出现错误: ORA-00603: ORACLE server session terminated by fatal error ORA-00600: internal error code, arguments: [2662], [4366], [4112122046], [4366], [4112228996], [12583040], [], [], [], [], [], [] ORA-00600: internal error code, arguments: [2662], [4366], [4112122045], [4366], [4112228996], [12583040], [], [], [], [], [], [] ORA-01092: ORACLE instance terminated. Disconnection forced ORA-00600: internal error code, arguments: [2662], [4366], [4112122040], [4366], [4112228996], [12583040], [], [], [], [], [], [] 进程 ID: 4644 会话 ID: 1701 序列号: 3
这个问题比较简单,通过修改scn即可绕过去,之后数据库open报ORA-600 4194等错误
SQL> alter database open ; alter database open * 第 1 行出现错误: ORA-00600: 内部错误代码, 参数: [4194], [
SMON: enabling tx recovery Database Characterset is ZHS16GBK Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\trace\orcl_smon_5112.trc (incident=322982): ORA-00600: internal error code, arguments: [4137], [10.33.3070116], [0], [0], [], [], [], [], [], [], [], [] Incident details in: D:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\incident\incdir_322982\orcl_smon_5112_i322982.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. ARC3: Archival started ARC0: STARTING ARCH PROCESSES COMPLETE replication_dependency_tracking turned off (no async multimaster replication found) LOGSTDBY: Validating controlfile with logical metadata LOGSTDBY: Validation complete Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\trace\orcl_ora_3340.trc (incident=323030): ORA-00600: 内部错误代码, 参数: [4194], [ Incident details in: D:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\incident\incdir_323030\orcl_ora_3340_i323030.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Tue May 31 09:05:04 2022 Sweep [inc][322982]: completed ORACLE Instance orcl (pid = 13) - Error 600 encountered while recovering transaction (10, 33). Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\trace\orcl_smon_5112.trc: ORA-00600: internal error code, arguments: [4137], [10.33.3070116], [0], [0], [], [], [], [], [], [], [], [] Checker run found 1 new persistent data failures Tue May 31 09:05:05 2022 Sweep [inc][323030]: completed Sweep [inc2][322982]: completed Tue May 31 09:05:14 2022 Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\trace\orcl_smon_5112.trc (incident=322983): ORA-00600: internal error code, arguments: [4193], [10.33.3070116], [0], [], [], [], [], [], [], [], [], [] Incident details in: D:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\incident\incdir_322983\orcl_smon_5112_i322983.trc Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. Tue May 31 09:05:14 2022 ORA-600 signalled during: alter database open... Block recovery stopped at EOT rba 2.61.16 Block recovery completed at rba 2.61.16, scn 4366.4112429058 Block recovery from logseq 2, block 60 to scn 18755939643393 Recovery of Online Redo Log: Thread 1 Group 2 Seq 2 Reading mem 0 Mem# 0: D:\APP\ADMINISTRATOR\FAST_RECOVERY_AREA\ORCL\ONLINELOG\O1_MF_2_K9BSVC11_.LOG Block recovery completed at rba 2.61.16, scn 4366.4112429058 Dumping diagnostic data in directory=[cdmp_2022053],requested by(instance=1,osid=5112(SMON)),summary=[incident=322983]. Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\trace\orcl_smon_5112.trc: ORA-01595: error freeing extent (3) of rollback segment (1)) ORA-00600: internal error code, arguments: [4193], [10.33.3070116], [3], [], [], [], [], [], [], [], [], []
对异常undo进行处理,数据库正常open成功
SQL> shutdown immediate; ORA-00600: 内部错误代码, 参数: [4193], [ SQL> shutdown abort; ORACLE 例程已经关闭。 SQL> startup mount ORACLE 例程已经启动。 Total System Global Area 2.0310E+10 bytes Fixed Size 2290000 bytes Variable Size 3690991280 bytes Database Buffers 1.6576E+10 bytes Redo Buffers 40837120 bytes 数据库装载完毕。 SQL> alter database open; 数据库已更改。
hcheck检测有一些字典不一致,建议客户逻辑导出,然后导入到新库中
HCheck Version 07MAY18 on 31-5月 -2022 09:12:22
----------------------------------------------
Catalog Version 11.2.0.4.0 (1102000400)
db_name: ORCL
Catalog Fixed
Procedure Name Version Vs Release Timestamp Resul
t
------------------------------ ... ---------- -- ---------- -------------- -----
-
.- LobNotInObj ... 1102000400 <= *All Rel* 05/31 09:12:22 PASS
.- MissingOIDOnObjCol ... 1102000400 <= *All Rel* 05/31 09:12:22 PASS
.- SourceNotInObj ... 1102000400 <= *All Rel* 05/31 09:12:22 PASS
.- OversizedFiles ... 1102000400 <= *All Rel* 05/31 09:12:22 PASS
.- PoorDefaultStorage ... 1102000400 <= *All Rel* 05/31 09:12:22 PASS
.- PoorStorage ... 1102000400 <= *All Rel* 05/31 09:12:22 PASS
.- TabPartCountMismatch ... 1102000400 <= *All Rel* 05/31 09:12:22 PASS
.- OrphanedTabComPart ... 1102000400 <= *All Rel* 05/31 09:12:22 PASS
.- MissingSum$ ... 1102000400 <= *All Rel* 05/31 09:12:22 PASS
.- MissingDir$ ... 1102000400 <= *All Rel* 05/31 09:12:22 PASS
.- DuplicateDataobj ... 1102000400 <= *All Rel* 05/31 09:12:22 PASS
.- ObjSynMissing ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- ObjSeqMissing ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- OrphanedUndo ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- OrphanedIndex ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- OrphanedIndexPartition ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- OrphanedIndexSubPartition ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- OrphanedTable ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- OrphanedTablePartition ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- OrphanedTableSubPartition ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- MissingPartCol ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- OrphanedSeg$ ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- OrphanedIndPartObj# ... 1102000400 <= *All Rel* 05/31 09:12:23 FAIL
HCKE-0024: Orphaned Index Partition Obj# (no OBJ$) (Doc ID 1360935.1)
ORPHAN INDPART$: OBJ#=149167 BO#=6378 - no OBJ$ row
ORPHAN INDPART$: OBJ#=149168 BO#=6378 - no OBJ$ row
.- DuplicateBlockUse ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- FetUet ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- Uet0Check ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- SeglessUET ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- BadInd$ ... 1102000400 <= *All Rel* 05/31 09:12:23 FAIL
HCKE-0030: OBJ$ INDEX entry has no IND$ or INDPART$/INDSUBPART$ entry (Doc ID 13
60528.1)
OBJ$ INDEX PARTITION has no INDPART$ entry: Obj#=148278 SYS Name=WRH$_FILESTATXS
_PK PARTITION=WRH$_FILEST_1572571104_16462
OBJ$ INDEX PARTITION has no INDPART$ entry: Obj#=148920 SYS Name=WRH$_FILESTATXS
_PK PARTITION=WRH$_FILEST_1572571104_16678
.- BadTab$ ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- BadIcolDepCnt ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- ObjIndDobj ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- TrgAfterUpgrade ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- ObjType0 ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- BadOwner ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- StmtAuditOnCommit ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- BadPublicObjects ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- BadSegFreelist ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- BadDepends ... 1102000400 <= *All Rel* 05/31 09:12:23 WARN
HCKW-0016: Dependency$ p_timestamp mismatch for VALID objects (Doc ID 1361045.1)
[E] - P_OBJ#=6376 D_OBJ#=6765
.- CheckDual ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- ObjectNames ... 1102000400 <= *All Rel* 05/31 09:12:23 PASS
.- BadCboHiLo ... 1102000400 <= *All Rel* 05/31 09:12:24 PASS
.- ChkIotTs ... 1102000400 <= *All Rel* 05/31 09:12:24 PASS
.- NoSegmentIndex ... 1102000400 <= *All Rel* 05/31 09:12:24 PASS
.- BadNextObject ... 1102000400 <= *All Rel* 05/31 09:12:24 PASS
.- DroppedROTS ... 1102000400 <= *All Rel* 05/31 09:12:24 PASS
.- FilBlkZero ... 1102000400 <= *All Rel* 05/31 09:12:24 PASS
.- DbmsSchemaCopy ... 1102000400 <= *All Rel* 05/31 09:12:24 PASS
.- OrphanedObjError ... 1102000400 > 1102000000 05/31 09:12:24 PASS
.- ObjNotLob ... 1102000400 <= *All Rel* 05/31 09:12:24 PASS
.- MaxControlfSeq ... 1102000400 <= *All Rel* 05/31 09:12:24 PASS
.- SegNotInDeferredStg ... 1102000400 > 1102000000 05/31 09:12:24 PASS
.- SystemNotRfile1 ... 1102000400 > 902000000 05/31 09:12:24 PASS
.- DictOwnNonDefaultSYSTEM ... 1102000400 <= *All Rel* 05/31 09:12:24 PASS
.- OrphanTrigger ... 1102000400 <= *All Rel* 05/31 09:12:24 PASS
.- ObjNotTrigger ... 1102000400 <= *All Rel* 05/31 09:12:24 PASS
---------------------------------------
31-5月 -2022 09:12:24 Elapsed: 2 secs
---------------------------------------
Found 4 potential problem(s) and 1 warning(s)
Contact Oracle Support with the output and trace file
to check if the above needs attention or not
PL/SQL 过程已成功完成。
发表在 Oracle备份恢复
标签为 krsi_al_hdr_update.15, ORA-00742, ORA-600 2662, ORA-600 4194, oracle异常恢复, oracle断电恢复
评论关闭
commit_wait和commit_logging设置不当导致数据库无法正常启动
客户数据库设置以下参数，突然掉电之后，数据库无法正常启动
commit_wait = "NOWAIT" commit_logging = "BATCH"
数据库open报错
alter database open Block change tracking file is current. Beginning crash recovery of 1 threads parallel recovery started with 31 processes Started redo scan Errors in file /media/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_28711.trc (incident=8002955): ORA-00353: log corruption near block 3 change 17372812227460 time 03/20/2022 00:11:51 ORA-00312: online log 12315 thread 1: '/media/oracle/redolog/redo05.log' Aborting crash recovery due to error 399 Errors in file /media/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_28711.trc: ORA-00399: corrupt change description in redo log ORA-00353: log corruption near block 3 change 17372812227460 time 03/20/2022 00:11:51 ORA-00312: online log 12315 thread 1: '/media/oracle/redolog/redo05.log' Errors in file /media/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_28711.trc: ORA-00399: corrupt change description in redo log ORA-00353: log corruption near block 3 change 17372812227460 time 03/20/2022 00:11:51 ORA-00312: online log 12315 thread 1: '/media/oracle/redolog/redo05.log' ORA-399 signalled during: alter database open...
报错信息比较明显是由于redo损坏导致,尝试强制open库
Sun Mar 20 18:32:35 2022 alter database open resetlogs RESETLOGS is being done without consistancy checks. This may result in a corrupted database. The database should be recreated. RESETLOGS after incomplete recovery UNTIL CHANGE 17372812227456 Resetting resetlogs activation ID 1627598093 (0x61032d0d) Sun Mar 20 18:34:08 2022 Setting recovery target incarnation to 2 Sun Mar 20 18:34:08 2022 Initializing SCN for created control file Database SCN compatibility initialized to 3 Warning - High Database SCN: Current SCN value is 17372812227459, 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. Sun Mar 20 18:34:08 2022 Assigning activation ID 1627615603 (0x61037173) Thread 1 opened at log sequence 1 Current log# 2 seq# 1 mem# 0: /media/oracle/redolog/redo02.log Successful open of redo thread 1 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Sun Mar 20 18:34:08 2022 SMON: enabling cache recovery Errors in file /media/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_14369.trc (incident=8003142): ORA-00600: internal error code, arguments: [2662], [4044], [3964482439], [4044], [3964488833], [12669344], Incident details in: /media/oracle/diag/rdbms/orcl/orcl/incident/incdir_8003142/orcl_ora_14369_i8003142.trc Errors in file /media/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_14369.trc (incident=8003143): ORA-00353: log corruption near block 3 change 17372812227462 time 03/20/2022 18:34:10 ORA-00312: online log 2 thread 1: '/media/oracle/redolog/redo02.log' ORA-00600: internal error code, arguments: [2662], [4044], [3964482439], [4044], [3964488833], [12669344], Incident details in: /media/oracle/diag/rdbms/orcl/orcl/incident/incdir_8003143/orcl_ora_14369_i8003143.trc Errors in file /media/oracle/diag/rdbms/orcl/orcl/incident/incdir_8003142/orcl_ora_14369_i8003142.trc: ORA-00399: corrupt change description in redo log ORA-00353: log corruption near block 3 change 17372812227462 time 03/20/2022 18:34:10 ORA-00312: online log 2 thread 1: '/media/oracle/redolog/redo02.log' ORA-00600: internal error code, arguments: [2662], [4044], [3964482439], [4044], [3964488833], [12669344], Errors in file /media/oracle/diag/rdbms/orcl/orcl/trace/orcl_ora_14369.trc (incident=8003144): ORA-00353: log corruption near block 3 change 17372812227462 time 03/20/2022 18:34:10 ORA-00334: archived log: '/media/oracle/redolog/redo02.log' ORA-00600: internal error code, arguments: [2662], [4044], [3964482439], [4044], [3964488833], [12669344], Incident details in: /media/oracle/diag/rdbms/orcl/orcl/incident/incdir_8003144/orcl_ora_14369_i8003144.trc Sun Mar 20 18:34:11 2022 ORA-00603: ORACLE server session terminated by fatal error ORA-00600: internal error code, arguments: [2662], [4044], [3964482444], [4044], [3964488833], [12669344], ORA-00600: internal error code, arguments: [2662], [4044], [3964482443], [4044], [3964488833], [12669344], ORA-01092: ORACLE instance terminated. Disconnection forced ORA-00600: internal error code, arguments: [2662], [4044], [3964482439], [4044], [3964488833], [12669344],
强制open数据库报ora-600 2662错误,比较常见,通过修改scn再尝试open库
Sun Mar 20 18:38:43 2022
alter database open resetlogs
RESETLOGS is being done without consistancy checks. This may result
in a corrupted database. The database should be recreated.
RESETLOGS after incomplete recovery UNTIL CHANGE 17372812227460
Resetting resetlogs activation ID 1627615603 (0x61037173)
Sun Mar 20 18:40:02 2022
Setting recovery target incarnation to 2
Sun Mar 20 18:40:02 2022
Initializing SCN for created control file
Database SCN compatibility initialized to 3
Warning - High Database SCN: Current SCN value is 17372812227463, 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.
Sun Mar 20 18:40:02 2022
Assigning activation ID 1627669665 (0x610444a1)
Thread 1 opened at log sequence 1
Current log# 2 seq# 1 mem# 0: /media/oracle/redolog/redo02.log
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Sun Mar 20 18:40:02 2022
SMON: enabling cache recovery
Undo initialization finished serial:0 start:779809538 end:779809788 diff:250 (2 seconds)
Dictionary check beginning
Tablespace 'TEMP' #3 found in data dictionary,
but not in the controlfile. Adding to controlfile.
Dictionary check complete
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
*********************************************************************
WARNING: The following temporary tablespaces contain no files.
This condition can occur when a backup controlfile has
been restored. It may be necessary to add files to these
tablespaces. That can be done using the SQL statement:
ALTER TABLESPACE <tablespace_name> ADD TEMPFILE
Alternatively, if these temporary tablespaces are no longer
needed, then they can be dropped.
Empty temporary tablespace: TEMP
*********************************************************************
Database Characterset is AL32UTF8
No Resource Manager plan active
**********************************************************
WARNING: Files may exists in db_recovery_file_dest
that are not known to the database. Use the RMAN command
CATALOG RECOVERY AREA to re-catalog any such files.
If files cannot be cataloged, then manually delete them
using OS command.
One of the following events caused this:
1. A backup controlfile was restored.
2. A standby controlfile was restored.
3. The controlfile was re-created.
4. db_recovery_file_dest had previously been enabled and
then disabled.
**********************************************************
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Sun Mar 20 18:40:04 2022
QMNC started with pid=55, OS id=16232
LOGSTDBY: Validating controlfile with logical metadata
LOGSTDBY: Validation complete
Sun Mar 20 18:40:05 2022
db_recovery_file_dest_size of 3882 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Sun Mar 20 18:40:05 2022
Starting background process CJQ0
Sun Mar 20 18:40:05 2022
CJQ0 started with pid=58, OS id=16251
Completed: alter database open resetlogs
后续增加temp,导出数据到新库,恢复完成
ora-600 2662和ora-600 kclchkblk_4恢复
这两天连续处理两个case,一个是12.1.0.2版本数据库屏蔽一致性,强制open之后,报ORA-600 2662故障
这个错误本身是一个非常常见的错误,直接推scn即可解决,但是问题是12.1.0.2版本,oracle不允许以前常规的操作方法,就连oradebug都报错oradebug poke ORA-32521/ORA-32519故障解决,而且可以是rac环境,bbed修改文件头也相当麻烦,最后我们使用patch方法轻松解决
另外一例是11.2.0.4版本,强制open库报ora-600 kclchkblk_4
Wed Apr 28 21:25:38 2021 SMON: enabling cache recovery Instance recovery: looking for dead threads Instance recovery: lock domain invalid but no dead threads Errors in file /u01/app/oracle/diag/rdbms/dc/dc1/trace/dc1_ora_27832.trc (incident=564430): ORA-00600: internal error code, arguments: [kclchkblk_4], [2959], [904341694], [2959], [904131717], [] Incident details in: /u01/app/oracle/diag/rdbms/dc/dc1/incident/incdir_564430/dc1_ora_27832_i564430.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/dc/dc1/trace/dc1_ora_27832.trc: ORA-00704: bootstrap process failure ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [kclchkblk_4], [2959], [904341694], [2959], [904131717], [] Errors in file /u01/app/oracle/diag/rdbms/dc/dc1/trace/dc1_ora_27832.trc: ORA-00704: bootstrap process failure ORA-00704: bootstrap process failure ORA-00600: internal error code, arguments: [kclchkblk_4], [2959], [904341694], [2959], [904131717], [] Error 704 happened during db open, shutting down database USER (ospid: 27832): terminating the instance due to error 704 Instance terminated by USER, pid = 27832 ORA-1092 signalled during: alter database open resetlogs...
这个比较简单,参考redo异常 ORA-600 kclchkblk_4 故障恢复.
