Oracle EBS 12.2.7 Fresh Installation

In this post you can find the complete detailed step by step process for EBS 12.2.7 Fresh Installation

Here in this post I've did my Fresh Installation in Linux Environment. My environment details are below.

Operating System  : RHEL 6 Update 2
Memory                  : 32 GB
Storage                  : 4 TB

Reference Documents
Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.2) for Linux x86-64 (Doc ID 1330701.1)
Oracle E-Business Suite Release Notes, Release 12.2 (Doc ID 1320300.1)
R12.2: How To Create the Stage In Preparation For Installation (Doc ID 1596433.1)
Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes (Doc ID 1594274.1)
Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1)
Oracle E-Business Suite Release 12.2.7 Readme (Doc ID 2230783.1)

High Level Steps

1. Software Download
2. Preparing the system for Installation
3. Installation
4. Testing 

Software Download

Follow the below steps to download the required software files

• Login to oracle edelivery site and search using the keyword Oracle Financials.
• Select the below highlighted file.

• Now go to your cart and click on the selected software

• Now choose only the below files alone for a Fresh Installation.
• You can leave the other files unless you need them.

Preparing the system for Installation

Follow the below document and check the requirements according to your OS and fulfill other needed requirements as well.

• Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.2) for Linux x86-64 (Doc ID 1330701.1)

Installation

First create a directory, called StageR122, into which you will copy all the downloaded software.

Next you unzip the files and run the build script.

Then patch the stage area with the latest consolidated fixes.

Now, we are ready to run Rapid Install.

Follow the below steps as Root user. 

• Stage Creation
• Patching stage area
• Running rapidwiz

Stage Creation

In the following example, the stage area directory is created under a mount point called

/u01:

$ cd /u01

$ mkdir Stage122

Copy all the downloaded files into the stage area created.

Now download the Patch 22066363. This patch is used to create the stage area. Copy this patch into the stage area, we created in the above step. Unzip this patch, then build the stage. 

Note : Build the stage as Root user.

$ cd /u01/StageR122/startCD/Disk1/rapidwiz/bin
$ ./buildStage.sh

Main Menu
Build Stage Menu
------------------------------------------------------
1. Create new stage area
2. Copy new patches to current stage area.
3. Display existing files in stage TechPatches.
4. Exit menu
Enter your choice [4]:1

Rapid Install Platform Menu
------------------------------------------------------
1. Oracle Solaris SPARC (64-bit)
2. Linux x86-64
3. IBM AIX on Power Systems (64-bit)
4. HP-UX Itanium
5. Exit Menu
Enter your choice [5]:2

Please enter the directory containing the zipped installation media: [Enter your stage area path]


Build Stage Menu
------------------------------------------------------
1. Create new stage area
2. Copy new patches to current stage area.
3. Display existing files in stage TechPatches.
4. Exit menu
Enter your choice [4]:2

Rapid Install Platform Menu
------------------------------------------------------
1. Oracle Solaris SPARC (64-bit)
2. Linux x86-64
3. IBM AIX on Power Systems (64-bit)
4. HP-UX Itanium
5. Exit Menu
Enter your choice [5]:2


Build Stage Menu
------------------------------------------------------
1. Create new stage area
2. Copy new patches to current stage area.
3. Display existing files in stage TechPatches.
4. Exit menu
Enter your choice [4]:3

Directory /s0/oracle/XB45/startCD/Disk1/rapidwiz/bin/../../../..
/TechPatches
|--DB
| |--11071989
| | |--p11071989_112030_Linux-x86-64.zip
| |--11820674
| | |--p11820674_R12_LINUX.zip
| |--12949905
| | |--p12949905_112030_Linux-x86-64.zip
| |--12951696
| | |--p12951696_112030_Generic.zip
| |--12955701
| | |--p12955701_112030_Linux-x86-64.zip
| |--13040331
| | |--p13040331_112030_Linux-x86-64.zip
| |--13388104


Build Stage Menu
------------------------------------------------------
1. Create new stage area
2. Copy new patches to current stage area.
3. Display existing files in stage TechPatches.
4. Exit menu
Enter your choice [4]:4

Patching stage area

After running the buildStage script, you should patch the stage area with the latest
consolidated fixes since the release of the current StartCD. For StartCD 12.2.0.51, the
consolidated fixes are delivered in Patch 25525148.

