Fine Tuning RLM Demand Processor and Order API Process After 12722228 (Doc ID 1447082.1)

Last updated on OCTOBER 04, 2016

Applies to:

Oracle Release Management - Version 11.5.10.2 to 11.5.10.2 [Release 11.5.10]
Information in this document applies to any platform.
***Checked for relevance on 22-APR-2015***

Symptoms

On : 11.5.10.2 version, Demand Processor Related Issue

ACTUAL BEHAVIOR
---------------
On : 11.5.10.2 version, Demand Processor Related Issue

DSP process taking time even though no other program is running
in parallel. As per the stats provided in uploaded trc/tkprof:

1st DSP reqId=58498171 Items=10351 ran for 67 min vs 33 min expecting
16 min runtime & trace size=1.9Gb
2nd DSP reqId=58498176 Items=39036 ran in 5hr 7min and huge trace file
was 9.1Gb
3rd DSP reqId=58498177 Items=69339 ran in 10hr 35min and hugest trace
file was 20.6Gb with < 70000 items.

Need clarification as to what is causing Demand Processor to create huge
trace files when NO DEBUG LEVELs set and only TRACE LEVEL-1 used. This
was NOT the case during our previous testing and work to get patch
12722228 in AEES D740 instance.

Please assist via this new bug to provide some root cause from your analysis.

This issue has been ongoing for more than a month... and developers
haven't suggested cause or solution, please help AEES receive some
feedback from the uploaded Trace(s) and TKprof(s) provided.

OBSERVATION
-------------------
This new performance bug.13097898 has been logged as per the developments request
to review/address the "continued" performance issue AFTER applying Performance
bug.12722228.


EXPECTED BEHAVIOR
-----------------------
Expect better performance for this particular DSP process.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Responsibility: Release Management
2. Run DSP
3. Trace / Tkprof log files show an enormous performance issue

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot successfully run the DSP in a timely manner via the
PRODUCTION instance due to the performance issue it creates.

Changes

After applying Performance Patch 12722228

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