服务器:AIX 5309
数据库:Oracle 10.2.0.4
当时那哥们正在执行的语句是:
select distinct t1.loan_no ,--,
t.customer_cname ,
t3.industry_class1_name ,
t3.industry_class1_code,
t3.industry_class2_name,
t3.industry_class2_code,
t3.industry_class3_name,
t3.industry_class3_code,
t3.industry_class4_name,
t3.industry_class4_code,
t.customer_scale "大中小微分类",
t7.second_type,
t7.first_type,
t7.path_code,
t7.path_name,
t2.loan_start_date,
t2.mature_date,
t2.loan_amt "发放金额",
t2.cmis_five_class,
t1.loan_amt "贷款余额",
t4.sec_code,
t4.sec_name,
t4.fir_code,
t4.fir_name,
t.customer_id
-- sum(t1.loan_amt)
from srcb_ods.c_customer_info t,srcb_fsd.cl_loan_acct t1,srcb_fsd.cl_loan t2,
srcb_fsd.country_standard_industry_clas t3,srcb_fsd.com_bank_hierarchy t4,srcb_fsd.prod_map_tbl t6,
() t7
where t.data_date = '20120229'
and t1.fdate='20120229'
and t.customer_id=t1.client_no
and t2.fdate='20120229'
and t1.loan_no=t2.loan_no
and substr(t.industry_id,2)=t3.industry_class4_code
and t2.loan_branch=t4.fir_code
and t4.fiv_code='00001'
and t1.settle_ind='N'
-- and t.customer_scale='01'
and t2.loan_cate='01'
and t2.loan_sub_type=t6.fsd_prod_code
and t6.s_prod_code=t7.loan_type_id
在网上Google和在MOS上查了一些,都说是因为使用了sys_connect_by_path的原因,注意SQL中的红色部分,单独执行红色SQL是没问题的,但是如果整个SQL语句一起执行的话就会报错。这说明该错误不是那个子SQL造成的,而是与其他语句结合才会出现的错误(Bug)。
:不过还发现一个比较奇怪的问题,就是同样是这条语句,我在另一套环境执行则是没问题的。不知道为何,两套环境的数据库补丁集神马都是一样的。
直接附官文:
ORA-600 [evapth : unexpected evaluation] [ID 284511.1] 修改时间 19-DEC-2011 类型 REFERENCE 状态 PUBLISHED
Note: For additional ORA-600 related information please read Note:146580.1 PURPOSE: This article represents a partially published OERI note. It has been published because the ORA-600 error has been reported in at least one confirmed bug. Therefore, the SUGGESTIONS section of this article may help in terms of identifying the cause of the error. This specific ORA-600 error may be considered for full publication at a later date. If/when fully published, additional information will be available here on the nature of this error. ERROR: ORA-600 [evapth : unexpected evaluation] [a] [b] [c] [d] [e] SUGGESTIONS: If the Known Issues section below does not help in terms of identifying a solution, please submit the trace files and alert.log to Oracle Support Services for further analysis. Known Issues: Bug# 5262483 See Note:5262483.8 OERI[evapth : unexpected evaluation] from CONNECT BY query Fixed: 10.2.0.5, 11.2 Bug# 5234295 See Note:5234295.8 OERI[evapth : unexpected evaluation] from SYS_CONNECT_BY_PATH Fixed: 10.2.0.5, 11.1.0.6 Bug# 3703176 See Note:3703176.8 OERI[evapth : unexpected evaluation] selecting from set view using SYS_CONNECT_BY_PATH Fixed: 9.2.0.7, 10.1.0.4, 10.2.0.1 Bug# 3365439 See Note:3365439.8 OERI[evapth : unexpected evaluation] using SYS_CONNECT_BY_PATH Fixed: 9.2.0.7, 10.1.0.4, 10.2.0.1 Bug# 2627306 See Note:2627306.8 OERI:[evapth : unexpected evaluation] using SYS_CONNECT_BY_PATH() Fixed: 9.2.0.4, 10.1.0.2
Bug 5234295 - OERI[evapth : unexpected evaluation] from SYS_CONNECT_BY_PATH [ID 5234295.8] 修改时间 13-JUL-2011 类型 PATCH 状态 ARCHIVED
Bug 5234295 OERI[evapth : unexpected evaluation] from SYS_CONNECT_BY_PATH This note gives a brief overview of bug 5234295.The content was last updated on: 27-MAY-2009
Click here for details of each of the sections below.
Affects: Product (Component) Oracle Server (Rdbms) Range of versions believed to be affected Versions < 11 Versions confirmed as being affected Platforms affected Generic (all / most platforms affected) Fixed: This issue is fixed in Symptoms: Related To: Description
An invalid evaluation of the SYS_CONNECT_BY_PATH with a PRIOR clause in front of it during execution of a CONNECT BY START WITH statement can fail with an ORA-600 . Workaround Use a NO_CONNECT_BY_FILTERING hint on the query.Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. Always consult with Oracle Support for advice. References Bug:5234295 (This link will only work for PUBLISHED bugs)
Note:245840.1 Information on the sections in this article