ORA-00600: internalerrorcode, arguments: [evapth: unexpec

Looking at the book, suddenly received a text message from the monitoring platform: data appeared ORA-00600: internalerrorcode, arguments: [evapth: unexpectedev

Looking at the book, suddenly received a text message from the monitoring platform: data appears ORA-00600: internal error code, arguments: [evapth: unexpected ev

Looking at the book, I suddenly received a text message from the monitoring platform: The data appeared.ORA-00600: internal error code, arguments: [evapth: unexpected evaluation], [], [], [], [], [], [], []An internal error occurred. I ran to the data center and checked it. I was told that this error was caused by an SQL statement executed by a buddy. Fortunately, it was just a false alarm, however, I still want to understand this problem.

Server: AIX 5309

Database: Oracle 10.2.0.4

The statement that the Buddy was executing was:

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 "Medium and Small Businesses ",
T7.second _ type,
T7.first _ type,
T7.path _ code,
T7.path _ name,
T2.loan _ start_date,
T2.mature _ date,
T2.loan _ amt "payment amount ",
T2.cmis _ five_class,
T1.loan _ amt "loan balance ",
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,
(Select t5.loan _ type_id, connect_by_root t5.loan _ type_id as second_type, connect_by_root t5.upper _ loan_type_id as first_type,
Sys_connect_by_path (t5.loan _ type_id, '/') as path_code, sys_connect_by_path (t5.loan _ type_name, '/') as path_name
From los. loan_type_info @ los t5 start with t5.loan _ type_id <> t5.upper _ loan_type_id
Connect by nocycle prior t5.loan _ type_id = t5.upper _ loan_type_id) T7
Where t. data_date = '123'
And t1.fdate = '123'
And t. customer_id = t1.client _ no
And t2.fdate = '20140901'
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 = '20140901'
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
Order by t4.sec _ code, t4.fir _ code, t. mermer_id

I checked some information on Google and MOS on the Internet, both because sys_connect_by_path is used. Note that the red part in SQL is okay to execute the red SQL statement separately ,, however, if the entire SQL statement is executed together, an error is reported. This indicates that this error is not caused by the subsql statement, but is caused by a combination of other statements (Bug ).

Note: But I also found a strange problem, that is, this statement. I can execute it in another environment. I don't know why, the two sets of database patch sets are the same.

Directly attach the official documents:

ORA-600 [evapth: unexpected evaluation] [ID 284511.1]

Modification time: 19-DEC-2011 type REFERENCE status PUBLISHED

Notes: 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 beenreported 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 informationwill be available here on the nature of this error. ERROR: The 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 OracleSupport Services for further analysis. known Issues: Bug #5262483 See Note: 5262483.8 OERI [evapth: unexpected evaluation] from connect by queryFixed: 10.2.0.5, 11.2Bug #5234295 See Note: 5234295.8 OERI [evapth: unexpected evaluation] from notice: 10.2.0.5, 11.1.0.6Bug #3703176 See Note: 3703176.8 OERI [evapth: unexpected evaluation] selecting from set view using comment: 9.2.0.7, 10.1.0.4, 10.2.0.1Bug #3365439 See Note: 3365439.8 OERI [evapth: unexpected evaluation] using failed: 9.2.0.7, 10.1.0.4, 10.2.0.1Bug #2627306 See Note: 2627306.8 OERI: [evapth: unexpected evaluation] using failed () Fixed: 9.2.0.4, 10.1.0.2

Bug 5234295-OERI [evapth: unexpected evaluation] from SYS_CONNECT_BY_PATH [ID 5234295.8]