My Oracle Support Banner

Demantra Daily Jobs (workflows) Are Erroring Out With Generic "Program Internal Error" (Doc ID 2508152.1)

Last updated on DECEMBER 04, 2019

Applies to:

Oracle Demantra Demand Management - Version 12.2 and later
Information in this document applies to any platform.

Symptoms

On : 12.2 version, Workflow

Our Demantra daily jobs (workflows) are failing with generic error.

ERROR
-----------------------
2018-12-08 06:30:01,646 PST [WFProcess_12] ERROR dpweb.general: Process ID: 791799
Schema ID: 2018
Schema name: 'WEEKLY_JOB'
Step ID: 'Step8'
Step name: 'DM_ERROR_RPT'

Error description 'Program internal error:'

2.
2018-12-08 06:30:01,630 PST [WFProcess_12] ERROR dpweb.general: Process ID: 0
Schema ID: 1937
Schema name: 'IMP_MI_SE'
Step ID: 'Step4'
Step name: 'DM_DATA_LOAD'

Error description 'Program internal error:'

3.
2018-12-08 06:30:01,602 PST [WFProcess_12] ERROR dpweb.general: Process ID: 0
Schema ID: 1936
Schema name: 'IMP_SFDC'
Step ID: 'Step1'
Step name: 'DM_DATA_LOAD'

Error description 'Program internal error:'

 

4.
2018-12-07 07:00:06,291 PST [WFProcess_17] ERROR dpweb.general: Process ID: 791829
Schema ID: 1812
Schema name: 'ITEM_LOAD'
Step ID: 'Step4'
Step name: 'EP_LOAD_ITEMS'

Error description 'Program internal error:'

When looking at the DB_EXCEPTION_LOG table, we see the following error:

ROC_NAME = EP_LOAD_SALES
-------------------------
-913 ORA-00913: too many values Error in PROCEDURE
EP_LOAD_SALES.EP_LOAD_SALES line 764

dynamic_ddl( 'INSERT INTO T_SRC_SALES_TMPL_TMP (
SELECT /*+ parallel(T_SRC_SALES_TMPL 4)
full(T_SRC_SALES_TMPL)*/ T_SRC_SALES_TMPL.*,9 ,'01-09-2019 06:39:36',
'LOCATION IN SALES source does NOT exist IN LOCATION', ROWID
FROM T_SRC_SALES_TMPL
MINUS
SELECT /*+ parallel(T_SRC_SALES_TMPL 4)
full(T_SRC_SALES_TMPL)*/ T_SRC_SALES_TMPL.*,9 ,'01-09-2019 06:39:36',
'LOCATION IN SALES source does NOT exist IN LOCATION', T_SRC_SALES_TMPL.ROWID
FROM T_SRC_SALES_TMPL, LOCATION , t_ep_ls1, t_ep_lr1,
t_ep_organization, t_ep_ebs_sales_ch, t_ep_site
WHERE 1 = 1
AND location.t_ep_ls1_ep_id =
t_ep_ls1.t_ep_ls1_ep_id
AND LOWER(T_SRC_SALES_TMPL.t_ep_ls1) = LOWER(t_ep_ls1.ls1)
AND location.t_ep_lr1_ep_id =
t_ep_lr1.t_ep_lr1_ep_id
AND LOWER(T_SRC_SALES_TMPL.t_ep_lr1) = LOWER(t_ep_lr1.lr1)
AND location.t_ep_organization_ep_id =
t_ep_organization.t_ep_organization_ep_id
AND LOWER(T_SRC_SALES_TMPL.dm_org_code) =
LOWER(t_ep_organization.organization)1
AND location.t_ep_ebs_sales_ch_ep_id =
t_ep_ebs_sales_ch.t_ep_ebs_sales_ch_ep_id
AND LOWER(T_SRC_SALES_TMPL.ebs_sales_channel_code) =
LOWER(t_ep_ebs_sales_ch.ebs_sales_ch)
AND location.t_ep_site_ep_id =
t_ep_site.t_ep_site_ep_id
AND LOWER(T_SRC_SALES_TMPL.dm_site_code) =
LOWER(t_ep_site.site))')



STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Run workflows.

 

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.