PROCEDURE EP_LOAD_SALES Creates Hundreds Of Sessions
Last updated on MARCH 08, 2017
Applies to:Oracle Demantra Demand Management - Version 12.2.4 and later
Information in this document applies to any platform.
We're attempting to load sales history using the PROCEDURE named EP_LOAD_SALES included in a Demantra 12.2.4 install that has been patched with patch #18139794. Whenever we execute EP_LOAD_SALES hundreds of slave sessions are created. I suspect this is a result of the "ALTER SESSION FORCE PARALLEL DML" and "ALTER SESSION FORCE PARALLEL QUERY" statements that appear in EP_LOAD_SALES. I have set the PVAL column value to "FALSE" for the PNAME column value "DBHintEp_Load_SalesUseParallelDML" and PNAME column value "DBHint_Ep_Load_SalesUseParallel" in the TABLE named DB_PARAMS, but these settings don't seem to have any effect on the operation of EP_LOAD_SALES. I would like to know how to prevent EP_LOAD_SALES from using parallel processing because the parallelized SQL execution causes contention problems in the TABLE named T_SRC_SALES_TMPL.
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