APPS OE RAISES ORA-07445 [qersoProcessULS()+347]

(Doc ID 1676436.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Database - Enterprise Edition - Version and later
Information in this document applies to any platform.


The following symptoms have been attributed to this issue :-

a) ORA-7445 [QERSOPROCESSULS()+347] is seen in alert log and from APPS OE operations.  The 'offset' is typically 347 but if another value this note might still be applicable

b) The incident trace file will show a 'Context Dump' similar to

----- Incident Context Dump -----
Address: 0x2ae28d9a05a8
Incident ID: 684967
Problem Key: ORA 7445 [qersoProcessULS()+347]
Error: ORA-7445 [qersoProcessULS()+347] [SIGSEGV] [ADDR:0x168] [PC:0x250FD23] [Address not mapped to object] [] [] [] [] [] [] []
[00]: dbgexExplicitEndInc [diag_dde]
[01]: dbgeEndDDEInvocationImpl [diag_dde]
[02]: dbgeEndDDEInvocation [diag_dde]
[03]: ssexhd []
[04]: __sighandler []
[05]: qersoProcessULS [SQL_Execution]<-- Signaling
[06]: qerjoFetch [SQL_Execution]
[07]: qerstFetch [SQL_Execution]
[08]: qersqFetch [SQL_Execution]
[09]: qerstFetch [SQL_Execution]
[10]: rwsfcd []
[11]: qerstFetch [SQL_Execution]
[12]: qerltcFetch [SQL_Execution]
[13]: qerstFetch [SQL_Execution]
[14]: insexe [DML]
[15]: opiexe []

c) The following workaround stops the error

alter system set "_optimizer_sortmerge_join_enabled"=false;

Such workarounds might have a performance impact so need to be tested first.



Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms