Provision an Applications Environment

Installing Oracle Fusion Applications > Setting up Fusion Applications Node > Provision an Applications Environment

Previous: Create new Applications Provisioning Response File

Pro Oracle Fusion Applications – Installation and Administration

Now you can buy the first and only comprehensive book on Oracle Fusion Applications Installation and Administration which covers end to end information on introduction, planning, installation and troubleshooting guides for implementing Fusion Applications on premise. Buy it now from any of the following stores.

http://www.amazon.com/Pro-Oracle-Fusion-Applications-Administration/dp/1484209842

http://www.barnesandnoble.com/w/pro-oracle-fusion-applications-tushar-thakker/1121094340

http://www.apress.com/9781484209844

http://www.springer.com/us/book/9781484209844

Preparing for Provisioning

We will need following libraries in the repository installers webgate directory. Let’s make sure if we have the required libraries. The output of all these should be more than 0.

[fusion@fahost bin]$ strings -a /lib64/libgcc_s.so.1 | grep -v .GCC_3.3.1. | grep -c “GCC_3.3”

2

[fusion@fahost bin]$ strings -a /lib64/libgcc_s.so.1 | grep -c “GCC_3.0”

1

[fusion@fahost bin]$ strings -a /lib64/libgcc_s.so.1 | grep -c “GCC_4.2.0”

1

[fusion@fahost bin]$ strings -a /lib64/libgcc_s.so.1 | grep -v “GCC_3.3.1” | grep -c “GCC_3.3”

1

[fusion@fahost bin]$ file -L /lib64/libgcc_s.so.1 | grep “64-bit” | grep -c “x86-64”

1

[fusion@fahost bin]$ file -L /usr/lib64/libstdc++.so.6 | grep “64-bit” | grep -c “x86-64”

1

 

Keep local copy of the libraries as well (optional)

[fusion@fahost bin]$ mkdir /app/fusion/oam_lib

[fusion@fahost bin]$ cp -p /lib64/libgcc_s.so.1 /app/fusion/oam_lib/

[fusion@fahost bin]$ cp -p /usr/lib64/libstdc++.so.6 /app/fusion/oam_lib/

[fusion@fahost bin]$ cp -p /usr/lib64/libstdc++.so.5 /app/fusion/oam_lib/

 

Copy the files in repository installers/webgate directory.

