核心内容摘要
gemma-3-12b-it多模态实战：扫描合同附件→关键条款高亮+风险点文字提示
一台运行在aix环境下面的
10.
2.
1的数据库由于控制器异常导致数据库启动的时候报ORA-600 4000错误Wed Jan 28 18:17:06 2026Completed crash recovery atThread 1: logseq 499321, block 14459, scn 17457591400427257 data blocksread, 41 data blocks written, 14457 redo blocksreadWed Jan 28 18:17:06 2026Thread 1 advanced to log sequence 499322Thread 1 opened at log sequence 499322Current log# 2 seq# 499322 mem# 0: /dev/rrk_redo2Successfulopenof redo thread 1Wed Jan 28 18:17:06 2026MTTR advisory is disabled because FAST_START_MTTR_TARGET is notsetWed Jan 28 18:17:06 2026SMON: enabling cache recoveryWed Jan 28 18:17:07 2026Errorsinfile/u01/app/oracle/admin/orcl1/udump/orcl1_ora_
trc:ORA-00600: internal error code, arguments: [4000], [9], [], [], [], [], [], []Wed Jan 28 18:17:08 2026Errorsinfile/u01/app/oracle/admin/orcl1/udump/orcl1_ora_
trc:ORA-00704: bootstrap process failureORA-00704: bootstrap process failureORA-00600: internal error code, arguments: [4000], [9], [], [], [], [], [], []Wed Jan 28 18:17:08 2026Error 704 happened during dbopen, shutting down databaseUSER: terminating instance due to error 704Instance terminated by USER, pid 16187632ORA-1092 signalled during: alter databaseopen...ORA-600 4000这个是在10g版本中非常常见的一个错误,一般是由于对应的block上面有事务没有提交或者scn过大导致,跟踪数据库启动过程发现在以下sql语句报错,而且报错为file 1 block 27527EXEC#2:c0,e62,p0,cr0,cu0,mis0,r0,dep1,og4,tim437860213380WAIT#2: namdb file sequential read ela 139 file#1 block#27527 blocks1 obj#-1 tim437860213555***
15:31:
4
417ksedmp: internal or fatal errorORA-00600: internal error code, arguments: [4000], [9], [], [], [], [], [], []Current SQL statementforthis session:selectrowcnt,blkcnt,empcnt,avgspc,chncnt,avgrln,nvl(degree,
, nvl(instances,
from tab$ where obj# :1这里可以获取到两个有效信息:
报错block为file 1 block
报错sql为select rowcnt,blkcnt,empcnt,avgspc,chncnt,avgrln,nvl(degree,
, nvl(instances,
from tab$ where obj# :1进一步对报错数据块进行分析Block header dump: 0x00406b87Objectidon Block? Yseg/obj: 0x2 csc: 0xfe
a99d3719 itc: 2 flg: - typ: 1 - DATAfsl: 0 fnx: 0x0 ver: 0x01Itl Xid Uba Flag Lck Scn/Fsc0x01 0x000b.
0
00f1bb09 0x008027a
eada.0e C--- 0 scn 0x0fda.f353b1980x02 0x
0
01e.00212e2a 0x01400cdf.113e.01 --U- 1 fsc 0x
a99d371b这里可以确认几个有效信息:
该block的csc scn为:
一条已经提交的事务的scn为:
还有一条没有提交的事务,使用的回滚段为9,这个和我们报错的ORA-600[4000][9]这个回滚段名称匹配上基于上述分析,我们需要确认两件事情:
通过Oracle数据库异常恢复检查脚本(Oracle Database Recovery Check)脚本检查结果,确认当前是数据库的文件头scn为:17457591420434小于该block的csc scn
itl操上面有一个锁需要提交,通过bbed工具对其进行提交,然后得出dump block信息Block header dump: 0x00406b87Objectidon Block? Yseg/obj: 0x2 csc: 0xfe
a99d3719 itc: 2 flg: - typ: 1 - DATAfsl: 0 fnx: 0x0 ver: 0x01Itl Xid Uba Flag Lck Scn/Fsc0x01 0x000b.
0
00f1bb09 0x008027a
eada.0e C--- 0 scn 0x0fda.f353b1980x02 0x
0