Tuesday, November 16, 2021

Troubleshooting Guide for the Demantra Engine Issues (Doc ID 1456714.1)

 In this Document

Purpose
Troubleshooting Steps
References

APPLIES TO:

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

PURPOSE

 To trouble shoot demantra engine issues

TROUBLESHOOTING STEPS

 

Whenever you face the problem with the Batch/Simulation Engine, you need to provide the following information to the oracle support for troubleshooting the engine issues.

 

1. Engine 2k log files

2. Engine manager log files

3.Please also upload these query outputs in the Excel sheet with the column headers:

Select * from forecast_history order by time_sig;
Select * from version_details_history order by upgrade_date desc;
Select * from sys_params;
Select * from init_params_0;

 

In addition to, for the simulation engine you need to provide the following:

Simulation only:

select * from simulation_q;
select * from simulation_list;

4. Whenever you run the engine from the workflow, If the engine is taking long time to complete it, please enable the Enhanced Logging for Workflow

http://<Host  Name of Webserver : Port Number>/demantra/admin/loggerManager.jsp

Turn on following Workflow related entries:

Once you enable the Enhanced Logging, you need to  Re-run the workflow and upload/Review the collaborator log file.

Note that this logging will be turned off either by the next time the web server is restarted or by the user turning off the lines that were earlier turned on.

5.Please make sure command line in the workflow provided is correct  as it needs to have full path:

"#application_root#\..\..\Demand Planner\Analytical Engines\bin\EngineManager.exe" 1 1

6. Please make sure that engine is running on 32-bit oracle client version on the client or server machine when you run the engine from the workflow.

7. Please also make sure that the AppServerURL is correctly in this path

Login to the Business Modeler
Parameters---->System parameters--->System--->AppServerURL
OR

select pval from sys_params where pname = 'AppServerURL'

8. When you run the engine on Linux machine,

Engine Manager Pre Run Log.txt
$ORACLE_HOME/j2ee/home/Engine Manager Pre Run Log.txt or $ENGINE_ROOT/bin/Engine Manager Pre Run Log.txt file.

settings.xml

9. Please enhance the Engine logs using this path
EngineAdmininstrator.exe
setting>>configure
please enhance by clicking once the SQL tab, If the tab is down, then it is enhanced.

10.When you are running the engine and your Demantra schema is large or big, you need to make sure that BranchID Multiple is set correctly using this formula

Check how many active combinations are in MDP_MATRIX

 select count(*) from mdp_matrix where do_fore=1 and prediction_status = 1


This result will be called TOTAL which then you use in the following calculation:

BranchID Multiplier = TOTAL / 2000 / Number of engines configured to run (ex. 1 if you have only one localhost).  Note that the number of engines allowed on one machine would roughly be 2 per physical CPU as long as there is around 1.5GB memory available per engine instance.

So in this example if Total = 200,000 and  Number of CPU = 2 the calculation would look like:   200,000 divided by 2000 divided by number of engines, which is 4 since you have 2 Engines per CPU.   200,00/2000/4=25, as your BranchID Multiplier

Save the change.  There is no need to re-register the engine after changing and saving this setting. 

 

11. Whenever the Proportions(P1 to P12 values) are high on a new combination even though very less sales on this combination, then you need to review these parameters(proport missing and proport spread) in the init_params_0 table.

select * from init_params_0 where pname='proport_missing';
select * from init_params_0 where pname='proport_spread';
select * from init_params_0 where pname='def_delta';

You can also re-calculate the proportions using this update statement

BEGIN
UPDATE mdp_matrix
SET prop_changes = 1
where item_id = << your_item_id>>
and location_id = << your_location_id>>;
COMMIT;
proport;
END;

You can also run this update statement whenever you change the engine parameters manually.

These parameters control how proportions will be assigned to months with no history, either those which were prior to the first sale or those which have null values.
By modifying these two parameters you can control how proportions will be assigned to months which did not have demand.
Please review Demantra Implementation Guide for more information.

 

12.If you find out of sync in the mdp_matrix table and sales_data table,then you can run this query on Demantra schema

