Wednesday Jun 04, 2014

Demantra New Cumulative Patch Covering EP_LOAD, INSERT_UNITS, PROPORT , ROLLING_UPDATES and CHAINING

Hello Demantra Customers!  There is a new accumulative patch available that addresses issues in the following areas; DATA_MODEL METADATA package, EP_LOAD, INSERT_UNITS, PROPORT , ROLLING_UPDATES and CHAINING.  This patch is meant for versions 7.3.1.0 to 7.3.1.5.  Please review the readme for patch 18048597.

Wednesday May 21, 2014

Topical Procedural Demantra Debugging Using Log Files

Demantra Debugging Using Log Files


Default log location is the Demantra_root/Collaborator/virtual_directory/portal/logs directory.
Review the comments in the Demantra_root/Collaborator/virtual_directory/portal/conf/logconf.lcf  file to specify this log file information:
- Name and location
- Maximum size of the log file
- Number to keep
- Log categories and log level

You can also set log levels at runtime with the following URL:
http://Demantra_root/Collaborator/virtual_directory /admin/loggerManager.jsp

 

Application server memory configuration (-Xmx)

Web Application troubleshooting:
- Demantra Web application includes 2 components:
  Application Server
  – Demantra Web application deployment inside a Web server.

  Client
  – User side browser and resources (CPU, Memory) running SUN Java Plug-in.

  They are connected by a Network (LAN, WAN...).
  SQL*Net log

  For better troubleshooting we need to understand where we have a problem is it on the Server side/Client side / Both ?


If Application out of memory errors:
- Identify where the problem is by using logs:
  Collaborator log, application server side log.   Plug-in log, Client side log.


Server side issues:
- Heap dump from the webserver
- Thread dump from the Webserver, in case of application freeze or slow down
- Application server memory configuration ( -Xmx)
- Count of Level members, need level member caching?


Client side issues:
- Heap dump from the Java plug-in
- Thread dump from the Java plug-in
- Plug-in memory configuration ( -Xmx)


When having installation errors there are a few files that can be analyzed:
• Installer log
• Screenshots of the selections in the different Installer panels.
• Review db_audit_log table for object changes made by the upgrade DB_Exception_Log table


Data Model: When having data model errors there are few files that can be analyzed:
• An Export of the Data model
• Review db_audit_log table for object changes made by the upgrade.
• LOG_DATA_MODEL table (an automatic LOG_IT log).


Data Loading
– Ep_Load, Ep_load Errors:
• Enable LOG_IT process on relevant Demantra stored procedures as defined in LOG_IT_PARAMS table
• DB_Exception_Log.


Ep_Load performance:
• Count of data from the staging tables.
• DB_Params table
  – Ep_Load performance related parameters
• Execute “Call_DM_Build_Procedures” after changing parallelization parameters in DB_Params
• DB HW definitions.
• System Memory Disk IO and CPU Utilization monitoring
Either system performance monitor or Linux top events
• AWR /ADDM reports.


Data Loading, Integration:

Integration Errors:
• Collaborator & Integration log (Enable sql logging: appserver.sql, appserver.update.sql)
• Concurrent request logs (collaborator.login.user)
• apscheck.sql (Note:246150.1)


Integration Performance:
• Count of data from the staging tables.
• APS_Params
  – Integration Interface related parameters
• DB HW definitions.
• system memory disk IO and CPU utilization monitoring
  - either system performance monitor or Linux top events.
• AWR/ADDM reports.


DB deadlock/ internal database error:
• Collaborator Log
• Database \ udump logs (USER_DUMP_DEST specifies the pathname for a directory where the DB server will write debugging trace files on behalf of a user process.)
• Enable LOG_IT process on selected Demantra stored procedures as defined in LOG_IT_Params table.


Web Application troubleshooting:
• Demantra Web application includes 2 components:
• Application Server


Demantra Web application deployment inside a Web server.
• Client
  – User side browser and resources (CPU, Memory) running SUN Java Plug-in.
• They are connected by a Network (LAN, WAN...).
• For better troubleshooting we need to understand where we have a problem is it on the Server side/Client side / Both ?


Application out of memory errors:
• Identify where the problem is by using logs:
• Collaborator log
  – server side log.
• Plug-in log
  – Client side log.
• Server side issues:
• Heap dump from the webserver
• Thread dump from the Webserver (in case of application freeze or slow down)
• Application server memory configuration (-Xmx)
• Count of Level members (need level member caching?)
• Client side issues:
• Heap dump from the Java plug-in.
• Thread dump from the Java plug-in
• Plug-in memory configuration (-Xmx)


WS performance and errors:
• Identify where the problem is:
• Server side
  – AWR /ADDM reports, DB side CPU and Memory.  Application server CPU and configuration, APS_PARAMS relevant parameters.
• Client side
  - CPU utilization (and for how long).
• Server side issues:
• Demantra Index Advisor report.
• Thread dump (in case of application freeze or slow down).
• System Memory Disk IO and CPU Utilization monitoring
  - either system performance monitor or Linux top events.
• DB HW definitions.
• Number of concurrent users at the time (concurrent user log)
- Also see Level Member Caching Purpose Performance Guidance (Doc ID 1627689.1)
- Also see Oracle Demantra Worksheets Caching, Details how the Caching Functionality can be Leveraged to Potentially Reduce Performance (Doc ID 1627652.1)

 

Client side issues:
• Plug-in –Xmx setting
• WS wizard panels screen shots.
• Client side log
  – If requested (Number of combinations in the WS).


Engine errors:
Always provide a full Engine log (manager and engine) with relevant logging option.
• DB errors:
• Engine log with Sql logging
  – depends on where the DB error is Engine manager or engine2k.


Processor error:
• Engine log with DebugPro logging’ groups 100/110
• Engine Out of memory errors:
• No of Tasks
• Count of Active Combinations (Select Count(1) from MDP_Matrix where prediction_status = 1)
• Engine not running:
• On Linux
  – Application server log
• Engine performance:
• AWR report
• Check whether CPU Hyper threading enabled on Engine servers
  – Disable if its enabled
• Engine Blades/Server + DB HW definitions.
• DB/Engine Blades Memory Disk IO and CPU Utilization Monitoring
  - Either system performance monitor or Linux top events.
• For more information check Oracle Support note 800030.1 "Demantra Engine Troubleshooting” Presentation (April 6th, 2011)


Configure auditing capabilities for BM configuration changes:
• This is a customization enhancement introduced by DEV application team in a white paper (“Implementing Demantra Audit log”)
  - Configuring an Audit Log in Demantra Using Database Triggers (Doc ID 1629974.1)
    * Currently captures Inserts/ Updates on Sessions/Computed_fields tables by a trigger based process
• The mechanism and idea can easily be enhanced for further Metadata audit opportunities
• Difference from BAL diff
  – This mechanism captures all the changes, not just how the latest change differs between schemas
• The logs are kept in a separate table (AUDIT_LOG ), so no impact on the out of the box schema.
• AUDIT_LOG table includes the following information (columns):
  - log_date
  - session_id
  - os_user
  - host_name
  - module
  - user_id
  - object_type
  - object_name
  - old_value
  - new_value
  - Message

Monday May 05, 2014

New Demantra Webcast 7-May-21014. This is Part II and very comprehensive!

Do you want to gain a solid understanding of Demantra Logs?  Perhaps you would like to enhance your knowledge of Demantra logs. 

The May webcast:

  • Demantra Logs by Procedure.
  • Where are They?
  • When are They Updated? 

Topics include

  • Install
  • Workflow
  • Member Management and Chaining Logs
  • Procedures and Logs, plus more! 

This webcast promises to deliver at least one Demantra log fact that you did not previously know.
Please see My Oracle Support (MOS) note 800030.1, Demantra Solutions Advisor Webcast Calendar And Archive.

