Installing Enterprise Back Office on Oracle Database

This chapter describes the prerequisites, instructions, and verification steps for installing the Enterprise Back Office databases on Oracle Database:

• Enterprise Back Office Database Configurations

• Installing the Enterprise Back Office Database

• Verifying the Database Installation

• Enterprise Back Office Database Configurations
  
• Installing the Enterprise Back Office Database
  
• Verifying the Database Installation
  

Enterprise Back Office Database Configurations

Oracle MICROS recommends setting the following Oracle Database configurations when creating the database instance and before running an Enterprise Back Office product installer. While some configurations can be changed after the installation, preparing the database instance prior to schema installation can prevent unexpected errors and problems.

Oracle Database Configuration for Enterprise Back Office Database

Use the following table for a set of guidelines for setting up the Oracle Database instance for Enterprise Back Office:

Parameter	Recommended Value
Instance Name	<CustomerName><Environment ID><EnvironmentPurpose P/S/T>MM For example, for customer ABC, environment ID 1, and environment purpose P for production: ABC01PMM
db_block_size	16384
open_cursors	20000
db_recovery_file_dest_size	Set as the amount of storage allocated to FRA and DATA.
job_queue_processes	64
aq_tm_processes	1
session_cached_cursors	100
optimizer_mode	first_rows_10
optimizer_index_caching	20
optimizer_index_cost_adj	20
cusrsor_sharing	exact
processes	1024
sga_max_size	Set as 50% of database RAM, to be tuned by the DBA during the life of the environment.
sga_target	Set as the same value as sga_max_size.
pga_target	Set as 25% of sga_target.

Oracle Database Tablespaces for Enterprise Back Office Database

Make sure to create the following tablespaces in the Enterprise Back Office database. Each tablespace requires Transparent Data Encryption (TDE) encryption.

• COREDB

• PORTALDB

• LOCDB

• LOC_INDX

• RTA

• PENTAHO or SMALLFILE

• CEDB

• SAML_INDX

• ORCLRNA_BIPLATFORM

• ORCLRNA_MDS

• TEMP

Oracle Database Configuration for Enterprise Back Office Aggregation Database

Use the following table for a set of guidelines for setting up the Oracle Database instance for the Aggregation database:

Parameter	Recommended Value
Instance Name	<CustomerName><Environment ID><EnvironmentPurpose P/S/T>AGG For example, for customer ABC, environment ID 1, and environment purpose P for production: ABC01PAGG
db_block_size	8192
open_cursors	20000
db_recovery_file_dest_size	Set as the amount of storage allocated to FRA and DATA.
job_queue_processes	64
aq_tm_processes	1
session_cached_cursors	100
optimizer_mode	first_rows_10
optimizer_index_caching	20
optimizer_index_cost_adj	20
cusrsor_sharing	exact
processes	1024
sga_max_size	Set as 50% of database RAM, to be tuned by the DBA during the life of the environment.
sga_target	Set as the same value as sga_max_size.
pga_target	Set as 25% of sga_target.
deferred_segment_creation	TRUE
_index_partition_large_extents	FALSE
_partition_large_extents	FALSE

Oracle Database Tablespaces for Enterprise Back Office Aggregation Database

Make sure to create the following tablespaces in the Enterprise Back Office Aggregation database. Each tablespace requires Transparent Data Encryption (TDE) encryption.

• AGGREGATE_DB

• AGGREGATE_INDX

• TEMP

Installing the Enterprise Back Office Database

1. Make sure Oracle Database is installed and running. If Oracle Database 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 Oracle Database.
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 Oracle Database 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 Oracle, enter the network port used by the database server, and then enter the database SID in Database SID. By default, Oracle Database uses port 1521.
   2. Fill out the rest of the form. For new installations, the form allows you to create passwords for the database users. For upgrades, you must enter the existing passwords.
7. On the Oracle Agg DB Config page, set up the Enterprise Back Office aggregation database:
   1. Enter the hostname, port, and SID of the aggregation database server.
   2. For new installations, create a password for the aggregation database. For upgrades, enter the existing aggregation database password.
8. For new installations:
   1. On the Additional Users page, create passwords for the database users.
   2. On the Sys Admin Password page, create a password for the sys admin account for the M super organization.
   3. On the Tablespace Locations page, enter the path to the folder for storing the database tablespace files.
   4. 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 Enterprise Back Office 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 Get 6.2 Oracle Tokens page, create a password for an Online Analytical Processing (OLAP) user account.
    2. 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 CORE_OPTIONS table containing MODULENAME=obieeRcu.

    3. On the Aggregation Users page, create passwords for the Aggregate_DB users.

       If you are installing the Aggregate_DB schema with the Enterprise Back Office database, enter the same password for the SA, RPT, and UTIL users.

    4. On the Get Oracle Aggregation tokens page, enter the path to the folder for storing the aggregation database tablespace and the aggregation database index tablespace.
12. On the Pre-Installation Summary page, click Install and allow the database installation or upgrade to complete.
13. After installation completes, increase the OPEN_CURSORS parameter for Oracle Database to at least 30,000.

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