ITPub博客

又是一个ANSI标准SQL导致的BUG。 [@more@]数据库版本10.2.0.1，错误信息为：Wed Nov 09 19:15:27 2011Errors in file c:oracleproduct10.2.0adminorcludumporcl_ora_784.trc:ORA-00600: 内部错误代码, 参数: [kkoljt1], [], [], [], [], [], [], []根据文档Bug 5864217 - OERI [kkoljt1] from ANSI query with join elimination [ID 5864217.8]，在10.2.0.3以前版本中标准SQL如果出现了连接消除会导致ORA-600[kkoljt1]的错误。Oracle在11.1.0.6和10.2.0.4中解决了这个问题。除了升级外，避免标准SQL的写法是最好

客户10.2.0.1 for Windows出现ORA-7445错误。 [@more@]没有打过补丁的数据库出现问题的几率果然很大：Thu Mar 29 15:11:50 2012Errors in file c:oracleproduct10.2.0adminorcludumporcl_ora_880.trc:ORA-07445: 出现异常错误: 核心转储 [ACCESS_VIOLATION] [_kkdlavc+233] [PC:0x7F6661] [ADDR:0x0] [UNABLE_TO_READ] []这个问题是由于访问了一个不正常的视图所致，解决方法就是重建视图。关于这个bug的描述可以参考文档ORA-07445 [kkdlavc()+284] When Performing Query Against a View。

客户10.2.0.1 for Windows 32数据库出现ORA-7445[_kkqtnloCbk]错误。 [@more@]告警日志中错误信息为：Tue Nov 08 14:56:39 2011Errors in file c:oracleproduct10.2.0adminorcludumporcl_ora_4720.trc:ORA-07445: 出现异常错误: 核心转储 [ACCESS_VIOLATION] [_kkqtnloCbk+124] [PC:0x1DB818C] [ADDR:0xF5] [UNABLE_TO_READ] []导致这个错误的原因是Oracle处理ANSI语法时出现异常，参考文档Bug 4204383 Dump [kkqtnlocbk] optimizing ANSI OUTER JOINs with subqueries。这个错误影响10.2.0.3以下版本，Oracl

之前一直认为这是Oracle的一个bug，直到前一段时间通读网络服务参考手册时，才发现问题的真相。TNSNAMES配置中空格导致的bug：http://yangtingkun.itpub.net/post/468/487506 [@more@] 当时测试发现，只要在SERVICE_NAME下面的一行缺少空格，就会导致错误的产生： TEST08 = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 172.25.13.229)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = test08) ) ) 替换下划线的版本为： TEST08 = __(DESCRIPTION = ____(ADD

虽然AWR功能已经完全可以替代STATSPACK的功能，但是目前存在的9i的数据库还有不少，而且却是发现有不少人不了解如何更改STATSPACK的级别。 [@more@]STATSPACK默认是LEVEL 5收集，而LEVEL 5收集的数据是不包括执行计划的，因此对于关注SQL性能的情况，至少需要调整到LEVEL 6，下面是检查和调整STATSPACK收集等级的方法，比较简单，就不多解释了：SQL> exec statspack.snapPL/SQL procedure successfully completed.SQL> select snap_id, dbid, snap_level from stats$snapshot; SNAP_ID DBID SNAP_LEVEL---

一个由于低版本JDBC驱动导致的错误。 [@more@] 告警日志中错误信息为：Fri Aug 12 19:00:03 2011Errors in file /opt/app/oracle/admin/orcl/udump/orcl2_ora_28464.trc:ORA-07445: exception encountered: core dump [lnxadd()+471] [SIGSEGV] [Address not mapped to object] [0x000000000] [] []Fri Aug 12 19:00:04 2011 Trace dumping is performing id=[cdmp_20110812190004]根据MOS文档setDouble On INSERT Corrupts Data In NUMBER Column Using Oracle10g JDBC Driver [ID 313373.1]，导致问题的原因是使用了低版本的J

