Ora Training Blog

Previous: Install Oracle Identity and Access Management Components

 

Important mandatory patches to be applied before proceeding further

 

Patch Oracle Identity Management (IDM)

[Patches under /u02/stage/installers/pltsec/patch]

 

1. Patch 14178750 for Oracle Internet Directory (OID)

2. Patch 14249414 for OID Tools

3. Patch 14034245 for Oracle Virtual Directory

4. Patch 13531666 for T2P OID/OVD Plug-in

 

Patch Oracle Common

[Patches under REPOSITORY_LOCATION/installers/oracle_common/patch]

 

IDM Patches

1. Patch 14222702 for Oracle Platform Security for Java

2. Patch 14051044 for Oracle Web Services Manager

3. Patch 14054792 for Oracle Virtual Directory LibOVD

4. Patch 13787495 for Oracle Access Manager Configuration Tool

5. Patch 13713159 for Oracle Access Manager Registration Tool

6. Patch 14228599 for OAM Identity Asserter

7. Patch 14247121 for OID Client Tool

 

Non-IDM Patches

1. Patch 12556084 for Oracle XML Developers Kit

2. Patch 13639146 for Enterprise Manager

3. Patch 13805105 for Oracle Patch Set Assistant MDS Schema

4. Patch 13897534 forT2P Framework

5. Patch 14099904 for Oracle HTTP Client

6. Patch 14226604 for Oracle WebCenter Patch# 3

7. Patch 14296054 for Oracle JDeveloper MLR5

8. Patch 13511837 for Oracle XML SQL Utility

9. Patch 13713541 for Oracle Patch Set Assistant Backports

10. Patch 13807335 for Oracle JDeveloper MDS Schema

11. Patch 14246779 for Oracle SOA Bundle

12. Patch 14109342 for Oracle Web Services

13. Patch 14326776 for Oracle FMW Diagnostics

 

Patch Identity and Access Management (IAM)

[Patches under REPOSITORY_LOCATION/installers/idm/patch]

 

1. Patch 13399365 for Oracle Identity Manager Bundle Patch 2 (OIM BP-02)

2. Patch 14193741 for Oracle Identity Manager Patch on top of OIM BP-02

3. Patch 12418680 for Oracle Applications Access Control Governor (OAACG) Client

4. Patch 14179564 for Oracle IDM Tools

5. Patch 14248646 for Oracle IDM Scripts

6. Patch 13115859 for Oracle Access Manager Bundle Patch 2 (OAM BP-02)

7. Patch 14171065 for Oracle Access Manager Patch on top of OAM BP-02

 

Patch SOA

[Patches under REPOSITORY_LOCATION/installers/soa/patch]

 

1. Patch 14246779 for Oracle SOA Bundle 6

2. Patch 13897549 for Oracle SOA Plug-in fixes for T2P

3. Patch 13263008 for Oracle Wireless

 

Patch Web

[Patches under REPOSITORY_LOCATION/installers/webtier/patch]

 

1. Patch 14264658 for Oracle HTTP Server (OHS)

2. Patch 13897557 for OHS Plug-in fixes for T2P

Patch Webgate

[Patches under REPOSITORY_LOCATION/installers/webgate/patch]

 

1. Patch 14329669 for Oracle WebGate

 

Patch Database Server

[Patches under REPOSITORY_LOCATION/ installers/database/patch]

 

Patch 14019600

 

Patch Database Client

[Patches under REPOSITORY_LOCATION/ installers/dbclient]

 

1. Patch 7256230

 

Patch Oracle Identity Management (IDM)

[Patches under /u02/stage/installers/pltsec/patch]

 

Set ORACLE_HOME

-bash-3.2$ export ORACLE_HOME=/app/fusion/fmw/idm

 

Patch 14178750

-bash-3.2$ cd /u02/stage/installers/pltsec/patch/14178750

-bash-3.2$ cd /u02/stage/installers/pltsec/patch/14178750

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

Is the local system ready for patching? [y|n]

y

…

OPatch succeeded.

 

Patch 14249414

-bash-3.2$ cd /u02/stage/installers/pltsec/patch/14249414

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

Is the local system ready for patching? [y|n]

y

User Responded with: Y

…

OPatch succeeded.

 

Special Instructions:

———————

 

If the oidldapd server is running on ports below 1024, then after the

