Migrate Oracle Apps DBA (EBS) Ver 12.2.

0, Oracle DataBase Vers

11.2.0.3 From OS Linux6.5 x86
x86--64
to Solaris 11.1 (64bit)
By GowraInfosys
Migrate Oracle Applications (EBS) Version 12.2.0 is Database Version
11.2.0.3 From Linux x64 to Solaris 11.1, Oracle Private Cloud

contact@gowrainfosys.com

Introduction
How to Migrate Oracle Applications 12.2.0 Database Instance ver 11.2.0.3 to Solaris 11.1
This document describes the process of re-creating an existing Applications Release 12.2
database instance using the datapump utilities
Datapump is the only Method certified as of now for migration EBS ver12.2.0 Oracle database
Vers 11.2.0.3
The Datapump utilities allow you to move existing data in Oracle format to and from Oracle
databases.
Datapump export files can archive database data, or move data among different Oracle
databases that run on the same or different operating systems.
This document assumes that you are already familiar with datapump.
Trouble shooting Errors, Warning and Know Issues.
Dont forget to have fun while migration.

Welcome and Introduction

contact@gowrainfosys.com

This Document address migration of Oracle Database ver 11.2.0.3 from Linux to Solaris
Source Oracle EBS version 12.2.0 with Oracle Database version 11.2.0.3 on a Linux6.5 x64
Target Oracle EBS version 12.2.0 on Linux6.5 x64. Database version 11.2.0.3 on Solaris 11.1 x64.
This document assumes that the instance R12.2.x is stable and no errors and warnings from OS or
Database or Applications (components), database Init parameters or set for the Migration.
Linux OS 6.5 is running on Oracle VM and VM server Version 3.2.8-735 Using iSCSI to access
Storage, with 520MB/s read/write, with 10GbE Network with Jumbo Frames.
Source Oracle VM configuration: (DB and EBS) 12 virtual CPUs, 14GB RAM, with two virtual NICs.
Virtual Disk 50GB for the OS, Virtual Disk 200GB for Application file system (d01), Virtual Disk
300GB for Oracle EBS data files and binaries (u01)
Target Database OS, Oracle VM configuration:(Solaris 11.1) 12 virtual CPUs, 24GB RAM, with two
virtual NICs. Virtual Disk 70GB for the OS, Virtual Disk 30GB for oracle database binaries (u01),
Virtual Disk 270GB for Oracle EBS data files (u02).
Target Application OS, Oracle VM configuration:(Linux6.5 x64) 12 virtual CPUs, 14GB RAM, with
two virtual NICs. Virtual Disk 50GB for the OS, Virtual Disk 200GB for Application file system
(d01)
Assumes good understanding and knowledge of R12.2 Application architecture and EBS adop
patching tool and oracle opatch tool and other sizing tools like SLOB2, Hammerora, swingbench
etc.

Overview

contact@gowrainfosys.com

This document is divided into Six(6) major sections

Section 1: Prepare the source system

Tasks that must be performed to prepare the source system for the database Datapump export
Section 2: Prepare a target Release 12 database instance
Tasks for creating an empty database instance in preparation for Datapump import
Section 3: Export the source Release 12 database instance
Tasks that must be performed to produce a valid export of an Applications Release 12 database
instance
Section 4: Import the Release 12 database instance
Tasks for running the datapump import utility
Section 5: Update the imported Release 12 database instance
Tasks that must be performed to restore the imported Applications Release 12 database
instance to a fully functional state

Section 6: Verification and Testing end Result

Testing using OATS and Manual verification of the Migration.

Vocabulary
contact@gowrainfosys.com

EBS Architecture Diagram

contact@gowrainfosys.com

EBS Architecture Diagram

contact@gowrainfosys.com

Source Virtual Machine configuration (EBS and DB):

Virtual Machine Disks:

Virtual Machine Networks:

contact@gowrainfosys.com

Target Virtual Machine configuration (DB only):

Virtual Machine Disks:

Virtual Machine Networks:

contact@gowrainfosys.com

Section 1: Prepare the source system

