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 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, 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 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 CDP enhancements, and upgrading from 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.

Upgrading to 12.2.2? Do you want extra speed? Use a logon trigger for parallelism

When upgrading your Demantra application from an older version directly to 12.2.2, you can minimize the upgrade time.  You can force parallelism using a Logon trigger on the server.

   Creation of new Indexes on sales data can take long time.

   As part of the upgrade there is a script building a new set of indexes, one per engine profile, on each profile quantity_form expression.

   The creation of the index can take a long time on big data tables.

    - Remember to disable or drop that trigger when the upgrade has completed.

   The following trigger was created as SYS database user and tested successfully by creating DEMANTRA database user and logging in with it:

 CREATE OR REPLACE TRIGGER force_parallel_ddl_trg






END force_parallel_ddl_trg;


 Make sure to:

  1. Modify DEMANTRA to be the database schema name.
  2. drop it after it is not needed anymore using the foillowing:

 DROP TRIGGER force_parallel_ddl_trg;

Monday Nov 25, 2013

New Demantra Version - REPLACES - Existing


A new version of Demantra has been released and we want to ensure that all customers/partners who are using uptake it.

This version is meant to replace the existing some of you may have installed.

Regards!  Jeff


Thursday Nov 21, 2013

Upgrading to Demantra 12.2.2? There are known Issues and Fixes

When upgrading your Demantra application from an older version directly to 12.2.2 there are some issues of which you need to be aware.
- You are upgrading to Oracle Demantra 12.2.2
- ORA errors, Excel missing cut/paste data, performance issues, Notes, Calendar and other known upgrade issues.

See MOS note:

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)

Tuesday Nov 19, 2013

Oracle Demantra Gathering Statistics on Large Partitioned Tables in 11gR2

Hello!   Have you implemented partitions on a large Demantra table?  Are you using RDBMS version 11gR2?  Then consider implementing incremental statistics.

For all 11gr2 environments with large partitioned or subpartitioned objects turn on incremental statistics using this command:

exec dbms_stats.set_table_prefs('OWNER','TABLE','INCREMENTAL','TRUE');

Once this is set for any given table we should gather statistics on that table using the normal tool (fnd_stats in ebs or dbms_stats elsewhere). This first gather after turning it on will take longer than previous analyzes. Then going forward we will see the following :

1 – the normal dbms_stats (or fnd_stats) will only gather statistics on lower level partitions if the statistics on that partition are stale. This is a significant change. That is going forward using the default options of a gather command may in fact perform no reanalyze on the actual data if the modifications to the table don’t warrant it.

2 – if a subpartition is stale the normal stats will ONLY gather statistics on that subpartition. The partition for that subpartition will be re-derived as will the global statistics – no other statistics will be gathered.

Making this change promises to reduce gather stats by hours in some cases.


Friday Nov 15, 2013

Feb 12, 2014 Upcoming Webcast: Demantra Logs by Procedure. Where are They, When are They Updated

Hello!   Feb 12, 2014, We will present a webcast that details the Demantra log file matrix.   Here are the essentials:

Title: Demantra Logs by Procedure.  Where are They, When are They Updated

- Abstract: When you are installing, cloning, updating the worksheet, etc, which logs are updated and where are they?

- Target Audience: Technical Users, Functional Users, System Administrators, DBAs

- This one-hour session is recommended for technical and functional users who utilize Demantra processes

- Benefits/Agenda List:

  - Describe the log files by function or procedure
  - Locating the log files
  - Controlling the log files
  - Producing deeper verbage in the log file
  - Review and explain examples

To register in January 2014, follow

Tuesday Nov 12, 2013

Managing Custom Series

Custom series that have been added should be done with client Defined Prefix, ex. ACME Final Forecast, so they are can be identified as non-standard series.  With that said, it is not always done, so beginning in v7.3.0 there is a new column called Application_Id in the Computed_Fields table.  This is the table that stores the Series information. 

Standard Series will have have a prefix similar to COMPUTED_FIELD, while a custom series will have an Application_Id value similar to 9041128B99FC454DB8E8A289E5E8F0C5.

So a SQL that will return the list of custom series in your database might look something like this:

select computed_title Series_Name, application_id

from computed_fields where application_id not like '%COMPUTED_FIELD%' order by 1;

Saturday Oct 26, 2013

Demantra Partitioning and the First PK Column

  We have found that it is necessary in Demantra to have an index that matches the partition key, although it does not have to be the PK.  It is ok
  to create a new index instead of changing the PK.

  For example, if my PK on SALES_DATA is (ITEM_ID, LOCATION_ID, SALES_DATE) and I decide partition by SALES_DATE, then I should add an index starting
  with the partition key like this: (SALES_DATE, ITEM_ID, LOCATION_ID).

  * Note that the first column of the new index matches the partition key.

  It might also be helpful to create a 2nd index with the other PK columns reversed (SALES_DATE, LOCATION_ID, ITEM_ID). Again, the first column
  matches the partition key.

Wednesday Oct 23, 2013

Demantra Performance Clustering Factor Out of Order Ratio TABLE_REORG CHECK_REORG (Doc ID 1594372.1)

Hello!   There is a new document available:

Demantra Performance Clustering Factor Out of Order Ratio TABLE_REORG CHECK_REORG (Doc ID 1594372.1)

Demantra Performance Clustering Factor Out of Order Ratio TABLE_REORG CHECK_REORG

The table reorganization can be setup to automatically run in version 

In version 12.2.2 we run the TABLE_REORG.CHECK_REORG function at every appserver restart.
If the function recommends a reorg then we strongly encourage to reorg the database object. 
This is documented in the official docs.

In versions and, the TABLE_REORG module exists and can be used.
It has two main functions that are documented in the Implementation Guide Supplement,
Release 7.3, Part No. E26760-03, chapter 4.

In short, if you are using version or higher, you can check for the need to run a reorg by doing the following 2 steps:

2. Check the table LOG_TABLE_REORG for recommendations

If you are on a version before, you will need to follow the instructions below to determine if you need to do a manual reorg.

How to determine if a table reorg is needed

1. It is strongly encouraged by DEV that You gather statistics on the required table.  The prefered percentage for the gather is 100%.

2. Run the following SQL to evaluate how table reorg might affect Primary Key (PK) based access:

SELECT ui.index_name,trunc((ut.num_rows/ui.clustering_factor)/(ut.num_rows/ut.blocks),2)
FROM user_indexes ui, user_tables ut, user_constraints uc
WHERE ui.table_name=ut.table_name
AND ut.table_name=uc.table_name
AND ui.index_name=uc.index_name
AND ut.table_name=upper('&enter_table_name');

3. Based on the result:




Updates to the Demantra Partial Schema Exporter Tool, Patch 13930627, are Available.

Hello!  Updates to the Demantra Partial Schema Exporter Tool, Patch 13930627, are Available.
This is an updated re-release of the generic Partial Schema Exporter Tool.  The generic patch is for 7.3.1.x and 12.2.x.
TABLE_REORG was introduced in 12.2.0.  Therefore for 7.3.1.x the schema must be at or above.

This is build 3 of the patch.

It contains fixes for the following bugs
  It now only uses DATA_PUMP COMPRESSION only on Enterprise Edition for 11g and and up.

  It now builds GL level filters with and without the GL id column where applicable.

These bugs are also fixed in and 12.2.3.


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


« May 2015