patch is applied, the ownership of the “$ORACLE_HOME/bin/oidldapd”

process must be changed to root and the sticky bit set.

 

To do this, run the $ORACLE_HOME/oidRoot.sh script as root user.

 

Patch 14034245

-bash-3.2$ cd /u02/stage/installers/pltsec/patch/14034245

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

OPatch succeeded.

 

Patch 13531666

-bash-3.2$ cd /u02/stage/installers/pltsec/patch/13531666

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

OPatch succeeded.

 

 

Patch Oracle Common

[Patches under REPOSITORY_LOCATION/installers/oracle_common/patch]

 

Set ORACLE_HOME

-bash-3.2$ export ORACLE_HOME=/app/fusion/fmw/oracle_common

 

IDM Patches

1. Patch 14222702

-bash-3.2$ cd /u02/stage/installers/oracle_common/patch/14222702

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

OPatch succeeded.

 

2. Patch 14051044

-bash-3.2$ cd /u02/stage/installers/oracle_common/patch/14051044

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

OPatch succeeded.

 

3. Patch 14054792

-bash-3.2$ cd /u02/stage/installers/oracle_common/patch/14054792

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

OPatch succeeded.

 

4. Patch 13787495

-bash-3.2$ cd /u02/stage/installers/oracle_common/patch/13787495

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

Is the local system ready for patching? [y|n]

Y

…

OPatch succeeded.

 

5. Patch 13713159

-bash-3.2$ cd /u02/stage/installers/oracle_common/patch/13713159

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

OPatch succeeded.

 

6. Patch 14228599

-bash-3.2$ cd /u02/stage/installers/oracle_common/patch/14228599

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

OPatch succeeded.

 

7. Patch 14247121

-bash-3.2$ cd /u02/stage/installers/oracle_common/patch/14247121

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

OPatch succeeded.

 

 

Non-IDM Patches

1. Patch 12556084

-bash-3.2$ cd /u02/stage/installers/oracle_common/patch/12556084

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

Is the local system ready for patching? [y|n]

Y

…

OPatch succeeded.

 

2. Patch 13639146

-bash-3.2$ cd /u02/stage/installers/oracle_common/patch/13639146

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

Is the local system ready for patching? [y|n]

Y

…

OPatch succeeded.

 

3. Patch 13805105

-bash-3.2$ cd /u02/stage/installers/oracle_common/patch/13805105

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

Is the local system ready for patching? [y|n]

Y

…

OPatch succeeded.

 

4. Patch 13897534

-bash-3.2$ cd /u02/stage/installers/oracle_common/patch/13897534

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

OPatch succeeded.

 

5. Patch 14099904

-bash-3.2$ cd /u02/stage/installers/oracle_common/patch/14099904

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

Is the local system ready for patching? [y|n]

Y

…

OPatch succeeded.

 

6. Patch 14226604

-bash-3.2$ cd /u02/stage/installers/oracle_common/patch/14226604

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

OPatch succeeded.

 

7. Patch 14296054

-bash-3.2$ cd /u02/stage/installers/oracle_common/patch/14296054

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

OPatch succeeded.

 

8. Patch 13511837

-bash-3.2$ cd /u02/stage/installers/oracle_common/patch/13511837

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

Is the local system ready for patching? [y|n]

y

…

OPatch succeeded.

 

9. Patch 13713541

-bash-3.2$ cd /u02/stage/installers/oracle_common/patch/13713541

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

Is the local system ready for patching? [y|n]

y

…

OPatch succeeded.

 

10. Patch 13807335

-bash-3.2$ cd /u02/stage/installers/oracle_common/patch/13807335

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

Do you want to proceed? [y|n]

y

…

Is the local system ready for patching? [y|n]

y

…

OPatch succeeded.

 

11. Patch 14246779

-bash-3.2$ cd /u02/stage/installers/oracle_common/patch/14246779

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…
Do you want to proceed? [y|n]

y

…

OPatch succeeded.

[ did not do following since it seems it is not required

2. Redeploy the sca_UpdateSOAMDS composite from $SOA_HOME/soa/prov directory

– Needed for the SOA Oracle Home only

– Not Needed for the Oracle Common Home

– Full details and requirements can be found in Bug 12703684 which

was done for the previous bundle.

]

 

12. Patch 14109342

-bash-3.2$ cd /u02/stage/installers/oracle_common/patch/14109342

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

