Streams Hangs After ORA-07445 [ksrconsume] Core Dump and Repeated Alert Log Messages "Pmon Failed To Acquire Latch, See Pmon Dump"
Last updated on SEPTEMBER 12, 2015
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 to 10.2.0.4 [Release 10.2]
Information in this document applies to any platform.
Oracle Server Enterprise Edition - Version: 10.2.0.1 to 10.2.0.4
In a 10.2 Streams environment, it is observed that no messages are flowing after errors similar to the following are reported in the alert log:
Errors in file /opt/oracle/admin/orcl/bdump/orcl_j001_23372.trc:
ORA-07445: exception encountered: core dump [ksrconsume()+772] [SIGFPE] [Integer divide by zero] [0x1005E5944]  
Looking in orcl_j001_23372.trc, we see:
ORA-07445: exception encountered: core dump [ksrconsume()+772] [SIGFPE] [Integer divide by zero]
[0x1005E5944]  
Current SQL statement for this session:
DECLARE job BINARY_INTEGER := :job; next_date DATE := :mydate; broken BOOLEAN := FALSE; BEGIN next_date := sys.dbms_aqadm.aq$_propaq(job); :mydate := next_date; IF broken THEN :b := 1; ELSE :b := 0; END IF; END;
Also, messages similar to the following are written repeatedly to the alert log:
PMON failed to acquire latch, see PMON dump
From the PMON dump:
Location from where latch is held: ksrsconsume():
Context saved from call: 21218704936
state=busy(exclusive) (val=0x2000000000000466) holder orapid = 1126
Querying v$process shows that orapid 1126 is theOraclePID for the job queue process that is running the propagation referenced in the ORA-07445 [ksrconsume] trace file orcl_j001_23372.trc (J001):
Killing the job queue process (orapid 1126) does not resolve the problem, nor does disabling / re-enabling or dropping / recreating the propagation job.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms