8 Install Oracle Fusion Applications Transaction Database

Table 8-1 shows the commonly recommended initialization parameters.

WARNING:

When the Provisioning Wizard is used to install the database using the dbca template, the default values for the disk_asynch_io and filesystemio_options parameters are as follows:

disk_asynch_io is set to TRUE

filesystemio_options is set to the default value based on the platform where the database is installed. It could be either none, setall, asynch, or diskio. To verify that the filesystemio_options parameter is using the default value, run the following query: "select isdefault from v$parameter where name='filesystemio_options". If it returns TRUE, the default value is set.

If the parameter value is changed from the original default value to another value and then change it back to the original default value, the default value still remains FALSE.

The following Warning messages is displayed based on the values set:

If disk_asynch_io is set to FALSE and filesystemio_options is set to the default value, a Warning message is displayed recommending setting the value for disk_asynch_io to TRUE.

If disk_asynch_io is set to FALSE and filesystemio_options is not set to the default value, a Warning message is displayed recommending setting the value for disk_asynch_io to TRUE for the best performance optimization.

Due to the addition of Fusion Applications Read Only Diagnostic schemas, the database audit trail is turned on via the audit_trail=DB, EXTENDED initialization parameter to monitor all database activities with the FUSION_RO and FUSION_ERO schema users. To minimize impact to performance, it is also recommended that auditing system operations be excluded via the AUDIT_SYS_OPERATIONS = FALSE initialization parameter. Furthermore, if the Fusion Applications database is created manually (and the Provisioning Wizard is not used) it is recommended to move the AUDIT segment from the SYSTEM tablespace to the SYSAUX tablespace and create a custom index for audit. Do so as a post installation task after provisioning the Oracle Fusion Applications Environment.

For more information about setting the kernel parameter value, see Set the Kernel Parameter Value.

For more information about tuning Oracle database, see Manage Oracle Database for Oracle Fusion Applications in the Oracle Fusion Applications Administrator's Guide.

Table 8-2 lists the mandatory Oracle Database (Enterprise Edition and RAC) patches required for Oracle Fusion Applications. The list is organized by operating system platforms.

• If Oracle Database is installed using the Provisioning Wizard, these patches are automatically applied.

• If Oracle Database is installed manually, apply the mandatory database patches by following the instructions detailed in Run RUP Lite for RDBMS.

For both scenarios described above, ensure that the following steps are completed before running the Oracle Fusion Applications RCU:

• Complete the manual postinstallation tasks detailed in the patch readme file (Complete Database Patch Postinstallation Tasks).

• Refer to Oracle Database patch details listed in Additional Patches for the Tech Stack in the latest Oracle Fusion Applications Release Notes for any additional patches required for the current release.

Create directories in the file system accessible by the database which is referenced by the DBA directories used by Oracle Fusion Applications. These directories are specified in the Oracle Fusion Applications Installation Workbook, Database tab, FA transaction Database table and they are:

• RCU APPLCP_FILE_DIR

• RCU APPLLOG_DIR

• RCU FUSIONAPPS_PROV_RECOVERY_DIR (OBIEE Backup Dir)

• RCU OTBI_DBINSTALL_DUMP_DIR (OTBI Dump File Directory)

• RCU FUSIONAPPS_DBINSTALL_DP_DIR (FA Dump File Directory)

For more information about the specific requirements for these directories, see Oracle Fusion Applications RCU Directories.

Complete the following steps to make the Oracle Fusion Applications software available in the host where it is run.

• Locate the appropriate Oracle Fusion Applications RCU software for a specific platform. For Linux, go to REPOSITORY_LOCATION/installers/apps_rcu/linux to find the rcuHome_fusionapps_linux.zip file. For Windows, go to REPOSITORY_LOCATION/installers/apps_rcu/windows and locate the rcuHome_fusionapps_win.zip file. These files were staged when the installer repository was created.

• Extract the contents of rcuHome_fusionapps_linux.zip (or rcuHome_fusionapps_win.zip) to a directory (APPS_RCU_HOME) on a Windows or Linux machine where the Oracle Fusion Applications RCU is run. All dependent components that the Oracle Fusion Applications RCU needs are included in this zipped file.

Complete the following steps to make dmp files available on the database server. If the Oracle Fusion Applications database is configured as multiple RAC nodes, make sure the dmp files are accessible from all RAC nodes.

• Locate the file APPS_RCU_HOME/rcu/integration/fusionapps/export_fusionapps_dbinstall.zip.

• Unzip export_fusionapps_dbinstall.zip to the directory specified for FUSIONAPPS_DBINSTALL_DP_DIR.

• Go to APPS_RCU_HOME/rcu/integration/biapps/schema and locate the otbi.dmp file.

• Copy otbi.dmp to OTBI_DBINSTALL_DUMP_DIR.

Note the following requirement when installing a transaction database on a UNIX platform:

