DM BAL Upgrade From 7.3.12 To 184.108.40.206 fails with Check_Fore_Series_by_Profile issues
(Doc ID 1542285.1)
Last updated on FEBRUARY 28, 2019
Applies to:Oracle Demantra Real-Time Sales and Operations Planning - Version 220.127.116.11 and later
Information in this document applies to any platform.
On : 18.104.22.168 version, BAL
When attempting to upgrade from 7312 to 7314, the upgrade gets stopped into a BAL issue, - Upgrade Schema Option and Automatic Upgrade with Platform and Application Option.
While Validating the series at "Validating BAL Import" Screen it gave ora-20002 error. Although all the functionality checked are working fine; version_details_history is not updated; only BM appears to have the new version mark.
CHECK_FORE_SERIES_BY_PROFILE -1 ORA-00001: unique constraint (DEMANTRA.FORECAST_HISTORY_PK) violated Error in PROCEDURE line 388
dynamic_ddl( 'INSERT INTO forecast_history ( time_sig , status, engine, engine_profiles_id , init_params_table_name , fore_column_name ) VALUES ('01-21-1901 00:00:00', 2, 0,'106', 'INIT_PARAMS_141' ,'FORE_15')')
GET_EXP_WITH_NO_TOKEN -20005 ORA-20005: ii_profile_id=269 is not valid Error parsing expression sum(#FORE@0@269#*1)
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