Symbolic link creation failed in R12.2 PREPARE Phase

In my environment, Prepare phase of R12.2 patching cycle failed. On examining the log found a unique issue, tried a small workaround, it worked like a charm. Actually I was not sure that my workaround will help me, but I give it a try and it worked.

Issue: 

FMW JDK version in use: 1.7.0_85
/u01/PROD/apps/fs1/FMW_Home/Oracle_EBS-app1/jdk is not a symbolic link, creating it...
Running ln -s /u01/PROD/apps/fs1/EBSapps/comn/util/jdk64 /u01/PROD/apps/fs1/FMW_Home/Oracle_EBS-app1/jdk  ERROR: Command failed, exit code 1

After seeing this issue I went to respective directory and I can see the directory named jdk.

Actually that jdk should have been created as a sym link but here it is created as a normal directory. I couldn't find the reason for that, after all the permissions and ownership are right as it should be.

So I decided to move that particular file and restart the prepare phase again.

Now this time, jdk was created as a proper symlink and the prepare phase completed successfully.

FMW JDK version in use: 1.7.0_85
/u01/PROD/apps/fs1/FMW_Home/Oracle_EBS-app1/jdk is not a symbolic link, creating it...
Running ln -s /u01/PROD/apps/fs1/EBSapps/comn/util/jdk64 /u01/PROD/apps/fs1/FMW_Home/Oracle_EBS-app1/jdk

START: Updating status APPLY-APPLTOP-DONE for action ApplyApplTop

END: Updated status APPLY-APPLTOP-DONE for action ApplyApplTop

END: ApplyApplTop Completed Successfully.

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

APPS Login page is not coming

One fine morning after the backup has finished in Production environment, thought to have a health checkup. DB was fine. When tried to login to APPS the login page is throwing the below issue,

Apps Login Issue with Unable to generate forwarding URL. Exception: java.lang.RuntimeException: Guest user/pwd does not exist or match: GUEST/ORACLE

Quick search on google yields some hits on my issue.

Solution 1:

The root cause of the issue is with GUEST User and Password not in sync.

Running the below query, confirmed that GUEST user and password was not in sync

select fnd_web_sec.validate_password('GUEST','ORACLE') from dual;

FND_WEB_SEC.VALIDATE_PASSWORD('GUEST','ORACLE')
--------------------------------------------------------------------------------
N

Also, confirmed with the below error on the oacore log

javax.servlet.ServletException: java.lang.RuntimeException: Guest user/pwd does not exist or match: GUEST/ORACLE

Fix:

1. Shutdown the EBS services.

2. The only supported way to change the Guest user password is to update the context variable s_guest_pass and run AutoConfig, which runs the AdminAppServer utility internally.

3. Run autoconfig on DB Node and then application node.

4. Execute the below sql again:

select fnd_web_sec.validate_password('GUEST','ORACLE') from dual;

Check whether query output is showing Y.

If no,  Please check whether the below error is seen on autoconfig log:

Unable to update GUEST_USER_PWD in database to GUEST/ORACLE - Password was not changed, this point to the DB parameter JAVA_JIT_ENABLED which is set as TRUE.

5. On 11g DB you need to have the below settings for EBS specifically, run the below sql

alter system set JAVA_JIT_ENABLED= FALSE scope = both;

6. Follow the steps 2 and 3 again.

7. Run the below command:

perl $FND_TOP/patch/115/bin/ojspCompile.pl --compile --flush -p 2

8. Check whether the compile completed successfully.

9. Restart the application services.

Ref : Doc ID 1673030.1

Solution 2:

SQL> select fnd_web_sec.validate_login('GUEST','oracle') from dual;

FND_WEB_SEC.VALIDATE_LOGIN('GUEST','ORACLE')
--------------------------------------------------------------------------------
N

SQL> 
SQL> 
SQL> select fnd_message.get from dual; 