[fusion@fahost bin]$ cp -pr /app/fusion/oam_lib/* /stage/installers/webgate/

[fusion@fahost bin]$ ls -ltr /stage/installers/webgate/

total 1820

-rwxrwxrwx 1 root root 2480 Mar 3 2013 Labels.txt

drwxrwxrwx 1 root root 0 Oct 24 03:01 Disk1

drwxrwxrwx 1 root root 0 Oct 24 03:01 patch

-rwxrwxrwx 1 root root 58400 Oct 27 14:51 libgcc_s.so.1

-rwxrwxrwx 1 root root 825400 Oct 27 14:51 libstdc++.so.5

-rwxrwxrwx 1 root root 976312 Oct 27 14:51 libstdc++.so.6

 

Start Fusion Applications Provisioning

Launch the installer from <provisioning_repository>/bin

It is important to start it with “-ignoreSysPrereqs true” switch

[fusion@fahost bin]$ cd /app/fusion/provisioning/bin/

[fusion@fahost bin]$ ./provisioningWizard.sh -ignoreSysPrereqs true &

 

Click Next

Select “Provision an Applications Environment” and browse for the response file created in last step. Click Next

 

Review and click Next

Validate the information and click Next

In case if you want to revisit some of the section in the Response File then you can do so here. Click Next

Review the summary and click Next to begin. Good luck J

You can ignore the warning about HWR mount point size (1024GB). Click Next

Installation takes a few hours on entry level systems. Click Next once finished

Preconfigure shall finish maximum within an hour. Click Next once finished

Configure takes a few hours. Click Next once finished

Configure Primary/Secondary may take a few minutes. Click Next

Postconfigure phase takes very long time. Do not panic if you see errors during this phase since most of the errors are transient and can be fixed upon rerunning based on the error. You can see that HCM postconfigure failed and the error was related to timeout during high CPU activity.

We can rerun the phase by clicking on Retry and it will do cleanup/resotre to previous step (only for the failed product domains).

 

 

Here you can see the despite you see a red corss mark against HCM and still it is successful. This is due to following flexfield related errors which are not actually “errors” but the provisioning wizard incorrectly shows them as red mark. This does not affect the phase at all and installation continues.

 

Here is an example of the same. This may or may not occur during your installation.

 

Let’s go back to our postconfigure screen.

Click Next to start the “Startup” phase.

 

Here is the current memory utilization at this stage. (Apprpx 60GB used buffers)

[fusion@fahost fahost]$ free -m

total used free shared buffers cached

Mem: 90819 87601 3218 0 797 25526

-/+ buffers/cache: 61277 29542

Swap: 0 0 0

 

Validate phase might encounter some known errors as follows.

 

MESSAGE=Failed connecting to http://fahost:7010/integration/worklistapp/faces/login.jspx, Server redirected too many times (20)!DETAIL=Failed connecting to http://fahost:7010/integration/worklistapp/faces/login.jspx, Server redirected too many times (20)

 

The web page http://fahost:7001/em/faces/fa-faLogin;jsessionid=UUk-ZidyFeG2FHkJupePpadc6Jwez7Iy9yk5uqIxxteJK7VQDv_d!-1008637013?target=Farm_CommonDomain&type=oracle_ias_farm&FromContextInitFilter=true does not contain the text, html

 

These and few more expected error messages are documented in Oracle Support Document ID 1487115.1 and 1404577.1

 

If there are any other validation errors you must resolve them before proceeding to the Summary phase. After resolving all validation errors, if the Next button on the Provisioning Wizard is not enabled, perform these steps from the command line to enable it:

 

cd <APPLICATIONS_CONFIG>/phaseguards (for example /app/oracle/provisioning/phaseguards)

rm validate-<host>-FAILED.grd.

touch validate-<host>-COMPLETED.grd.

touch validate-<host>-ENDED.grd (this last part is not mentioned in Oracle documents but this is required for Next button to be enabled). Since there is no direct way to ignore this. We can skip this as follows.

 

WARNING:

Deleting and creating files in the phase guard directory should be used as a workaround to resolve validation phase issues ONLY if none of the other options work. In any other case, you should never modify or make changes to the phase guard files.

 

[fusion@fahost ~]$ cd /app/oracle/provisioning/phaseguards/

[fusion@fahost phaseguards]$ ls -ltr validate-fahost-*

-rwx—— 1 fusion dba 0 Nov 10 13:02 validate-fahost-STARTED.grd

-rwx—— 1 fusion dba 0 Nov 10 14:23 validate-fahost-FAILED.grd

[fusion@fahost phaseguards]$ rm validate-fahost-FAILED.grd

[fusion@fahost phaseguards]$ touch validate-fahost-COMPLETED.grd

[fusion@fahost phaseguards]$ touch validate-fahost-ENDED.grd

 

Now you can see the Next button enabled. Click Next to go to post-installation summary.

No need to manually copy the content since once you click Finish, it will create a provisioning summary file which contains all above information.

 

Login to Fusion Applications homepage URL https://fahost:10634/homePage with FAADMIN user. This would first redirect you to Single Sign-on screen and then redirect you back to Fusion Applications.

 

 

 

Click on Navigator to see list of functions.

Click on Setup and Maintenance to see the functional setup screen.

 

 

 

You can see that the products are “provisioned” but not “Implemented”. You can refer to individual product implementation guide to further implement the products.

 

This concludes our Fusion Applications 11.1.8 Installation..

 

Happy Learning !
Tushar Thakker

ORA Training
(A Division of Param Labs)

 

Installing Oracle Fusion Applications – steps

A. Setting up Identity and Access Management Node

1. Install Fusion Applications Provisioning Framework

2. Install Oracle 11g Database (Identity management database)

3. Run Repository Creation Utility (RCU) for Oracle Identity Management components

4. Install Identity Management Provisioning Wizard

5. Create IDM provisioning Response File

6. Provision Identity Management

7. Perform Post-Provisioning Configuration

B. Setting up Fusion Applications Node

1. Install Fusion Applications Provisioning Framework

2. Install Oracle 11g Database (Fusion Apps Database)

3. Run Oracle Fusion Applications Repository Creation Utility (Applications RCU)

4. Create new Applications Provisioning Response File

5. Provision an Applications Environment

Nov 3rd, 2013 | Posted by Tushar Thakker | Filed under Uncategorized

Run Oracle Fusion Applications Repository Creation Utility (Applications RCU)

Installing Oracle Fusion Applications > Setting up Fusion Applications Node > Run Oracle Fusion Applications Repository Creation Utility (Applications RCU)

Previous: Install Oracle 11g Database (Fusion Apps Database)

Pro Oracle Fusion Applications – Installation and Administration

Now you can buy the first and only comprehensive book on Oracle Fusion Applications Installation and Administration which covers end to end information on introduction, planning, installation and troubleshooting guides for implementing Fusion Applications on premise. Buy it now from any of the following stores.

http://www.amazon.com/Pro-Oracle-Fusion-Applications-Administration/dp/1484209842

http://www.barnesandnoble.com/w/pro-oracle-fusion-applications-tushar-thakker/1121094340

http://www.apress.com/9781484209844

http://www.springer.com/us/book/9781484209844

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 has both Applications and Fusion Middleware RCUs for Linux but for Windows only Apps RCU is included in the installer.

 

We will go ahead with Linux RCU here.

For Linux, the RCU is included in repository_location/installers/apps_rcu location.

Create a directory on physical partition and call it APPS_RCU_HOME

 

[fusion@fahost dbs]$ mkdir /app/fusion/provisioning/apps_rcu

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

Extract the contents of rcuHome_fusionapps_linux.zip to a directory (APPS_RCU_HOME) on the database server. All dependent components that Applications RCU needs are included in this zipped file.

[fusion@fahost dbs]$ cd /app/fusion/provisioning/apps_rcu

[fusion@fahost apps_rcu]$ unzip /stage/installers/apps_rcu/linux/rcuHome_fusionapps_linux.zip

 

Create a temporary directory on the database server. Make a note of the location. You will need to enter this location when you specify a value for FUSIONAPPS_DBINSTALL_DP_DIR

[fusion@fahost apps_rcu]$ mkdir /app/fusion/provisioning/apps_rcu/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.

[fusion@fahost apps_rcu]$ cd /app/fusion/provisioning/apps_rcu/dp_dir

[fusion@fahost dp_dir]$ unzip /app/fusion/provisioning/apps_rcu/rcu/integration/fusionapps/export_fusionapps_dbinstall.zip

Archive: /app/fusion/provisioning/apps_rcu/rcu/integration/fusionapps/export_fusionapps_dbinstall.zip

inflating: fusionapps_dbinstall_latest_06.dmp

inflating: fusionapps_dbinstall_latest_02.dmp

inflating: fusionapps_dbinstall_latest_07.dmp

inflating: fusionapps_dbinstall_latest_04.dmp

inflating: fusionapps_dbinstall_latest_03.dmp

inflating: fusionapps_dbinstall_latest_01.dmp

inflating: fusionapps_dbinstall_latest_05.dmp

inflating: fusionapps_dbinstall_latest_08.dmp

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)

[fusion@fahost dp_dir]$ cp -p /app/fusion/provisioning/apps_rcu/rcu/integration/biapps/schema/otbi.dmp .

Launch Repository Creation Utility (RCU)

 

[fusion@fahost dp_dir]$ cd /app/fusion/provisioning/apps_rcu/bin

[fusion@fahost bin]$ ./rcu

 

Click Next

Click Next

Enter details of the Fusion Apps database created in previous step. Click Next

 

Once prerequisite check completes, click OK

Select ALL components and click Next

If you had reduced SGA/PGA/Memory size in previous step then you might get an error. Click OK to see the error.

 

The error is as follows.

 

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.

 

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

 

[fusion@fahost ~]$ cp -p /app/fusion/provisioning/apps_rcu/rcu/integration/fusionapps/fusionapps.xml /app/fusion/provisioning/apps_rcu/rcu/integration/fusionapps/fusionapps.xml.bak

 

Edit the file as follows

[fusion@fahost ~]$ vi /app/fusion/provisioning/apps_rcu/rcu/integration/fusionapps/fusionapps.xml

<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>

 

[fusion@fahost ~]$ diff /app/fusion/provisioning/apps_rcu/rcu/integration/fusionapps/fusionapps.xml /app/fusion/provisioning/apps_rcu/rcu/integration/fusionapps/fusionapps.xml.bak

111c111

< <PrereqValue>0</PrereqValue>

> <PrereqValue>4294967296</PrereqValue>

144c144

< <PrereqValue>0</PrereqValue>

> <PrereqValue>9663676416</PrereqValue>

 

Click “Back” TWICE and click next. The check should be successful now.

Click OK

Enter same password (eg. Oracle123) for all schemas and click Next

 

Open another terminal window. Create following directories for custom environment variables.

 

[fusion@fahost ~]$ mkdir /app/database/applcp

[fusion@fahost ~]$ mkdir /app/database/appllog

[fusion@fahost ~]$ mkdir /app/database/obieebkp

Specify these above values in the same screen under Fusion Applications Component (expect first value which is the temporary DP directory created before /app/fusion/provisioning/apps_rcu/dp_dir)

 

Supervisor Password: You must enter the same password you set up as ODI SUPERVISOR in Applications RCU. Since we kept all passwords as Oracle123, nothing much to remember. Enter the same password.

 

Work Repository Password: Default = None. You must enter the same password set up as ODI SUPERVISOR in Applications RCU.

 

Oracle Transactional BI : Directory on the database server where Oracle Transactional Business Intelligence import and export files are stored. Enter /app/fusion/provisioning/apps_rcu/dp_dir again.

 

Review the list and click Next

 

Click OK

Once tablespaces are created, click OK to proceed with schemas creation.

 

Review the details and click Create to start creating the schemas.

This might take long time depending on the machine configuration.

Once completed, review the summary and click Close

 

Next: Create new Fusion Applications Response File

 

Installing Oracle Fusion Applications – steps

A. Setting up Identity and Access Management Node

1. Install Fusion Applications Provisioning Framework

2. Install Oracle 11g Database (Identity management database)

3. Run Repository Creation Utility (RCU) for Oracle Identity Management components

4. Install Identity Management Provisioning Wizard

5. Create IDM provisioning Response File

6. Provision Identity Management

7. Perform Post-Provisioning Configuration

B. Setting up Fusion Applications Node

1. Install Fusion Applications Provisioning Framework

2. Install Oracle 11g Database (Fusion Apps Database)

3. Run Oracle Fusion Applications Repository Creation Utility (Applications RCU)

4. Create new Applications Provisioning Response File

5. Provision an Applications Environment

Nov 3rd, 2013 | Posted by Tushar Thakker | Filed under Uncategorized

Install Oracle 11g Database (Fusion Apps Database)

Installing Oracle Fusion Applications > Setting up Fusion Applications Node > Install Oracle 11g Database (Fusion Apps Database)

Previous: Install Fusion Applications Provisioning Framework

Pro Oracle Fusion Applications – Installation and Administration

Now you can buy the first and only comprehensive book on Oracle Fusion Applications Installation and Administration which covers end to end information on introduction, planning, installation and troubleshooting guides for implementing Fusion Applications on premise. Buy it now from any of the following stores.

http://www.amazon.com/Pro-Oracle-Fusion-Applications-Administration/dp/1484209842

http://www.barnesandnoble.com/w/pro-oracle-fusion-applications-tushar-thakker/1121094340

http://www.apress.com/9781484209844

http://www.springer.com/us/book/9781484209844

Let us first install JDK6 since we will need this to be on a permanent location.

[fusion@fahost ~]$ cd /app/fusion/

[fusion@fahost fusion]$ unzip /stage/installers/jdk/jdk6.zip

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

[fusion@fahost ~]$ cd /app/fusion/provisioning/bin/

[fusion@fahost bin]$ export JAVA_HOME=/app/fusion/jdk6

[fusion@fahost bin]$ ./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 (change it I you need)

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

Oracle Base: /app/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)

You might see some warning related to memory if you are using less than 26 GB memory for this host. You can ignore this since we are going to reduce the memory target after installation.

Once prerequisites check is successful, click Next. Save summary if required

Once Installation completes (20% progress), it will prompt as above. Open another window and run the following script as root user.

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

Check /app/database/product/11.2.0/dbhome_1/install/root_fahost.paramlabs.com_2013-11-01_16-43-36.log for the output of root script

[root@fahost fusion]# more /app/database/product/11.2.0/dbhome_1/install/root_fahost.paramlabs.com_2013-11-01_16-43-36.log

Performing root user operation for Oracle 11g

The following environment variables are set as:

ORACLE_OWNER= fusion

ORACLE_HOME= /app/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.

Click OK

Once installation till validation is complete, click Next

Click Close to complete the installation

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.

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

export ORACLE_HOME

PATH=$PATH:$ORACLE_HOME/bin

export PATH

ORACLE_SID=fusiondb

export ORACLE_SID

[fusion@fahost bin]$ sqlplus / as sysdba

SQL> show parameter pga

NAME TYPE VALUE

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

pga_aggregate_target big integer 4G

SQL> show parameter sga

NAME TYPE VALUE

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

lock_sga boolean FALSE

pre_page_sga boolean FALSE

sga_max_size big integer 9G

sga_target big integer 9G

SQL> show parameter memory

NAME TYPE VALUE

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

hi_shared_memory_address integer 0

memory_max_target big integer 0

memory_target big integer 0

shared_memory_address integer 0

SQL> shut immediate;

Database closed.

Database dismounted.

ORACLE instance shut down.

[fusion@fahost dbs]$ cp -pr initfusiondb.ora initfusiondb.ora.bak

[fusion@fahost dbs]$ vi initfusiondb.ora

Edit the values as follows and add last line as memory_target

#fusiondb.__db_cache_size=7482638336

#fusiondb.__java_pool_size=67108864

#fusiondb.__large_pool_size=33554432

fusiondb.__oracle_base=’/app/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=3G

Let’s recreate spfile using this pfile.

[fusion@fahost dbs]$ sqlplus / as sysdba

Connected to an idle instance.

SQL> create spfile from pfile;

File created.

SQL> startup

Also change the value for open_cursors parameter to 800

SQL> show parameter open_cursors

NAME TYPE VALUE

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

open_cursors integer 500

SQL> alter system set open_cursors=800 scope=both sid=’*’;

System altered.

SQL> show parameter open_cursors

NAME TYPE VALUE

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

open_cursors integer 800

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

 

Installing Oracle Fusion Applications – steps

A. Setting up Identity and Access Management Node

1. Install Fusion Applications Provisioning Framework

2. Install Oracle 11g Database (Identity management database)

3. Run Repository Creation Utility (RCU) for Oracle Identity Management components

4. Install Identity Management Provisioning Wizard

5. Create IDM provisioning Response File

6. Provision Identity Management

7. Perform Post-Provisioning Configuration

B. Setting up Fusion Applications Node

1. Install Fusion Applications Provisioning Framework

2. Install Oracle 11g Database (Fusion Apps Database)

3. Run Oracle Fusion Applications Repository Creation Utility (Applications RCU)

4. Create new Applications Provisioning Response File

5. Provision an Applications Environment

Nov 3rd, 2013 | Posted by Tushar Thakker | Filed under Uncategorized