Last updated on JULY 19, 2017
Applies to:Oracle Demantra Demand Management - Version 184.108.40.206 and later
Information in this document applies to any platform.
Customer has upgraded to 220.127.116.11
VERSION BUILD SP Upgrade Date
12.2.6 2 12260250 27-APR-2017 03:17:34
12.2.6 1 12260251 27-APR-2017 02:57:20
12.2.6 112 0 26-APR-2017 13:23:00
7.3.1 48 UPGRADED FROM 26-APR-2017 06:12:59
7.3.1 1 7310234 10-MAY-2014 19:46:11
7.3.1 2 7302173 20-AUG-2013 23:11:54
7.3.1 48 0 13-SEP-2011 13:38:22
Post that they have noticed that the Rolling_profiles job in demantra doesn't execute through DBMS_JOBS anymore
They have turned on the below db parameters, but dont see that rolling_profiles are executing through dbms_jobs and ITEMS join is not added in update statement.
UPDATE DB_PARAMS SET PVAL='TRUE' WHERE PNAME='RollingUpdatesUseJobQueues';
UPDATE DB_PARAMS SET PVAL='TRUE' WHERE PNAME='RollingUpdatesRenameColumns';
UPDATE DB_PARAMS SET PVAL='ITEMS' WHERE PNAME='RollingupdatesDimLevelStep';
UPDATE DB_PARAMS SET PVAL='TRUE' WHERE PNAME='RollingUpdatesOneCommit';
In the upgraded instance it now does not run through dbms_jobs , but as a direct SQL driven by application
There is no issue with the execution. Question is, rolling_profiles execution is driven by dbms_jobs before , now not by it. Ask is to know if that is how the latest version is designed to.
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