ORA-07445: exception encountered: core dump [ksuklms()+] [SIGSEGV] [Address not mapped to object]

ORA-07445: exception encountered: core dump [ksuklms()+672] [SIGSEGV] [Address not mapped to object] [0x000000062] [] []
========================================================


Analysis of ORA-07445: exception encountered: core dump [ksuklms()+672] first argument


====================in alert log file =========================

Errors in file /d01/admin/orcl/bdump/orcl_j000_29155.trc:
ORA-07445: exception encountered: core dump [ksuklms()+672] [SIGSEGV] [Address not mapped to object] [0x000000062] [] []
Sun Apr 3 10:02:32 2011


===============================in the associate trace file=========
ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [ksuklms()+672] [SIGSEGV] [Address not mapped to object] [0x000000062] [] []
Current SQL statement for this session:
ALTER SYSTEM KILL SESSION '2192,1'
----- PL/SQL Call Stack -----
object line object
handle number name
504e1e2b0 23 procedure orcl.DPR_USER_LOCKS
5107b8b28 1 anonymous block
----- Call Stack Trace -----





SQL>
SQL> select * from v$version ;

BANNER
----------------------------------------------------------------
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for Solaris: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - Production


SQL>
SQL> show parameter compatible

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
compatible string 10.2.0.3.0
SQL>



Cause of this problem:
======================

This problem is introduced in 10.2.0.4 and fixed in 10.2.0.5

A dump can occur under ksuklms leading to an instance crash following a kill of a system process.
Such a kill can occur automatically in RAC. It is not required that you be on RAC to encounter this problem but the issue is much less likely to occur in non-RAC.

It is caused by the Controlfile timeout


In this case the solution will be
=================================

if trace file we are seeing that

procedure orcl.DPR_USER_LOCKS try to killing a session with command "ALTER SYSTEM KILL SESSION '2192,1'" . but in that time Controlfile timeout occure. so stop the procedure will solve the problem.