GET
--------------------------------------------------------------------------------
Oracle error -4031: ORA-04031: unable to allocate 4096 bytes of shared memory ("
java pool","unknown object","joxs heap",":Intern") has been detected in FND_WEB_
SEC.VALIDATE_LOGIN(u,p).

here the problem is clear.

Then I checked.

SQL> show parameter java

NAME                                           TYPE        VALUE

------------------------------------        ----------- ------------------------------

java_jit_enabled                          boolean       TRUE

java_max_sessionspace_size    integer         0

java_pool_size                            big integer   0

java_soft_sessionspace_limit     integer         0

SQL>

Solution:

Increase the java_pool_size=128M

SQL> alter system set java_pool_size =128M scope=both;

System altered.

Now bounce both DB and APPS. This time login page appears. This should fix the Issue.

Solution 3:

The same issue happened again, but this time the reason for the issue is different. No need to bother about the Guest password even though the issue stated so.

Issue:

Reason:

One of the background process MMON got shutdown abrubtly.

Solution:

Take a complete bounce on both DB and APPS, this will resolve your issue.

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

DR Configuration

The following are the list of tasks for DR configuration.

Primary Server

1. Enable Force Logging
2. Enable Archive log 
3. Set remote_login_passwordfile=EXCLUSIVE
4. Adding parameters in pfile
5. Adding parameters in tnsnames.ora file
6. TNSPING check
7. Create Password file
8. RMAN backup for stand-by Instance

Stand-by Server

1. OH Creation
2. Set remote_login_passwordfile=EXCLUSIVE
3. Adding parameters in pfile
4. Adding parameters in tnsnames.ora file
5. TNSPING check
6. Copy Password file
7. Create NFS mount point
8. Duplicate database for standby using RMAN

Primary Server

Below steps should be performed on Primary Instance.

Enable Force Logging

SQL> ALTER DATABASE FORCE LOGGING;

Database altered.

SQL> select force_logging from v$database;

FOR
---
YES

Enable Archive Log

You can follow the steps mentioned in this post to enable archive log in your database. Change the directories as per your environment. Click Here


Set remote_login_passwordfile=EXCLUSIVE
sqlplus '/as sysdba'

SQL> alter system set remote_login_passwordfile='EXCLUSIVE' scope = both;

Adding parameters in pfile

Edit your pfile and comment the below line
log_archive_dest_1 = 'LOCATION=/r12tst/R12TEST/ebs/db/datafiles/archive'

Once the above line is committed add the following at the end of the pfile
db_file_name_convert='/proddb/gnpoc/ebs/db/proddata','/r12tst/R12TEST/ebs/db/dat
afiles'
log_file_name_convert='/proddb/gnpoc/ebs/db/proddata','/r12tst/R12TEST/ebs/db/da
tafiles'
log_archive_dest_1='LOCATION=/r12tst/R12TEST/ebs/db/proddata/archive'
log_archive_dest_2='SERVICE=stdby LGWR'

Adding parameters in tnsnames.ora file

Copy the lines from tnsnames.ora file of the Stand-by instance, paste and save.

TEST=
        (DESCRIPTION=
                (ADDRESS=(PROTOCOL=tcp)(HOST=<hostname.domain>)(PORT=1571))
            (CONNECT_DATA=
                (SERVICE_NAME=TEST)
                (INSTANCE_NAME=TEST)
            )
        )

stdby = (DESCRIPTION=
                (ADDRESS=(PROTOCOL=tcp)(HOST=<hostname.domain>)(PORT=1571))
                (CONNECT_DATA=(SID=TEST))
            )

TNSPING check

Now check ping to check the connectivity between our Primary and Stand-by servers.

$ tnsping stdby

TNS Ping Utility for HPUX: Version 11.2.0.4.0 - Production on 09-FEB-2018 12:53:03

Copyright (c) 1997, 2013, Oracle.  All rights reserved.

Used parameter files:

/r12tst/R12TEST/ebs/db/tech_st/11.2.0/network/admin/TEST_erp12/sqlnet_ifile.ora

Used TNSNAMES adapter to resolve the alias

Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=<hostname.domain>)(PORT=1571)) (CONNECT_DATA=(SID=TEST)))