SELECT ITEM_ID,LOCATION_ID FROM (
SELECT ITEM_ID,LOCATION_ID,FROM_DATE,UNTIL_DATE FROM MDP_MATRIX
UNION
SELECT ITEM_ID,LOCATION_ID, MIN(SALES_DATE), MAX(SALES_DATE) FROM SALES_DATA
GROUP BY ITEM_ID,LOCATION_ID)
GROUP BY ITEM_ID,LOCATION_ID
HAVING COUNT(*) > 1
ORDER BY ITEM_ID,LOCATION_ID;

If the above query returns zero rows, it means that the tables are in sync.

If the above query returns rows, then the tables are not sync. Then, you need to run this update statement

UPDATE MDP_MATRIX
SET FROM_DATE = NULL,
UNTIL_DATE = NULL;
COMMIT;
EXEC UPDATE_MDP_MATRIX_DATES;

 

13. When ever you run the engine on Linux, if the engine has hang, then you should review this metalink document to solve the problem

Unable to start the Engine on Linux server Note 1325321.1

14. Whenever you get this error message

WARNING Retrying bulk insert for file: sqlldr due to communication Error: 256

There was no executable permissions for $ENGINE_ROOT/lib/sqlldr file, so you need to give the full or executable permissions for this file.

15. Whenever EngineStarters become stacked for some reason if corresponding engines are killed brutally. So after killing engine with "kill -9" you need to restart the EngineStarter.

List Of High Priority Patches For Oracle Demantra Including EBS, Siebel and E1 Integrations (Doc ID 470574.1)

 

APPLIES TO:

Oracle Demantra Real-Time Sales and Operations Planning - Version 7.0.2 and later
Oracle Demand Planning - Version 11.5.10 to 12.0.3 [Release 11.5 to 12]
Oracle Demantra Deduction and Settlement Management - Version 7.0.2 and later
Oracle Demantra Advanced Forecasting and Demand Modeling - Version 7.0.2 and later
Oracle Demantra Predictive Trade Planning - Version 7.0.2 to 7.2 [Release 7 to 7.2]
Information in this document applies to any platform.

PURPOSE

!!!PLEASE READ NOTE 788671.1 AS THERE IS AN IMPORTANT ALERT THAT DEALS WITH DEMANTRA CUMULATIVE PATCH AND BASE VERSION INSTALLATIONS!!!

This document is intended to provide the latest rollup patches available for Demantra as well as general patch number information for EBS/Siebel/E1 to/from Demantra integrations.  There are other reference note links to topics that would be beneficial to the customer and Oracle personnel.  Please note that all Rollup patches are cumulative unless otherwise specified.

It should be remembered that when applying a Demantra patch that if you are using a WAR file to deploy the application to the web server (common, but not limited, to those clients using Oracle Application  Server (OAS), WebLogic, and Websphere) that after the patch is installed on the centralized box that the WAR file needs be recreated and redeployed.  This is so that the changes that the patch made to the web application files (ex. java, .jsp, classes, etc.) are propagated to the web server. 

 In addition, if the patch you are applying contained changes to the Demantra Engine executables (check the Patch ReadMe), and you are utilizing a multi-machine distributed engine, then follow Note 751772.1 as to how to propagate those changes to these distributed machines.

 

SCOPE

The intended audiences include Oracle Support, Oracle Partners, Oracle Development, Oracle Sales, Oracle Consulting and Oracle Customers

DETAILS

This Document was last updated on 17-MARCH-2021

Demantra 12.2.x:

From 12.2.x onward compatibility between Demantra VCP is as follows:

Demantra 12.2.x will work with VCP 12.2.x, same version for both demantra and VCP

Demantra 12.2.x individual versions compatibly as follows:

Demantra 12.2.10 will only work with VCP 12.2.10

  • Demantra patches for 12.2.10  see Note 2714991.1
  • For VCP Patching see Note 1361221.1  - Known Issues for 12.2.10 - R12.SCP_PF.C.delta.11
  • Demantra 12.2.10 and VCP 12.2.10 will work with
    • EBS 12.1.3 
    • EBS 12.2.10