• Verify that the length of the PATH environment variable is less than 900 characters. Use this command to check the character count:

  env | grep ^PATH= | wc -m
  

To start the Provisioning Wizard, do the following:

Table 8-3 shows the steps necessary to install a transaction database. For help with any of the interview screens, click Help.

If the values required are not entered correctly, the error and warning messages are displayed at the bottom of the screen.

On the Database Install Configuration interview screen, specify values for these database configuration parameters.

• Database Listener Port: The port number designated for the database server. The default port for Oracle Database is 1521.

  Tip:

  This value is available in the Oracle Fusion Applications Installation Workbook, Database tab, FA Transactional Database table, FA DB Instances row.

• Installers Directory Location: Enter the path to the REPOSITORY_LOCATION directory created when the provisioning repository was downloaded.

  Tip:

  This value is available in the Oracle Fusion Applications Installation Workbook, Storage tab, Temporary Shared Storage table, Installers Directory Location row.

• Oracle Base: Enter the top-level directory for Oracle software installations. The path can be changed based on the requirements.

  Tip:

  This value is available in the Oracle Fusion Applications Installation Workbook, Database tab, FA Transactional Database table, FA DB Oracle Home (The ORACLE_BASE is part of the ORACLE_HOME).

• Software Location: Accept the default value or enter the Oracle home directory path that points to where the data files reside. The directory path must not contain spaces.

  Tip:

  This field is automatically filled. This value is available in the Oracle Fusion Applications Installation Workbook, Database tab, FA Transactional Database table, FA DB Oracle Home row.

• Database File Location: Accept the default value or enter the path to the .dbf, .dtl, and .log files.

  Tip:

  This value is available in the Oracle Fusion Applications Installation Workbook, Database tab, FA Transactional Database table, FA DB Datafiles Location row.

• OSDBA Group: The UNIX operating system group that the database administrator is a member of. This field is displayed only if the platform detected by the installer is UNIX.

  Tip:

  If the database is installed on the FA shared storage as defined in the Oracle Fusion Applications Installation Workbook, Storage tab, Shared Storage table, FA Shared row, OS Group Owner column.

• Global Database Name: Enter a name to distinguish this database instance from other Oracle Database instances running on the same host. The name can be written as database name or database name.domain name. This is the database service name.

  Tip:

  This value is available in the Oracle Fusion Applications Installation Workbook, Database tab, FA Transactional Database table, FA DB Service Namerow.

• Administrative Password: Specify a valid password. Retype the password to Confirm.

For more information about configuring OCM, see Introduction to Oracle Configuration Manager in the Oracle Configuration Manager Installation and Administration Guide.

• Configure the database listener as described in the Oracle 11g Release 2 Documentation Library.

• After completing the configuration, start the database listener.

Use the Oracle Database Configuration Assistant (DBCA) to create the transaction database from the database template that is shipped with Oracle Fusion Applications software. This template contains the database structure and features, but is not seeded. It is generic for use across platforms.

Instructions on database installation and configuration can be found in the Oracle 12c Release 1 Documentation Library.

If the database template is not used, ensure that the database configuration parameters are aligned with the values specified in Minimum Configuration Parameters for Oracle Database.

Use DBCA to manually create an instance of Oracle Database from the nonseeded database template that is shipped with Oracle Fusion Applications software.

To create a single-node Oracle Database instance:

1. Review and edit the nonseeded database template at FAPROV_HOME/provisioning/template/dbca/empty_database_12.1.dbt or empty_database_12.1.large.dbt (for a large database instance).

2. Navigate to the database ORACLE_HOME/bin directory and execute the following command. Make appropriate changes based on the selected database template.

   dbca -silent -createDatabase -templateName\
   FAPROV_HOME/provisioning/template/dbca/empty_database_12.1.large.dbt  \
   -gdbName "ORACLE_SID" \
   -sid "ORACLE_SID" \
   -sysPassword "SYS_PASSWORD" \
   -systemPassword "SYSTEM_PASSWORD" \
   -emConfiguration "NONE" \
   -characterSet "AL32UTF8" - \
   -nationalCharacterSet "AL16UTF16" \
   -variables ORACLE_BASE=ORACLE_BASE, ORACLE_HOME=ORACLE_HOME \
   -datafileDestination DATAFILE_LOC
   

   Use the following steps to set the AUDIT_TRAIL parameter:

   1. Login to SQL*Plus using the sys as sysdba identity.

   2. Run the following command to set AUDIT_TRAIL parameter: alter system set AUDIT_TRAIL=db,extended scope=spfile;

   3. Restart the database by running the following commands:

      shutdown immediate
      startup
      

   Replace the following variables with the appropriate values:

   • FAPROV_HOME: Home of Oracle Fusion Applications Provisioning framework.

   • ORACLE_SID: Global database name of the Oracle Fusion Applications database.

   • SYS_PASSWORD: Password for the SYS user. The SYS schema is the location of base tables and views.

   • SYSTEM_PASSWORD: User SYSTEM password. The user can create additional tables and views.

   • ORACLE_BASE: Top-level directory for the database installation.

   • ORACLE_HOME: Oracle home of the database installation.

   • DATAFILE_LOC: Physical location of the files that store the data of all logical structures in the database.

