Oracle Fusion Applications Installation: Installing Transactional Database

Previous: Installing Fusion Applications Provisioning Framework

To install Applications Transactional Database we need to run Oracle Fusion Applications Provisioning Wizard from <framework_location>/provisioning/bin

<framework_location> is same what we mentioned in previous post. i.e. /app/fusion

[oracle@fusion $ cd /app/fusion/provisioning/bin

We need to temporarily set JAVA_HOME to jdk6 directory shipped with the installation media

[oracle@fusion bin]$ export JAVA_HOME=/mnt/fusion/jdk6

[oracle@fusion bin]$ ./provisioningWizard.sh

Click Next

Click Next

Deselect security updates notification. Click Next

Provide database listener port (default is 1521, if you change this port please note to enter the new port in future screens where we have mentioned 1521)

Installer directory location will be the same as you created the stage setup or provisioning repository.

Provide a location for Oracle Base. Press TAB, next values should automatically be populated, if not, go back and click next again.

Enter dba as OSDBA group.

We have specified “fusiondb” as our database name. please note that if you are using any other name then don’t forget to change it in further screens whenever we have mentioned fusiondb.

You can keep simple password like “oracle” also but try to keep something like “oracle123” for all passwords so that it will follow requirements for all further passwords and it will be easier for you to remember all passwords in further installations.

Next it will finish the pre-requisite checks. Click Next

On next page, you can Save the summary. Click Install to start the installation.

Note: This will install the software as well as create a database named “fusiondb” which we provided earlier.

At this point it will prompt for running root.sh as root user.

Do not press Ok until run the following as root user in separate terminal window. Once following is executed, press Ok to continue.

[root@fusion ~]# /app/fusion/database/product/11.2.0/dbhome_1/root.sh

Check /app/fusion/database/product/11.2.0/dbhome_1/install/root_fusion_2012-01-1 5_12-29-28.log for the output of root script

[root@fusion ~]# tail -f /app/fusion/database/product/11.2.0/dbhome_1/install/root_fusion_2012-01-15_12-29-28.log

The following environment variables are set as:

ORACLE_OWNER= oracle

ORACLE_HOME= /app/fusion/database/product/11.2.0/dbhome_1

 

Creating /etc/oratab file…

Entries will be added to the /etc/oratab file as needed by

Database Configuration Assistant when a database is created

Finished running generic part of root script.

Now product-specific root actions will be performed.

Finished product-specific root actions.

It may take a few hours (at least on a non-high end host machine) and then installation will finish.

Important Note: After installation is finished we reduced the SGA and PGA (from 10GB to 2GB). We are doing this since we are running on a VM and have allocated total 2.5 or 3 GB RAM only. This is not recommended for production installation but since this is only a demo/development installation, you can safely do this. If you wish to keep it 10GB you can do it but this will increase the swap usage exponentially.

Since we are reducing the size of SGA and PGA, next step (RCU) may fail in pre-requisite check. So we will need to change the pre-req check xml file to look for lower value. We will explain this in next post.

Next:  Running Oracle Fusion Applications Repository Creation Utility (Applications RCU)

Installing Oracle Fusion Applications – steps

1. Installing Fusion Applications Provisioning Framework
   
2. Installing Oracle 11g Database (Applications Transactional Database)
   
3. Running Oracle Fusion Applications Repository Creation Utility (Applications RCU)
   
4. Creating another database for Oracle  Identity Management Infrastructure (optional)
   
5. Running Repository Creation Utility (RCU) for Oracle Identity Management components
6. Installing Oracle Identity and Access Management Components
   
7. Configuring Oracle Identity and Access Management components
   
8. Preparing Identity and Policy Stores
   
9. Creating a New Provisioning Plan
   
10. Provisioning an Applications Environment

(Based on Oracle Metalink note: 783188.1 as on 3-Mar-2009)

This document is divided into the following sections:

• Section 1: Terminology
• Section 2: Supported Scenarios
• Section 3: References

The most up-to-date version of this document can be obtained in Note 783188.1.

Section 1: Terminology

Cloning an Oracle E-Business Suite system that uses an Oracle Real Application Clusters (Oracle RAC) enabled database involves numerous different technology components and steps, and would therefore be a complex, error-prone process if carried out manually.

To speed up, simplify, and enhance reliability of the process, Oracle offers the following tools for use in cloning RAC Enabled Oracle E-Business Suite systems:

• Rapid Clone – Command-line tool
• Oracle Application Management Pack for Oracle E-Business Suite (AMP) – GUI-based tool used for automated end-to-end cloning

This document provides details of the RAC scenarios that are currently certified for cloning using these tools. Other scenarios are planned as shown.

Note: Scenarios not shown are not supported.

Section 2: Supported Scenarios

The following table illustrates the various cloning permutations that exist with different versions of Oracle E-Business Suite and its components, operating system software, and the cloning tools available.

Key:

N/A = Not Applicable
TBD = To Be Decided