Last updated on MAY 26, 2017
Applies to:Oracle Demantra Demand Management - Version 12.2.4 and later
Information in this document applies to any platform.
Customer is on 18.104.22.168 and mentions that they load sales history on a monthly basis, on first of every month.
After load is complete they run proport prior to running engine.
Run times of proport vary greatly from run to run with similar data volumes.
On Jan 1st proport ran in 35 minutes but on Feb 1st proport ran for 3hrs 34 min. (On Jan 27th with almost same data proport ran in 35 minutes in a prod identical test environment)
Customer has enabled proport to run in parallel by following the below doc
Proport performance ProportPropChanges--How to configure the same in init_params table? (Doc ID 2101661.1)
They have also enable parallel degree of 4 in tables sales_data and mdp_matrix
However the subsequent run of proport was run for 2 hours 30 minutes
It seems like every time the customer runs proport , it does not necessarily run in parallel.
They load data for SALES_DATA on a monthly basis for 6 months. Data volume is pretty consistent.
When proport runs in parallel it completes in about 35 minutes otherwise it takes 2.5+ hrs.
Seems like DEM.DYN_PROPORT_SALES_1 is the procedure that gets run. And it seems it is setting session to use parallel but system is not honoring it.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms