Wednesday Nov 26, 2014

Oracle Demantra Demand Planning Announcing New Release 12.2.4.1 is Now Available MOS Note 1948684.1

Announcing Oracle Demantra Demand Planning 12.2.4.1 Release

We are excited to announce Oracle Demantra Demand Planning 12.2.4.1 is now available for new and existing customers.

Oracle Demantra Demand Planning 12.2.4.1 includes several features in 12.2.4. Key features include:

  • Oracle In-Memory Consumption-Driven Planning
  • 64-bit Analytical Engine
  • User Access Control
  • Additional Demantra Hierarchies in APCC
  • Launch Management Extended to DM and PTP Components
  • APCC Support for Trade Hierarchies and Data
  • Streamlined Promotion Creation and Improved Method Usability
  • Promotion Calendar Enhancements
  • Printing Promotion Calendar
  • Streamlined Simulations
  • Enhanced Shipment and Consumption Planning Support
  • Demantra- Improved Worksheet Performance
  • VCP and Demantra- Support E1 Long Item Code
  • VCP and Demantra- Certified with Oracle 12.1.0.2 DB in Memory


Uptake of VCP 12.2.4.1 is mandatory for all VCP and Demantra 12.2.4 installations.

  • Demantra Patch Number is 19973580.
  • For E1 customers Long Item Code  Patch Number is 19608405.
  • Demantra 12.2.4.1 will only work with VCP 12.2.4.1.
  • Demantra 12.2.4.1 and VCP 12.2.4.1 will work with EBS 12.1.3 or EBS 12.2.4.


Questions?


If you would like additional information regarding Oracle Demantra 12.2.4.1 functionality, certification and deployment please refer to the Demanta Documentation Library on My Oracle Support (Document  443969.1).

Contact Jeffery.goulette@oracle.com with direct questions.   Regards!   Jeff

Monday Nov 24, 2014

UPDATED: Does Demantra support Edition Based Redefinition (EBR)? How do I address EBR in my EBS instance?

Hello Demantra Customers!  Do you know what Edition Based Redefinition (EBR) is or how it impacts Demantra?  EBS uses EBR for online patching.

There is a new update to the referenced MOS note below.  Demantra DOES NOT support Edition Based Redefinition. 

Edition-Based Redefinition enables you to upgrade an application's database objects while the application is in use, thus minimizing or eliminating down time. This is accomplished by changing (redefining) database objects in a private environment known as an edition.  Only when all changes have been made and tested do you make the new version of the application available to users.

Edition-based redefinition allows multiple versions of PL/SQL objects, views and synonyms in a single schema, which makes it possible to perform upgrades of database applications with zero down time.

Large, mission critical applications built on Oracle Database 11g Release 1 and earlier versions are often unavailable for tens of hours while the application’s database objects are patched or upgraded.  Oracle Database 11g Release 2 introduces edition-based redefinition, a revolutionary new capability that allows online application upgrades with uninterrupted availability of the application.  When the installation of the upgrade is complete, the pre-upgrade application and the post-upgrade application can be used at the same time.

EBS supports EBR from the 12.2 release onwards in the online patching feature.

To read about EBR and Demantra, see the new white paper, Oracle Demantra and RDBMS Edition-Based Redefinition (EBR) EBS schema - Processing and Patching (Doc ID 1932210.1)

Friday Oct 31, 2014

Demantra Upgrading to 12.2.x? Critical Known Issues and Lessons Learned

Oracle Demantra customer, are you considering an upgrade to you Oracle Demantra software?  There are three ciritical MOS notes that you may want to review.

  • 12.2.1, 12.2.2, 12.2.3 and 12.2.4 Install Upgrade ADVISOR: Demantra (Doc ID 1664177.2)
  • DEMANTRA WARNING Have you OR are you Planning to Upgrade to Release 12.2.2? Upgrade from 12.2.2 to 12.2.3 or 12.2.4 Collections EP Load is Failing ORA-20002, ORA-00001, ORA-06512 (Doc ID 1917715.1)
  • Upgrading to Demantra 12.2.4? Here are current known issues from Demantra Development, Proactive Services and Oracle Support (Doc ID 1928367.1)

New White Papers in Development Sponsored White Paper Library!

