Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.5 to 12.1.0.2 [Release 10.2 to 12.1]
Information in this document applies to any platform.
Symptoms
Observing ORA-7445 error below in database:
ORA-07445: exception encountered: core dump [kkorminl()+317] [SIGSEGV] [ADDR:0x7FFF0995BFF8] [PC:0x971165B] [Address not mapped to object] []
Changes
Cause
Based on the call stack and symptoms this is a match for the following unpublished bug:
Bug 13809241 - ORA 7445 [KKORMINL] FOR APPS R12 WHILE RUNNING CONCURRENT SQLTUNE JOBS
This bug regressed and was replaced with the following unpublished bug:
Bug 17339455 - EBS12.2: ORA-600 [QERIXADDNOTNULLSTOPKEYPREDICATE:1] WITH TUNE SQL
Reference:
Bug 13809241 - ora 7445 [kkorminl] for apps r12 while running concurrent sqltune jobs. (Doc ID 13809241.8)
Bug 17339455 - ORA-7445 [kkorminl] or similar can occur when running Automatic tuning tasks / DBMS_SQLTUNE Index Advisor (Doc ID 17339455.8)
Bug 13809241 happens while calling SQL Tuning Advisor which if we look at the plsql stack in the incident trace:
----- PL/SQL Call Stack -----
object line object
handle number name
0x3c34d8148 11829 package body SYS.DBMS_SQLTUNE_INTERNAL
0x343e4e560 7 SYS.WRI$_ADV_SQLTUNE
0x3c3620708 601 package body SYS.PRVT_ADVISOR
0x3c3620708 2658 package body SYS.PRVT_ADVISOR
0x3bfe86df8 241 package body SYS.DBMS_ADVISOR
0x3bfedc730 821 package body SYS.DBMS_SQLTUNE
0x36f81bc08 4 anonymous block
Solution
1. Apply patch 17339455 if available for your platform or Database version. If no patch is available please open an SR to request a patch.
2. Upgrade to a version where this is resolved, it is first included in 12.1.0.2.
3. Use the following workaround: disable the automatic tuning job. (Note this is for only if it occurs during automatic tuning)
BEGIN
dbms_auto_task_admin.disable(
client_name => 'sql tuning advisor',
operation => NULL,
window_name => NULL);
END;
/