ORA-00600: internal error code, arguments: [2252]
第一次遇见 ora-00600
OS linux 5
DB 11.2.0.1
故障发生的背景 2017年02月07日下午,往数据库加了个数据文件,过会发现数据库连不上,系统都连不上了
联系机房管理人员,被告知 key过期,暂停使用,实际上就是这台虚拟机被挂起了
第二天恢复后,使用dblink报错
如下,这里截取了第四次使用dblink的报错
Wed Feb 08 10:01:52 2017
Errors in file /u01/app/oracle/diag/rdbms/jmtdb3/jmtdb3/trace/jmtdb3_ora_1914.trc (incident=40244):
ORA-00600: internal error code, arguments: [2252], [3568], [2032328633], [], [], [], [], [], [], [], [], []
Incident details in: /u01/app/oracle/diag/rdbms/jmtdb3/jmtdb3/incident/incdir_40244/jmtdb3_ora_1914_i40244.trc
第一次报错dump文件,也就是上面列出的文件的内容如下
[oracle@jmt ~]$ cat /u01/app/oracle/diag/rdbms/jmtdb3/jmtdb3/trace/jmtdb3_ora_29478.trc
Trace file /u01/app/oracle/diag/rdbms/jmtdb3/jmtdb3/trace/jmtdb3_ora_29478.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /u01/app/oracle/product/11.2.0/db_1
System name: Linux
Node name: jmt
Release: 2.6.32-431.el6.x86_64
Version: #1 SMP Sun Nov 10 22:19:54 EST 2013
Machine: x86_64
Instance name: jmtdb3
Redo thread mounted by this instance: 1
Oracle process number: 33
Unix process pid: 29478, image: oracle@jmt
*** 2017-02-07 17:54:23.855
*** SESSION ID:(209.16592) 2017-02-07 17:54:23.855
*** CLIENT ID:() 2017-02-07 17:54:23.855
*** SERVICE NAME:(jmtdb3) 2017-02-07 17:54:23.855
*** MODULE NAME:(PL/SQL Developer) 2017-02-07 17:54:23.855
*** ACTION NAME:(SQL ′°??- т?¨) 2017-02-07 17:54:23.855
Incident 32271 created, dump file: /u01/app/oracle/diag/rdbms/jmtdb3/jmtdb3/incident/incdir_32271/jmtdb3_ora_29478_i32271.trc
ORA-00600: internal error code, arguments: [2252], [3568], [1073102123], [], [], [], [], [], [], [], [], []
[oracle@jmt ~]$ cat /u01/app/oracle/diag/rdbms/jmtdb3/jmtdb3/trace/jmtdb3_ora_29478.trc
Trace file /u01/app/oracle/diag/rdbms/jmtdb3/jmtdb3/trace/jmtdb3_ora_29478.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /u01/app/oracle/product/11.2.0/db_1
System name: Linux
Node name: jmt
Release: 2.6.32-431.el6.x86_64
Version: #1 SMP Sun Nov 10 22:19:54 EST 2013
Machine: x86_64
Instance name: jmtdb3
Redo thread mounted by this instance: 1
Oracle process number: 33
Unix process pid: 29478, image: oracle@jmt
*** 2017-02-07 17:54:23.855
*** SESSION ID:(209.16592) 2017-02-07 17:54:23.855
*** CLIENT ID:() 2017-02-07 17:54:23.855
*** SERVICE NAME:(jmtdb3) 2017-02-07 17:54:23.855
*** MODULE NAME:(PL/SQL Developer) 2017-02-07 17:54:23.855
*** ACTION NAME:(SQL ′°??- т?¨) 2017-02-07 17:54:23.855
Incident 32271 created, dump file: /u01/app/oracle/diag/rdbms/jmtdb3/jmtdb3/incident/incdir_32271/jmtdb3_ora_29478_i32271.trc
ORA-00600: internal error code, arguments: [2252], [3568], [1073102123], [], [], [], [], [], [], [], [], []
[oracle@jmt ~]$
只能看出引起错误的程序是PLSQL和一些session信息,其他并看不出有什么有用的信息
一筹莫展之际,发现盖总的一篇文章
当数据库系统的时间被调整，回到历史状态时，数据库可能出现ORA-600 2252错误。
这个错误指，数据库的SCN被认为是错误和不合理的，Oracle内部控制每秒产生的SCN数量小于 16K 个，然后以1988年1月1日，0点0分0秒开始，可以计算出一个SCN可能的合理最大值。
如果当前SCN的指标超过了这个合理值，则系统就会出现ORA-600 2252错误。
这类错误的错误号可能类似如下：
Mon May 14 17:55:54 2012
Errors in file /t3/orat3/product/admin/ora1020410/bdump/ora1020410_mmon_25386.trc:
ORA-00600: internal error code, arguments: [2252], [2988], [9], [], [], [], [], []
Mon May 14 17:56:06 2012
Errors in file /t3/orat3/product/admin/ora1020410/bdump/ora1020410_smon_23805.trc:
ORA-00600: internal error code, arguments: [2252], [2988], [13], [], [], [], [], []
Mon May 14 17:56:06 2012
Non-fatal internal error happenned while SMON was doing extent coalescing.
SMON encountered 1 out of maximum 100 non-fatal internal errors.
Mon May 14 17:56:07 2012
Errors in file /t3/orat3/product/admin/ora1020410/bdump/ora1020410_smon_23805.trc:
ORA-00600: internal error code, arguments: [2252], [2988], [13], [], [], [], [], []
Non-fatal internal error happenned while SMON was doing extent coalescing.
SMON encountered 2 out of maximum 100 non-fatal internal errors.
Mon May 14 17:56:09 2012
Errors in file /t3/orat3/product/admin/ora1020410/bdump/ora1020410_smon_23805.trc:
ORA-00600: internal error code, arguments: [2252], [2988], [14], [], [], [], [], []
Non-fatal internal error happenned while SMON was doing extent coalescing.
SMON encountered 3 out of maximum 100 non-fatal internal errors.
Mon May 14 17:56:10 2012
Errors in file /t3/orat3/product/admin/ora1020410/bdump/ora1020410_smon_23805.trc:
ORA-00600: internal error code, arguments: [2252], [2988], [14], [], [], [], [], []
Non-fatal internal error happenned while SMON was doing extent coalescing.
SMON encountered 4 out of maximum 100 non-fatal internal errors.
Mon May 14 17:56:11 2012
Errors in file /t3/orat3/product/admin/ora1020410/bdump/ora1020410_smon_23805.trc:
ORA-00600: internal error code, arguments: [2252], [2988], [15], [], [], [], [], []
Non-fatal internal error happenned while SMON was doing extent coalescing.
SMON encountered 5 out of maximum 100 non-fatal internal errors.
如果确实因为调整系统时间导致，则可以将时间调整回正确日期，如果系统SCN真的非法跃迁，则可以等候一定时间，等候SCN合理值可以容纳该跃迁或不一致。
查看系统发现,原来系统时间慢了一天,因为虚拟机当时挂起了一天,恢复后,时间并没有恢复
于是修改时间
1.先关闭数据库
2.date -s "20170209 09:35:50"
3.保存时间,以免重启后失效 hwclock -w
4,重启系统,用date查看时间,修改成功,启动数据库,再使用dblink,发现不会报错了
来自 “ ITPUB博客 ” ，链接：https://blog.itpub.net/30440124/viewspace-2133933/ ，如需转载，请注明出处，否则将追究法律责任。
上一篇：
没有了~
下一篇：
没有了~
请登录后发表评论
登录
全部评论