OK (50 msec)

$

Create Password file

$ pwd

/r12tst/R12TEST/ebs/db/tech_st/11.2.0/dbs

$

$ ls ora*

orapwGNPOCDB

$ mv orapwGNPOCDB orapwGNPOCDB_OLD

$ echo $ORACLE_SID

TEST

$

$ orapwd file=orapwTEST password=welcome 

RMAN backup for stand-by Instance

Configure RMAN and take a backup for Stand-by Instance from your Primary.

1. Configuring RMAN - Click Here

2. Take Backup using the below commands

RMAN > backup database include current controlfile for standby plus archivelog;

for compressed backup, use the below command

RMAN> backup as compressed backupset database include current controlfile for standby plus archivelog;

Stand-by Server

Below steps should be performed on Stand-by Instance.

OH Creation

Run pre-clone on Primary Instance and copy the OH to Stand-by server.

Run adcfgclone with dbTechStack option and create the OH with the same directory structure as the Primary instance.

cd $ORACLE_HOME/appsutil/scripts


Set remote_login_passwordfile=EXCLUSIVE

sqlplus '/as sysdba'

SQL> alter system set remote_login_passwordfile='EXCLUSIVE' scope = both;

Adding parameters in pfile

Edit your pfile and comment the below line
log_archive_dest_1='LOCATION=/DRDB/ebsdr/db/proddata/archive'

Once the above line is committed add the following at the end of the pfile
db_file_name_convert='/r12tst/R12TEST/ebs/db/proddata/','/DRDB/ebsdr/db/proddata
/'
log_file_name_convert='/r12tst/R12TEST/ebs/db/proddata/','/DRDB/ebsdr/db/proddat
a/'
standby_file_management=auto
fal_server=prdb
fal_client=stdby
log_archive_dest_1='LOCATION=/DRDB/ebsdr/db/proddata/archive'
log_archive_dest_2='SERVICE=stdby LGWR'

Adding parameters in tnsnames.ora file

Copy the lines from tnsnames.ora file of the Primary instance, paste and save.

TEST = (DESCRIPTION=
                (ADDRESS=(PROTOCOL=tcp)(HOST=<hostname.domain>)(PORT=1571))
                (CONNECT_DATA=(SID=TEST))
            )

prdb =
        (DESCRIPTION=
                (ADDRESS=(PROTOCOL=tcp)(HOST=<hostname.domain>)(PORT=1571))
            (CONNECT_DATA=
                (SERVICE_NAME=TEST)
                (INSTANCE_NAME=TEST)
            )
        )

TNSPING check

$ tnsping prdb

TNS Ping Utility for HPUX: Version 11.2.0.4.0 - Production on 09-FEB-2018 13:09:36

Copyright (c) 1997, 2013, Oracle.  All rights reserved.

Used parameter files:

Used TNSNAMES adapter to resolve the alias

Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp)(HOST=<hostname.domain>)(PORT=1571)) (CONNECT_DATA= (SERVICE_NAME=TEST) (INSTANCE_NAME=TEST)))

OK (10 msec)

$

Copy Password file

Copy password file from Primary to Stand-by

scp orapwTEST oradr@xxxxxxx:<OH Location/dbs>

Create NFS Mount Point

Make the RMAN Backup location of your Primary DB Instance as an NFS mount point and mount that in the Stand-by Instance. It is mandatory that the backup location should be same for both Primary and Stand-by Instance. So we need NFS mount point to proceed further.

Duplicate database for standby using RMAN

Now we can start duplicating the target database for stand-by instance using the below command. Here we can start the duplication in two ways, choose the one which suits you.

Method 1:

@Primary Instance

rman target / auxiliary=sys/<pwd you created for password file>@stdby