Do you want to proceed? [y|n]

y

…

Is the local system ready for patching? [y|n]

y

…

OPatch succeeded.

 

13. Patch 14326776

-bash-3.2$ cd /u02/stage/installers/oracle_common/patch/14326776

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

Do you want to proceed? [y|n]

y

…

Is the local system ready for patching? [y|n]

y

…

OPatch succeeded.

 

[ Did not do following since we don’t have domain created yet.

Post Install Instructions:

————————–

– Apply the Click History WLS Template for your domain (i.e. set targets for all clusters and

servers). You can use config.sh or WLST to apply the template. The template file is located at

$MW_HOME/oracle_common/common/templates/applications/oracle.clickhistory_template_11.1.1.jar

]

 

 

 

Patch Identity and Access Management (IAM)

[Patches under REPOSITORY_LOCATION/installers/idm/patch]

 

Set ORACLE_HOME to iam

-bash-3.2$ export ORACLE_HOME=/app/fusion/fmw/iam

 

1. Patch 13399365 (Bundle patch)

Note: We will not do the post-steps here since we are yet to create Weblogic domain or OIM instance and the steps required are to be performed if you already have the domain.

 

Please complete the post steps once you have configured Weblogic and all manged servers since we cannot proceed without completing the post step mentioned below.

 

-bash-3.2$ cd /u02/stage/installers/idm/patch/13399365

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Is the local system ready for patching? [y|n]

y

…

OPatch succeeded.

 

(To be done only after configuring all managed servers)

-bash-3.2$ cd /app/fusion/fmw/iam/server/bin

-bash-3.2$ cp -pr weblogic.profile weblogic.profile.orig

-bash-3.2$ cp -p /u02/stage/installers/idm/patch/13399365/sample_weblogic.profile.fa /app/fusion/fmw/iam/server/bin/weblogic.profile

 

Modify the profile based on your environment

 

-bash-3.2$ ./patch_weblogic.sh

…

Buildfile: /app/fusion/fmw/iam/server/setup/deploy-files/setup.xml

[input]Enter the oim db password:

 

[input]Enter AdminServer password:

 

2. Patch 14193741

[ Need to check the post steps]

-bash-3.2$ cd /u02/stage/installers/idm/patch/14193741

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

Is the local system ready for patching? [y|n]

y

…

OPatch succeeded.

 

3. Patch 12418680

-bash-3.2$ cd /u02/stage/installers/idm/patch/12418680

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

OPatch succeeded.

 

4. Patch 14179564

[ It has post steps for Fusion Applications that has already been provisioned so ignored them]

-bash-3.2$ cd /u02/stage/installers/idm/patch/14179564

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

OPatch succeeded.

 

5. Patch 14248646

-bash-3.2$ cd /u02/stage/installers/idm/patch/14248646

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

OPatch succeeded.

 

6. Patch 13115859

[ The post steps are required only if you already have domain configured]

-bash-3.2$ cd /u02/stage/installers/idm/patch/13115859

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Is the local system ready for patching? [y|n]

y

…

OPatch succeeded.

 

7. Patch 14171065

-bash-3.2$ cd /u02/stage/installers/idm/patch/14171065

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

Is the local system ready for patching? [y|n]

y

…

OPatch succeeded.

 

 

Patch SOA

[Patches under REPOSITORY_LOCATION/installers/soa/patch]

 

Set ORACLE_HOME

-bash-3.2$ export ORACLE_HOME=/app/fusion/fmw/soa

 

1. Patch 14246779

-bash-3.2$ cd /u02/stage/installers/soa/patch/14246779

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

OPatch succeeded.

 

Note: This patch also needs to be applied on oracle_common home. But as you can see we have already applied it on oracle_common home earlier in above steps.

 

[ Pending following steps since it seems it is not required on fresh installation

Redeploy the sca_UpdateSOAMDS composite from $SOA_HOME/soa/prov directory

– Needed for the SOA Oracle Home only

– Not Needed for the Oracle Common Home

– Full details and requirements can be found in Bug 12703684 which

was done for the previous bundle.

]

 

2. Patch 13897549

-bash-3.2$ cd /u02/stage/installers/soa/patch/13897549

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

OPatch succeeded.

 

3. Patch 13263008

-bash-3.2$ cd /u02/stage/installers/soa/patch/13263008

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

