Installing and Upgrading Oracle Demantra

This chapter covers the following topics:

Overview

If you are running a pre-7.3.0.1 version of Oracle Demantra, you must upgrade to 7.3.0.1 first and then upgrade to the latest version.

For more information, see the Oracle Demantra Installation guide.

If you are upgrading from release 7.3.0 and are using CTO functionality, see Upgrading Software and Data to Support Configure to Order.

Note: Oracle does not support Microsoft SQL Server. Monitor My Oracle Support for versions supporting SQL Server.

Note: When installing Demantra for the first time, install Tomcat version 8.5. When upgrading or re-installing Demantra, you only need to re-install Tomcat if the version installed is older than version 8.5.

After running the Installer, be sure to review sections in Configuring Your Database, Web Server and Browser and Deploying Demantra on UNIX, Solaris or Linux.

About the Installer

The Installer displays depend on the following options:

When running the Installer, you can choose from the following options:

Selecting any subset of these applications during install will activate that functionality only and deactivate other functionality. Therefore, every time you run the Oracle Demantra Installer, select all desired applications. For example:

If you are using the Installer to import a custom DMP file and experiencing difficulties, please ensure the directory the DMP file is in does not include any spaces in its name. For example, C:\Tmp is better than C:\My Files\.

In order to make the installation process clear, this manual lists the installation steps in a table, with information about the conditions under which you see each step. This allows you to skim easily to the next step that applies to you.

In general, to proceed from step to step, click Next. You can also return to previous screens, if you have not yet reached the step where the Installer begins copying files.

Oracle Demantra classifies applications as:

This table shows the primary and secondary applications.

Primary Application Secondary Application
Oracle Demantra Demand Management Oracle Demantra Advanced Forecasting and Demand Modeling (AFDM)
Oracle Demantra Demand Management Oracle Demantra Real-Time Sales & Operations Planning (S&OP)
Oracle Demantra Predictive Trade Planning Oracle Demantra Trade Promotion Optimization
Oracle Demantra Predictive Trade Planning Oracle Demantra Settlement Management

Running the Installer

Note: If you will be leveraging Service Parts Forecasting (SPF) functionality, refer to Upgrading Software and Data to Support Service Parts Forecasting in 7.3.1 before running the installer.