Monday Mar 17, 2014

Demantra 16 Newly Published White Papers from PMO and Proactive Support

Hello Everyone!   There are 16 newly published white papers from Demantra PMO and Proactive Services.   Take a look.  As always, email Jeffery.goulette@oracle.com

if you have questions.    Regards! 

  1. Configuring an Audit Log in Demantra Using Database Triggers, Doc ID 1629974.1
  2. Demantra Configure to Order (CTO) Integration EBS Model BOM Example How To, Doc ID 1630040.1
  3. Demantra APIs to Facilitate Integration with External - Third Party Source Systems, Doc ID 1630505.1
  4. Demantra Indirect Modeling, Lift Decomposition, Definitions and Issues, Doc ID 1630545.1
  5. Demantra Indirect Customer Modeling, Customer Scenarios, Modeling Approaches, Key Recommendations and More! Doc ID 1630604.1
  6. Demantra PTP – Shipment vs. Consumption Forecasting White Paper, Doc ID 1630628.1
  7. REPLACEMENT OF APS SIZER with VALUE CHAIN PLANNING REFERENCE SIZING TOOL (RAS), Doc ID 1630684.1
  8. Troubleshooting Strategy and Processes that Execute Enormous data sets in Demantra, Doc ID 1634925.1
  9. Oracle Demantra Database Best Practices White Paper, Doc ID 1627586.1
  10. Oracle Demantra Customizations and BAL Upgrade White Paper, Doc ID 1627590.1
  11. Oracle Demantra New Product Introduction (NPI) - Pooled Time Series (PTS), Doc ID 1627623.1
  12. Demantra Platform or Application Upgrading - Program Manager Recommendations, Doc ID 1627664.1
  13. Oracle Demantra Worksheets Caching, Details how the Caching Functionality can be Leveraged to Potentially Reduce Performance, Doc ID 1627652.1
  14. Level Member Caching Purpose Performance Guidance, Doc ID 1627689.1
  15. Oracle Demantra BLE Mechanism Explanation and Details, Doc ID 1627716.1
  16. Demantra Integration Real Time Sales & Operations Planning, Advanced Supply Chain Planning and Strategic Network Optimization, 7.3.1.4 and Higher (Doc ID 1636614.1)

Wednesday Mar 12, 2014

Troubleshooting Strategy and Processes that Execute Enormous data sets in Demantra

Hello Demantra Customers!   There is a new white paper that discusses large data set loading.

See MOS Note 1634925.1

Recently we have encountered a few scenarios where customers tried to process huge amounts of data within a Demantra process.
Examples:

  • Customer wanted to load over 50M records via EP_LOAD process on weekly bases.
  • Customer wanted to process millions of rows via BLE process on daily bases.
  • Customer wanted to load via integration interface 40M rows on weekly bases.


In all of the above the customer complained about the system inability to process the amount of data, either being too slow or it simply could not be completed at all meaning the process erred out.
In all of the above examples an escalated defect was logged, and development worked troubleshooting the problem.

An additional common theme between all the above examples and many more is that there was no real need to have a product fix although performance improvement opportunities may have been identified, they were not the final solution that addressed the problem.
What helped was understanding that there is no real need to process all the data and recognizing the data that really needed to be loaded.  The data could have been loaded in a more efficient way using some best practices and creative thinking.

The scope of this document is to provide some guidance how to troubleshoot such customer situations.
The document will focus on three main areas:

  • Learning and understanding the business needs
  • Understanding the actual data that needs to be loaded, understand the gap between this number and the number of rows that the customer actually tries to load.
  • Provide some best practices that can help the customer work with the data efficiently.


This document will not deal with the initial Data load processes although some of the best practices can be adopted for such situations as well.
We will illustrate the concepts in this document using three real life examples of service requests and/or defects that were logged on behalf of the customer.

 

Friday Feb 28, 2014

