今日在Oracle控制台中看到预警中有"
. 查看日志中显示问题:
ORA-00600: internal error code, arguments: [kkqcscpopn_Int: 0], [], [], [], [], [], [], [], [], [], [], []
在Trc中也没发现具体问题.将问题发给DBA的朋友看了之后. 他在MOS中看到类似的记录.
NB Bug Fixed Description
11810296 11.2.0.3, 12.1.0.0 ORA-600 [kkqcscpopn_Int: 0] with subquery unnesting and view merging
11661678 11.2.0.3, 12.1.0.0 ORA-600 [kkqcscpopn_Int: 0] / dump from query with function based index
10242303 11.2.0.2.BP15, 11.2.0.3, 12.1.0.0 Internal errors from query with ANSI join and many columns
10184115 11.2.0.2.BP15, 11.2.0.3, 12.1.0.0 Wrong Results, Assorted Internal Errors and Dumps with ANSI join of tables with large number of columns
9324531 11.2.0.1.BP04, 11.2.0.2, 12.1.0.0 ORA-600 [kkqcscpopn_Int: 0] from ANSI query
8537544 11.2.0.2, 12.1.0.0 Excess memory use / ORA-600 / dumps parsing SQL with many nested outer joins / ANSI joins
8337618 11.2.0.1 ORA-600 [kkqcscpopn_int: 0] using complex views and GROUP BY
Description
Cost based query transformation involving combined unnest subquery and
view merging could cause ORA-600[kkqcscpopn_Int: 0]
Rediscovery Notes:
If kkqctPrepQuerySQUN() is in stack there is a chance of this bug
Workaround
Prevent Subquery Unnesting or complex view merging.
eg: Disable cost based query transformations by setting
"_optimizer_cost_based_transformation"=off
本文详细分析了Oracle控制台中遇到的ORA-00600: internal error code错误及其背后的Bug记录。通过查阅相关文档和社区反馈,我们了解到该错误可能由特定的查询操作引发,如子查询展开、复杂视图合并等。文中提供了预防措施,包括禁用基于成本的查询转换,以避免此类问题的发生。

414

被折叠的 条评论
为什么被折叠?