Demantra 12.2.9 will only work with VCP 12.2.9

  • Demantra patches for 12.2.9  see Note 2652288.1
  • For VCP Patching see Note 1361221.1 - Known Issues for 12.2.9 - R12.SCP_PF.C.delta.10
  • Demantra 12.2.9 and VCP 12.2.9 will work with
    • EBS 12.1.3 (EBS Source on must be on VCP 12.1.3.9.2)
    • EBS 12.2.9

Demantra 12.2.8 will only work with VCP 12.2.8

  • Demantra patches for 12.2.8 see Note 2482698.1
  • For VCP Patching see Note 1361221.1 - Known Issues for 12.2.8 - R12.SCP_PF.C.delta.9
  • Demantra 12.2.8 and VCP 12.2.8 will work with
    • EBS 12.1.3 (EBS Source on must be on VCP 12.1.3.9.2)
    • EBS 12.2.8

Demantra requires 12.2.7.1 which works with VCP 12.2.7.1

  • Demantra patches for 12.2.7.1 see Note 2413191.1
  • For VCP Patching see Note 1361221.1 - Known Issues for 12.2.7 - R12.SCP_PF.C.delta.8
  • Demantra 12.2.7.1 and VCP 12.2.7.1 will work with
    • EBS 12.1.3 (EBS Source on must be on VCP 12.1.3.9.2)
    • EBS 12.2.4
    • EBS 12.2.5
    • EBS 12.2.6 
    • EBS 12.2.7.1

Demantra requires 12.2.6.3 which works with VCP 12.2.6.3

  • Demantra patches for 12.2.6.3 see Note 2392888.1
  • For VCP Patching see Note 1361221.1 - Known Issues for 12.2.6 - R12.SCP_PF.C.delta.7
  • Demantra 12.2.6 and VCP 12.2.6 will work with
    • EBS 12.1.3 (EBS Source on must be on VCP 12.1.3.9.2)
    • EBS 12.2.4
    • EBS 12.2.5 
    • EBS 12.2.6
  • Demantra 12.2.6 will work with JD Edwards EnterpriseOne 9.1 and 9.2.

Demantra requires 12.2.5.1 which works with VCP 12.2.5.1

  • Demantra patches for 12.2.5.1 see Note 2069281.1 
  • For VCP Patching see Note 1361221.1 - Known Issues for 12.2.5 - R12.SCP_PF.C.delta.6
  • Demantra 12.2.5.1 and VCP 12.2.5.1 will work with
    • EBS 12.1.3 with VCP Cum Patch 12.1.3.9.1 OR 12.1.3.9.2
    • EBS 12.2.4
    • EBS 12.2.5
  • Demantra 12.2.5.1 will work with JD Edwards EnterpriseOne 9.1 and 9.2.

Demantra requires 12.2.4.1 which works with VCP 12.2.4.1

  • Demantra patches for 12.2.4.1 see Note 1342064.1
  • For VCP Patching see Note 1361221.1 - Known Issues for 12.2.4.1
  • Demantra 12.2.4.1 and VCP 12.2.4.1 will work with
    • EBS 12.1.3 with VCP Cum Patch 12.1.3.9.1 OR 12.1.3.9.2
    • EBS 12.2.4
  • Demantra 12.2.4.1 will work with JD Edwards EnterpriseOne 9.1 using the AIA 11.4 for the Value Chain Planning Base Integration Pack.

Demantra 12.2.3 will  work with VCP 12.2.3.

  • Demantra patches for 12.2.3 see Note 1342064.1
  • Demantra 12.2.3 and VCP 12.2.3 will work with
    • EBS 12.2.3
  • Demantra 12.2.3 will work with JD Edwards EnterpriseOne 9.1 using the  AIA 11.4 for the Value Chain Planning Base Integration Pack.

Demantra 12.2.2 will work with VCP 12.2.2.

  • Demantra patches for 12.2.2 see Note 1342064.1
  • Demantra 12.2.2 and VCP 12.2.2 will work with
    • EBS 12.2.2

 

I. Demantra Version 7.3.1

a) 7.3.1.5 -  Install PATCH 17850720 - from INSTALL Main Release Patches & How to Upgrade Note. - -Document: 1342064.1