Proactive Support and Oracle Demantra PMO Deliver 13 Excellent Functional and Technical White Papers + Announcement

Hello!   Working together, Oracle Proactive Support and the Demantra PMO organization deliver 13 excellent white papers and a new sizer announcement.   These white papers touch some difficult functional areas, NPI, BLE, BAL, modeling techniques, APIs, CTO integration plus more!   Take a look, you might find some valuable ideas.

Configuring an Audit Log in Demantra Using Database Triggers (Doc ID 1629974.1)
Demantra Configure to Order (CTO) Integration EBS Model BOM Example How To (Doc ID 1630040.1)
Demantra APIs to Facilitate Integration with External - Third Party Source Systems (Doc ID 1630505.1)
Demantra Indirect Modeling, Lift Decomposition, Definitions and Issues (Doc ID 1630545.1)
Demantra Indirect Customer Modeling, Customer Scenarios, Modeling Approaches, Key Recommendations and More! (Doc ID 1630604.1)
Demantra PTP – Shipment vs. Consumption Forecasting White Paper (Doc ID 1630628.1)
Oracle Demantra Database Best Practices White Paper (Doc ID 1627586.1)
Oracle Demantra Customizations and BAL Upgrade White Paper (Doc ID 1627590.1)
Oracle Demantra New Product Introduction (NPI) - Pooled Time Series (PTS) (Doc ID 1627623.1)
Demantra Platform or Application Upgrading - Program Manager Recommendations (Doc ID 1627664.1)
Oracle Demantra Worksheets Caching, Details how the Caching Functionality can be Leveraged to Potentially Reduce Performance (Doc ID 1627652.1)
Level Member Caching Purpose Performance Guidance (Doc ID 1627689.1)
Oracle Demantra BLE Mechanism Explanation and Details (Doc ID 1627716.1)

Announcement:
REPLACEMENT OF APS SIZER with VALUE CHAIN PLANNING REFERENCE SIZING TOOL (RAS) (Doc ID 1630684.1)

REPLACEMENT OF APS SIZER with VALUE CHAIN PLANNING REFERENCE SIZING TOOL (RAS)

The Value Chain Planning - Reference Sizing Tool (RAS) provides Capacity & Deployment planning for the Value Chain Planning customers.  It is part of your early sales cycle to qualify, scope and budget your opportunity.  It provides a System Sizing for Oracle Software on Oracle Hardware as well as competitor hardware.  The tool provides guidelines on what the customer should consider for deployment of Value Chain Planning, as well as a comparison to Oracle hardware.  The tool will advise on suitable hardware and software configuration based on the user responses to a series of questions related to the customer requirements.  The more accurate the input, the more accurate the results will be.

The output reports can be used as a sizing estimate.  Most typical scenario is for a System Integrator (SI) to provide the inputs based on the customer’s implementation strategy.  

With a unified methodology across all Oracle software and hardware, RAS supports greenfield as well as consolidation or hardware refresh opportunities. The extremely quick turnover and what-if scenarios enables you to help guide you through the sales-implementation cycle.  Results displayed are estimates based on benchmark results produced by Oracle and best practices gained over the years from customer support and feedback.

For training, to download or to read more, see MOS Note: REPLACEMENT OF APS SIZER with VALUE CHAIN PLANNING REFERENCE SIZING TOOL (RAS) (Doc ID 1630684.1)

Monday Feb 24, 2014

Announcement: Oracle Demantra 12.2.3 Available

We are excited to announce Oracle Demantra 12.2.3 is now available for new and existing customers.  All customers who are not incorporating Demantra with other VCP products are welcome to upgrade without any restrictions.  Customers who are using Demantra in conjunction with VCP products will need to upgrade VCP to 12.2.3.
Demantra 12.2.3 encompasses the same functional scope as Demantra 12.2.2 with additional security and functional bug fixes.

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.3 will only work with VCP 12.2.3.
Demantra 12.2.3 and VCP 12.2.3 will work with EBS 12.1.3 or EBS 12.2.3.
Please review the release readme and all 12.2.3 documentation carefully to determine content details for this patch. You can also find documentation in the Demantra Documentation Library on My Oracle Support (note 443969.1).

