Modification In MSONWL64.exe with regards to msc_full_pegging_s (Doc ID 1581048.1)

Last updated on MARCH 23, 2016

Applies to:

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

Symptoms

On 12.1.3.8:

CUSTOMER REPORTS
===========================
We have been seeing Huge "User Commits" when MSONWL64.exe was running. After taking a closer look we found that MSONWL64.exe is fetching multiple times of Next Value in the sequence.

Our site is having a Cache Size of 1000 for MSC.MSC_FULL_PEGGING_S. Fetching next value of sequence is Normal but interesting point here is once it is incrementing by 1 and next time by 500 subsequently by 1 and then again 500. This goes in a loop. This means 4th Fetch is going to invoke a DDL to update the latest value in the SEQ$ as value in the Cache would have been exhausted. This ends up in "Log File Sync" causing so much of Redo IO waits in database causing Response time in Storage to go high.

ALTER SEQUENCE MSC.MSC_FULL_PEGGING_S increment by 1
ALTER SEQUENCE MSC.MSC_FULL_PEGGING_S increment by 500
.
.
ALTER SEQUENCE MSC.MSC_FULL_PEGGING_S increment by 1
ALTER SEQUENCE MSC.MSC_FULL_PEGGING_S increment by 500
.
.

We want MSONWL64.exe to be modified by changing this increment from 500 to 1 or lower value which what ever oracle things is right.

Cause

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