My Oracle Support Banner

OEXOEMCG / OE_MASS_CHANGE_PVT : issue with Mass Change operation in the sales order form (Doc ID 1401564.1)

Last updated on MAY 23, 2018

Applies to:

Oracle Order Management - Version 12.1.3 and later
Information in this document applies to any platform.
***Checked for relevance on 23-Oct-2013***

Symptoms


In 12.1.3 in PROD:
The following is visible in the DB alert log file ( this occurs 20- 30 times in the alert log file) :

ORA-07445: core dump [lxdgetobj()+40] [SIGSEGV] [ADDR:0x84014128D1F2F0EE] [PC:0x1001DA408] [Address not mapped to object] []
Incident details in: /oracle/OEBS/db/11.2.0/admin/OEBS_oebsdb/diag/rdbms/oebs/OEBS/incident/incdir_6745/OEBS_ora_5768542_i6745.trc

---

from the trace file name mentioned in alert log file :OEBS_ora_5768542_i6745.trc, it can be seen:

Dump continued from file: /oracle/OEBS/db/11.2.0/admin/OEBS_oebsdb/diag/rdbms/oebs/OEBS/trace/OEBS_ora_5768542.trc
ORA-07445: core dump [lxdgetobj()+40] [SIGSEGV] [ADDR:0x84014128D1F2F0EE] [PC:0x1001DA408] [Address not mapped to object] []

========= Dump for incident 6745 (ORA 7445 [lxdgetobj()+40]) ========
----- Beginning of Customized Incident Dump(s) -----
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x84014128D1F2F0EE] [PC:0x1001DA408, lxdgetobj()+40] [flags: 0x0, count: 1]
Registers:
iar: 0x00000001001da408 lr: 0x00000001001da2f4
msr: 0xa00000000200d032 cr: 0x0000000035595050
r00: 0x00000001001da2f4 r01: 0x0fffffffffff4910 r02: 0x000000011065a220
r03: 0x84014128d1f2f0ee r04: 0x0000000000000002 r05: 0x0000000111d211f0
r06: 0x00000000000000ab r07: 0x00000000000007d0 r08: 0x0000000111285298
r09: 0x0000000111d211f0 r10: 0x0fffffffffff4e80 r11: 0x0fffffffffff7108
r12: 0x0000000000000040 r13: 0x00000001106fd260 r14: 0x0fffffffffff51c0
r15: 0x0000000165477eb8 r16: 0x0000000109a8fba0 r17: 0x070000449158f5a3
r18: 0x0000000110ce0038 r19: 0x0000000110ccf6d4 r20: 0x0000000000000000
r21: 0x0000000000000000 r22: 0x0000000000000060 r23: 0x0000000000000060
r24: 0x0000000111d211f0 r25: 0x0000000000000000 r26: 0x0000000000000000
r27: 0x0fffffffffff72f8 r28: 0x00000000000000fd r29: 0x0000000000000002
r30: 0x00000000000007e8 r31: 0x0000000111d211f0

*** 2012-01-24 06:31:02.255
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x3, level=3, mask=0x0)
----- SQL Statement (None) -----
Current SQL information unavailable - no cursor.
penexc: bad structure: PF_UMP=ff20eee1f0e0e1ee, PF_ULP=0
Because of this, no line numbers will be available for this native-mode library unit on the stack.

==============
it can be seen that the form is OEXOEMCG - Mass Change

Customer used the select from v$session which returns SQL_ID of users which use this form.
Also, Customer retrieved the SQL statement via sql_id :

SELECT X.ID1, X.ORG_ID, L.HEADER_ID, L.ARRIVAL_SET_ID, L.SHIP_SET_ID, L.TOP_MODEL_LINE_ID
FROM TABLE(OE_MASS_CHANGE_PVT.GET_SEL_REC_TBL) X, OE_ORDER_LINES_ALL L
WHERE L.LINE_ID = X.ID1 ORDER BY L.HEADER_ID, NVL(L.ARRIVAL_SET_ID, -1), NVL(L.SHIP_SET_ID, -1), NVL(L.TOP_MODEL_LINE_ID, -1)

The query comes from the package OEXVMSCB.pls 


Customer wants to address this error from alert log file.

Changes

 

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!


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