This section describes how to ensure that you have the required patches, create your datapump
export file, and capture important information that is required to import your database.
1. Apply the Applications consolidated expdp/impdp utility patch
Apply Patch 16541956 to the source administration server node. This patch provides several SQL
scripts that facilitate exporting and importing an Applications database instance.
adop phase=prepare
adop phase=apply patches=16541956
************* Start of AutoPatch session *************
AutoPatch version: 12.2.0
AutoPatch started at: Thu May 01 2014 14:57:59
APPL_TOP is set to /d01/app/oracle/EBSCRP1/fs2/EBSapps/appl
Defaults Feature Enabled = YES.
Non-Interactive Mode = YES.
Num Workers = 8.
Flags = "autoskip".
Patch Top = "/d01/app/oracle/EBSCRP1/fs_ne/EBSapps/patch/16541956".
Patch Driver File = "u16541956.drv".
Please enter the batchsize [1000] : 1000 *
...................................................
...................................................
AutoPatch is complete.
...................................................
Errors and warnings are listed in the log file
/d01/app/oracle/EBSCRP1/fs_ne/EBSapps/log/adop/2/apply_20140501_145629/EBSCRP1_g6ebscrp
1/16541956/log/u16541956.log
contact@gowrainfosys.com

2. Create a Working or /home/oracle/sol_mig_proj Database Directory

Create a working directory named sol_mig_proj in the source system that will contain all
generated files and scripts required to complete this section.
[oracle@g6ebscrp1 ~]$mkdir p /home/oracle/sol_mig_proj

3. Generate target database instance creation script aucrdb.sql

The target database instance must be created with the same tablespace structure as the source
database instance.
The export/import patch provides the auclondb.sql script which generates the aucrdb.sql script,
which you use to create the target database instance with the appropriate tablespace and file
structure.
The script converts all tablespaces except for SYSTEM to locally managed tablespaces with auto
segment space management.
Copy the $AU_TOP/patch/115/sql/auclondb.sql script from the Patch APPL_TOP on the source
administration server node to the working directory in the source database server node.
[applmgr@g6ebscrp1 ~]$ scp $AU_TOP/patch/115/sql/auclondb.sql \
oracle@g6ebscrp1:/u01/app/oracle/EBSCRP1/11.2.0/appsutil/admin/sql/
Use SQL*Plus to connect to the database as SYSTEM and run the auclondb.sql script.
It creates aucrdb.sql in the current directory. /home/oracle/sol_mig_proj
[oracle@g6ebscrp1 ~]$ sqlplus system/XXXX @$ORACLE_HOME/appsutil/admin/sql/auclondb.sql 11

contact@gowrainfosys.com

4. Record Advanced Queue settings

Copy the auque1.sql script from the $AU_TOP/patch/115/sql, It generates auque2.sql.
[applmgr@g6ebscrp1 ~]$ scp $AU_TOP/patch/115/sql/auque1.sql \
oracle@g6ebscrp1:/u01/app/oracle/EBSCRP1/11.2.0/appsutil/admin/sql/
[oracle@g6ebscrp1 ~]$ sqlplus /as sysdba \
@/u01/app/oracle/EBSCRP1/11.2.0/appsutil/admin/sql/auque1.sql

5. Remove rebuild index parameter in spatial indexes

Sqlplus /as sysdba
select table_owner,INDEX_NAME from dba_indexes where index_type='DOMAIN' and
upper(parameters) like '%REBUILD%';
set heading off
SET LINESIZE 500
set longchunksize 200000 long 200000 pages 0
spool step5_idx_parameter_spatial_idx
select 'alter index '|| INDEX_NAME || ' rebuild parameters '|| parameters ||';'
from dba_indexes where index_type='DOMAIN' and
upper(parameters) like '%REBUILD%' and table_owner='CSF';
spool off

contact@gowrainfosys.com

4. Record Advanced Queue settings - 2

Rebuild_index parameter removed
sqlplus csf/csf
alter index CSF_WOM_AREA_LAKE_N1 rebuild parameters ( 'sdo_indx_dims=2 sdo_rtr_pctfree=10
tablespace=APPS_TS_TX_IDX') ;
alter index CSF_WOM_AREA_LANDUSE_N1 rebuild parameters ('sdo_indx_dims=2
sdo_rtr_pctfree=10 tablespace=APPS_TS_TX_IDX') ;
alter index CSF_WOM_AREA_OCEAN_N1 rebuild parameters ( 'sdo_indx_dims=2 sdo_rtr_pctfree=10
tablespace=APPS_TS_TX_IDX') ;
alter index CSF_WOM_BOUNDARY_COUNTRY_N1 rebuild parameters ('sdo_indx_dims=2
sdo_rtr_pctfree=10 tablespace=APPS_TS_TX_IDX') ;
alter index CSF_WOM_BOUNDARY_STATE_N1 rebuild parameters ( 'sdo_indx_dims=2
sdo_rtr_pctfree=10 tablespace=APPS_TS_TX_IDX') ;
alter index CSF_WOM_CITY_CAPITAL_N1 rebuild parameters ( 'sdo_indx_dims=2
sdo_rtr_pctfree=10 tablespace=APPS_TS_TX_IDX') ;
alter index CSF_WOM_CITY_METROPOLIS_N1 rebuild parameters ('sdo_indx_dims=2
sdo_rtr_pctfree=10 tablespace=APPS_TS_TX_IDX') ;
alter index CSF_WOM_CITY_SMALL_N1 rebuild parameters ( 'sdo_indx_dims=2 sdo_rtr_pctfree=10
tablespace=APPS_TS_TX_IDX') ;
alter index CSF_WOM_POI_N1 rebuild parameters ('sdo_indx_dims=2 sdo_rtr_pctfree=10
tablespace=APPS_TS_TX_IDX') ;
alter index CSF_WOM_ROAD_HIGHWAY_N1 rebuild parameters ('sdo_indx_dims=2
sdo_rtr_pctfree=10 tablespace=APPS_TS_TX_IDX') ;

contact@gowrainfosys.com

6. Synchronize Text indexes

Unsynchronized Oracle Text indexes slow down the export process. Ensure that the indexes are
synchronized before running the export.

To synchronize the indexes, run the following command:

contact@gowrainfosys.com

6. Synchronize Text indexes - 2

contact@gowrainfosys.com

Section 2: Prepare a target Release 12 database instance Solaris 11.1

This section describes how to create the empty target database and populate it with all of the
required system objects prior to running import.

1. Create target Oracle 11g Oracle home (conditional)

contact@gowrainfosys.com

Required Database Patches

Note: Refer to My Oracle Support Knowledge Document 1355068.1, Oracle E-Business Suite
12.2 Patching Technology Components Guide for guidance with the application of Database
patches.
Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes
(Doc ID 1594274.1)
Solaris 11.1 For DB required patch numbers
17600719
17693770
17875948
18116376
18259911

EBS Technology Codelevel Checker

The EBS Technology Codelevel Checker (ETCC) analyzes a Oracle Database Oracle Home and warns
of missing database bug fixes required for Oracle E-Business Suite Release 12.2. Oracle strongly
recommends the use of this utility to ensure that required database bug fixes have been installed.
ETCC can be downloaded via Patch 17537119.

contact@gowrainfosys.com

Create nls/data/9idata directory by running

oracle@gsxebscrp1db:~$ perl /u01/oracle/EBSCRP1/11.2.0/nls/data/old/cr9idata.pl
Creating directory /u01/oracle/EBSCRP1/11.2.0/nls/data/9idata ...
Copying files to /u01/oracle/EBSCRP1/11.2.0/nls/data/9idata...
Copy finished.
Please reset environment variable ORA_NLS10 to /u01/oracle/EBSCRP1/11.2.0/nls/data/9idata!

Collect fixed and dictionary Statistics

oracle@gsxebscrp1db:$ sqlplus "/as sysdba"
EXEC DBMS_STATS.GATHER_SCHEMA_STATS ('SYS');
EXEC DBMS_STATS.GATHER_DATABASE_STATS (gather_sys=>TRUE);
EXEC DBMS_STATS.GATHER_DICTIONARY_STATS;
EXEC DBMS_STATS.GATHER_FIXED_OBJECTS_STATS;

contact@gowrainfosys.com

2. Create the target initialization parameter file and CBO parameter file
The initialization parameter file (init[SID].ora) and cost-based optimizer (CBO) parameter file
(ifilecbo.ora) are located in the $ORACLE_HOME/dbs directory on the source database server
node. Copy both files to the Oracle 11g $ORACLE_HOME/dbs directory on the target database
server node.
Copy Initialization parameter from source to target (Solaris 11.1), modify parameters
accordingly

3. Create a working directory

[oracle@g6ebscrp1 ~]$ mkdir /u01/expimp

4. Create the target database instance

Copy the aucrdb.sql script, generated in Section 1, Target
/export/home/oracle/sol_mig_proj
[oracle@g6ebscrp1 ~]$ sqlplus /as sysdba
sql>spool aucrdb.log
sql>@aucrdb.sql
sql> exit

contact@gowrainfosys.com

5. Copy database preparation scripts to target Oracle home

The export/import patch that you applied to the source administration server node in
Section 1 contain four scripts that are needed on the target database server node. Copy
the following files from the $AU_TOP/patch/115/sql directory in the Patch APPL_TOP in the
source administration server node to the working directory in the target database server
node: audb1120.sql, ausy1120.sql, aujv1120.sql, and aumsc1120.sql (UNIX or Linux).
[applmgr@g6ebscrp1 ~]$ scp $AU_TOP/patch/115/sql/audb1120.sql
oracle@gsxcrp1db:~/sol_mig_proj/
[applmgr@g6ebscrp1 ~]$ scp $AU_TOP/patch/115/sql/ausy1120.sql
oracle@gsxcrp1db:~/sol_mig_proj/
[applmgr@g6ebscrp1 ~]$ scp $AU_TOP/patch/115/sql/aujv1120.sql
oracle@gsxcrp1db:~/sol_mig_proj/
[applmgr@g6ebscrp1 ~]$ scp $AU_TOP/patch/115/sql/aumsc1120.sql
oracle@gsxcrp1db:~/sol_mig_proj/
oracle@gsxcrp1db:~/sol_mig_proj$
oracle@gsxcrp1db:~/sol_mig_proj$
oracle@gsxcrp1db:~/sol_mig_proj$
oracle@gsxcrp1db:~/sol_mig_proj$

sqlplus
sqlplus
sqlplus
sqlplus

"/ as sysdba" @audb1120.sql

system/xxx @ausy1120.sql
system/xxx @aujv1120.sql
system/xxx @aumsc1120.sql FALSE SYSAUX TEMP

oracle@gsxcrp1db:$ cd $ORACLE_HOME/rdbms/admin
oracle@gsxcrp1db:$ sqlplus "/ as sysdba" @dbmsxdbschmig.sql
oracle@gsxcrp1db:$ sqlplus "/ as sysdba" @prvtxdbschmig.plb
oracle@gsxcrp1db:$ sqlplus "/ as sysdba"
SQL> exec ctxsys.ctx_adm.set_parameter('file_access_role', 'public');
contact@gowrainfosys.com

6. Disable automatic gathering of statistics

[applmgr@g6ebscrp1 ~]$ scp $APPL_TOP/admin/adstats.sql oracle@gsxcrp1db:~/sol_mig_proj/
oracle@gsxcrp1db:~/sol_mig_proj$ sqlplus "/ as sysdba"
SQL> alter system enable restricted session;
SQL> @adstats.sql
oracle@gsxcrp1db:~/sol_mig_proj $ sqlplus "/ as sysdba"
SQL> alter system disable restricted session;
SQL> exit;

7. Back up the Target (Solaris 11.1) database instance

It is important a backup is done, u01 and u02 on Solaris 11.1

Make sure it is restorable at easy.

contact@gowrainfosys.com

Section 3: Export the source Release 12 database instance - Source

Tasks that must be performed to produce a valid export of an Applications Release 12 database
instance
1. Create the export parameter file and Oracle directory in Source instance
[applmgr@g6ebscrp1 ~]$ scp $AU_TOP/patch/115/import/auexpdp.dat
oracle@g6ebscrp1:~/sol_mig_proj/
oracle@g6ebscrp1:~/sol_mig_proj$ sqlplus "/ as sysdba"
SQL> create directory dmpdir as '/u01/expimp';
2. Ensure Applications patching cycle is complete
[applmgr@g6ebscrp1 ~]$ adop phase=cutover
*** Source new envinoment variables
[applmgr@g6ebscrp1 ~]$ adop phase=cleanup
3. Shut down Applications server processes
***Shut down all Applications server processes except the database and the Net8 listener for the
database. Users cannot use the Applications until the import is completed. -- Down Time
4. Export the Applications database instance
oracle@g6ebscrp1:~/sol_mig_proj$ expdp "'/ as sysdba'" parfile=[export parameter file name]
5. Revoke privilege from source system schema
oracle@g6ebscrp1:~/sol_mig_proj$ sqlplus /as sysdba
SQL> revoke EXEMPT ACCESS POLICY from system;
contact@gowrainfosys.com

Section 4: Import the Release 12 database instance

Tasks for running the datapump import utility
1. Create the import parameter files
[applmgr@g6ebscrp1 ~]$ scp $AU_TOP/patch/115/import/auimpdp.dat
oracle@gsxcrp1db:~/sol_mig_proj/
oracle@gsxcrp1db:~/sol_mig_proj$ sqlplus "/ as sysdba"
SQL> create directory dmpdir as '/u02/expimp';
2. Copy the export dump files
[oracle@g6ebscrp1 ~]$ scp /u01/expimp/* oracle@gsxcrp1db:/u02/expimp/
3. Import the Applications database instance
[oracle@gsxcrp1db ~]$ impdp "'/ as sysdba'" parfile=auimpdp.dat
***Typically, import runs for several hours.
4. Revoke privilege from target system schema
[oracle@gsxcrp1db ~]$ sqlplus /as sysdba
SQL> revoke EXEMPT ACCESS POLICY from system;

contact@gowrainfosys.com

Error not related to Oracle Apps

Section 5: Update the imported Release 12 database instance

Tasks that must be performed to restore the imported Applications Release 12 database instance to a fully
functional state

1. Reset Advanced Queues

Copy the auque2.sql script that was generated in Section 1 from the working directory in the
source database server node to the working directory in the target database server node.
[oracle@g6ebscrp1 ~]$ cd ~/sol_mig_proj/
[oracle@g6ebscrp1 ~]$ scp auque2.sql oracle@gsxcrp1db:~/sol_mig_proj/
oracle@gsxcrp1db:~/sol_mig_proj$ sqlplus "/ as sysdba @auque2.sql
2. Run adgrants.sql
[applmgr@g6ebscrp1 ~]$scp $APPL_TOP/admin/adgrants.sql

oracle@gsxcrp1db:~/sol_mig_proj/

oracle@gsxcrp1db:~/sol_mig_proj$ sqlplus "/ as sysdba @adgrants.sql apps

3. Grant create procedure privilege on CTXSYS
[applmgr@g6ebscrp1 ~]$scp $AD_TOP/patch/115/sql/adctxprv.sql
oracle@gsxcrp1db:~/sol_mig_proj/
oracle@gsxcrp1db:~/sol_mig_proj$ sqlplus "/ as sysdba" @adgrants.sql [system passwd] CTXSYS
4. Start the new database listener (conditional)
Attention: Set the TNS_ADMIN environment variable to the directory where you created
your listener.ora and tnsnames.ora files.
contact@gowrainfosys.com

5. Deregister the current database server

oracle@gsxcrp1db:~/sol_mig_proj$ sqlplus apps/[APPS password]
SQL> exec fnd_conc_clone.setup_clean;
6. Implement and run AutoConfig
Implement and run AutoConfig in the new Oracle home on the database server node. You must
also run AutoConfig on each application tier server node on both the Patch and Run APPL_TOP
to update the system with the listener.
[applmgr@g6ebscrp1 ~]$ $AD_TOP/bin/adconfig.pl contextfile=[PATCH CONTEXT FILE] run=INSTE8
7. Gather statistics for SYS schema
[oracle@gsxcrp1db ~]$ sqlplus "/ as sysdba
SQL> alter system enable restricted session;
SQL> @adstats.sql
[oracle@gsxcrp1db ~]$ sqlplus "/ as sysdba
SQL> alter system disable restricted session;
SQL> exit;
8. Re-create custom database links (conditional)
[oracle@gsxcrp1db ~]$ sqlplus apps/[apps password]
SQL> select db_link from dba_db_links;

**The EDW_APPS_TO_WH and APPS_TO_APPS database links, if they exist, should have
been updated with the new port number by AutoConfig in the previous step.
contact@gowrainfosys.com

9. Create ConText objects

Certain ConText objects are not preserved by the import process.
The consolidated
export/import utility patch that you applied to the source administration server node in
Section 1 contains a perl script, dpost_imp.pl, that you can run to generate an AutoPatch
driver file. You use this driver file to call the scripts that create these objects.
[applmgr@g6ebscrp1 ~]$ cd /d01/oracle/EBSCRP1/fs_ne/EBSapps/patch
[applmgr@g6ebscrp1 ~]$ perl $AU_TOP/patch/115/bin/dpost_imp.pl solmig.drv 11
[applmgr@g6ebscrp1 ~]$ adop phase=apply hotpatch=yes
***When prompted for additional command line arguments, type
options=nocopyportion,nogenerateportion.
10. Populate CTXSYS.DR$SQE table
oracle@gsxcrp1db: $ sqlplus apps/[apps password]
SQL> exec icx_cat_sqe_pvt.sync_sqes_for_all_zones;
11. Compile invalid objects
oracle@gsxcrp1db:$ sqlplus "/ as sysdba" @$ORACLE_HOME/rdbms/admin/utlrp.sql
12. Re-create XLA packages (conditional)
[applmgr@g6ebscrp1 ~]$ scp $XLA_TOP/patch/115/sql/xla6128278.sql
oracle@gsxcrp1db:~/sol_mig_proj/
oracle@gsxcrp1db:$ sqlplus /as sysdba
SQL> @xla6128278.sql xla6128278.spool.out

contact@gowrainfosys.com

13. Run AutoConfig on the Run APPL_TOP

Certain ConText objects are not preserved by the import process.
The consolidated
export/import utility patch that you applied to the source administration server node in
Section 1 contains a perl script, dpost_imp.pl, that you can run to generate an AutoPatch
driver file. You use this driver file to call the scripts that create these objects.
[applmgr@g6ebscrp1 ~]$ $INST_TOP/admin/scripts/adautocfg.sh

14. Maintain Applications database objects

Run AD Administration on the target administration server node. From the Maintain Applications
Database Objects menu, perform the following tasks:
a. Compile flexfield data in AOL tables
b. Recreate grants and synonyms for APPS schema

15. Start Applications server processes

Start all the server processes on the target Applications system. You can allow users to access the
system at this time.

16. Create DQM indexes

Create DQM indexes by following these steps:
a. Log on to Oracle Applications with the "Trading Community Manager" responsibility
b. Click Control > Request > Run
c. Select "Single Request" option
d. Enter "DQM Staging Program" name
e. Enter the following parameters:
Number of Parallel Staging Workers: 4
Staging Command: CREATE_INDEXES
Continue Previous Execution: NO
Index Creation: SERIAL
f. Click "Submit"

Database Version: 11.2.0.3 (Solaris 11.1)

Result
contact@gowrainfosys.com

Oracle Applications: 12.2.0 (Linux x86-64)

Database Version: 11.2.0.3 (Solaris 11.1)

Result
contact@gowrainfosys.com

Oracle Applications: 12.2.0 (Linux x86-64)

Export/Import Process for Oracle E-Business Suite Release 12.2 Database Instances Using Oracle
Database 11.2 (Doc ID 1613716.1)
Oracle Database Utilities 11g Release 2 (11.2). - Documentation
Database Initialization Parameters for Oracle E-Business Suite Release 12 (Doc ID 396009.1)
Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes (Doc
ID 1594274.1)
Using Oracle E-Business Suite Release 12.2 with a Database Tier Only Platform on Oracle 11.2
(Doc ID 1613707.1)
Migrating OLAP From 32 Bits to 64 Bits or Across Platforms (Doc ID 352306.1)
Oracle Database Net Services Administrator's Guide, 11g Release 2 (11.2) - Documentation
Oracle E-Business Suite Setup Guide Release 12.2 - Documentation
Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes (Doc
ID 1594274.1)ADOP phase=prepare Is Failing At adconfig On The adgenjky.sh Script (Doc ID
1638491.1)

Refrences
contact@gowrainfosys.com

 How to upgrade Oracle Applications 12.2.2 to 12.2.3

Database and Application server running on Single Node
OS version Linux 6.5 verify and apply patches.
Oracle Database version 11.2.0.3 apply required patches.
Forms and Reports 10.1.2.3 apply required Patches.
Web Tier and Utilities (OHS) 11.1.1.6 required Patches.
Weblogic server version 10.3.6.0 required patches.
Applying R12.AD.C.Delta.4 and R12.TXK.C.Delta.4 Release Update Packs.
Apply Oracle E-Business Suite 12.2.3 Release Update Pack
HR Global Patch, DataInstall and hrglobal.drv
Apply Oracle E-Business Suite Release 12.2.3 Help

Summary
contact@gowrainfosys.com

11gR2.0.4 RAC Installation and configuration, Non-GNS,

ASM, on Oracle Private Cloud with Vmotion on Linux,
Solaris, AIX, HP-UX, Linux 6.511.1. Oracle Apps R12.2
/R12.1/11i Migration, Upgrade, re - implementation
Reference oracle Installation and configuration documents,
and Admin documents, As always, My oracle support for
changes and updates with oracle technology.
To engage and services from GowraInfosys, Please contact,
contact@gowrainfosys.com, Phone: (510) 371-6999 with
Oracle databases, oracle applications, installation
configure, update, Migrate, DR, Tuning, Infrastructure
sizing and recommendations for Oracle Apps and Oracle
database. Remote support for customers
Send your Questions to contact@gowrainfosys.com

Contact and other information

contact@gowrainfosys.com