标签云
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,879)
- DB2 (22)
- MySQL (82)
- Oracle (1,705)
- 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备份恢复 (659)
- 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)
-
最近发表
- 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
- Oracle 19c 202607补丁(RUs+OJVM)-19.32
- Patch_SCN快速修复ORA-01555数据库open故障
- 快速处理 ORA-01210: data file header is media corrupt 故障
分类目录归档:Oracle
再现ORA-600 4000故障处理
有一个10g的库,由于redo损坏导致无法正常recover成功

正常途径无法open成功,尝试强制打开库
Wed Oct 18 11:23:25 2023 alter database open resetlogs Wed Oct 18 11:23:25 2023 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 236715370 Resetting resetlogs activation ID 4009817354 (0xef00f50a) Wed Oct 18 11:23:26 2023 Setting recovery target incarnation to 3 Wed Oct 18 11:23:26 2023 Assigning activation ID 4271120987 (0xfe94225b) Thread 1 opened at log sequence 1 Current log# 1 seq# 1 mem# 0: D:\ORADATA\EAIS\REDO01.LOG Successful open of redo thread 1 Wed Oct 18 11:23:26 2023 MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set Wed Oct 18 11:23:26 2023 SMON: enabling cache recovery Wed Oct 18 11:23:27 2023 Errors in file d:\hys_db\admin\eais\udump\eais_ora_10916.trc: ORA-00600: 内部错误代码, 参数: [4000], [9], [], [], [], [], [], [] Wed Oct 18 11:23:28 2023 Errors in file d:\hys_db\admin\eais\udump\eais_ora_10916.trc: ORA-00704: 引导程序进程失败 ORA-00704: 引导程序进程失败 ORA-00600: 内部错误代码, 参数: [4000], [9], [], [], [], [], [], [] Wed Oct 18 11:23:28 2023 Error 704 happened during db open, shutting down database USER: terminating instance due to error 704 Wed Oct 18 11:23:28 2023 Errors in file d:\hys_db\admin\eais\bdump\eais_pmon_1764.trc: ORA-00704: bootstrap process failure Wed Oct 18 11:23:29 2023 Errors in file d:\hys_db\admin\eais\bdump\eais_reco_9628.trc: ORA-00704: bootstrap process failure Wed Oct 18 11:23:29 2023 Errors in file d:\hys_db\admin\eais\bdump\eais_smon_9884.trc: ORA-00704: bootstrap process failure Wed Oct 18 11:23:29 2023 Errors in file d:\hys_db\admin\eais\bdump\eais_ckpt_10096.trc: ORA-00704: bootstrap process failure Wed Oct 18 11:23:29 2023 Errors in file d:\hys_db\admin\eais\bdump\eais_lgwr_8932.trc: ORA-00704: bootstrap process failure Wed Oct 18 11:23:29 2023 Errors in file d:\hys_db\admin\eais\bdump\eais_dbw0_9892.trc: ORA-00704: bootstrap process failure Wed Oct 18 11:23:29 2023 Errors in file d:\hys_db\admin\eais\bdump\eais_mman_9472.trc: ORA-00704: bootstrap process failure Wed Oct 18 11:23:29 2023 Errors in file d:\hys_db\admin\eais\bdump\eais_psp0_7692.trc: ORA-00704: bootstrap process failure Instance terminated by USER, pid = 10916 ORA-1092 signalled during: alter database open resetlogs...
resetlogs失败,报ora-600 4000错误,查看相关trace文件
*** 2023-10-18 11:23:27.103
ksedmp: internal or fatal error
ORA-00600: 内部错误代码, 参数: [4000], [9], [], [], [], [], [], []
Current SQL statement for this session:
select ctime, mtime, stime from obj$ where obj# = :1
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
_ksedst+38 CALLrel _ksedst1+0 0 1
_ksedmp+898 CALLrel _ksedst+0 0
_ksfdmp+14 CALLrel _ksedmp+0 3
603A816A CALLreg 00000000 6AE8258 3
603A8550 CALLrel 603A80D8 6AE8258 4FB1090 FA0 1 8C886B0
__VInfreq__ktudba+1 CALLrel _kgeasi+0 6AE8258 4FB1090 FA0 2 1 0 9 0
26
_ktrgcm+851 CALLrel _ktudba+0 9 8C88B68 0 0
_ktrgtc+526 CALLrel _ktrgcm+0 4FC753C
_kdsgrp+937 CALLrel _ktrgtc+0 4FC753C 4FC74E0 1F1FB00
8C88CB4 240 2AED19C 1F1F71C
_kdsfbrcb+432 CALLrel _kdsgrp+0 4FC7538 0 4FC7538
_qertbFetchByRowID+ CALLrel _kdsfbrcb+0 4FC7538 4FDF004 0 1 0 0
4344 4FC74E0 22E8078 8C88E14 0
_opifch2+3104 CALL??? 00000000 8DA05838 20135FC 8C890AC 1
_opifch+51 CALLrel _opifch2+0 89 5 8C891F0
_opiodr+1099 CALLreg 00000000 5 2 8C89938
_rpidrus+178 CALLrel _opiodr+0 5 2 8C89938 5
_rpidru+88 CALLrel _rpidrus+0 8C894C4
_rpiswu2+426 CALLreg 00000000 8C8988C
_rpidrv+1461 CALLrel _rpiswu2+0 90F3CCB4 0 8C89860 2 8C89880
0 8C89860 0 84DF58 84E018
8C8988C 8
_rpifch+44 CALLrel _rpidrv+0 5 5 8C89938 8
_kqdpts+166 CALLrel _rpifch+0 5 5 5 3 90AE2383 7 C 0 0 0 0
0 0 0 5 2 90AE237C 7 C 0 0 0
0 0 0 0
_kqrlfc+478 CALLrel _kqdpts+0 90AE21F4
_kqlbplc+102 CALLrel _kqrlfc+0
_kqlblfc+240 CALLrel _kqlbplc+0 0
_adbdrv+12911 CALLrel _kqlblfc+0 0 8C8D034
_opiexe+11778 CALLrel _adbdrv+0
_opiosq0+6088 CALLrel _opiexe+0 4 0 8C8D894
_kpooprx+232 CALLrel _opiosq0+0 3 E 8C8D9AC A4
_kpoal8+775 CALLrel _kpooprx+0 8C8F6CC 8C8E248 1D 1 0 A4
_opiodr+1099 CALLreg 00000000 5E 17 8C8F6C8
60FEFF8D CALLreg 00000000 5E 17 8C8F6C8 0
_opitsk+1017 CALL??? 00000000
_opiino+1087 CALLrel _opitsk+0 0 0
_opiodr+1099 CALLreg 00000000 3C 4 8C8FC60
_opidrv+819 CALLrel _opiodr+0 3C 4 8C8FC60 0
_sou2o+45 CALLrel _opidrv+0 3C 4 8C8FC60
_opimai_real+112 CALLrel _sou2o+0 8C8FC54 3C 4 8C8FC60
_opimai+92 CALLrel _opimai_real+0 2 8C8FC8C
_OracleThreadStart@ CALLrel _opimai+0
4+708
74A93438 CALLptr 00000000
76F09830 CALLreg 00000000
76F09800 CALLrel 76F0980B
--------------------- Binary Stack Dump ---------------------
通过一些技巧处理数据库正常open,导出数据完成本次恢复,参考以前恢复类似case:
重现ORA-600 4000异常
通过bbed解决ORA-00600[4000]案例
记录一次ORA-600 4000数据库故障恢复
ORACLE 8.1.7 数据库ORA-600 4000故障恢复
ORA-600 12807(CON$.CON#达到最大值) 处理
这次阳了有点严重,客户现场打patch无法去,在家里远程值守,在电脑前面闲着就查询和重现了最近朋友和我说的他们的客户遇到ORA-600 12807的故障.查询了下mos,基本上可以确认是由于CON$.CON#达到理论最大值无法继续增加从而报该错误,参考文档:
Mechanism to Recycle Database Constraint Identifiers (Doc ID 2925056.1)
Bug 13781691 – ORA-600 [12807] if CON$.CON# very high due to bug 13784384 (Doc ID 13781691.8)
Bug 25343563 – Mechanism to Implement Constraint Identifier (con#) Recycling (Doc ID 25343563.8)
在12及其之后的版本中oracle发布了patch 25343563 并设置event启用该patch进行解决.但是如果是12c之前版本,官方没有提供直接的解决方案.最基本的解决方法就是进行数据逻辑迁移,以及避免频繁创建约束导致con$.con#消耗太大
通过试验重现该错误
SQL> create table t_xff (id number not null,name varchar2(100) not null);
create table t_xff (id number not null,name varchar2(100) not null)
*
ERROR at line 1:
ORA-00600: internal error code, arguments: [12807], [], [], [], [], [], [], [],
[], [], [], []
SQL> create table t_xff (id number,name varchar2(100));
Table created.
SQL> alter table t_xff add primary key(id);
alter table t_xff add primary key(id)
*
ERROR at line 1:
ORA-00600: internal error code, arguments: [12807], [], [], [], [], [], [], [],
[], [], [], []
SQL> select con# from sys.con$ where name='_NEXT_CONSTRAINT';
CON#
----------
4294967294
通过一些底层分析,并对部分底层基表进行patch实现数据库可以继续创建约束
SQL> alter table t_xff add primary key(id); Table altered.
使用临时的patch方法,可以快速的恢复业务,后续找适当时间点安排迁移.
在此提醒:对于一些创建中间对象或者临时对象频繁的系统(特别是大量主键,not null等)注意检查该值距离天花板距离,如果比较接近了最好安排一次逻辑迁移和找出来原因(是oracle bug还是应用触发)
非tns方式登录pdb方法
非tns方式登录pdb方法之—-alter session set container
[oracle@db01 ~]$ env|grep ORA
ORACLE_SID=DCXFF
ORACLE_BASE=/u01/app/oracle
ORACLE_HOME=/u01/app/oracle/product/19c/db_1
[oracle@db01 ~]$ sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 - Production on Mon Oct 9 22:10:34 2023
Version 19.20.0.0.0
Copyright (c) 1982, 2022, Oracle. All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.20.0.0.0
SQL> show pdbs;
CON_ID CON_NAME OPEN MODE RESTRICTED
---------- ------------------------------ ---------- ----------
2 PDB$SEED READ ONLY NO
3 XFFPDB1 READ WRITE NO
SQL> show con_name;
CON_NAME
------------------------------
CDB$ROOT
SQL> alter session set container=XFFPDB1;
Session altered.
SQL> show con_name;
CON_NAME
------------------------------
XFFPDB1
SQL> exit
Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.20.0.0.0
非tns方式登录pdb方法之—-ORACLE_PDB_SID
[oracle@db01 ~]$ export ORACLE_PDB_SID=XFFPDB1
[oracle@db01 ~]$ sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 - Production on Mon Oct 9 22:11:30 2023
Version 19.20.0.0.0
Copyright (c) 1982, 2022, Oracle. All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.20.0.0.0
SQL> SHOW pdbs;
CON_ID CON_NAME OPEN MODE RESTRICTED
---------- ------------------------------ ---------- ----------
3 XFFPDB1 READ WRITE NO
SQL> show con_name;
CON_NAME
------------------------------
XFFPDB1
SQL> exit
Disconnected from Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.20.0.0.0
参考:How To Connect to PDB By OS Authentication In 19c Container Database Environment (Doc ID 2729416.1)

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

