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

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.

 

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 7.3.1.5. 

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 7.3.1.3 and 7.3.1.4, 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 7.3.1.3 or higher, you can check for the need to run a reorg by doing the following 2 steps:

1. Run TABLE_REORG.CHECK_REORG('T');
2. Check the table LOG_TABLE_REORG for recommendations

If you are on a version before 7.3.1.3, 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 UC.CONSTRAINT_TYPE='P'
AND ut.table_name=upper('&enter_table_name');
 

3. Based on the result:

VALUE ABOVE 0.75 - DOES NOT REQUIRE REORG

VALUE BETWEEN 0.5 AND 0.75 - REORG IS RECOMMENDED

VALUE LOWER THAN 0.5 - IT IS HIGHLY RECOMMENDED TO REORG

Tuesday Aug 13, 2013

Do Not Run Multiple Branch Processes in Parallel

Query to show log:
------------------

select (select schema_name
        from  demantra.wf_schemas
        where schema_id = a.schema_id),
        to_char(a.record_created, 'DD-MON-YYYY HH24:MI:SS'),
        to_char(a.record_updated, 'DD-MON-YYYY HH24:MI:SS'),
        a.*
from    demantra.wf_process_log a
where process_id >= 922599
order by a.record_created desc


Does the above output indicate that you are running multiple batch processes in parallel?

Please review your environment and make sure you run processes in the correct order and
that the processes are not competing for hardware resources.

If you are trying to run processes that compete for same data in same tables you can try extending
your undo space and settings to be much larger, assuming your hardware can support this path.

However, running overlapping engines is not recommended.

* Attain the process ID from the OS for the most recently ran batch process 

Thursday Aug 08, 2013

Worksheet Issues During or After Upgrade?

 Proactive action During/After an Upgrade may help.  Please review the following:

  1. Clean the Java cache by deleting the Java cache windows folder 
  2. Set the Java console debug mode to '5'
  3. Reproduced the issue
  4. Review the Client Java console
  5. Review the collaborator.log
  6. Produce an action plan

Wednesday Jul 17, 2013

Demantra Using Oracle database Real Application Clusters (RAC)

Demantra version:7.3.1.2

Database version:11.2.0.3

Due to the large amount of data within our system we are plannig to implement RAC to improve performance.  We have already recommended other performance guidelines from Oracle like reordering columns, partitioning sales_data table etc.  For further performance improvement since we expect more stores and items being introduced which would increase data we are planning to go for RAC as it is mentioned in the Demantra Installation Guide that RAC is supported in Demanra.

We would like the below information before proceeding with this major step:-

1.) For Distributed Engine Scaling - The Oracle Doc ID 468688.1 states that "The number of engines/machines defined in the Engine Administrator should not exceed 3 times the number of database CPUs".  So we want to know in case of RAC will the above calculation be based on cumulative CPU nodes of all database RAC nodes? I.e when using RAC can we set the total number of Engines upto 3 times the cumulative CPU nodes of all database RAC nodes.

Answer 1: For Distributed Engine Scaling -- using the cumulative CPU nodes is not quite right for RAC, since there will be extra interconnect overhead in a RAC system.  So you can try using the "3 times CPU's" but you might have to scale it back based on empirical performance.

2.) Using a Distributed Engine with one master and multiple slave machines. Is it possible to point different slave engines to different RAC nodes?

Answer 2: Is it possible to point different slave engines to different RAC nodes?  No.  The RAC will automatically load balance when you connect using the SCAN addresses.

Oracle Demantra 12.2.1 Available

We are excited to announce Oracle Demantra 12.2.1 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.1 which requires application and participation in Oracle E-Business Suite early adopter program.
Demantra 12.2.1 includes a wide array of new features driven by customer requirements and needs. Key features include:
• Streamlined import and export from Microsoft Excel
• Support Gregorian Month data aggregation in weekly system
• Multilanguage support for eleven languages
• Promotion Calendar Optimization
• Enhanced integration with Advanced Planning Command Center (VCP 12.2.1 Required)

Demantra 12.2.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.1 will only work with VCP 12.2.1.
Demantra 12.2.1 and VCP 12.2.1 will work with EBS 12.1.3 or EBS 12.2.1.

Please review the release readme and all 12.2.1 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 16409031.

Friday Jun 21, 2013

Announcing Oracle-Demantra 12.2.1 Release

We are excited to announce Oracle Demantra 12.2.1 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.1 which requires application and participation in Oracle E-Business Suite early adopter program.

Demantra 12.2.1 includes a wide array of new features driven by customer requirements and needs. Key features include:

·       Streamlined import and export from Microsoft Excel

·       Support Gregorian Month data aggregation in weekly system

·       Multilanguage support for eleven languages

·       Promotion Calendar Optimization

·       Enhanced integration with Advanced Planning Command Center (VCP 12.2.1 Required)

Demantra 12.2.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.1 will only work with VCP 12.2.1.

Demantra 12.2.1 and VCP 12.2.1 will work with EBS 12.1.3 or EBS 12.2.1.

Friday Oct 26, 2012

WARNING Retrying Bulk Insert for file:sqlldr due to Communication Error:256

WARNING Retrying Bulk Insert for file:sqlldr due to Communication Error:256

I am running my engine on Linux and am receiving an intermittent message

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

