Max_fore_level Is Set Right, But Engine Log Has Warning On 'Initparam.Max_fore_level'
(Doc ID 1134119.1)
Last updated on MARCH 08, 2017
Applies to:Oracle Demantra Demand Management - Version: 7.3.0 to 126.96.36.199 - Release: 7.3.0 to 7.3.0
Information in this document applies to any platform.
***Checked for relevance on 20-Dec-2011***
There are 6 forecast levels in the forecast tree. Max_fore_level is set to 5 However the customer gets the following message WARNING in the engine logs:
21:12:35:117 <PIT-SV-DMANDEV1-0> 21:12:35:117 WARNING 'InitParam.max_fore_level' parameter has incorrect value: 6. Value must be less than max(forecast_level) from forecast_tree table (6) Setting to 5
Customer has verified that the values for the following parameters are right as per initi_params_0 table:
select max(forecast_level) from forecast_tree;
select pname, value_float from init_params_0 where pname='max_fore_level';
select pname, value_float from init_params_0 where pname='top_level';
select pname, value_float from init_params_0 where pname='InfluenceRangeLevel';
They have also verified that the engine profile being used is Base;
Business Modeler--->Parameters--->system parameters--->engine
They also tried bouncing the server, but the WARN messages persists in the engine logs
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|