How to Create an Oracle RAC Database Instance from the Template

Use DBCA to manually create a database instance for each Oracle RAC node using the nonseeded database template that is shipped with Oracle Fusion Applications software.

To create an Oracle RAC database instance:

See Run RUP Lite for RDBMS in a Single Instance Database in the Oracle Fusion Applications Upgrade Guide.

See Complete Database Patch Postinstallation Tasks.

After completing the steps in Getting Ready, run the Oracle Fusion Applications RCU from (UNIX) APPS_RCU_HOME/bin or (Windows) APPS_RCU_HOME\bin with the following command:

UNIX: ./rcu

Windows: rcu.bat

The Oracle Fusion Applications RCU is available only on Linux and Windows platforms. On Windows systems, do not extract the rcuHome_fusionapps_win.zip file to a directory whose name contains spaces.

Table 8-4 lists the steps for running the Oracle Fusion Applications RCU. For help with any of the screens, click Help.

Specify the following connection credentials:

• Database Type: Select the database type.

• Host Name: Enter the name of the node on which the database resides, for example, myhost.mydomain.com. For Oracle RAC, specify the VIP name or one of the node names as the host name.

• Port: Specify the listener port number for the database. The default port number is 1521.

• Service Name: This is the global database name. To obtain the service name, see the SERVICE_NAMES parameter in the database initialization file. If the service name is not in the database initialization file, use the global name in DB_NAME and DB_DOMAIN. For Oracle RAC, specify the service name of one of the nodes, for example, examplehost.exampledomain.com.

  Tip:

  This value is available in the Oracle Fusion Applications Installation Workbook, Database tab, FA Transactional Database table.

• User Name: Supply the name of the user with DBA or SYSDBA privileges. The default user name with SYSDBA privileges is SYS.

• Password: Enter the password for the database user.

• Role: Select Normal or SYSDBA. All schemas installed for Oracle Database require the SYSDBA role. For Oracle Internet Directory (OID) database schemas, use SYS and SYSDBA.

Enter a pre-existing physical directory on the database server where the custom variables for each component should be created.

• FUSIONAPPS_DBINSTALL_DP_DIR: The directory on the database server where the export_fusionapps_dbinstall.zip is unzipped and the otbi.dmp file is copied (see Make dmp Files Available on the Database Server).

  Tip:

  This value is available in the Oracle Fusion Applications Installation Workbook, Database tab, FA Transactional Database table, RCU OTBI_DBINSTALL_DUMP_DIR row.

• APPLCP_FILE_DIR: Used by Oracle Enterprise Scheduler to store the log and output files. This directory must be valid on the database server with read-write permissions to the database owner. For Oracle RAC, must point to a location that is shared across all nodes.

  Tip:

  This value is available in the Oracle Fusion Applications Installation Workbook, Database tab, FA Transactional Database table, RCU APPLCP_FILE_DIR row.

• APPLLOG_DIR: Location of the PL/SQL log files from Oracle Fusion Applications PL/SQL procedures on the database server. Ensure that the database owner has read-write privileges. For Oracle RAC, this value must point to the same location that exists in each node or a location shared across all nodes.

  Tip:

  This value is available in the Oracle Fusion Applications Installation Workbook, Database tab, FA Transactional Database table, RCU APPLLOG_DIR row.

• OBIEE Backup Directory: Location of the Oracle Business Intelligence Enterprise Edition dump files. These files are used for enabling a restart action.

MANDATORY: Directories must be manually created on the database server and enter the full file path to the directories as the corresponding custom variable.

This value is available in the Oracle Fusion Applications Installation Workbook, Database tab, FA Transactional Database table, RCU FUSIONAPPS_PROV_RECOVERY_DIR row.

Secure Enterprise Search

• Do you have Advanced Compression Option (ACO) License? Yes (Y) or No (N): Default is No.

• Do you have Oracle Partitioning option License? Yes (Y) or No (N): Default is No.

Primary and Work Repository

Note: The default values are the only valid values. If any of these values is changed, the ODI-related provisioning process does not work.

• Primary Repository ID: Default = 501

• Supervisor Password: Enter and confirm the ODI supervisor password.

• Work Repository Type: (D) Development or (R). Default = D

• Work Repository ID: Default = 501

• Work Repository Name: Default = FUSIONAPPS_WREP

• Work Repository Password: Enter and confirm the Work Repository supervisor.

Oracle Transactional BI

• Directory on the database server where Oracle Transactional Business Intelligence import and export files are stored.

Activity Graph and Analytics

• Install Analytics with Partitioning (Y/N): Default is N.