Hello Demantra Customers!  There is a new Development sponsored Value Chain Planning and Demantra library!  This library is exclusive to Demantra Development and Oracle Proactive Support.  There are excellent white papers and more!  See Development and Proactive Services Document Library White Papers (Doc ID 1669052.1)

 As of today, we provide

    Value Chain Planning
    - ASCP Data Collections
    - Demantra Demand Planning  * see below
    - Strategic Network Optimization
    - Rapid Planning
    - Global Order Promising
    - Collaborative Planning
    - WebLogic
    - IO Inventory Optimization
    - SPP Service Parts Planning
    - DP Distribution Planning
    - Integration
    - Information Centers

    Specifically for Demantra
    - Architecture
    - Install and Upgrade
    - Integration, Data Loading and CTO
    - Workflow Issues
    - Worksheet Related
    - Engine Related
    - Performance
    - User Interface Use and Design
    - Diagnostic Tools
    - Weblogic Related

Demantra Development Sponsored White Paper Library, NEW ADDITIONS!

Hello Demantra Customers!  As you know we a Development and Proactive Services document library.  These are hand picked, powerful notes.  Two new notes have been added;

Custom Hierarcies and Demantra SSO using Oracle Access Manager (OAM) 11g - synchronization between Demantra and Oracle Identity Management / Oracle Virtual Directory (OID/OVD).

Look under Demantra Worksheets and Demantra Integration.  See My Oracle Support note 1669052.1.

New Development Sponsored White Paper Single Sign On Using OAM OID and OVD

Hello Demantra Customers!   There is a new Development sponsored white paper! Single Sign-on Setup for Demantra Using the Oracle Access Manager (OAM) 11g - synchronization between Demantra and Oracle Identity Management / Oracle Virtual Directory (OID/OVD) (Doc ID 1940438.1).  This doc will guide you through the steps to achieve integration.  

 

This white paper covers the following topics and much more.   Complete with references and guides.

  • Prerequisites
  • Configuring Single Sign-on
  • Configure a new Oracle HTTP Server (OHS) instance specifically to protect the Demantra WebLogic server
  • Install the new Oracle Access Manager Webgate 11g
  • Ensure that the global logout work properly
  • Configuring Demantra application server(weblogic) to setup OAMIdentityAsserter security provider
  • Authentication in the web.xml file of the Demantra Application
  • Modifying security realm of the weblogic server to setup Identity asserter provider
  • Create a new Authentication Schemes (DemAuthScheme)
  • Resolve the issue of java applets that are not loading in OAM 11g or 10g
  • Demantra with OAM supports the following links
  • Test that you have successfully configured SSO for Demantra

Thursday Oct 23, 2014

Oracle Demantra 12.2.4 RDBMS 12C Important Updates to Consider

Hello Demantra Customer!   Are you considering an upgrade to you Oracle Demantra software?  Are you implementing Oracle RDBMS 12C with Demantra?  There are critical MOS notes that you may want to review.

  • 12.2.1, 12.2.2, 12.2.3 and 12.2.4 Install Upgrade ADVISOR: Demantra (Doc ID 1664177.2)
  • DEMANTRA WARNING Have you OR are you Planning to Upgrade to Release 12.2.2? Upgrade from 12.2.2 to 12.2.3 or 12.2.4 Collections EP Load is Failing ORA-20002, ORA-00001, ORA-06512 (Doc ID 1917715.1)
  • Upgrading to Demantra 12.2.4? Here are current known issues from Demantra Development, Proactive Services and Oracle Support (Doc ID 1928367.1)
  • Demantra Startup Times can be Longer When Running Demantra on Oracle 12c RDBMS due to RDBMS Defects (Doc ID 1937616.1).

Monday Oct 06, 2014

Does Demantra support Edition-Based Redefinition (EBR)? How do I address EBR in my EBS instance?

Hello Demantra Customers!  Do you know what Edition-Based Redefinition (EBR) is or how it impacts Demantra?  EBS uses EBR for online patching.

Edition-Based Redefinition enables you to upgrade an application's database objects while the application is in use, thus minimizing or eliminating down time. This is accomplished by changing (redefining) database objects in a private environment known as an edition.  Only when all changes have been made and tested do you make the new version of the application available to users.

Edition-based redefinition allows multiple versions of PL/SQL objects, views and synonyms in a single schema, which makes it possible to perform upgrades of database applications with zero down time.

Large, mission critical applications built on Oracle Database 11g Release 1 and earlier versions are often unavailable for tens of hours while the application’s database objects are patched or upgraded.  Oracle Database 11g Release 2 introduces edition-based redefinition, a revolutionary new capability that allows online application upgrades with uninterrupted availability of the application. When the     installation of the upgrade is complete, the pre-upgrade application and the post-upgrade application can be used at the same time.

EBS supports EBR from the 12.2 release onwards in the online patching feature.

To read about EBR and Demantra, see the new white paper, Oracle Demantra and RDBMS Edition-Based Redefinition (EBR) EBS schema - Processing and Patching (Doc ID 1932210.1)

