Bug 9020054 : ORA-8103 BEING HIT DURING GATHERING OF STATISTICS ON TABLE PARTITION |
|
|
|
Type |
B - Defect |
Fixed in Product Version |
|
Severity |
2 - Severe Loss of Service |
Product Version |
10.2.0.4.0 |
Status |
92 - Closed, Not a Bug |
Platform |
23 - Oracle Solaris on SPARC (64-bit) |
Created |
14-Oct-2009 |
Platform Version |
NO DATA |
Updated |
03-Nov-2009 |
Base Bug |
N/A |
Database Version |
10.2.0.4.0 |
Affects Platforms |
Generic |
Product Source |
Oracle |
Line |
Oracle Database Products |
Family |
Oracle Database |
Area |
Oracle Database |
Product |
5 - Oracle Database - Enterprise Edition |
Hdr: 9020054 10.2.0.4.0 RDBMS 10.2.0.4.0 BUFFER CACHE PRODID-5 PORTID-23 ORA-8103
Abstract: ORA-8103 BEING HIT DURING GATHERING OF STATISTICS ON TABLE PARTITION
*** 10/14/09 06:37 am ***
TAR:
----
PROBLEM:
--------
Provide the following:
1. Clear description of the problem encountered
ora-8103 is being hit at analyze of table partition
2. Pertinent configuration information (MTS/OPS/distributed/etc)
3. Indication of the frequency and predictability of the problem
Problem is not reproducable at will but frequency is high
4. Sequence of events leading to the problem
- truncate of multiple partitions
- populating new content in partitions
- gathering statistics per table partition
5. Technical impact on the customer. Include persistent after effects.
Failure in job as done, gathering of statistics at later timestamp is
successful
DIAGNOSTIC ANALYSIS:
--------------------
1) double checked that gathering of statistics is done at partition level:
- checked the code of the customer: etl_load.sql + etl_util.sql
==> confirms that statistics are gathered at table level
==> logging as done confirms that statistics are gathered at table level
- checked the tracefile of a failing run (library_cache) + successful run
==> confirms that statistics are gathered at table level
2) during the job run multiple partitions are being truncated
(library_cache), the failing gathering of statistics is started in between
3) tried to reproduce the problem using the steps as done by customer but was
not successful
WORKAROUND:
-----------
WorkAround is to gather statistics after all table manipulation (truncate +
populate of data) has finished
RELATED BUGS:
-------------
bug:7011872 was created before to address this problem. events as asked in
bug (10236 + 8103 ..) did generate a tremendous tracefile which only showed
blockdumps in the 1st couple of Gb.
REPRODUCIBILITY:
----------------
Although problem is not reproducable at will it does occur frequently
TEST CASE:
----------
Unfortunately there is no testcase available, have tried but was unsuccessful
STACK TRACE:
------------
*** 10:29:00.081
ksedmp: internal or fatal error
ORA-8103: object no longer exists
Current SQL statement for this session:
select /*+ parallel(t,8) parallel_index(t,8) dbms_stats cursor_sharing_exact
use_weak_name_resl dynamic_sampling(0) no_monitoring */
count(*),sum(sys_op_opnsize("PARTY_OP_ISSUANCE_PLACE")),sum(sys_op_opnsize("PA
RTY_PASSPORT_NUM")),sum(sys_op_opnsize("PARTY_TITLE_BEFORE")),sum(sys_op_opnsi
ze("PARTY_TITLE_AFTER")),sum(sys_op_opnsize("PARTY_BUSINESS_NAME")),sum(sys_op
_opnsize("PARTY_ICO_NUM")),sum(sys_op_opnsize("PARTY_DIC_NUM")),sum(sys_op_opn
size("LEGALFORM_CODE")),sum(sys_op_opnsize("CONS_PARTY_KEY")),sum(sys_op_opnsi
ze("IC_PARTY_KEY")),sum(sys_op_opnsize("PARTY_RC_NUM")),sum(sys_op_opnsize("PA
RTY_OP_NUM")),sum(sys_op_opnsize("STDALN_CUST_RATING_KEY")),sum(sys_op_opnsize
("STDALN_COLL_RATING_KEY")),sum(sys_op_opnsize("MIS_CUST_RATING_KEY")),sum(sys
_op_opnsize("MIS_COLL_RATING_KEY")),sum(sys_op_opnsize("APPROVED_RATING_KEY"))
,count("PARTY_TAX_RATE"),sum(sys_op_opnsize("PARTY_TAX_RATE")),sum(sys_op_opns
ize("PARTY_FULL_NAME")),sum(sys_op_opnsize("PARTY_IDENTIFICATION_NUM")),sum(sy
s_op_opnsize("PARTY_COCUNUT_NUM")),sum(sys_op_opnsize("PARTY_SURNAME")),sum(sy
s_op_opnsize("PARTY_FIRST_NAME")),sum(sys_op_opnsize("PROFITCENTER_CODE")),sum
(sys_op_opnsize("BANKRELATION_CODE")),sum(sys_op_opnsize("PARTY_SOURCE_CODE"))
,sum(sys_op_opnsize("PARTY_NUM")),sum(sys_op_opnsize("PARTYTYPE_CODE")),sum(sy
s_op_opnsize("DOMICILE_COUNTRY_CODE")),sum(sys_op_opnsize("CITIZENSHIP_COUNTRY
_CODE")),sum(sys_op_opnsize("OKEC_CODE")),sum(sys_op_opnsize("ESA95_CODE")),su
m(sys_op_opnsize("OENACE_CODE")),sum(sys_op_opnsize("COCUNUTTYPE_CODE")),sum(s
ys_op_opnsize("CNBCLASS_CODE")) from "ETL_OWNER"."SCURR_ODS_PARTY" sample
block ( 5.0000000000) t
----- PL/SQL Call Stack -----
object line object
handle number name
39ab58ff8 1218 package body SYS.DBMS_SYS_SQL
39998ed90 334 package body SYS.DBMS_SQL
39991f250 10982 package body SYS.DBMS_STATS
39991f250 12468 package body SYS.DBMS_STATS
39991f250 12892 package body SYS.DBMS_STATS
39991f250 13345 package body SYS.DBMS_STATS
39991f250 13457 package body SYS.DBMS_STATS
398256460 137 package body ETL_OWNER.ETL_UTIL
3981e0c58 500 package body ETL_OWNER.ETL_LOAD
3981e0c58 1734 package body ETL_OWNER.ETL_LOAD
39a624c68 2 anonymous block
----- Call Stack Trace -----
ksesec0 <- kcbzib <- kcbgtcr <- ktecgsc <- ktecgetsh <- ktecgshx <-
kteinicnt1 <- qertbFetch <- qergiFetch
SUPPORTING INFORMATION:
-----------------------
BUGnnnnn_20091014 will be uploaded containing the following:
etl_load.sql + etl_util.sql - pl/sql code as shown in stacktrace
ods1_ora_1544.trc tracefile of failing run, event 8103 stacktrace level 3 +
library_cache level 8
ods1_ora_14508_successfull_analyze.trc - tracefile of successful run
s_m_ods_party_xps_log.txt - logging made during failing run
do_it - testcase as being used to try to reproduce the problem of customer
24 HOUR CONTACT INFORMATION FOR P1 BUGS:
----------------------------------------
DIAL-IN INFORMATION:
--------------------
IMPACT DATE:
------------
*** 10/14/09 07:50 am *** (CHG: Sta->10 Asg->CAHOLLAN)
*** 10/14/09 07:50 am ***
*** 10/14/09 09:11 am ***
*** 10/22/09 02:27 am ***
*** 11/03/09 12:18 am ***
*** 11/03/09 01:57 am *** (CHG: Sta->92 SubComp->BUFFER CACHE)
参考至:https://support.oracle.com/epmos/faces/BugDisplay?_afrLoop=180160866562482&id=9020054&_afrWindowMode=0&_adf.ctrl-state=nx97sd9db_77
本文原创,转载请注明出处、作者
如有错误,欢迎指正
邮箱:czmcj@163.com
分享到:
相关推荐
ORA-03113 "end_of_file on communication channel" ORA-03113 "end_of_file on communication channel" ORA-03113 "end_of_file on communication channel
### Oracle 错误 ORA-00132 和 ORA-00214 解析及处理 #### 一、错误概述 在Oracle数据库管理过程中,遇到ORA-00132和ORA-00214这类错误时,往往意味着数据库配置或启动过程中出现了问题。下面将对这两个错误进行...
在使用Oracle Data Pump工具IMPDP(Import Data Pump)进行数据导入的过程中,可能会遇到ORA-39002和ORA-39070等错误。本文将针对这些错误的排查方法进行详细介绍,帮助用户理解问题的原因及解决策略。 ### 错误...
Oracle数据库不同版本间的客户端与服务端的连接问题通常涉及到安全和兼容性配置,这篇文章主要讲述了在Oracle 11g R2客户端尝试连接Oracle 19c服务端时,遇到了两个特定的错误:ORA-28040和ORA-01017,以及如何解决...
ora-00604 错误 解决 方法 ora-00604 错误 解决 方法 ora-00604 错误 解决 方法 ora-00604 错误 解决 方法 ora-00604 错误 解决 方法ora-00604 错误 解决 方法
ORA-00604: 递归SQL层1出现错误 ORA-03106: 致命的双工通信协议错误 ORA-02063: 紧接着line(源于dblink) 以及 ORA-04052: 在查找远程对象时出错 ORA-00604: 递归SQL层1出现错误 ORA-03120: 双工转换例行程序:整数...
oracle网络配置(listener_ora-sqlnet_ora-tnsnames_ora).mht
ORACLE8I数据库应用EXP工具时ORA-06553报错的解决方法 摘要:本文主要解决ORACLE 8I数据库应用EXP工具时ORA-06553报错的问题,分析出现问题的原因,并提供了正确的解决方法和措施。 知识点1:Oracle 8I数据库EXP...
在创建Oracle数据库连接时遇到的错误ORA-01017和ORA-02063涉及到用户认证问题以及Oracle数据库版本之间的差异处理。ORA-01017错误表示用户名或密码无效,登录被拒绝,而ORA-02063则通常表示在Oracle数据库之间进行...
### Oracle12cRAC数据库出现ora-12520, ora-12516问题解析 #### 一、问题概述 在使用Oracle12cRAC(Real Application Clusters)数据库的过程中,可能会遇到客户端连接时出现ora-12520或ora-12516错误的问题。这两...
Oracle数据库发生ORA-04031错误原因浅析及处理 Oracle数据库是甲骨文公司提供的一种分布式数据库管理系统,以分布式数据库为核心的软件产品。它具有完整的数据管理功能,作为一个关系数据库,它是一个非常实用的...
### 如何处理错误ORA-29275:部分多字节字符 #### 问题背景与描述 在Oracle数据库操作过程中,用户可能会遇到一个特定的错误提示——ORA-29275:部分多字节字符。这一错误通常出现在执行查询`SELECT * FROM V$...
ORA-00312: online log 1 thread 1: '/oradata/10g/db/instant/redo01.log' ``` 此错误表明,在尝试归档序列号为230的日志文件时出现了问题,并且达到了恢复文件目的地大小的限制。同时给出了具体的问题文件路径为`...
然而,在日常运维过程中,我们可能会遇到各种错误,比如“ORA-00702”就是其中之一。这个错误通常在尝试重启Oracle数据库服务时出现,意味着数据库实例在启动过程中遇到了问题。本文将详细介绍如何在Windows和Linux...
### 离线误删空间文件导致的ORA-01033及ORA-01145问题的解决办法 #### 概述 在Oracle数据库管理过程中,偶尔会遇到因误操作导致的数据文件出现问题的情况,例如误删除数据文件或者数据文件损坏等。这些问题可能会...
Oracle数据库在运行过程中,经常会遇到各种错误代码,错误代码ORA-00845是其中的一个,它是指“MEMORY_TARGET not supported on this system”。这个错误一般发生在尝试在不支持MEMORY_TARGET参数的系统上设置该参数...
ORA-03113 是一个较为常见的Oracle错误,通常出现在网络通信出现问题时,具体表现为“end-of-file on communication channel”(通信通道上的文件结束)。此错误可能由多种因素引发,包括但不限于Unix核心参数设置...
### Oracle ORA-12518 故障处理 #### 概述 在Oracle数据库管理过程中,遇到ORA-12518错误是较为常见的问题之一。此错误通常发生在客户端试图连接到数据库服务器的过程中,当监听器无法将客户端连接顺利地移交给...