ITPub博客

客户9.2.0.6数据库出现ORA-600(kauxs_do_jou:3)错误。  错误信息为：Wed Mar 28 22:44:48 2012Errors in file /data/oracle/admin/orcl/udump/orcl_ora_19724.trc:ORA-00600: 内部错...

客户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_

客户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

客户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

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=

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.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

虽然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---

之前一直认为这是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

客户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。

又是一个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的写法是最好

Oracle 11.1.0.6数据库在归档到远端实例时出现这个错误。 [@more@]详细错误信息为：Wed Dec 26 12:39:20 2012Error 1017 received logging on to the standby------------------------------------------------------------Check that the primary and standby are using a password fileand remote_login_passwordfile is set to SHARED or EXCLUSIVE, and that the SYS password is same in the password files. returning error ORA-16191------------------------------------------------------------Errors

一个临时表空间无法分配导致的ORA-600错误。 [@more@] 错误信息如下： Wed May 16 17:26:23 2012 ORA-1652: unable to extend temp segment by 128 in tablespace ATEMP Wed May 16 17:26:31 2012 ORA-1652: unable to extend temp segment by 128 in tablespace ATEMP Wed May 16 17:26:37 2012 ORA-1652: unable to extend temp segment by 128 in tablespace ATEMP Wed May 16 17:26:38 2012 ORA-1652: unable to extend temp segment by 128 in ta

Oracle 9206 RAC环境访问LOGMINER视图时报错。 [@more@] 错误信息： Wed Aug 10 17:06:37 2011 Errors in file /opt/app/oracle/admin/orcl/udump/orcl2_ora_20704.trc: ORA-07445: exception encountered: core dump [000000010069AB88] [SIGSEGV] [Address not mapped to object] [0x000000008] [] [] Wed Aug 10 17:07:22 2011 Trace dumping is performing id=[cdmp_20110810170722] 对应的TRACE信息为： *** 2011-08-10 17:06:37.463 *** SESSION ID:(49.28760) 2011-08-10 17:06:37.461 Excep

9206数据库在收集统计信息时出现这个错误。 [@more@] 错误信息如下： Fri Oct 14 05:00:52 2011 Errors in file /opt/app/admin/orcl/bdump/orcl2_p010_16736.trc: ORA-00600: internal error code, arguments: [kghpih:ds], [0x494217CE8], [], [], [], [], [], [] Fri Oct 14 05:00:53 2011 Trace dumping is performing id=[cdmp_20111014050053] Fri Oct 14 05:00:53 2011 Errors in file /opt/app/admin/orcl/bdump/orcl2_j000_16586.trc: ORA-12012: error on auto execute of job 291 ORA-12801:

在10.2.0.4 RAC环境中，出现了更改SERVICE_NAME导致大量会话被KILL的现象。 [@more@] 告警日志中信息如下： Wed Oct 24 20:06:16 2012 ALTER SYSTEM SET service_names='' SCOPE=MEMORY SID='orcl2'; Wed Oct 24 20:06:16 2012 ALTER SYSTEM SET service_names='orcl' SCOPE=MEMORY SID='orcl2'; Wed Oct 24 20:06:16 2012 Immediate Kill Session#: 1418, Serial#: 22066 Immediate Kill Session: sess: 0x18dc79b70 OS pid: 4879 Immediate Kill Session#: 1424, Serial#: 108 Immediate Kill Sessio

客户9.2.0.6 RAC出现ORA-600[17067]错误。 [@more@] 错误信息如下： Wed Dec 3 00:51:02 2008 Errors in file /ora9i/app/oracle/admin/orcl9i/udump/orcl9i2_ora_25250.trc: ORA-00600: internal error code, arguments: [17067], [0], [], [], [], [], [], [] Wed Dec 3 00:51:07 2008 Errors in file /ora9i/app/oracle/admin/orcl9i/udump/orcl9i2_ora_25250.trc: ORA-00600: internal error code, arguments: [26599], [1], [229], [], [], [], [], [] ORA-00600: internal error code, arguments:

Exadata环境在收集统计信息时出现这个错误。 [@more@] 客户数据库11.2.0.2 RAC on Exadata在收集统计信息是出现的错误： Sun Feb 05 22:22:44 2012 Errors in file /u01/app/oracle/diag/rdbms/orcl/orcl2/trace/orcl2_j002_21084.trc (incident=255085): ORA-00600: internal error code, arguments: [ktspfnsb-1], [1], [1], [], [], [], [], [], [], [], [], [] Incident details in: /u01/app/oracle/diag/rdbms/orcl/orcl2/incident/incdir_255085/orcl2_j002_21084_i255085.trc Sun Feb 05 22:22:56

客户Oracle 10.2.0.1数据库告警日志出现大量的ORA-21780错误，并包含SMG-3000和SMG-3503信息，紧接着出现了ORA-4030和ORA-600(keltenq)错误。 [@more@] 错误信息如下： Mon Aug 17 10:37:48 2009 ORA-21780 encountered when generating server alert SMG-3000 Mon Aug 17 10:38:27 2009 ORA-21780 encountered when generating server alert SMG-3503 Mon Aug 17 10:47:48 2009 ORA-21780 encountered when generating server alert SMG-3000 Mon Aug 17 10:48:42 2009 ORA-21780 encountered when gener

客户10.2.0.4 RAC环境，出现大量的library cache lock和cursor: pin S wait on X等待，经分析是由于统计信息收集僵死导致的。 [@more@] 数据库在8点到9点期间，数据库两个节点都存在明显的cursor: pin S wait on X和library cache lock的等待： Event Waits Time(s) Avg Wait(ms) % Total Call Time Wait Class cursor: pin S wait on X 1,573,056 30,651 19