RMAN >duplicate target database for standby;

Method 2:

@Stand-by Instance

duplicate target database for standby backup location '<RMAN Backup location>' nofilenamecheck;

Once the duplication is finished, check and start the database at stand-by side.

SQL> select name,open_mode,database_role,protection_mode,switchover_status from v$database;

NAME      OPEN_MODE            DATABASE_ROLE    PROTECTION_MODE
---------     --------------------          --------------------------- ------------------------------
SWITCHOVER_STATUS
--------------------------------
TEST      MOUNTED              PHYSICAL STANDBY MAXIMUM PERFORMANCE
TO PRIMARY


SQL> select max(sequence#) from v$archived_log;

MAX(SEQUENCE#)
---------------------------


SQL> shut immediate;
ORA-01109: database not open


Database dismounted.
ORACLE instance shut down.


SQL> startup
ORACLE instance started.

Total System Global Area 4275781632 bytes
Fixed Size                  2212392 bytes
Variable Size             671092184 bytes
Database Buffers         3590324224 bytes
Redo Buffers               12152832 bytes
Database mounted.
Database opened.

If faced any issue like "ORA-10458: standby database requires recovery" Click Here

SQL>
SQL> show parameter background;

SQL> show parameter diag;

NAME                                 TYPE        VALUE
-------------------------------- ----------- ------------------------------
diagnostic_dest                      string      /DRDB/ebsdr/db/tech_st/11.2.0/admin/TEST_erpdr                                         
SQL> select name,open_mode,database_role,protection_mode,switchover_status from v$database;

NAME      OPEN_MODE            DATABASE_ROLE    PROTECTION_MODE
---------     --------------------          --------------------------  -------------------------------
SWITCHOVER_STATUS
--------------------------------
TEST      READ ONLY            PHYSICAL STANDBY MAXIMUM PERFORMANCE
NOT ALLOWED


SQL> select max(sequence#) from v$archived_log;

MAX(SEQUENCE#)
--------------------------
           267

SQL> recover managed standby database disconnect;
Media recovery complete.
SQL>
SQL> col GROUP# format a15
SQL> select process,status,group#,thread#,sequence# from v$managed_standby;

PROCESS   STATUS       GROUP#             THREAD#  SEQUENCE#
---------        ------------    --------------            -------------- ------------------
ARCH      CONNECTED    N/A                      0          0
ARCH      CONNECTED    N/A                      0          0
ARCH      CONNECTED    N/A                      0          0
ARCH      CONNECTED    N/A                      0          0
RFS          IDLE                   N/A                      0          0
RFS          IDLE                   N/A                      0          0
MRP0      WAIT_FOR_GAP N/A                    1        268
RFS          RECEIVING      N/A                       1        268

8 rows selected.

SQL> select sequence#,applied from v$archived_log;

 SEQUENCE# APPLIED
------------------ ------------
       266             YES
       267             YES

SQL> select sequence#,applied from v$archived_log;

 SEQUENCE# APPLIED
------------------ ------------
       266             YES
       267             YES
       268             YES

SQL> select sequence#,applied from v$archived_log;

 SEQUENCE# APPLIED
------------------ -------------
       266             YES
       267             YES
       268             YES
       269             YES
       270             YES

SQL> select max(sequence#) from v$archived_log;

MAX(SEQUENCE#)
--------------------------
           270

Useful Queries
===========

1. select name,open_mode,database_role,protection_mode,switchover_status from v$database; - on both

2. select max(sequence#) from v$archived_log; - on both

3. select process,status from v$managed_standby;

4. recover managed standby database disconnect;(standby) - To initiate the SYNC between Primary and Stand-by

5. col GROUP# format a15
   select process,status,group#,thread#,sequence# from v$managed_standby;
 
6.SQL> select PROCESS,CLIENT_PROCESS,THREAD#,SEQUENCE#,BLOCK# from v$managed_standby where process = 'MRP0' or client_process='LGWR';

7. select sequence#,applied from v$archived_log;(standby)

8. recover managed standby database cancel; - to stop the SYNC between Primary and Stand-by

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

Viewing Oracle APPS Reports in Browser

After I've Installed 12.2.7 in my Linux Server, all the reports are opening in oracle default viewer in application level. In one of my client location all their reports irrespective of the report type is opening in browser. So my search on this leads to a profile option and it worked for me. Below are the steps for how to do it.

Step 1: Log in as SYSADMIN user and choose System Administrator Responsibility

Step 2: Choose Profile à System

Step 3: In profile search as below "Viewer%"

Step 4: Choose the following values in LOV

Viewer: Application for HTML	Browser
Viewer: Application for PCL	Printer Control Language
Viewer: Application for PDF	Browser
Viewer: Application for PostScript	Browser
Viewer: Application for Text	Browser
Viewer: Application for XML	Browser
Viewer: Default Font Size	10
Viewer: Text	Browser

Step 5: Save the form and log out from the current session

Step 6: Log in again and submit a sample request and once completed, press view output button. Your output will be opened in browser...... 

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

RMAN Configurations

CONFIGURE RETENTION POLICY

It used with the 2 different options. Recovery Window or Redundancy

Redundancy: CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
If you set Redundancy to 1, RMAN will keep one backup. If you take second backup , RMAN will sign previous backup as obsolete. You can delete obsolete backup with “delete obsolete” command.

Recovery Windows: CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
If you set Recovey windows to 3 days, RMAN will sign backups as obsolete older than 3 days. For example, we have 4 backups. And our backup dates are 16 may, 18 may, 21 may and 23 may. If we set Recovery window to 3 days, RMAN must sign 16may and 18 may backups as obsolete (23may – 3 days=20may). But RMAN signs 18may backup as not obsolete. Because RMAN automatically detects backups. And 18may backup is needed for recovery of 20may.

CONFIGURE DEFAULT DEVICE TYPE

Backup can be taken two different locations. Tape and Disk
For backing up to disk: CONFIGURE DEFAULT DEVICE TYPE TO DISK;
For backing up to tape: CONFIGURE DEFAULT DEVICE TYPE TO SBT;

CONFIGURE CONTROLFILE AUTOBACKUP ON/OFF

Automatically backups the controlfile to fra. (If you dont set FRA then it puts backup of controlfile to $ORACLE_HOME/dbs by default)

CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO ‘%F’

By default, RMAN automatically names control file backups and  saves them into FRA. To configure RMAN  to write control file backups to the specific directory:  %F will generate a unique filename likes  c-‘IIIIIIIIII-YYYYMMDD-QQ’ . Here  ‘IIIIIIIIII’ is DBID, ‘YYYYMMDD’ is date and  ‘QQ’ is hexadecimal id. You can also backup controlfile to specific location. For example;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO ‘ora_home/oradata/cf_%F’;
You can also reset configuration.
CONFIGURE CONTROLFILE AUTOBACKUP FOR DEVICE TYPE DISK CLEAR;
You can also write in RUN script.

RMAN> SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE sbt TO 'controlfile_%F';
RMAN> BACKUP AS COPY DATABASE;
RMAN> RUN {
       SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/tmp/%F.bck';
       BACKUP AS BACKUPSET DEVICE TYPE DISK DATABASE;
      }

Format	Description
%a	Specifies the activation id number of the database.
%A	Specifies the activation id number of the database completed 0
%c	Specifies the copy number of the backup piece within a set of duplexed backup pieces. The maximum value is 256.
%d	Specifies the name of the database
%D	Specifies the current day of the month in format DD
%e	Specifies the archived log sequence number
%f	Specifies the absolute file number
%F	Combines the DBID, day, month, year, and sequence into a unique and repeatable generated name
%h	Specifies the archived redo log thread number
%I	Specifies the DBID
%M	Specifies the month in format MM
%n	Specifies the name of the database. padded on the right with x characters to a total length of eight characters.
%N	Specifies the tablespace name.
%p	Specifies the piece number within the backup set
%r	Resetlogs ID
%s	Specifies the backup set number
%S	Specifies the backup set number completed 0
%t	Specifies the backup set time stamp.
%T	Specifies the year, month, and day in format YYYYMMDD
%u	Specifies an 8-character name constituted by compressed representations of the backup set or image copy number.
%U	Specifies a system-generated unique file name.
%Y	Specifies the year in this format: YYYY.

CONFIGURE BACKUP OPTIMIZATION OFF/ON

If you set this configuration to ON then the backup command skips backing up files when the identical file has already been backed up. RMAN uses to determine whether a file is identical to a file that it is backed up with following criterias.

File type	The understanding of the same file
Datafile	The data file must have the same dbid, SCN, creation SCN, and RESETLOGS SCN and time as a data file in a backup
Archive log file	Same DBID, thread, sequence number and RESETLOGS SCN and time
Backup set	Same backup set recid and stamp.

CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET

Specifies number of channels which determines whether RMAN reads or writes in parallel. You must also specify DEVICE TYPE.

CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 3

The configure “datafile backup copies” used to specify how many copies of each backup piece should be created on the specified device type for the datafile. In my example above, it will take backup 3 copy. It is known as mirror backup. You can specify 3 different location with FORMAT option.
BACKUP DEVICE TYPE DISK COPIES 3 DATAFILE 7 FORMAT
‘/tmp/%U’,’?/oradata/%U’,’?/%U’;

CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1

The configure “archivelog backup copies” used to specify how many copies of each backup piece should be created on the specified device type for the arhive log files. You can specify 2 different location with FORMAT option.

CONFIGURE MAXSETSIZE TO UNLIMITED

You can use the MAXSETSIZE parameter on the BACKUP and configure commands to set a limit for the size of backup sets. If you set maxsetsize less than backing up datafile size then you will get an error. Default value of this configuration is “unlimited”.

CONFIGURE ENCRYPTION FOR DATABASE OFF/ON

Encrypted backups cannot be read if they are obtained by unauthorized users. This configuration specifies whether encryption will be used or not.
CONFIGURE ENCRYPTION ALGORITHM ‘AES128’

CONFIGURE COMPRESSION ALGORITHM ‘BASIC’ AS OF RELEASE ‘DEFAULT’ OPTIMIZE FOR LOAD TRUE

There are two compression method ZLIB and BZIP2. ZLIB consumes less cpu but the compression rate is low. BZIP2 consumes more cpu but the compression rate is high.
CONFIGURE COMPRESSION ALGORITHM ‘ZLIB’;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO COMPRESSED BACKUPSET;
There are 3 compression level. LOW, MEDIUM and HIGH. HIGH level is not recommended because of suited for backups over slower networks. MEDIUM level is recommended.

CONFIGURE ARCHIVELOG DELETION POLICY TO NONE

Specifies the archive log deletion policy.
In 10g you can set;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO {ARCHIVERETENTION};
In 11g you can set;
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO DISK;
The archived log deletion policy also has option specific to Data Guard. For example, if you set archive log deletion policy to the “APPLIED ON STANDBY” then RMAN can delete logs after they have been applied at all mandatory remote destinations.
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;

CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE

You can use maxpiecesize channel parameter to set limits on the size of backup pieces. In my example below, I limit the backup piece size to 2G.
CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE = 2G;

CONFIGURE SNAPSHOT CONTROLFILE NAME TO ‘/oracle/ora10g/dbs/snapcf_test11g.f’

RMAN needs a snapshot control file when resynchronizing with the recovery catalog or taking a backup of the current control file. The default location is platform specific and depends on the Oracle home of each target database. In Linux environment it locates in $ORACLE_HOME/dbs directory. You can change its location with this configuration.


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

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.

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