The engine seems to have completed successfully, but it is not clear if this error caused some of the forecast to not complete. It is also not clear what caused the error.

Generally if you see only the WARNING of it, it means that next retries of the same load request have eventually succeeded and so the run a a whole is not affected.

In order to know more about what happens, look for .log/.bad files left in the engines bin directory or possibly a quote of them within the specific engine log that had the issue.  The sqlnet.log file may also have some information about it and perhaps at the database server side there may be some log/alert regarding what happened.  Look at the alert.log.

In general it could be that the database server/network was over loaded at the time and somehow the connection was rejected/failed/aborted either due to specific setting on concurrent connections/sessions or inadvertently due to glitch in network/os/hardware.

If this repeats and becomes more frequent during the run you should look further into it as mentioned above.

You can also track this using either SQL*Trace or java.util.logging. 

- Globally enable logging by setting the oracle.jdbc.Trace system property java -Doracle.jdbc.Trace=true

- Client Side Tracing:

Your SQLNET.ORA file should contain the following lines to produce a client side trace file:

trace_level_client = 10
trace_unique_client = on
trace_file_client = sqlnet.trc
trace_directory_client = <path_to_trace_dir>

Server Side Tracing:

To enable server side tracing, use the following parameters:

trace_level_server = 10
trace_file_server = server.trc
trace_directory_server = <path_to_trace_dir>

Tracing Levels:

The following values can be used for TRACE_LEVEL* parameters:

    16 or SUPPORT — WorldWide Customer Support trace information
    10 or ADMIN — Administration trace information
    4 or USER — User trace information
    0 or OFF — no tracing, the default

Additional information is readily available via the web.

Thursday May 24, 2012

Announcing: Oracle Demantra 7.3.1.3 Available

We are pleased to announce the availability of Oracle Demantra 7.3.1.3.

Please review the release readme and all 7.3.1.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 as Patch 14076370.

Regards

Wednesday Apr 04, 2012

Need to Determine the Engine Status?

If you need to establish the status of the engine, begin with this SQL:

select status, engine, engine_version,fore_column_name
from dm.forecast_history

The status of an engine run is stored in the FORECAST_HISTORY table, in the “status” field.  We can also find in that table the FORE_COLUMN_NAME field. This field includes the name of the column in SALES_DATA in which the relevant forecast is stored.

Here are the possible statuses:
-1, -2 : The engine failed in the initialization phase.  Which means, before the engine manager created the engines.
 0 : The engine stopped in the optimization phase.  Which means, after the engines were created.
 1: The engine finished the run successfully.
 2: Forecast was never calculated for the relevant column that is mentioned in FORE_COLUMN_NAME.


 

Thursday Mar 08, 2012

Loading Product Family into Demantra Using Legacy Collection

I am using legacy collection to load product family into Demantra.  In the soucre EBS/Value Chain Planning (VCP)
I can see my product family and member in the ASCP plan.

I would like to be able to have product family dimension populated in a Demantra Hierarchy.  I have used demhistory
flat file to upload forecasts for my items (members) and I expect to have product family dimension populated.

I started to analyse demantra collection and EP launch, and it seems to me that stagging table T_SRC_ITEM_TMPL is
populated by process "Collect Level Type (2)"  or perhaps a subprocess.

The stagging table stores the link between members and product family itself, ebs_product_family_code field, but it
is populated with default value (0).

The profile 'MSD_DEM: Master Org' is used for collecting item -> product family rollups into demantra.
Item to product family rollup needs to be available in ASCP under the master organization specified by the above profile.

This is a source side profile, and cannot be set by hand in case of legacy source.  To set the value, you will need to run the
request 'Configure Legacy Profiles' from 'Demand Management System Administrator' responsibility.  Parameters for this
request are as follows:

- Legacy Instance
- Master Org
- Category set

After running this, check for records in msd_dem_legacy_setup_params table.  Then try running flat file load and verify
product family is populated in t_src_item_tmpl table in demantra schema.

Also the product family members/product family relationship comes from the msc_system_items table for the master organization,
not organization where product family/product members is defined

You can check for a link between members and product family in the master org within msc_system_items and then the product family
should be visible within Demantra.

Monday Feb 27, 2012

Demantra T_UPDATE Performance Issues? Supply an Enhanced AWR Report Using Logger

When communicating with Support or Development the performance issue you are experiencing with the T_UPDATE object, follow the instructions below to produce an AWR report with logger turned on. This may expedite your solution.

Please do the following:

1. Turn on the Logger Category 'appserver.update.sql' via server admin page.
    For example: http://<server>:8080/demantra/admin and then press the Logger Manager link.

2. Launch the AWR Report. See note 1279115.1, Producing an AWR Report for Demantra Performance Troubleshooting

3. Re-run the problematic scenario.

4. Turn off the Logger Category from step 1.

5. Supply the AWR report for the time period matching the Logger Category switch.

6. Supply the tables whose name starts with "T_UPDATE_". If they are very big then please list the T_UPDATE_  table names and their row counts.

Demantra Performance and Install/Upgrade Questions

Hello!  We are reworking this blog to specifically focus on Demantra performance and install/upgrade issues.   When reviewing you will find articles, such as the following, added on a frequent basis.   Questions are welcome.   Regards!   Jeff
About

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

Search

Archives
« April 2014
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
   
       
Today