1. Download Patch 25525148 from My Oracle Support.
2. Unzip this patch using the following command:

unzip p25525148_R12_GENERIC.zip

3. Change to the 25525148 directory.
4. Patch the stage area using the following commands:

sh patchRIStage.sh

When prompted for the location of the Rapid Install stage, enter the path to the
stage area you created for StartCD 12.2.0.51.
Note: Run the script as the same user that you used to run the buildStage script when creating the stage area.


Running rapidwiz

cd /u01/StageR122/startCD/Disk1/rapidwiz
./rapidwiz

With this we have completed Oracle EBS 1220 Installation. Next we need to apply 1227 Patch on top of this base installation. Let us see the procedure in detail.

1227 Patch Installation

• Apply Required Database Patches
• Set Database Parameter (Conditional)
• Apply Consolidated Seed Table Upgrade Patch (Required)
• Apply the Latest AD and TXK Delta Release Update Packs
• Update Database Tier to Latest Code
• Apply Oracle E-Business Suite 12.2.7 Release Update Pack

Apply Required Database Patches

Before you apply the AD and TXK Delta 10 release update packs (RUPs), you must run the latest version (available via Patch 17537119) of the EBS Technology Codelevel Checker (ETCC). Use the command checkDBpatch.sh (on UNIX)

Running the latest version is required in order to check that all the required database patches have been applied. To learn more about the prerequisite database patches needed for applying the Delta 10 RUPs, refer My Oracle Knowledge Document 1594274.1, Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes. Ensure all the required ETCC database objects will be found by the Delta 10 RUP installation process. This means that even if you already have all the required database patches installed, you must still run the latest version of ETCC on your database.


Set Database Parameter

Oracle Database 12c Release 1 uses cost based optimization. If you are using Oracle Database 12.1.0.2, the following optimizer parameter should always be set to 'false'. This setting should be completed before proceeding with the next steps and should not be changed thereafter.

optimizer_adaptive_features=false

You can verify the parameter was set correctly by running the following command, which should return the value FALSE:

SQL>show parameter optimizer_adaptive_features


Apply Consolidated Seed Table Upgrade Patch (Required)

1.Stop all application tier services on the run file system.
sh $ADMIN_SCRIPTS_HOME/adstpall.sh

2.Start up only the Oracle Weblogic Admin Server on the run file system.
$ sh $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start

3.Apply the consolidated seed table upgrade Patch 17204589:12.2.0 on the run file system using adop hotpatch mode. Since our New Installation was created using startCD 12.2.0.51 (Patch 22066363), you must apply Consolidated Seed Table Upgrade Patch 17204589:12.2.0 by merging with Patch 21900871:12.2.0 on the run file system using adop hotpatch mode.
$ adop phase=apply patches=17204589,21900871 merge=yes hotpatch=yes

4.Start up all application tier services.
$ sh $ADMIN_SCRIPTS_HOME/adstrtal.sh


Apply the Latest AD and TXK Delta Release Update Packs

Run the codelevel checker utility (checkDBpatch.sh and checkMTpatch.sh or checkDBpatch.cmd and checkMTpatch.cmd, respectively for Linux and Windows) to identify and apply any missing patches (for example, ones that may have become available after release of the startCD).

1. Source the run edition environment file.

$ . <RUN_BASE>/EBSapps/appl/APPS<CONTEXT_NAME>.env

2. Start up only the Oracle Weblogic Admin Server on the run edition application tier file system.

$ sh $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start

3. Unzip patches and run adgrants.

a) Download and unzip the following patches:

Patch 25820806 (R12.AD.C.Delta.10)

Patch 24591000:R12.AD.C [AD Critical Patch]

Patch 26482811:R12.AD.C [AD Critical Patch]

Patch 25828573 (R12.TXK.C.Delta.10)

Patch 26400116:R12.TXK.C [TXK Critical Patch]

Patch 26720231:R12.TXK.C [TXK Critical Patch]

Patch 26720905:R12.AD.C

b) Execute adgrants by following the instructions in the readme of Patch 25820806 (R12.AD.C.Delta.10).

4. On the run edition application tier file system, apply Patch 25820806 (R12.AD.C.Delta.10) and Patch 26720905:R12.AD.C in hotpatch mode.

$ adop phase=apply patches=25820806,26720905 merge=yes hotpatch=yes

