My Oracle Support Banner

ORA-7445 ksuklms After Upgrade To (Doc ID 725951.1)

Last updated on FEBRUARY 14, 2022

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 10.2]
Information in this document applies to any platform. *** ***


This issue was observed on Oracle 64-bit on a Enterprise Manager repository database.

In this case, the problem showed up as many spawned perl processes on the server, not on the repository. Disabling the EM agent stopped the problem.

The alert log on the Enterprise manager repository shows the error, and it is preceded by a Controlfile timeout:

ORA-00240: control file enqueue held for more than 120 seconds
Killing enqueue blocker (pid=23270) on resource CF-00000000-00000000 by killing session 151.1
ORA-07445: exception encountered: core dump [ksuklms()+527] [SIGSEGV] [Address not mapped to
object] [0x000000062] [] []

The trace file may show a failing statement similar to this:
begin sys . dbms_backup_restore . commitRmanStatusRow
( row_id => :row_id , row_stamp => :row_stamp , mbytes => :mb , status => :status ,
ibytes => :ib , obytes => :ob , odevtype => :odevtype ) ;
end ;

The trace file will also show a Controlfile timeout :
ORA-00494: enqueue [CF] held for too long (more than 900 seconds) by 'inst 1, osid 23270
This traces to PID 23274
service name: SYS$BACKGROUND
waiting for 'Streams AQ: qmn coordinator idle wait'

Function stack for ORA-600 [ksuklms] error

ksedst ksedmp ssexhd funlockfile
ksuklms kjdgkblkr kjukblkr ksikblkr ksqactioninvoke ksqgtlctx
ksqgelctx  kcc_get_enqueue kccocx  kccbcx  krbmmrsr  krbimrsr

The function stack could also show these functions:
ksuklms kjdgkblkr kjsbstat kjsbstat_batch


You recently upgraded to


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.