Rebuild_Schema procedure - One of the Keys to Improved Demantra performance
Last updated on DECEMBER 18, 2017
Applies to:Oracle Demantra Demand Management - Version 7.0.2 and later
Information in this document applies to any platform.
Since the Demantra back end sits on a Relational Database (most times Oracle, but some clients do run SQL Server), keeping that Database healthy will help to ensure the optimal performance when it comes to elements such as Data Loading, Caching of Worksheets, Workflows, running the Demantra Forecast Engine, etc.
Clients should ensure that tables and indexes in the Database suffer from as minimun Fragmentation (Chaining) of rows as possible and that the latest Stats have been generated on these objects.
When submitting a performance related Service Request (ex. My Worksheet is slow, my Engine run is slow, etc.) to the Oracle Demantra support team, the first piece of information we will request is for you to run the following sql on the Demantra schema:
This sql will allow us to assess the fragmentation, chain_cnt column as a percentage of the num_rows column and Statistics freshness which is a product of the last_analyzed column as well as the sample_size column versus total row count in the num_rows column.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms