Demantra Engine Errors After Upgrading From 11G To 12C Database: ORA-04020: deadlock detected while trying to lock object TPO_O.PROMOTION_DATA

(Doc ID 2396800.1)

Last updated on MAY 24, 2018

Applies to:

Oracle Demantra Trade Promotion Optimization - Version 12.2.4 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.4 version, TPO-Gen

Demantra Engine Errors after upgrading from 11G to 12C Database



ERROR
-----------------------
07:19:31:380 07:19:31:380 ERROR - NativeErrorNumber: 4020
07:19:31:489 07:19:31:489 ERROR ORA-04020: deadlock detected while trying to lock object TPO_O.PROMOTION_DATA
ORA-06512: at "TPO_O.OCS_DISC_CAUSAL", line 48
ORA-06512: at line 1

07:19:32:971 07:19:32:971 WARNING GetDataObject() - Variable: PdeTable not found in dictionary!
07:19:33:080 07:19:33:080 ERROR ---------------------------------------------------------------
07:19:33:189 07:19:33:189 ERROR DB_Command::Execute threw an exception:
07:19:33:299 07:19:33:299 ERROR SELECT sales_date, promo_id, promo_type ,TACTIC,CONSUMER_DISC,I_CONSUMER_DISC,NET_DISC_CHANGE,DISP_LOC_TYPE,CONS_OVERLAY From where item_id = ? and location_id = ? AND sales_date >= ? and sales_date <= ? order by sales_date, promo_id
07:19:33:408 07:19:33:408 ERROR - ErrorDescription: ORA-00903: invalid table name

07:19:33:517 07:19:33:517 ERROR - ErrorNumber: 0x80040e14 - Undefined Error.
07:19:33:626 07:19:33:626 ERROR - NativeErrorNumber: 903
07:19:33:735 07:19:33:735 ERROR - ErrorDescription: One or more errors occurred during processing of command.
07:19:33:845 07:19:33:845 ERROR - ErrorNumber: 0x80040e14 - Undefined Error.
07:19:33:954 07:19:33:954 ERROR - NativeErrorNumber: 0
07:19:34:063 07:19:34:063 ERROR Parameter 0 : 8757414
07:19:34:172 07:19:34:172 ERROR Parameter 1 : 61
07:19:34:281 07:19:34:281 ERROR Parameter 2 : 24:01:2016
07:19:34:391 07:19:34:391 ERROR Parameter 3 : 14:01:2018
07:19:34:515 07:19:34:515 WARNING Caught exception at: DmM3LPLTreeNode::LoadPromoCausalsFromDB()
07:19:34:625 07:19:34:625 WARNING GetDataObj




STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Upgrade database from 11g to 12g


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot get the forecast to work with

Changes

 

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