The release is currently available on My Oracle Support (formerly known as Metalink) as Patch 17921238.
Release will be available from e-delivery in a few weeks.

It is recommended for all customers who are on 12.2.1 or 12.2.2 to upgrade to 12.2.3 at earliest convenience.   Please do not upgrade to 12.2.2 and then 12.2.3.

Wednesday Feb 19, 2014

Demantra Performance and Setup Analyzer V1, MOS Doc ID 1618885.1

The Demantra Setup and Performance Analyzer is a Self-Service Health-Check script which reviews the overall footprint, analyzes the current configurations and settings for the environment providing feedback and recommendations on Best Practices.  This is a non-invasive script which provides recommended actions to be performed on the instance it was run on.  For production instances, always apply any changes to a recent clone to ensure an expected outcome.  

Benefits:
  • Immediate Analysis and Output of your Demantra Environment
    • Reveals Current Environment
    • Delivers Known Recommendations and Solutions
    • Perform Sanity Checks for Known Issues
  • Easy to add Tool for regular Maintenance
  • Execute Analysis anytime to compare current environment 
Audience:
  • DBA's / System Administrator's should run the script and review the output
  • Output usually will be reviewed by technical application DBA or super user
  • This script was designed for 7.3.1 and later.

Where to Run the Script & How to fix Items Identified:

You may run the script on a Production environment as it's non-invasive.  We recommend fixing items identified from the output first in a clone of production to test/verify the expected outcome.  Visit Doc ID 1618885.1 to download the script and view a complete output example. 

Wednesday Feb 12, 2014

Demantra 12.2.2 Upgrade WARNING

We have a MOS note for upgrade problems when upgrading to 12.2.2.

Oracle Demantra Platform Upgrade to 12.2.2 Known Issues Worksheet Performance Calendar Excel ORA-0179 ORA-06512 ORA-31003 java.lang.NullPointerException (Doc ID 1602288.1)

- DO NOT upgrade from 7.3.x, 12.2.0 or 12.2.1 to 12.2.2.

- DO NOT run the 12.2.2 upgrade twice.

Currently there is a bug in the 12.2.2 upgrade that can cause serious corruption in those cases.  Customers should instead upgrade from 7.3.x, 12.2.0 or 12.2.1 to 12.2.3.
I do not know when/if we will fix this issue.  Right now 12.2.2 cannot be downloaded.

Note:  that there is already a section in that MOS note detailing a work-around for a different problem when upgrading from 12.2.1 to 12.2.2.  The existence of that work-around might imply that it is ok to do the upgrade -- but it is NOT ok to do that upgrade

Friday Jan 03, 2014

Security Enhancement for Demantra Engine on Linux Versions 7.3.1.4 and Earlier

For added security please remove the existing file OCCITest from the $ENGINE_ROOT/lib directory as it is not needed for day to day activities.
It is used during detailed logging.  Alternatively, you can apply Patch 16970868, which is compatible with Demantra Linux versions 7.3.1.x.

To Comment, See MOS Note 1611623.1

Friday Dec 20, 2013

Demantra Platform or Application Upgrading - Program Manager Recommendations

Hello Demantra Customers!  Are you planning on an upgrade?  Should you follow a platform or application upgrade path?  MyOracleSupport (MOS) Note 1609763.1 delivers high impact information from the Demantra Program Management Office (PMO).  Take a look, it will help you make an informed decision for your upgrade path.    Regards!   Jeff

Monday Dec 16, 2013

Demantra 12.2.3 Is Now Available!

Greetings!   Demantra 12.2.3 is now available via ARU 17048199, Bug 17921238