---- VCP 12.1.3.9 is certified ONLY with Demantra Release 7.3.1.5.

-- In 12.2 Demantra/VCP connection to 11i EBS source will no longer be supported. 12.2 VCP supports only EBS 12.1 and EBS 12.2. So customer on EBS 11i will stay in 7.3.1.x line until they upgrade their EBS instance to 12.1 or 12.2.
-- Specific EBS/VCP (formerly ASCP) - Demantra Integration patches go away beginning in VCP 12.1.1 and higher; Please note that beginning with the release of VCP (the name previously given to ASCP) v12.1.1 and higher that no separate EBS/VCP - Demantra patches (ex. Bug 8551184) required. Customer should still run 'Update Synonyms' For Demantra 7.3.1

b) 7315 CDP - Install Patch 17248308 / Focuses on providing a new solution In-Memory Consumption Driven Planning. IMCDP provides the ability and scale to load support daily store level forecasting, safety stock generation and initialization of replenishment orders
Please note that customers upgrading to 7.3.1.5 will be unable to upgrade to currently available 12.2.1 and future release 12.2.2. A supported 12.2.X release for upgrade will be available in the future. Customers who believe they will upgrade to 12.2 branch in the near future should not implement using or upgrade to 7.3.1.5

1. 12.1.x VCP instance -
        The minimum VCP patch level required - 10192383:R12.SCP_PF.B - VCP 12.1.3.2 PATCH.  However it is recommended that you get to the latest VCP/ASCP patch for 12.1.3 that's shown in Note 746824.1      
        This means that, if you have a centralized environment, it should only be 12.1.3 or higher in order for Demantra to work.
        Note
        - Service Parts Forecasting (SPF) is only supported for 12.1 (source/destination). For 11510 or 12.0.6 source, SPF is not supported.
        - VCP 12.1.3.2 continues to support 7301, 730(without CTO), 720X 

  1.1 Supported SOURCE Instances for  12.1.x VCP instance -
  i) 12.1.x - 10192383:R12.SCP_PF.B - VCP 12.1.3.2 PATCH

  ii) 12.0.6 - (This scenario is not certified by QA. But we do have a patch available)
    1. Patch 9830310 :R12.MSD.A - R12 EBS-DEMANTRA INTEGRATION RUP#09
    2. Patch 11058441:R12.MSD.A - 12.0.6 COMPATIBILITY PATCH FOR VCP 12.1.3.2 (Controlled Release)

  iii) 11.5.10 CU2 -
      a. Patch 9072397 - DEMANTRA INTEGRATION RUP#07 PATCH FOR 11.5.10
      b. Patch 11058665 - 11.5.10 CU2 COMPATIBILITY PATCH FOR VCP 12.1.3.2

      Note : Patches 9072397 and 11058665 are mandatory patches for 11510CU2 source, if customer is upgrading his 12.1 instance to VCP 12.1.3.2 or above, irrespective of the Demantra version.

2. 12.0.X VCP instance - Not Supported.
3. 11510CU2 VCP instance - Not Supported.

-- Attention: Oracle Value Chain Planning (VCP) Release 12.1.3.8 can only be applied to Oracle EBS Release 12.1.3 or 12.1.2. VCP 12.1.3.8 can be integrated with Demantra Release 7.3.1.4.

Official Note on VCP 11.5.10.2

The VCP policy is to have customers stay with EBS 11i but upgrade their VCP install to the level compatible with Demantra. So for 7314 they would work with the following configuration:    EBS 11.5.10  (11i),     VCP 12.1.3.8    Demantra 7.3.1.4
Most customers are unwilling to upgrade their EBS due to customizations, users and overall effort required, but upgrading their VCP apps is easier and is supported.

The customers leave their 11i source system as it is now and installs a separate VCP 12.1 instance which will collect data from 11.5.10.2. This is a fully supported configuration and allows them to connect Demantra 7.3.1.4 to EBS 11i10.
They don't even need to use any VCP apps other than Demantra, but the data flows through the 12.1 VCP instance into Demantra 7.3.1.4. This is the certified configuration for 11i and Demantra 7314, so we advise customers to this.
The additional benefit the customers get is the ability to bring their VCP apps forward without impacting their other EBS applications.

 

