My Oracle Support Banner

ORA-07445 [LdiDateCompare()+36] Occurs At The Beginning Of Each Scheduling Window on the Database (Doc ID 1509202.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 to 11.2.0.3 [Release 11.2]
Information in this document applies to any platform.

Symptoms

ORA-7445 [LdiDateCompare()+36] is signaled by an MMON slave process in a RAC environment. The trace file written by the error shows no current cursor being executed.

 

The trace file will contain a stack similar to:

 

LdiDateCompare <- jsksAddBCastMsg <- jskacbf1 <- jskacbf0 <- rpiswu2 <- jskacbf <- ktcccdel <- ktccpcmt <- ktcCommitTxn <- ket_js_enable <- ket_job_enable <- ket_task_to_job <- ket_aba_main <- ket_aba_start <- ket_aba_slave <- kebm_slave_main <- ksvrdp <- opirip <- opidrv <- sou2o

 

In the trace, the second set of values in the argument values column will be zeroes:

 

jsksAddBCastMsg()+1  call     LdiDateCompare()     43499B80C ? 000000000 ?
250                                                7FFF92F315D0 ? 436BDAAC0 ?
                                                   000000040 ? 000000000 ?




Cause

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
Symptoms
Cause
Solution
References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.