How to Install the Demantra Base Application or Patches?
Create a C:/Tmp folder on the machine where the setup.exe will be executed prior to the installation as this will generate a log file to this folder
Note that there will also be some ancillary logs under the following folders:
Demand Planner\Database Objects\Oracle Server (Oracle back end database)
Demand Planner\Database Objects\Microsoft SQL Server (Sql Server back end database)
Tell the three modules that can be implemented separately.
Demand Management.
Advance Forecasting and Demand Modeling(AFDM)
Real-Time Sales and Operations Planning
Where you can run data load or data collect process?
to get the Demantra staging table populated properly (using SQL loader or through Collection process in case of integrated EBS-Demantra instance), after which you can run EP_LOAD_MAIN procedure manually or through workflow for downloading data to Demantra base table.
Demantra admin user is “dm/dm” or “sop/sop” based on which module you have installed.
Errors with the Demantra Batch or Simulation Engine?
The key engine logs are found under the root drive of the machine where the engine is launched. The folder that holds these logs usually have Engine2k somewhere in the name.
However, to write the master EngineManager logs to this folder you need to go to the Engine Administrator (..Demand Planner\Analytical Engines\bin –> Settings –> Configure) and change the Engine Manager Log tab from STD to FILE.
It is NOT advised to re-register the engine after making this change
How to get the Stored Procedure Errors with Active_Proc_Dyn somewhere in the error message
To view the errors go to Business Modeler –> Tools –> Procedure Error Log
Error starting the Web Server and/or deploying the Demantra WAR file
Review the Collaborator.log which is found under the Collaborator\demantra\logs folder on the webserver where Demantra is running.
Also, each individual webserver (ex. OAS, JRUN, Tomcat, Websphere, etc…) will have their own individual logs in various directories which can also be consulted.
The individual webserver documentation should be reviewed for these log locations.
What happens if RVWR cannot write to disk?
It depends on the context where the write error occurs:
If there’s a Guaranteed Restore Point, the database crashes to ensure the restore point guarantee is not voided.
If there isn’t a Guaranteed Restore Point and it’s a primary database, the Flashback Mode will be automatically turned off for the database, which will continued to operate normally.
If there isn’t a Guaranteed Restore Point and it’s a standby database, the database will hang until the cause of the write failure is fixed.
How should I set the database to improve Flashback performance?
Use a fast file system for your flash recovery area, preferably without operating system file caching. It is recommended to use a file system that avoids operating system file caching, such as ASM.
Configure enough disk spindles for the file system that will hold the flash recovery area. For large production databases, multiple disk spindles may be needed to support the required disk throughput for the database to write the flashback logs effectively.
If the storage system used to hold the flash recovery area does not have non-volatile RAM, try to configure the file system on top of striped storage volumes, with a relatively small stripe size such as 128K. This will allow each write to the flashback logs to be spread across multiple spindles, improving performance
For large, production databases, set the init.ora parameter LOG_BUFFER to be at least 8MB. This makes sure the database allocates maximum memory (typically 16MB) for writing flashback database logs.
Can RMAN be used to backup flashback logs?
No. Flashback Logs are not backed up. Even if the command BACKUP RECOVERY AREA is used to backup the contents of the FRA to tape only the following file types are backed up: full and incremental backup sets, control file autobackups, datafile copies, and archived redo logs.
Flashback Logs are considered to be transient files and cannot be backed up by RMAN. They are not needed for media recovery.
What happens if RVWR cannot write to disk?
It depends on the context where the write error occurs:
If there’s a Guaranteed Restore Point, the database crashes to ensure the restore point guarantee is not voided.
If there isn’t a Guaranteed Restore Point and it’s a primary database, the Flashback Mode will be automatically turned off for the database, which will continued to operate normally.
If there isn’t a Guaranteed Restore Point and it’s a standby database, the database will hang until the cause of the write failure is fixed.