OPatch succeeded.

 

Patch Web

[Patches under REPOSITORY_LOCATION/installers/webtier/patch]

 

Set ORACLE_HOME

-bash-3.2$ export ORACLE_HOME=/app/fusion/fmw/web

 

1. Patch 14264658

-bash-3.2$ cd /u02/stage/installers/webtier/patch/14264658

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

Is the local system ready for patching? [y|n]

y

…

OPatch succeeded.

 

2. Patch 13897557

-bash-3.2$ cd /u02/stage/installers/webtier/patch/13897557

-bash-3.2$ $ORACLE_HOME/OPatch/opatch apply

…

Do you want to proceed? [y|n]

y

…

OPatch succeeded.

Patch Database Server

[Patches under REPOSITORY_LOCATION/ installers/database/patch]

 

1. Patch 14019600

 

Already applied as part of DB Provisioning

-bash-3.2$ export ORACLE_HOME=/app/fusion/database/product/11.2.0/dbhome_1

-bash-3.2$ $ORACLE_HOME/OPatch/opatch lsinventory -patch | grep 14019600

Patch 14019600 : applied on Tue Dec 18 12:11:40 GST 2012

 

Patch Database Client

[Patches under REPOSITORY_LOCATION/ installers/dbclient]

 

1. Patch 7256230

[Ignored at the moment since the current files in DB Oracle home are higher version than provided by the patch]

Installing Oracle Fusion Applications – steps

1. Install Fusion Applications Provisioning Framework
2. Install Oracle 11g Database (Applications Transactional Database)
3. Run Oracle Fusion Applications Repository Creation Utility (Applications RCU)
4. Create another database for Oracle Identity Management Infrastructure (optional)
5. Run Repository Creation Utility (RCU) for Oracle Identity Management components
6. Install Oracle Identity and Access Management Components
7. Apply mandatory Patches
8. Configure Oracle Identity and Access Management components
9. Integrate Oracle Identity Manager (OIM) and Oracle Access Manager (OAM)
10. Create new Response File
11. Provision an Applications Environment

 

Next: Configure Oracle Identity and Access Management components

Previous: Install Oracle 11g Database (Applications Transactional Database)

Please note that RCU are available only for Windows and Linux platforms. Hence we may need to run the RCU on Windows or Linux machine which can connect to this database.

Fusion Applications stage already has both Applications and Fusion Middleware RCUs for Linux but for Windows only apps RCU is included in the installer.

For Windows Fusion Middleware RCU, you need to download V29675-01.zip or ofm_rcu_win_11.1.1.6.0_disk1_1of1.zip from
Oracle website or support website. We will update the links here.

Since we already published steps for Linux in our earlier post for Fusion installation on Linux, we will run RCUs on Windows instead.

Create a directory on your laptop or PC with Windows OS and call it APPS_RCU_HOME

For example, D:\fusion\apps_rcu

Go to <repository_location>/installers/apps_rcu/windows and locate the rcuHome_fusionapps_win.zip file. This file was staged when you created the installer repository.

Extract the contents of rcuHome_fusionapps_win.zip to a directory (APPS_RCU_HOME) on the client machine (your laptop or PC). All dependent components that Applications RCU needs are included in this zipped file.

This will create a folder named rcuHome for example D:\fusion\apps_rcu\rcuHome

Create a temporary directory on server. Make a note of the location.

You will need to enter this location when you specify a value for FUSIONAPPS_DBINSTALL_DP_DIR

For example /app/fusion/dp_dir

Locate and copy APPS_RCU_HOME/rcu/integration/fusionapps/export_fusionapps_dbinstall.zip to the directory you specified for FUSIONAPPS_DBINSTALL_DP_DIR.

Unzip export_fusionapps_dbinstall.zip to FUSIONAPPS_DBINSTALL_DP_DIR.

Now go to APPS_RCU_HOME/rcu/integration/biapps/schema and locate the otbi.dmp file.

Copy otbi.dmp to FUSIONAPPS_DBINSTALL_DP_DIR (where you unzipped the contents of export_fusionapps_dbinstall.zip).

To summarize, we are running the RCU with import data pump commands on Windows or Linux but since data pump requires dump files to be present on DB server, we are copying all required dump files to our Solaris DB server at /app/fusion/dp_dir directory

Launch Repository Creation Utility (RCU)