1. This release includes both a platform and application upgrade option. Please note the application upgrade installer option is available only to customers who have implemented the *standard* pre-configured applications (available from Demantra 7.1.1 onwards). You should choose the 'Platform Upgrade Only' option only if your implementation is highly customized. A platform-only upgrade will preserve custom configurations and enable new platform functionality. It will not introduce new application objects. Also note Demantra 7.2.1 customers should contact support prior to running an application upgrade, to get latest patch details for that release.

Please note the upgrade process may identify certain objects which have changed between your existing Demantra version (Demantra 7.1.1 or 7.2.0.2, for example) and the current release. This may be due to Oracle extensions in the latest release and/or due to customer extensions in their implementation. In a default upgrade mode, the current versions of these objects will be preserved during the upgrade process and, where there are conflicting definitions with the new Oracle version, we will create duplicate objects with a version suffix.

For example, if you extended the configuration of the workflow 'EBS Price List Download', the upgrade process will maintain this and introduce the Oracle standard workflow as 'EBS Price List Download_730'. In some cases, the original object may be suffixed with its version (for example, 'EBS Full Download_711'and the latest configuration will be 'EBS Full Download'). You will identify the latest version by either a suffix of the latest version, or by a sibling item with an earlier version stamp. You may then review the two and merge as appropriate. In the case of duplicate objects, it is recommended to use the latest version, preferably after removing the ‘_730’ suffix and merging any of your customizations into the latest version.

For Predictive Trade Planning customers, you will note that Promotion Type is no longer a level but instead a series, after application upgrade. This enables promotions to have multiple tactics per promotion, typically for different items or locations being promoted. While promotion type can now vary across different items, locations, it should not vary below the Lowest Promotional Level defined in the forecast tree.

If you are uncertain as to which upgrade option to choose, please contact support for guidance.


2.  If you already installed 12.2.1 or 12.2.2 (using the application upgrade or new installation), please do not choose the "platform and application upgrade" option. Instead, choose to perform only a "platform upgrade."

3.  If you are upgrading from a release that did not support Service Parts Forecasting (SPF) functionality and you want to use SPF, you MUST select the "Platform and Application Upgrade" option when running the Demantra Installer. SPF functionality will not work when upgrading from a pre-SPF supported release to 7.3.1 or later after a PLATFORM-only upgrade.

4. Customers who are on 7.3.1.5 or later who are using In-Memory Consumption Driven Planning (CDP) cannot upgrade to 12.2.3, as 12.2.3 does not support those enhancements.


A future release of the 12.2.x branch will include the 7.3.1.5 CDP enhancements, and upgrading from 7.3.1.5 or later will be supported at that time. Please contact Oracle Support for additional information.



For known issues and work arounds, see MOS note Demantra 12.2.3 Upgrade / Install Known Issues and Workarounds (Doc ID 1608474.1)

Wednesday Dec 04, 2013

Do you want to Review Demantra Patches Released in Real Time?

Hello Demantra Customers!   If you want to view a list of Demantra patches released in real time, review MOS note 1400207.2.   In the upper left you will see 'Real Time List of Released Patches'.  Regards!   Jeff

Tuesday Dec 03, 2013

Demantra Integration Interface Modifications via the Database

How does one do modifications to the Integration Interface from the database?  Is there a java class that can be used for this?

Looking to avoid logging into the Business Modeller to perform these modifications?

1) The interface tables in the database are a set of tables starting with "Transfer_", while transfer_query is the main one. There are separate tables for series, levels, filter etc.

2) I do not believe there is a Java class for this.

3) A Java servelet is triggered when an Integration interface is modified through business modeler so that an application server bounce is not required. This servelet is specific to integration interfaces only.

4) Any update to the "transfer_xxx" table(s) would need application server bounce.

As per my knowledge, logging into Business modeler and modifying is the recommended option, mainly where multiple tables in the database get updated.

About

This blog delivers the latest information regarding performance and install/upgrade. Comments welcome

Search

Archives
« April 2015
SunMonTueWedThuFriSat
   
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
  
       
Today