Wednesday Oct 01, 2014

Demantra Performance and Setup Analyzer v2.00 is FINALLY Available!

Hello Demantra Customer!  There is a new release of the Demantra Performance and Setup Analyzer!  Version 2.00 has been released!
You can pick and choose any SQL that you prefer to see given any type of task at hand.   See MyOracleSupport note
Demantra Analyzer script for Setup and Performance Monitoring (11.5.X and R12), 1618885.1

I am considering adding more topical analysis and deeper digging into additional details for the next release. 

Any questions / comments, please email Jeffery.goulette@oracle.com

Thank You!

Demantra 12.2.4 Performance Enhancement Data Points that you need to know!

Demantra 12.2.4 Customers, There is a new MyOracleSupport note highly recommended by Demantra Development.  There are new performance enhancements available!  However, there is additional information in this note that is critical to implement some of these new enhancements.

Please see, Demantra 12.2.4 Worksheet Performance Enhancements Parameter dynamic_hint_enabled. Development Recommended Proper Setup and Use (Doc ID 1923933.1)

Thursday Sep 25, 2014

Demantra Integration Webcast 24-Sep-2014

Hello!   Were you able to attend the the Demantra webcast 24-Sep-2014?   The topic was integration.  You can watch a replay found at:
Demantra Solutions Advisor Webcast Calendar And Archive (Doc ID 800030.1) and scroll to Integrating Demantra With Oracle Applications.

 

Coming up:

1) 8th OCT, V2 Analyzer review and Data Mining Live Demo

2) I am thinking about breaking the 24-Sep-2014 into two presentations.  This would allow us to dig deeper into debugging the integration and workflow.  These would concentrate on data once it arrives into the denorm table AND data mapping. 

Has anyone used the e_plan_tree database object?

SQL> desc msdem.e_plan_tree
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 E_PLAN_NODE_ID                            NOT NULL NUMBER(10)
 E_PLAN_CHILD_NODE                                  NUMBER(10)
 TABLE_NAME                                NOT NULL VARCHAR2(30)
 FIELD_NAME                                NOT NULL VARCHAR2(30)
 E_PLAN_NAME                                        VARCHAR2(30)
 E_PLAN_TITLE                                       VARCHAR2(100 CHAR)
 E_PLAN_BASE_DIM                                    VARCHAR2(30)
 E_PLAN_TYPE                                        VARCHAR2(10)
 E_PLAN_DATA_TYPE                                   VARCHAR2(10)
 E_PLAN_RELATION                                    NUMBER(10)
 SOURCE_NAME                                        VARCHAR2(30)
 E_PLAN_AGGRI                                       VARCHAR2(400)
 MODEL_VERSION                             NOT NULL NUMBER(5)
 VERSION_NAME                                       VARCHAR2(30)
 FICTIVE_COLUMN_NAME                                VARCHAR2(30)
 E_PLAN_TABLE_NAME                                  VARCHAR2(30)
 HYRARCHY_NO                                        NUMBER(5)
 ENABLE_LEVEL                                       VARCHAR2(20)
 USE_EP_GEN_ID_FOR_FILTER                           NUMBER(1)
 USE_ITEM_LOC_ID                                    VARCHAR2(20)
 AGGRI_FUNC                                         VARCHAR2(400)
 WAVG_DEPENDANT                                     VARCHAR2(30)
 PARTS_VERSION                             NOT NULL NUMBER(5)
 IS_HIERARCHY_LEVEL                                 NUMBER(1)
 PARENT_FIELD_NAME                                  VARCHAR2(30)
 APPLICATION_ID                                     VARCHAR2(63)

 

Demantra Performance and Setup News

Hello!   Sorry for being away so long!  I have been preparing version 2 of the Demantra Performance and Setup Analyzer.  More on that soon.


Have you seen the latest 12.2.1, 12.2.2, 12.2.3 and 12.2.4 Install Upgrade ADVISOR: Demantra (Doc ID 1664177.2)?  This is an excellent store
of hand picked notes and white papers.  Including White Papers, How To +! Documents from Development.  Check it out and let me know what you think.
Regards!  Jeffv

Monday Aug 11, 2014

Announcing the release of Demantra 12.2.4! Fantastic new functionality!

Hello Demantra Customers!  We are excited to announce that Oracle Value Chain Planning 12.2.4 is now available for new and existing customers. This release includes Demantra 12.2.4.  Providing a wide array of new features driven by customer requirements and needs.  This release includes over 20 key features including; In-Memory Performance Driven Planning, In-Memory Consumption Driven Planning, APCC – Custom Hierarchies and Measures, APCC – End Item Pegging-based Analysis and more!

