My Oracle Support Banner

Memory Based Snapshot / Memory based Planner Failing With ORA-03114 (Program Was Terminated By Signal 6) (Doc ID 2709710.1)

Last updated on SEPTEMBER 15, 2020

Applies to:

Oracle Advanced Supply Chain Planning - Version 12.2.8 and later
Information in this document applies to any platform.

Goal

How can we track down the problem where
MBS/MBP failing with ORA-03114 (Program was terminated by signal 6)

Logs are showing messages like


MSCNSPWL64 module: Memory Based Snapshot 64 bit Linux
+---------------------------------------------------------------------------+
Current system time is 25-AUG-2020 00:18:35
.....
.Selecting Calendar 0:00
APP-FND-01564: ORACLE error 3113 in mrllpi_load_planned_items

Cause: mrllpi_load_planned_items failed due to ORA-03113: end-of-file on communication channel
.

The SQL statement being executed at the time of the error was: select sr_tp_id ,partner_type from msc_trading_partners where ((calen and was executed from the file .
APP-MRP-22075: An internal error has occurred (mrsnii_snp_item_info, 103, , )
@ERRORTEXT Cause: The current routine encountered the specified@ERRORTEXT x Action: Contact your customer supportrepresentative.
APP-MRP-22075: An internal error has occurred (main, 10, 709, DIST-C)
@ERRORTEXT Cause: The current routine encountered the specified@ERRORTEXT x Action: Contact your customer supportrepresentative.
Error string=
Statement with the error:
select sr_tp_id ,partner_type from msc_trading_partners where ((calen



***** End Of Program - Memory Based Snapshot 64 bit Linux *****
+---------------------------------------------------------------------------+
Start of log messages from FND_FILE
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
End of log messages from FND_FILE
+---------------------------------------------------------------------------+
ORACLE error 3114 in AFPRSR-Resubmit_Time

Cause: AFPRSR-Resubmit_Time failed due to ORA-03114: not connected to ORACLE
.

The SQL statement being executed at the time of the error was: select To_Char(To_Date(Decode(Resubmit_Time,null ,'00:
Routine FDPCLS encountered an error changing request 9581490 status.

Contact your support representative.
ORACLE error 3114 in fetch_lines

Cause: fetch_lines failed due to ORA-03114: not connected to ORACLE.

The SQL statement being executed at the time of the error was: &SQLSTMT and was executed from the file &ERRFILE.
ORACLE error 3114 in fetch_lines

Cause: fetch_lines failed due to ORA-03114: not connected to ORACLE.

The SQL statement being executed at the time of the error was: &SQLSTMT and was executed from the file &ERRFILE.
ORACLE error 3114 in open_server_files

Cause: open_server_files failed due to ORA-03114: not connected to ORACLE.

The SQL statement being executed at the time of the error was: &SQLSTMT and was executed from the file &ERRFILE.
ORACLE error 3114 in close_user_handles

Cause: close_user_handles failed due to ORA-03114: not connected to ORACLE.

The SQL statement being executed at the time of the error was: &SQLSTMT and was executed from the file &ERRFILE.
ORACLE error 3114 in FDPCLS

Cause: FDPCLS failed due to ORA-03114: not connected to ORACLE
.

The SQL statement being executed at the time of the error was: lock TABLE FND_CONCURRENT_REQUESTS IN SHARE UPDATE MODE and was executed from the
*** glibc detected *** MSCNPL64.exe: free(): invalid pointer: 0x0000000005121e80 ***
======= Backtrace: =========
/lib64/libc.so.6[0x3297075e5e]
/lib64/libc.so.6[0x3297078cad]
 

Solution

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
Goal
Solution


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