客户10.2.0.4 RAC for Linux X64环境，告警日志出现ORA-600(6033)错误。 [@more@]详细错误信息为：/opt/app/oracle/admin/orcl/udump/orcl1_ora_25075.trcOracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit ProductionWith the Partitioning, Real Application Clusters, OLAP, Data Miningand Real Application Testing optionsORACLE_HOME = /opt/app/oracle/product/10.2.0/db_1System name: LinuxNode name: hb1Release: 2.6.9-78.ELlargesmpVersion: #1 SMP Wed Jul 9 16:03:59 EDT 200

10.2.0.4 RAC环境关闭数据库时出现ORA-600[2801]错误。 [@more@]详细错误信息为：Mon Apr 11 22:44:24 2011alter database add supplemental log dataTue Apr 12 00:11:42 2011Thread 1 advanced to log sequence 3108 (LGWR switch) Current log# 1 seq# 3108 mem# 0: +DATA/orcl/onlinelog/group_1.307.727394923 Current log# 1 seq# 3108 mem# 1: +DATA/orcl/onlinelog/group_1.306.727394925Tue Apr 12 00:16:55 2011Thread 1 advanced to log sequence 3109 (LGWR switch) Current log# 2 seq# 3109 mem# 0: +

这是一个10.2.0.1到10.2.0.4上都存在的bug。 [@more@]错误发生在DG的STANDBY数据库中：Fri Oct 19 12:01:16 2012Errors in file /data/oracle/admin/vodapp/bdump/vodapp_mrp0_21304.trc:ORA-00600: internal error code, arguments: [3689], [33], [], [], [], [], [], []Errors with log /baceldba/archive/1_30374_730819916.dbfMRP0: Background Media Recovery terminated with error 600导致这个错误的原因很简单，在主库执行了ALTER TABLESPACE DROP DATAFILE后，并不会导致DATAFILE的被删除，后随后在增加新

10.2.0.4 RAC环境的ASM实例出现这个ORA-7445错误。 [@more@]错误信息为：Fri Dec 3 19:49:49 2010Errors in file /opt/app/oracle/admin/+ASM/bdump/+asm2_lck0_19876.trc:Fri Dec 3 19:50:44 2010Errors in file /opt/app/oracle/admin/+ASM/bdump/+asm2_ckpt_19863.trc:ORA-07445: exception encountered: core dump [kgskhighthreshold()+32] [SIGSEGV] [Address not mapped to object] [0x0000001F6] [] []Fri Dec 3 19:51:00 2010Trace dumping is performing id=[cdmp_20101203195100]Fri Dec 3 19:51:27 201

客户10.2.0.3 RAC环境启动后碰到DRM问题导致实例崩溃。 [@more@]错误信息为：Mon Jan 19 12:42:58 2009Database Characterset is ZHS16GBKreplication_dependency_tracking turned off (no async multimaster replication found)Starting background process QMNCQMNC started with pid=28, OS id=4496Mon Jan 19 12:43:01 2009Completed: ALTER DATABASE OPENMon Jan 19 12:43:32 2009Thread 2 advanced to log sequence 2081 Current log# 3 seq# 2081 mem# 0: +DISKGROUP1/orcl1/onlinelog/group_3.258.628169029Mo

Oracle 11.2.0.2上SQL TUNING的bug。 [@more@]数据库版本为11.2.0.2 RAC for Solaris，错误信息为：Thu Jul 05 22:00:01 2012Begin automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_SQL_TUNING_TASK"Thu Jul 05 22:28:35 2012Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x4] [PC:0x102B3CC08, qsmmixComputeClusteringFactor()+1640] [flags: 0x0, count: 1]Errors in file /opt/oracle/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_j002_7688.trc (incident=

今天在使用awrextr.sql脚本导出AWR数据时碰到这个错误。 [@more@] 数据库版本为10.2.0.5 RAC for HP_UX，错误信息为：Using the dump file prefix: awrdat_15222_15448|| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| The AWR extract dump file will be located| in the following directory/file:| /orabak01/orabak| awrdat_15222_15448.dmp| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|| *** AWR Extract Started ...|| This operation will take a few moments. The| progress of the AWR extract opera