5. Apply AD Critical patches

$ adop phase=apply patches=<Your first critical AD patch>,<Your second critical AD patch> hotpatch=yes merge=yes

(i.e)

$ adop phase=apply patches=24591000,26482811 hotpatch=yes merge=yes

6. On the run edition application tier file system, use hotpatch mode to apply Patch 25828573 (R12.TXK.C.Delta.10)

$ adop phase=apply patches=25828573,26400116,26720231 hotpatch=yes merge=yes

7. Source the run edition environment file.

 $ . <EBS_ROOT>/EBSapps.env run

8. Run Middle Tier EBS Technology Codelevel Checker (MT-ETCC)

Execute the Middle Tier EBS Technology Codelevel Checker (MT-ETCC) utility checkMTpatch.sh (checkMTpatch.cmd on Microsoft Windows) on the run file system.

9. Stop Oracle WebLogic Server's Admin Server and Node Manager services.

To apply a patch in downtime mode, you must shut down all application tier services, including the Oracle WebLogic Server Admin Server and Node Manager.

Stop the Oracle Weblogic Server Admin Server on the run file system.

$ sh $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh stop

Stop the Oracle WebLogic Server Node Manager service on the run file system.

$ sh $ADMIN_SCRIPTS_HOME/adnodemgrctl.sh stop

Update Database Tier to Latest Code

Update all database tier nodes with the latest code, by performing the following steps:

1. On the application tier (as the APPLMGR user):

a)Source the run edition environment file.

$ . <EBS_ROOT>/EBSapps.env run

b)Execute the admkappsutil.pl utility to create the appsutil.zip file in <INST_TOP>/admin/out.

$ perl <AD_TOP>/bin/admkappsutil.pl

2. On the database tier (as the ORACLE user):

a)Source the environment for RDBMS ORACLE_HOME.

$ cd <RDBMS ORACLE_HOME>

$ . ./<RDBMS ORACLE_HOME>/<CONTEXT_NAME>.env

b)Copy or FTP the appsutil.zip file to <RDBMS ORACLE_HOME>.

c)Uncompress appsutil.zip, under <RDBMS ORACLE_HOME>.

$ cd <ORACLE_HOME>

$ unzip -o appsutil.zip

d)Run AutoConfig on <RDBMS ORACLE_HOME>.

$ sh <RDBMS_ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME>/adautocfg.sh

3. Run AutoConfig on the run file system.

Run AutoConfig on all application tier nodes (as the APPLMGR user) by executing the applicable command:

$ sh <INST_TOP>/admin/scripts/adautocfg.sh

Apply Oracle E-Business Suite 12.2.7 Release Update Pack

1. Source the run edition applications environment.

$ . <INSTALL_BASE>/EBSapps.env run

2. Stop Oracle WebLogic Server's Admin Server and Node Manager services. To apply a patch in downtime mode, you must shut down all application tier services, including the Oracle WebLogic Server Admin Server and Node Manager.

a)Stop the Oracle WebLogic Server Admin Server on the run file system.

$ sh $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh stop

b)Stop the Oracle WebLogic Server Node Manager service on the run file system.

$ sh $ADMIN_SCRIPTS_HOME/adnodemgrctl.sh stop

3. Apply Oracle E-Business Suite 12.2.7 Release Update Pack Patch 24690690 on the run edition application environment, using downtime mode.

$ adop phase=apply apply_mode=downtime patches=24690690

4. Start all application tier services on the run file system.

$ sh $ADMIN_SCRIPTS_HOME/adstrtal.sh

5. Perform adop cleanup action.

$ adop phase=cleanup

6. Synchronize file systems

Synchronize the file systems using the command shown below. This action will copy the new run edition code and configuration to the other file system, to ensure that both file systems are in sync before applying patches using the regular adop cycle on the other file system.

$ adop phase=fs_clone

7. Change site name and Java color and other post upgrade activities as per your need.

Testing

Once the services are UP and Running, follow the below steps to Test everything is normal and fine.

1. Check Concurrent Administer page for Actual and Target values are same or not
2. Submit a sample request (Active Users) and check the output
3. Perform a basic Health and Sanity check on both DB and APPS tiers to ensure the standard of the services.

Hope this post helps you in your Fresh Installation. Please leave comments in-case for any doubts.

                     *************************நன்றி*************************