Run rcu.bat from D:\fusion\apps_rcu\rcuHome\bin

Click Next

Click Next

Enter the values as mentioned here and click Next

Once the prerequisites check is finished, click OK

Select all components and click Next

If you have modified the memory size (SGA/PGA) then you might get the following error.

RCU-6083:Failed – Check prerequisites requirement for selected component:FUSIONAPPS Please refer to RCU log at D:\fusion\apps_rcu\rcuHome\rcu\log\logdir.2012-12-19_08-22\rcu.log for details. RCU-6107:DB Init Param Prerequisite failure for: pga_aggregate_target Current Value is 0. It should be greater than or equal to 4294967296. RCU-6107:DB Init Param Prerequisite failure for: sga_target Current Value is 0. It should be greater than or equal to 9663676416. RCU-6092:Component Selection validation failed. Please refer to log at D:\fusion\apps_rcu\rcuHome\rcu\log\logdir.2012-12-19_08-22\rcu.log for details.

To fix this issue, we need to modify the minimum requirement of SGA and PGA in installer pre-requisite config file located at apps_rcu /rcu/integration/fusionapps/fusionapps.xml

Change these values as follows.

<DBPrerequisite COMPARE_OPERATOR=”GE” DATA_TYPE=”NUMBER” PREREQ_TYPE=”InitParameter”>

<ValidIf DBTYPE=”ORACLE”/>

<PrereqIdentifier>sga_target</PrereqIdentifier>

<PrereqValue>0</PrereqValue>

</DBPrerequisite>

…

<DBPrerequisite COMPARE_OPERATOR=”GE” DATA_TYPE=”NUMBER” PREREQ_TYPE=”InitParameter”>

<ValidIf DBTYPE=”ORACLE”/>

<PrereqIdentifier>pga_aggregate_target</PrereqIdentifier>

<PrereqValue>0</PrereqValue>

</DBPrerequisite>

Note: You may need to click Back go to the database details window and click Next again to retry.

Once prerequisites check is successful, click OK

Enter same password (for example Oracle123) for all schemas for now. Click Next

Create following directories on our DB server and then enter values as mentioned here and click Next

-bash-3.2$ mkdir /app/fusion/database/applcp

-bash-3.2$ mkdir /app/fusion/database/appllog

-bash-3.2$ mkdir /app/fusion/database/obieebkp

-bash-3.2$ mkdir /app/fusion/database/ keyflexcombfilter

Once Tablespaces creation is complete, click OK

Review the summary and click Create to import the required users and data.

Above timings are just for your reference only to know how much time each may take.

You can also monitor the import logs at /app/fusion/dp_dir

We encountered following error due to firewall timeout. Clicked Ignore

That leads to above error. Don’t panic. Just keep monitoring import log. Once import finishes, you can safely finish the RCU J

You can also monitor the progress by

impdp attach=FUSIONDBJOB

For us above finished almost 3.5 hours, it may take more or less time based on the machine specs.

Make sure you uncheck Cleanup for failed components since import already finished in background.

We may need to update following in case if you faced error during RCU and you are sure that import has finished successfully.

SQL> select status from schema_version_registry where comp_name=’Fusion Applications’;

STATUS

———–

LOADING

SQL> select comp_name from schema_version_registry where status=’LOADING’;

COMP_NAME

——————————————————————————–

Fusion Applications

SQL> update schema_version_registry set status=’VALID’ WHERE COMP_NAME=’Fusion Applications’;

1 row updated.

SQL> COMMIT;

Commit complete.

Installing Oracle Fusion Applications – steps

1. Install Fusion Applications Provisioning Framework
2. Install Oracle 11g Database (Applications Transactional Database)
3. Run Oracle Fusion Applications Repository Creation Utility (Applications RCU)
4. Create another database for Oracle Identity Management Infrastructure (optional)
5. Run Repository Creation Utility (RCU) for Oracle Identity Management components
6. Install Oracle Identity and Access Management Components
7. Apply mandatory Patches
8. Configure Oracle Identity and Access Management components
9. Integrate Oracle Identity Manager (OIM) and Oracle Access Manager (OAM)
10. Create new Response File
11. Provision an Applications Environment

Next: Run Repository Creation Utility (RCU) for Oracle Identity Management components

Previous: Install Fusion Applications Provisioning Framework