To run the Installer, perform the following steps:

  1. See Preparing for Installation or Upgrades and complete the worksheets. They explain all the information needed by the Installer.

  2. Make sure that the database is running. The Installer requires access to the database.

  3. Make sure all applications (including virus-checking programs) are closed.

  4. Check the screen resolution. The Installer requires a screen resolution of at least 800x600 dpi. An error may occur if the resolution is lower, particularly if you are installing remotely via an application such as Citrix.

  5. The Installer creates an installation directory defined by the environment variable %temp%. Once installation is complete, you can review the log file Oracle_Demantra_Spectrum.log from the %temp% location. For details, see Checking the Log Files and Tables.

  6. Download the installation .zip file from Oracle Support and extract the files.

  7. If you run the Installer on Microsoft Windows Vista, do the following:

    • Right-click the file setup.exe and select Properties.

    • Navigate to the Compatibility tab.

    • Select Run this program in compatibility mode for: and choose Windows XP.

    • Click Apply, then click OK.

    The Installer displays these screens, one after the other. Complete the screens that apply to you.

  8. Specify general information.

    Screen When Screen is Displayed Action/Notes
    Introduction Always Click Next
    Select Unix/Linux/Solaris Deployment Always Select the relevant check box if you wish to install and configure the Web Application on UNIX, or the Analytical Engine on Linux or Solaris.
    For details of additional configuration steps, see Deploying Demantra on UNIX, Solaris or Linux.
    Select Exadata/Exalogic Deployment Always Select the checkboxes below if you are either deploying Oracle Demantra Database schema on Exadata, SPARC SuperCluster and/or deploying the Oracle Demantra middle tier on Exalogic, SPARC SuperCluster.
    Selecting the first checkbox is required to enable the option of CDP module installation. After the install is complete, manual configuration will be required to deploy Demantra on Exadata/Exalogic/SPARC Supercluster. For additional information, see Deploying Demantra on UNIX, Solaris or Linux.
    Choose Installation Set Always Choose the type of installation to perform and select the components that you want to install. This option controls:

    • Typical: Installs typical foundation components.

    • Complete: Installs all available Demantra components.

    • <components>: Installs the component(s).

    • Administrative Tools: Installs only the desktop utilities such as the Business Modeler and Engine Administrator.

    • Install Database: Imports a database dump file but does not install any files.

    • Custom – Allows you to select the components to be installed.
    Review Details of Installation Set If you choose Custom Browse the hierarchy and specify the items to install. To avoid errors when importing a database schema, be sure that the Demantra Foundation Tools and Basic Database Object options are selected.
    Choose Install Folder If you are installing files Specify the directory to install software into. The path must be no more than 40 characters long and must not include brackets.
    Specify Shortcut Location If you are installing files Specify the location of program shortcuts.
    If you install more than one version of Demantra, give each installation a distance name (for example, Oracle1 and Oracle2) so that each shortcut works properly.
    To make the shortcuts available to all users of this machine, click Create Icons for All Users.
    Select Oracle Client If multiple clients are detected by the installer Defaults to the configuration files folder located directly under the install directory ($INSTALL\ConfigurationFiles). Select Oracle database version.
    Select Database Home If more than one copy of the database software is installed Select the database home that Oracle Demantra will use.

  9. Specify how to access the database as a DBA.

    Screen When Screen is Displayed Action/Notes
    DBA Details Always Specify how to access the database as a database administrator:

    • DBA username: DBA username

    • Password: Password

    • TNS Name: TNS name of database. If you are using Oracle 12c, enter the name of the pluggable database that you want to use. For more information, see Additional Steps for Configuring Oracle 12c.

    Note: To allow the Installer to automatically run a script that enables user password encryption and performs additional database configuration, enter a user that has full SYSDBA privileges. If you do not enter a user with SYSDBA privileges, you will be prompted to run this script manually at the end of the installation (this method is recommended). SYS and SYSDBA typically have sufficient privileges, while SYSTEM does not. For details, see Running SYS_GRANTS.SQL Script.

  10. Specify user, schema, and JDBC configuration details.

    Screen When Screen is Displayed Action/Notes
    User/Schema Details Always Specify the user that will store the Oracle Demantra data. You do not have to create this database user ahead of time:

    • User: Database user name.

    • Password: Associated password.
    Configure JDBC Configuration Always Specify the JDBC connection that you will use to connect to the Oracle Demantra database:

    • Server name: Host or IP address where database resides.

    • Port: Port to which database is listening. If you are using Microsoft Windows XP, avoid using the default port number.

    • Oracle SID: Oracle SID or service name. If you are using Oracle 12c, enter the service name. For more information, see Additional Steps to Configure Oracle 12c.

    Note: If you are deploying Demantra with a Web application server other than Apache Jakarta Tomcat, additional configuration is required after running the installer. For details, see Configure JDBC Connection.

    Note: If the installation is interrupted, you can use ds_config.bat to configure the Demantra data source (DataSource.properties). The file ds_config.bat is located in $INSTALL\DemandPlanner\Integration.

  11. Specify the schema options.

    Screen When Screen is Displayed Action/Notes
    Schema Options If the database user already exists. Specify what to do with the existing database user:

    • Upgrade Schema: Runs a database procedure that updates the schema and default definitions for the specified user. It will not be possible to reverse this change. This option is available only if the database user is a valid Oracle Demantra database instance from a previous version of Oracle Demantra.

    • Replace schema with new application file: Completely removes the existing data for this user and installs the newest schema and data. It will not be possible to reverse this change. You generally use this option only for demo installations.

    • Install software without modifying schema: Leaves the database user unchanged.
    Upgrade Options After Schema Options if Upgrade Schema chosen Specify the upgrade type:

    • Platform Upgrade Only: Upgrades the software platform including the generic features of the software such as back-end tables or fields. However, content like series and worksheets are not upgraded. Choose this option only if your application is highly customized and does not follow the standard baseline Oracle application configuration (standard data model).

    • Application and Platform Upgrade: Both the software functionality and the database schema are upgraded. Choose this option if your application includes few or no customizations to the standard baseline Oracle application configuration (standard data model).You must select this option to enable certain application features, including Configure to Order (CTO) and Service Parts Forecasting (SPF).

      You must also select this option if you are installing the Oracle In-Memory Consumption-Driven Planning (CDP) module.


    See Additional Upgrade Steps for more information on upgrading from different application versions.

    Note: An application upgrade assigns all of the available series to user dm of the Oracle Demantra Demand Management application. This ensures that all new series are available to at least one username after the upgrade. To restrict access to these series after upgrading, remove them from specific usernames using Business Modeler (Security > Create/Modify User).
    BAL Upgrade Options After Application and Platform Upgrade option chosen Specify the type of application upgrade:

    • Automatic Upgrade: Schema objects and database are updated based on global upgrade preferences. New objects are inserted and overlapping objects are retained without change, duplicated, or aligned to the application standard.

    • Manual Upgrade: You can specify a different upgrade action by object. For new objects, select insert; for overlapping objects, select insert duplicate, align to the new, or ignore.


    You can update the upgrade actions for schema objects individually using the Business Application Language (BAL). Oracle recommends this option if you want more control in how the database schema is upgraded. If you choose this option, Oracle recommends that you read the following:
    Automatic Upgrade Options After Automatic Upgrade chosen Specify global handling of schema object conflicts between source and destination databases:

    • Overlapping object definitions: Choose to merge the source and destination objects, retain the source object by creating a duplicate object in the destination database, or ignore the new object.

    • New objects: Choose to insert or not insert new objects.
    Upload Dump If you choose Replace schema with new application file in the Schema Options screen Select to install either:

    • Standard Application: Standard Oracle Demantra best practices business configuration

    • Custom Application: Custom Oracle Demantra data model. If you load your own database dump file, you must also provide the name of the database user who performed that export.
    JVM Configuration (pop-up dialog) If Custom Application is selected in the Upload Dump screen and you are using a 32-bit JVM Specify the following JVM settings:
    JVM Path - If you are upgrading a large schema and are using a 32-bit JVM, then the JVM Path should be updated to refer to a 64-bit JVM.
    Max Memory Allocation (memory in GB) - You should allocate at least 4GB of RAM.

    Note: If the error message "Could not create the Java Virtual Machine" appears, exit the Demantra installer, and then perform the following:

    1. From the Windows client, go to Start > Control Panel > System > Advanced.

    2. Click Environment Variables.

    3. In the System Variables section, click New, enter " _JAVA_OPTIONS" as the Variable Name, and set its value to -Xmx512M.

    4. Click OK to save the changes.

    5. Re-run the Demantra installer.
    Select Tablespaces If replacing a database user or if database user does not exist. Specify the default tablespace you planned in the Installer Options Worksheet.

    Important: The default data tablespace is the only tablespace used by Demantra.
    Language Selection Always Select one or more languages for your Oracle Demantra installation. The default language is English and the other choices are:

    • Chinese Simplified

    • Chinese Traditional

    • Canadian French

    • Japanese

    • Korean

    • Portuguese (Latin America)

    • Russian

    • Spanish (Latin America)

    • French

    • German

    • Turkish

    • Italian

    • Dutch


    If you need to add or remove languages after upgrading or installing, rerun the Installer. For more information, see:
    The Installer is available only in U.S. English.

  12. Specify details for the Oracle Demantra web site (if installing web-based software).

    Screen When Screen is Displayed Action/Notes
    Specify Web Address If installing web-based software Specify the starting point of all Oracle Demantra Web addresses. You specify two basic parts that are used together:

    • Root Address is the root URL of the Web site.

    • Virtual Directory is the next section of the Oracle Demantra URL. This is case sensitive.


    The bottom part of this screen shows you how these are used together. See Installer Options Worksheet.

    Note: The Installer uses the database server name to initialize the root address that is generally suitable only for demo installations.

  13. Optionally specify details of Oracle Demantra administrator e-mail account.

    Screen When Screen is Displayed Action/Notes
    Designate Administrator Account Always Click one of the radio buttons to indicate whether to configure Oracle Demantra so that it can automatically send e-mail from within workflows. Specify the account details.
    See Designate Administrator Account for more information.

  14. Install the files and load or upgrade the database.

    Screen When Screen is Displayed Action/Notes
    Pre-Installation Summary Always Review the installation options you have chosen and, if you are satisfied, click Install. To make changes, click Back until you reach the appropriate screen.
    Wait for the installation process to complete. Among other actions, the Installer runs a database process that creates or updates the database user.
    Question (procedures log) Always Click Yes to view the procedures log.
    Information If you choose to view the procedures log Scan for any problems. In a particular, check for any procedures, functions, or views that are noted as invalid:

    • If you are installing a new system, all procedures, functions, and views should be valid.

    • If you are upgrading an existing system, the Installer will consider any existing custom procedures, functions, or views as invalid. Carefully check the list to be sure that you recognize the items as custom items.

    • If you see an error referring to the table mdp_matrix, you will have to set the system date in the correct format (as described in Basic Preparation Checklist) and then run the Installer again.


    You can also view the log afterwards; see Checking the Log Files and Tables.

  15. Install Java.

    Screen When Screen is Displayed Action/Notes
    Question (Java) If Java is not yet installed Click Yes to install Java components. The Oracle Installer launches the installer for JRE.
    After Java is installed, you are returned to the Oracle Demantra installation.
    If you decide not to install Java you can install it later from http://www.java.com.

  16. Specify the application password for the primary application owner(s).

    Screen When Screen is Displayed Action/Notes
    User Details New installations
    Demantra upgrade installations where additional components are being added.
    If installing or upgrading to 12.2.4 and later you will be prompted to enter a default password for the SysAdmin user. If you are upgrading from a previous release and a user called 'SysAdmin' already exists, this user will be appended with a number, for example "SysAdmin1." For details about this user, see the Oracle Demantra Implementation Guide.    		 New installationss: For each software component installed, specify a password for the primary application/component owner. Confirm the password. Only those components selected as part of the install set are shown.
    Demantra upgrades: Specify the passwords for any new software components being installed. The pre-upgrade software components retain their existing passwords, and are not displayed. For example, if you had only Demand Management before but are installing S&OP as part of your upgrade, you'll be prompted to enter a password for only S&OP.

    Passwords must adhere to the following rules:

    • Length must be 8-12 characters.

    • At least one character must be upper case.

    • At least one digit or special character must be included.

    • Password should not be a Security Dictionary Word. Disallowed words are stored in the table: SECURITY_DICTIONARY.

  17. Specify final details.

    Screen When Screen is Displayed Action/Notes
    InstallShield Wizard Complete Always Click the check box if you want to view the release notes. Click Finish to exit the Installer.

Review List of High Priority Patches

For a list of high priority patches for Oracle Demantra, see My Oracle Support Note 470574.1.