Installing Enterprise Back Office on Microsoft SQL Server

This chapter describes the prerequisites, instructions, and verification steps for installing the Enterprise Back Office databases on Microsoft SQL Server:

Parent topic: Enterprise Back Office on Two Servers

Installing the Enterprise Back Office Database

  1. Make sure Microsoft SQL Server is installed and running. If Microsoft SQL Server contains a previous deployment of Oracle Business Intelligence, or if the database installation previously failed or was interrupted, follow the instructions in Uninstalling Oracle Business Intelligence Schemas from Microsoft SQL Server.
  2. Extract the following from the installation file archive in the same file structure. Do not extract the files to a folder structure that contains spaces.

    /RCU/

    DBInstall.exe

  3. Double-click DBInstall.exe to launch the database installation wizard.
  4. On the Choose Installation or Upgrade page, select whether you are upgrading an existing database or installing a new shell database.

    If you are installing a new shell database, install a clean Microsoft SQL Server with no Reporting and Analytics objects.

  5. On the Choose Install Set page, select myMicros.
  6. On the MyMicros Database Information page:
    1. To set up the Enterprise Back Office database, select SQL Server, enter the network port used by the database server. By default, the Microsoft SQL Server uses port 1433.
    2. Fill out the rest of the form. For new installations, the form allows you to create passwords for the database users. For upgrades, enter the login credentials to the existing Microsoft SQL database server in the Upgrade login and password fields, and then enter the existing database passwords.
  7. On the SQL Agg DB Config page, set up the Enterprise Back Office aggregation database:
    1. Enter the hostname and port of the aggregation database server.
    2. If you are performing an upgrade, in the Upgrade Login and Upgrade Password fields, enter the login credentials to the existing Microsoft SQL database server.
    3. In the Additional Connection Parameters field, enter any required connection strings.
  8. For new installations:
    1. On the Sys Admin Password page, create a password for the sys admin account for the M super organization.
    2. On the Tablespace Locations page, enter the path to the folder for storing the database tablespace files.
    3. On the Tablespace location - SAML page, enter the path to the folder for storing the SAML database tablespace file.

      If you are upgrading the database, the installation wizard does not show this page if you did not perform the versionnum prerequisite.

  9. On the MyMicros Database Information - Master page, enter the database administrator (DBA) login credentials for the Reporting and Analytics database.
  10. On the MyMicros Database Information - Aggregation Master page, enter the database administrator (DBA) login credentials for the aggregation database.
  11. For new installations:
    1. On the Repository Creation Utility page, create a password for the MDS and BIPLATFORM database schema.

      This screen shows during upgrades if you deleted or set OPTIONVALUE=true for the record in the COREDB.DB_OPTIONS table containing MODULENAME=obieeRcu.

    2. On the RCU File Locations - SQL Server page, enter the path to the folder for the Repository Creation Utility database and log file.
    3. On the Get SQL Server Aggregation tokens page, enter the path to the folder for storing the aggregation database and the database log file.
  12. On the Pre-Installation Summary page, click Install and allow the database installation or upgrade to complete.

Parent topic: Installing Enterprise Back Office on Microsoft SQL Server

Verifying the Database Installation

  1. Verify that there is a versionnum entry for the Enterprise Back Office database version to which you upgraded in the following databases:

    • AGGREGATE_DB.AGG_VERSION_DB

    • BIREPOS.BIREPOS_VERSION_DB

    • CEDB.CE_VERSION_DB

    • COREDB.CORE_VERSION_DB

    • LOCATION_ACTIVITY_DB.VERSION_DB

    • PORTALDB.PORTAL_VERSION_DB

    • QUARTZ.QUARTZ_VERSION_DB

    • RTA.RTA_VERSION_DB

  2. Check the following logs for errors and exceptions:

    • root\temp\DBinstaller.log

    • root\temp\Logs\eBusiness_DatabaseUpgrade_Install_dateandtime.log

Related Topics

Parent topic: Installing Enterprise Back Office on Microsoft SQL Server