II. Important Reference Notes

            Note 443969.1 Oracle Demantra Demand Management Documentation Library
           Note 434991.1 EBS-Demantra Integration Installation Overview and Diagram

III. Latest Demantra Version for SQL Server Databases

The latest Demantra Version that supports Microsoft SQL Server Databases is v7.2.0.1.1 Patch 8811761.   Note that the resulting file that is downloaded from this link should be p8811761_720_WINNT.zip. After installing that version and/or upgrading from earlier Demantra versions then please also apply Cumulative Patch 8823379
NOTE:1319331.1 Latest Supported Demantra Release For Sql Server and Installation

 

 

REFERENCES

NOTE:434991.1 - EBS-Demantra Integration Installation Overview and Diagram
NOTE:223026.1 - List of High Priority Patches for the Value Chain Planning (aka APS - Advanced Planning & Scheduling) Applications
NOTE:727237.1 - What patches are required to integrate Demantra with EBS?
NOTE:751772.1 - Distributed Engine Windows and Linux Deploying Multiple Engines Howto and Troubleshoot
NOTE:1361221.1 - Release 12.2.x Oracle Value Chain Planning Installation Notes - Known Issues, FAQ and Latest Patch Information
NOTE:443969.1 - Oracle Demantra: Documentation, Release Notes, Transfer of Information (TOI), and Training
NOTE:1969589.1 - Is Demantra 7.3.0.2 supported on a distributed installation of EBS 12.1.3.9 and VCP 12.1.3.9
NOTE:746824.1 - 12.1.x - Latest Patches and Installation Requirements for Value Chain Planning (aka APS Advanced Planning & Scheduling)
NOTE:1319331.1 - Latest Supported Demantra Release For Sql Server and Installation
NOTE:865764.1 - Patches for Demantra version 7.2.0
NOTE:421097.1 - R12.0 - Latest Patches and Critical Information for VCP - Value Chain Planning (aka APS - Advanced Planning and Scheduling)
 

Was this document helpful?

 
   
 

Document Details

 
Email link to this documentOpen document in new windowPrintable Page
BULLETIN
PUBLISHED
Mar 17, 2020
Mar 23, 2021
   
 

Related Products

 
Oracle Demantra Real-Time Sales and Operations Planning
Oracle Demand Planning
Oracle Demantra Deduction and Settlement Management
Oracle Demantra Advanced Forecasting and Demand Modeling
Oracle Demantra Predictive Trade Planning
Show More
   
Didn't find what you are looking for?

Friday, October 1, 2021

Is It Safe To Lock The Listed Applications Accounts? (Doc ID 1357196.1)

 

APPLIES TO:

Oracle Application Object Library - Version 11.5.0 to 12.2 [Release 11.5 to 12.2]
Information in this document applies to any platform.

GOAL

Is it safe to lock/ deactivate the listed users?

APPLSYSPUB username OPEN
DMSYS username OPEN
JMF username OPEN
MTH username OPEN
QPR username OPEN
DDR username OPEN
INL username OPEN
IBW username OPEN
DPP username OPEN
RRS username OPEN
ITA username OPEN
FTP username OPEN
PFT username OPEN
GMO username OPEN
DNA username OPEN
IPM username OPEN
IZU username OPEN
SYSMAN username OPEN
MGMT_VIEW username OPEN
CTXSYS username OPEN
DBSNMP username OPEN
DMSYS username OPEN
OUTLN username OPEN
SYSTEM username OPEN
WH username OPEN


SOLUTION

Actually, it is each module's responsibility to provide the mechanism to de-activate obsolete products!

Here follows a generic answer and some guidelines:

-The applications schemas are listed in FND_ORACLE_USERID table. Any schema not listed here do not belong to applications.

-An applications schema should not be deactivated unless you are sure that the related product is obsoleted and not in use .
You should also ensure that no other product is depended on it and share its objects.