Please see My Oracle Support note, Oracle Demantra Documentation Library (Doc ID 443969.1), for complete details.

Thursday Jul 24, 2014

Demantra 12.2.x Focusing on 12.2.3 Install, Upgrade, Operation Bug Fixes and Best Practices

Hello Demantra Customers! 

There is a new r12, focusing on r12.2.3, MOS note that summarizes all known issues as of 24-Jul-2014.  Quickly review the
problems and solutions to help you save time!

See Demantra 12.2.x Focusing on 12.2.3 Install, Upgrade, Operation Bug Fixes and Best Practices.  Known Issue Summary (Doc ID 1910650.1).

Friday Jul 11, 2014

Demantra Index Cluster Factor Major Update Performance Impact

Hello Everyone!   Please check out the following important information regarding the cluster factor and the impact to the CBO.   Please comment if you like.

Regards!   Jeff

 The Cluster Factor (CF) of an index a very important statistic used by the Cost Based Optimizer (CBO) to determin
the most efficient execution plan.  However, there is a major flaw in the current CF calculation.  Simply put, the CF
is calculated by performing a Full Index Scan, looking at the rowid of each index entry.  If the table block being referenced
is different from the previous index entry, the CF is incremented.  However if the table block being referenced is the same
as the previous index entry, the CF is not incremented.  So the CF gives an indication of how well ordered the data in the table is
in relation to the chosen index entries.  

The lower the CF, closer to the number of blocks in the table vs the number of rows, the more efficient it is to use the index as
less table blocks would need to be accessed to retrieve the necessary data via the chosen index.

So far so good.  However, what if part of the incoming row is stored in block one and the remainder in block 2?  When the row is
required, block 1 and block 2 will be read into cache resulting in near zero waiting for the entire row.  OK, fast forward, what if
the table has 100m rows and imagine that this situation occurs 30% of the time.  Your current CF method is most likely skewed
and incorrect.  

Now for the good news, bug 13262857 - INDEX CLUSTERING FACTOR COMPUTATION IS PESSIMISTIC.  The computation of the index clustering
factor in dbms_stats package is pessimistic about the caching ratio of the table blocks.  It assumes that at most one block from the
table is cached.

This is an enhancement to allow a user to specify the number of blocks that dbms_stats package will consider when gathering the index clustering
factor statistics. Prior to this enhancement dbms_stats assumed 1 and it still does after the enhancement.  This enhancement allows the user to
specify a value between 1 and 255.  There is also an AUTO option which if specified then dbms_stats will use 1% of the table blocks up to
0.1% of the buffer cache size, in blocks.  

The new CF approach is currently available with patches that can be applied on both Exadata databases and Oracle versions 11.1.0.7, 11.2.0.2 and 11.2.0.3.
The Patch ID is 15830250.

Once applied, there is a new statistics collection preference that can be defined, called TABLE_CACHED_BLOCKS.  This basically sets the number of
table blocks we can assume would already be cached when performing an index scan and can be ignored when incrementing the CF during statistics gathering.
The default is 1, as stated, the same as today.  But can be set up to be a value between 1 and 255, meaning that during the collection of index statistics
the process will not increment the CF if the table block being referenced by the current index entry has already been referenced by any of the prior 255 index
entries, if set to 255.  It basically sets the appropriate parameter in the sys_op_countchg function used to calculate the CF value during statistic gathering
to not increment the CF if the current table block has already been accessed “x” index entries previously.

The TABLE_CACHED_BLOCKS preference can be set by either the DBMS_STATS.SET_TABLE_PREFS, DBMS_STATS.SET_SCHEMA_PREFS or DBMS_STATS.SET_DATABASE_PREFS procedures.
Apply the patch, change the TABLE_CACHED_BLOCKS preference for this table and re-calculate the index statistics:

SQL> exec dbms_stats.set_table_prefs(ownname=>dm, tabname=>'SALES_DATA',

pname=>'TABLE_CACHED_BLOCKS', pvalue=>50);

PL/SQL procedure successfully completed.

SQL> EXEC dbms_stats.gather_index_stats(ownname=>dm, indname=>'SALE_DATA', estimate_percent=> null);

PL/SQL procedure successfully completed.

SQL> SELECT t.table_name, i.index_name, t.blocks, t.num_rows, i.clustering_factor
2  FROM user_tables t, user_indexes i
3  WHERE t.table_name = i.table_name AND i.index_name='SALES_DATA';

Although I found this bug internally, many thanks to several on the WWW for their comments.



About

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

Search

Archives
« July 2015
SunMonTueWedThuFriSat
   
1
2
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
31
 
       
Today