已经在多个RAC环境碰到因为等待reliable message导致进程hang死的情况了。 [@more@]这个问题在RAC环境比较常见，在很多客户中都碰到过这个问题，而数据库版本多集中在10.2.0.4，个别的版本为10.2.0.5。而出现这个信息的进程也不太相同，最常见的的m000进程，这个进程的僵死会导致一个节点的AWR无法自动收集。另外比较常见的就是导致高级队列机制异常，直接影响是数据泵导出无法正常运行，会导致进程挂起。最近又碰到了类似的情况，在MOS文档中发现Bug 6148054 RAC hang waiting for "reliable message"文章描

前一段时间在客户测试TPCC的时候碰到这个问题，今天在MOS上找到问题的原因，简单记录一下。 [@more@]在11.2中，如果表设置了KEEP池，而在初始化参数中没有指定DB_KEEP_CACHE_SIZE的值，就可能会造成数据库中出现明显的ENQ: KO – Fast Object Checkpoint的等待，同时还伴有reliable message的等待。MOS文档ENQ: KO - Fast Object Checkpoint And Reliable Message Causing Bad Performance [ID 1377830.1]描述了这个问题，给出的解决方案是不使用KEEP池，改为使用DEFAULT池，或者设置DB_KEEP_CACHE_SIZE的值为非

客户11.2 RAC环境出现ORA-7445[pevm_icd_call_common]错误。 [@more@]详细错误信息为：Mon Aug 20 17:31:49 2012Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0xD8] [PC:0x93F1E34, pevm_icd_call_common()+754] [flags: 0x0, count: 1]Redo thread 1 internally disabled at seq 9 (SMON)Errors in file /oracle/diag/rdbms/orcl/orcl2/trace/orcl2_m003_21741.trc (incident=12433):ORA-07445: exception encountered: core dump [pevm_icd_call_common()+754] [SIGSEGV] [ADDR:0xD8] [P

客户的10.2.0.4 FOR AIX数据库在刷新物化视图时碰到这个错误。 [@more@]错误信息为：Fri Oct 5 06:20:27 2012Errors in file /home/oracle/app/admin/orcl/udump/orcl_ora_4272180.trc:ORA-00600: internal error code, arguments: [kghfrf1], [0x000000000], [], [], [], [], [], []从TRACE文件可以看到，出现错误时在执行的语句是物化视图的刷新：*** 2012-10-05 06:20:27.599ksedmp: internal or fatal errorORA-00600: internal error code, arguments: [kghfrf1], [0x000000000], [], [], [], [], [], []Current

客户9208 RAC环境出现ORA-600(15419)和ORA-6544(2603)错误。 [@more@]错误信息为：Sun Feb 5 15:58:52 2012Errors in file /oracle/app/admin/orcl/udump/orcl2_ora_250852.trc:ORA-00600: internal error code, arguments: [15419], [severe error during PL/SQL execution], [], [], [], [], [], []ORA-06544: PL/SQL: internal error, arguments: [2603], [], [], [], [], [], [], []ORA-06553: PLS-707: unsupported construct or internal error [2603]Sun Feb 5 15:58:53 2012Trace dumping is performing id=[c

Oracle 9208 RAC for AIX出现这个错误。 [@more@]错误信息为：Tue Jun 22 17:41:21 2010Errors in file /oracle/app/admin/orcl/udump/orcl2_ora_4293428.trc:ORA-00600: internal error code, arguments: [12804], [kkdlgtd: bad object type], [], [], [], [], [], []Tue Jun 22 17:41:22 2010Trace dumping is performing id=[cdmp_20100622174122]从错误信息上分析，这个问题发生在Oracle检查对象类型时。查询MOS文档ORA-600 [12804] [kkdlgtd: bad object type] Alter Table Add Column Or Running a Query [I

客户9.2.0.8 RAC for AIX环境出现ORA-600[KSSADP1]错误。 [@more@]错误信息为：Thu Apr 19 21:16:45 2012Errors in file /oracle/app/admin/orcl/udump/orcl1_ora_442896.trc:ORA-00600: internal error code, arguments: [KSSADP1], [], [], [], [], [], [], []Thu Apr 19 21:16:45 2012Errors in file /oracle/app/admin/orcl/udump/orcl1_ora_442896.trc:ORA-00600: internal error code, arguments: [KSSADP1], [], [], [], [], [], [], []Thu Apr 19 21:16:45 2012Trace dumping is performing id=[cdmp_