-For products not being obsoleted, there is no released document and no product team that can answer this question.
The products within eBS may share objects from each other and there is no given answer for which product share and is depended on which other products.
In general it is not recommended to lock any account belonging to eBS, due to advanced object relationship, even when using only few products e.g. GL and AP.

-Oracle does not remove the schema for the obsoleted products, considering that the customers may have custom codes based on them.

-APPLSYSPUB is the generic internal application user for login functionality and should not be deactivated.
Please see Note 403537.1, Revoke unnecessary grants GIVEN to APPLSYSPUB

-DMSYS:
This is an RDBMS related schema not related to applications.
From Bug 12388178:
In Oracle Database 11g, the DMSYS schema is no longer used. The Data Mining option is installed in the SYS schema.

-FPT: Obsolete, documented in Note 743513.1. Handling on Note 403537.1

-For other schemas listed here please execute following script to see the product behind.
The related product team should be able to tell you if it is safe or not to de-activate these accounts.

SQL> select ORACLE_USERNAME, DESCRIPTION from FND_ORACLE_USERID
where ORACLE_USERNAME=upper('&username');

 

REFERENCES

NOTE:403537.1 - Secure Configuration for Oracle E-Business Suite Release 12.1

Tuesday, September 21, 2021

OCI Listener timeout

 The default timeout values are:

  • 300 seconds for TCP listeners.

  • 60 seconds for HTTP listeners.

maximum timeout value is 7200 seconds.

XML Publisher Report Bursting Program taking time to start

 Customer Applied solution from:

XML Publisher Report Bursting Program (XDOBURSTREP) Performance Poor While Initializing ( Doc ID 2300674.1 )
SOLUTION: Replace random with urandom by modifying the Concurrent Program Define Execution Option
--All 5 reports completed in acceptable period of time.

This solution may work to resolve the issue.
However customer should still work on cleaning the out and log files as this situation will result in further issues.
Customer will discuss internally to decide if the purging / moving of the out and log (FSS directory) will occur tonight or
be put on hold until the weekend


-------------------- ACTION PLAN DETAILS BELOW---------------------

Customer Applied solution from:
XML Publisher Report Bursting Program (XDOBURSTREP) Performance Poor While Initializing ( Doc ID 2300674.1 )
SOLUTION: Replace random with urandom by modifying the Concurrent Program Define Execution Option
--All 5 reports completed in acceptable period of time.

(1) Responsibility: System Administrator
(2) Navigate to: Concurrent > Program > Define
(3) Query report
(4) Under "Executable" it shows Name = XDODTEXE
and (Options = NULL) or (Options = -Xms512M -Xmx512M)
(5) Update Options to = -Xms512M -Xmx512M -Djava.security.egd=file:/dev/./urandom
* note the space after -Xmx512M and before -Djava.security
(6) Save.
(7) Test using report that was updated



Action Plan From Here:
====================
Customer Actions:
1. Customer working on cleaning the out and log
Per Doc ID 2603009.1 - Concurrent Processing R12.2 : Too Many Concurrent Requests In Pending Status After Migrating To OCI
-- Log and Out files from concurrent processing in FSS directory needs to be restricted to 50000 records only

* Customer discussing internally to decide if the purging / moving of the out and log (FSS directory) will occur tonight or
be put on hold until the weekend 


2. If performance is still unacceptable, please provide the AWR and analyzer, per earlier action plan as follows
2.1> Generate AWR reports for intervals 20-Sep 13:15:to 13:30 , 13:30 to 13:45 . Generate instance level reports from all RAC instances using awrrpt.sql and addmrpt.sql scripts
2.2> Also run analyzer to check settings :
EBS Database Performance and Statistics Analyzer( Doc ID 2126712.1 )
NOTE: It is important that you review saved output file before uploading.
If you ran the Analyzer as a Concurrent Program, make sure to choose 'Web Page, HTML only' for the 'Save as type'.
Do not save as 'Webpage, complete (*.htm,*.html)' as it will be rejected when uploaded to Support. This applies to all Web browsers.

Database Options/Management Packs Usage Reporting for Oracle Databases 11.2 and later (Doc ID 1317265.1)

  Database Options/Management Packs Usage Report You can determine whether an option is currently in use in a database by running options_pa...