标签云
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,881)
- DB2 (22)
- MySQL (82)
- Oracle (1,706)
- 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备份恢复 (660)
- 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)
-
最近发表
- 记录一次云存储资源到期之后引起的数据库恢复
- 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
- Oracle 19c 202607补丁(RUs+OJVM)-19.32
标签归档:25343563
由于con$.con#值达到极限,触发数据库增加约束报ORA-600 12807错误
有客户数据库报ORA-600 12807错误,导致数据库无法创建任何约束(带约束条件的表也无法创建),alert 日志报错如下
2026-10-19T09:33:41.779082+08:00 Errors in file /oracle/database/diag/rdbms/oradb/oradb1/trace/oradb1_ora_184458.trc ORA-00600: 内部错误代码, 参数: [12807], [], [], [], [], [], [], [], [], [], [], [] Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. 2026-10-19T09:33:42.080313+08:00 Errors in file /oracle/database/diag/rdbms/oradb/oradb1/trace/oradb1_ora_221081.trc ORA-00600: 内部错误代码, 参数: [12807], [], [], [], [], [], [], [], [], [], [], [] Use ADRCI or Support Workbench to package the incident. See Note 411.1 at My Oracle Support for error and packaging details. 2026-10-19T09:33:42.401635+08:00 DDE: Problem Key 'ORA 600 [12807]' was completely flood controlled (0x6) Further messages for this problem key will be suppressed for up to 10 minutes
对应的trace文件报错
*** 2026-10-20T23:01:14.835258+08:00
dbkedDefDump(): Starting incident default dumps (flags=0x2, level=3, mask=0x0)
[TOC00004]
----- Current SQL Statement for this session (sql_id=czyqxdfu45w1c) -----
CREATE TABLE VT10RMC7BHYU76DDQ3DHV75RMV (KSQL_SEQ INT, FID VARCHAR2 (44) NOT NULL
……………………
FInPriceBizDate TIMESTAMP, CONSTRAINT ZC8SOAHBADTGB7OIBG PRIMARY KEY (FID)) NOLOGGING
[TOC00004-END]
[TOC00005]
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedst1()+95 call kgdsdst() 7FFF09990520 000000002
7FFF0998A860 ? 7FFF0998A978 ?
000000000 000000082 ?
ksedst()+58 call ksedst1() 000000000 000000001
7FFF0998A860 ? 7FFF0998A978 ?
000000000 ? 000000082 ?
dbkedDefDump()+2344 call ksedst() 000000000 000000001 ?
8 7FFF0998A860 ? 7FFF0998A978 ?
000000000 ? 000000082 ?
ksedmp()+577 call dbkedDefDump() 000000003 000000002
7FFF0998A860 ? 7FFF0998A978 ?
000000000 ? 000000082 ?
dbgexPhaseII()+2092 call ksedmp() 0000003EB 000000002 ?
7FFF0998A860 ? 7FFF0998A978 ?
000000000 ? 000000082 ?
dbgexExplicitEndInc call dbgexPhaseII() 7FBAB95976D8 7FBAB47D3148
()+285 7FFF09991700 7FFF0998A978 ?
000000000 ? 000000082 ?
dbgeEndDDEInvocatio call dbgexExplicitEndInc 7FBAB95976D8 7FBAB47D3148
nImpl()+314 () 7FBAB47D39F0 7FFF0998A978 ?
000000000 ? 000000082 ?
kqrHashTableInsert( call dbgeEndDDEInvocatio 7FBAB95976D8 7FBAB47D3148
)+2446 nImpl() 7FBAB95D79C0 7FFF0998A978 ?
7FBAB95D79C0 000000082 ?
kqrRelinkToHashTabl call kqrHashTableInsert( 000000000 ? 16F5F05F70 ?
e()+226 ) 15B7ED3EC0 ? FFFFFFFFF6B64B6B
7FBAB95D79C0 ? 2400000000
kqrUpdateHashTable( call kqrRelinkToHashTabl 000000000 ? 16F5F05F70 ?
)+417 e() 15B7ED3EC0 ?
FFFFFFFFF6B64B6B ?
7FBAB95D79C0 ? 2400000000 ?
kqrfpo()+729 call kqrUpdateHashTable( 7FBAB95D79C0 16F5F05F70 ?
) FFFFFFFFF5F05F70 00000000B
000000003 ? 2400000000 ?
kkdcnco()+1749 call kqrfpo() 16F5F05F70 16F5F05F70 ?
FFFFFFFFF5F05F70 ?
00000000B ? 24886FB6D8
2400000000 ?
kkdcico()+339 call kkdcnco() 000000057 7FBAB39D5420
7FFF09992B80 16167E3500
000000000 2400000000 ?
ctcdrv()+40399 call kkdcico() 000000057 7FBAB39D53F8
7FBAB9478950 16167E3500
14BF81D188 2400000000 ?
opiexe()+25553 call ctcdrv() 7FBAB9479388 7FFF099B5D60
7FFF099B5E50 16167E3500 ?
14BF81D188 ? 2400000000 ?
opiosq0()+4494 call opiexe() 000000004 7FFF099B5D60 ?
7FFF099B64A0 16167E3500 ?
14BF81D188 ? 2400000000 ?
kpooprx()+287 call opiosq0() 000000003 7FFF099B5D60 ?
7FBAB95D79C0 ? 0000000A4
000000000 000000001
kpoal8()+821 call kpooprx() 7FFF099BA5C4 7FBAB3967B58
000000736 000000001 000000000
0000000A4
opiodr()+1202 call kpoal8() 00000005E 000000026
7FFF099BA5C0 000000001 ?
000000000 ? 0000000A4 ?
ttcpip()+1218 call opiodr() 00000005E 000000026
7FFF099BA5C0 ? 000000000
000000000 ? 0000000A4 ?
opitsk()+1900 call ttcpip() 7FBAB9601B30 ? 000000026 ?
7FFF099BA5C0 000000000 ?
7FFF099BA020 7FFF099BA810 ?
opiino()+936 call opitsk() 000000000 000000000
7FFF099BA5C0 ? 000000000 ?
7FFF099BA020 ? 7FFF099BA810 ?
opiodr()+1202 call opiino() 00000003C 000000004
7FFF099BC198 000000000 ?
7FFF099BA020 ? 7FFF099BA810 ?
opidrv()+1094 call opiodr() 00000003C 000000004
7FFF099BC198 ? 000000000
7FFF099BA020 ? 7FFF099BA810 ?
sou2o()+165 call opidrv() 00000003C 000000004
7FFF099BC198 000000000 ?
7FFF099BA020 ? 7FFF099BA810 ?
opimai_real()+422 call sou2o() 7FFF099BC131 00000003C
000000004 7FFF099BC198
7FFF099BA020 ? 7FFF099BA810 ?
ssthrdmain()+417 call opimai_real() 000000000 7FFF099BC988
000000004 ? 7FFF099BC198 ?
7FFF099BA020 ? 7FFF099BA810 ?
main()+256 call ssthrdmain() 000000000 000000002
7FFF099BC988 000000001
000000000 7FFF099BA810 ?
__libc_start_main() call main() 000000002 7FFF099BCBC8
+245 7FFF099BC988 ? 000000001 ?
000000000 ? 7FFF099BA810 ?
_start()+41 call __libc_start_main() 000DCD110 000000002
7FFF099BCBC8 000000000 ?
000000000 ? 7FFF099BA810 ?
[TOC00005-END]
问题重现
[oracle@oradb1 ~]$ sqlplus / as sysdba SQL*Plus: Relorae 19.0.0.0.0 - Production on Tue Oct 20 21:45:57 2026 Version 19.14.0.0.0 Copyright (c) 1982, 2021, Oracle. All rights reserved. Connected to: Oracle Database 19c Enterprise Edition Relorae 19.0.0.0.0 - Production Version 19.14.0.0.0 SQL> create table t_test1020(id number not null); create table t_test1020(id number not null) * ERROR at line 1: ORA-00600: internal error code, arguments: [12807], [], [], [], [], [], [], [], [], [], [], []
分析故障原因(con$.con#=4294967294(_NEXT_CONSTRAINT)达到了理论最大值,无法继续增加所以报ORA-600 12807错误)
SQL> select 4294967294 - con# from sys.con$ where name='_NEXT_CONSTRAINT';
4294967294-CON#
---------------
0
SQL> select max(con#) from sys.con$;
MAX(CON#)
----------
4294967294
根据oracle官方描述打上25343563 patch可以实现con$.con#循环利用
[oracle@oradb1 25343563]$ opatch lspatches 25343563;MECHANISM TO REUSE CON# 33561310;OJVM RELoraE UPDATE: 19.14.0.0.220118 (33561310) 33529556;OCW RELoraE UPDATE 19.14.0.0.0 (33529556) 33515361;Database Relorae Update : 19.14.0.0.220118 (33515361) OPatch succeeded.
测试问题解决
SQL> create table t_test1020(id number not null);
Table created.
SQL>
SQL> select constraint_name
2 from user_cons_columns
3 where table_name = 'T_TEST1020'
4 and column_name = 'ID';
CONSTRAINT_NAME
--------------------------------------------------------------------------------
SYS_C0012094
SQL> SELECT CON# FROM CON$ WHERE NAME='SYS_C0012094';
CON#
----------
12094
SQL> SELECT COUNT(1) FROM con$recycle;
COUNT(1)
----------
100032699
SQL> select con# from sys.con$ where name='_NEXT_CONSTRAINT';
CON#
----------
4294967294
分析实现原因,其实oracle是通过创建sys.con$recycle表,把使用过的记录存储到这个表里面(新删除的约束的con#也会自动增加到这个表里面),后续使用直接从这个表中拿数据出来使用,从而实现con$中的con#循环使用,从而解决了ORA-600 12807问题,如果是12c之前版本参考:ORA-600 12807(CON$.CON#达到最大值) 处理
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还是应用触发)

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

