Memory Based Planner Is Generating Huge Log File
(Doc ID 2203004.1)
Last updated on MARCH 08, 2017
Applies to:Oracle Advanced Supply Chain Planning - Version 12.2.5 and later
Information in this document applies to any platform.
On : 12.2.5 version, Memory Based Planner
Issue occurs upon completion of the program 'Memory Based Planner' with signal 11. The log file size of the aborted job is huge.
Even after zipping, size of file is approximately 44 MB which is huge considering the fact that we included only 10 percent of the organizations in the plan.
If all the all the organizations will be included, the size will surely increase manifold times. Following messages are getting printed n number of times in the log file thus,increasing the size:
1.) unbucketed_demand_date = 2457662
2.) Could not find the trans_id in the transaction_id
3.) pre alloc for gid:-23453 pid:-23453 tid:-23453
Customer needs a way to avoid getting these messages printed in the log file. These messages are not useful for customer and not needed.
Log File of Memory Based Planner should be smaller.
The issue can be reproduced at will with the following steps:
1. Run Plan.
2. Request MSONWS64 module: Memory Based Planner 64-bit Sun terminated with error: "Program was terminated by signal 11".
3. Log file is huge.
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
|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.|