Fusion Applications 11.1.5 ships with Oracle 11g (11.2.0.3.0) database. You can either install it saperately (if you want to install RAC database) or use Fusion provisioning Wizard to create one. 

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

<framework_location> is same where we installed the framework in previous post. i.e. /app/fusion

-bash-3.2$ cd /app/fusion/provisioning/bin/

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

-bash-3.2$ export JAVA_HOME=/u02/stage/jdk6

-bash-3.2$ ./provisioningWizard.sh

Click Next

Select “Install an Applications Transactional Database” option. Click Next

Deselect the checkbox if you wish and click Next

Click Yes

Enter values as mentioned here and click Next.

Port: 1521 (we have kept it default, you can change it)

Installers directory location: /u02/stage (directory where we created the stage)

Oracle Base: /app/fusion/database

Software Location: Will be populated automatically

OSDBA group: dba

Global Database Name: fusiondb (you can keep any name you want)

Password: Oracle123 (We have used Oracle123 for any passwords during the installation since it satisfies all requirements during this installation. You can keep any complex password you want)

Once prerequisites check is successful, click Next

Verify summary and click Install to start installation

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

Once Installation completes (20% progress), it will prompt as follows.

Open another window and run the following scripts.

root@ad002aph01 # /app/fusion/database/product/11.2.0/dbhome_1/root.sh

Check /app/fusion/database/product/11.2.0/dbhome_1/install/root_ad002aph01_2012-12-18_12-08-54.log for the output of root script

root@ad002aph01 # tail -f /app/fusion/database/product/11.2.0/dbhome_1/install/root_ad002aph01_2012-12-18_12-08-54.log

The following environment variables are set as:

ORACLE_OWNER= fusion

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

Creating /var/opt/oracle/oratab file…

Entries will be added to the /var/opt/oracle/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.

Click OK

Once installation till validation is complete, click Next

Review the summary and click Close

Reduce memory size of database

We will reduce the size of SGA and PGA to avoid getting out of memory in server since fusion requires too much memory.

Important Note: We are reducing the SGA and PGA (from 10GB to 2GB). We are doing this since we are running on lesser RAM than required. 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.

-bash-3.2$ export ORACLE_HOME=/app/fusion/database/product/11.2.0/dbhome_1

-bash-3.2$ export ORACLE_SID=fusiondb

-bash-3.2$ export PATH=$PATH:$PATH:$ORACLE_HOME/bin

-bash-3.2$ sqlplus / as sysdba

SQL> create pfile from spfile;

File created.

SQL> shut immediate;

-bash-3.2$ more /app/fusion/database/product/11.2.0/dbhome_1/dbs/initfusiondb.ora

#fusiondb.__db_cache_size=7516192768

#fusiondb.__java_pool_size=33554432

#fusiondb.__large_pool_size=33554432

fusiondb.__oracle_base=’/app/fusion/database’#ORACLE_BASE set from environment

#fusiondb.__pga_aggregate_target=4294967296

#fusiondb.__sga_target=9663676416

#fusiondb.__shared_io_pool_size=536870912

#fusiondb.__shared_pool_size=1442840576

#fusiondb.__streams_pool_size=33554432

#*.pga_aggregate_target=4294967296

#*.sga_target=9663676416

*.memory_target=2147483648

-bash-3.2$ sqlplus / as sysdba

Connected to an idle instance.

SQL> create spfile from pfile;

File created.

SQL> startup

ORACLE instance started.

Total System Global Area 2138521600 bytes

Fixed Size 2161024 bytes

Variable Size 1795163776 bytes

Database Buffers 335544320 bytes

Redo Buffers 5652480 bytes

Database mounted.

Database opened.

Installing Oracle Fusion Applications – steps

1. Install Fusion Applications Provisioning Framework
2. Install Oracle 11g Database (Applications Transactional Database)
3. Run Oracle Fusion Applications Repository Creation Utility (Applications RCU)
4. Create another database for Oracle Identity Management Infrastructure (optional)
5. Run Repository Creation Utility (RCU) for Oracle Identity Management components
6. Install Oracle Identity and Access Management Components
7. Apply mandatory Patches
8. Configure Oracle Identity and Access Management components
9. Integrate Oracle Identity Manager (OIM) and Oracle Access Manager (OAM)
10. Create new Response File
11. Provision an Applications Environment

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