Migrating Oracle E-Business Suite R12 from Linux 32-bit to Linux 64-bit [ID 471566.

1]
Execution date [13 and 14 of May 2011]

Attention: A full backup of the Oracle E-Business Suite system should be made before carrying out the
migration to the target machine.

$ tar –cvzf oradata_data&time.tar.gz ?/oradata

Prerequisites
Prior to performing the migration, both the source and target systems must meet the requirements documented in
Installation and Upgrade Notes (Linux 32-bit and Linux 64-bit, respectively) and Cloning Oracle Applications Release 12
with Rapid Clone.
 Perform all prerequisite steps in the Rapid Clone document
Section 1: Prerequisites of the Cloning Oracle Applications Release 12 with Rapid Clone document details the
prerequisite steps to clone an Oracle E-Business Suite system. The platform migration process in this document
requires cloning the application tier components from the Linux 32-bit environment to the Linux 64-bit
environment. Perform all steps in Section 1: Prerequisites to prepare both the source and target systems for the
migration of the Oracle E-Business Suite system.
Section 1: Prerequisite Tasks
Before cloning, prepare the source system by applying any required patches and running AutoConfig.
1. Verify OS requirements on target system
Before cloning to a new server, ensure the target system meets all the requirements for Oracle Applications
Release 12 stated on the Oracle Applications Release Notes, and on the Oracle Applications Installation and
Upgrade Notes for each Platform. For the latest installation guidelines refer to My Oracle Support Knowledge
Document 405565.1.
Note: On Microsoft Windows, Rapid Clone is not currently certified for use from Domain User Accounts.
2. Verify source and target system software components and versions
In addition to the Oracle Applications software requirements (see Oracle Applications Installation Guide: Using
Rapid Install), the following software component versions must exist on the source or target nodes as
applicable. The 'Location' column indicates the node where the software component must reside.

Table 1: Software Requirements

Software Minimum Required
Comments
Component Version Location
2.3 All source Download from InfoZip. Zip must be in your $PATH. If using files bigger
Zip
(or higher) system nodes than 2Gb, you should use InfoZip ZIP 3.0 or higher.
5.52 All source Download from InfoZip. Unzip must be in your $PATH. If using files
Unzip
(or higher) system nodes bigger than 2Gb, you should use InfoZip UNZIP 5.52 or higher.
The required operating system utilities for your platform must be in your
Operating All target $PATH when running adcfgclone.pl. For example, make, ld, and ar on
N/A
system utilities system nodes UNIX. Refer to Oracle Applications Installation Guide: Using Rapid Install
(see Footnote 1)
Use the Perl shipped with OracleAS 10.1.3 and Database 10g, or
All target
Perl 5.x download it from Perl.com. Perl must be in your $PATH, and $PERL5LIB
system nodes
must be set correctly before cloning.

Footnote 1 This is the Release 12.1.1 version; versions for earlier releases are also available from the Oracle E-
Business Suite Online Documentation Library
3. Apply the latest AD patch
Refer to My Oracle Support to obtain the latest AD patch. At the time of writing this note, the following
patches were available:
4. For Release 12.1:

Apply patches as listed in Table 2.b.

5. Table 2.b: Release 12.1 AD patches
Patch Description
9239089 R12.AD.B.DELTA.3
6. Apply the latest AutoConfig template patch
Update the Oracle Applications file system with the latest AutoConfig template files by applying the TXK
AutoConfig Template rollup patch to all application tier server nodes. Refer to My Oracle Support Knowledge
Document 387859.1 for details of the latest AutoConfig Template rollup patch.
7. Apply the latest Rapid Clone patches
Update the Oracle Applications file system with the latest Rapid Clone files by applying the following patches
to all Applications nodes.
For Release 12.1:

Apply patches as listed in Table 3.b.

Table 3.b: Release 12.1 Rapid Clone patches
Patch Description
9171651:R12.OAM.B 12.1 RAPIDCLONE CONSOLIDATED FIXES JUL/2010
9833058:R12.OAM.B HOT CLONE FAILS WITH ORA-00201 DURING RECOVERY MANAGER
9833058:R12.OAM.B HOT CLONE FAILS WITH ORA-00201 DURING RECOVERY MANAGER
12404574:R12.OAM.B ORACLE_HOME REGISTRATION DOES NOT HAPPEN WITH CENTRAL INVENTORY ON LOZ
8. Apply Platform Migration Patches
Update the Oracle E-Business Suite file system with the following patches:
For Release 12.1:
No patches required at this time.
9. Apply Additional Patches (Conditional)
If not already applied, update the Oracle E-Business Suite file system with the following patches:
For Release 12.1:
No patches required at this time.

10. Identify Technology Stack Updates

If you have applied any patches on the Oracle E-Business Suite Technology Stack you must apply them on the
Target System after the migration. At this point, you must identify all the patches applied to the Oracle
Application Server 10.1.2 and 10.1.3 ORACLE_HOMEs on the Source System, so they can be applied to the
Target System in a later step.
a. Verify the patch level on the ORACLE_HOMEs by executing the Technology Stack Inventory Utility. This
utility will produce an HTML report (or text report if desired). Review any required actions before
proceeding with the Applications Technology updates.
b. Establish the needed environment parameters by sourcing the Applications environment file as the owner
of the application tier file system.
c. Ensure the "APPLRGF" variable is set in environment. If not, set it to the same value as "APPLTMP".
d. Navigate to [FND_TOP]/patch/115/bin. Run the utility as follows:
Operating
Command Line
System
UNIX/Linux $ perl $FND_TOP/patch/115/bin/TXKScript.pl
-script=$FND_TOP/patch/115/bin/txkInventory.pl
-txktop=$APPLTMP -contextfile=$CONTEXT_FILE
 -appspass=apps
-outfile=$APPLTMP/Report_Inventory.html
C:\>perl %FND_TOP%\patch\115\bin\TXKScript.pl
-script=%FND_TOP%\patch\115\bin\txkInventory.pl
Windows -txktop=%APPLTMP% -contextfile=%CONTEXT_FILE%
-appspass=apps
-outfile=%APPLTMP%/Report_Inventory.html

e. Where:
Parameter Usage
txktop Temporary working directory use by Perl Modules. Should not be an empty string.

contextfile Location of the context file. If not passed, default is picked from the environment.

appspass APPS schema password. If not passed, default password is used.

outfile Location for the report being generated. If not passed, the default location is [APPLTMP]/TXK.

To generate the report in text format, the parameter -reporttype=text needs to be passed to the above
commands. For example:

$ outfile=$APPLTMP/Report_Inventory.html -reporttype=text

11. Run AutoConfig on the application tiers

Follow the steps under section " Run AutoConfig on the Application Tiers " in My Oracle Support Knowledge
Document 387859.1 to run AutoConfig on all application tier nodes.
$ sh <INST_TOP>/admin/scripts/adautocfg.sh

12. Prepare the source system application tier for cloning

Log on to the source system as the APPLMGR user, and run the following commands on each node
that contains an APPL_TOP:
$ cd [INST_TOP]/admin/scripts
$ perl adpreclone.pl appsTier

13. Synchronize appsutil on the database tier nodes

Follow the steps under section "Copy AutoConfig to the RDBMS ORACLE_HOME" in My Oracle Support
Knowledge Document 387859.1 to copy AutoConfig and Rapid Clone files to each database node via the
admkappsutil.pl utility.
14. Copy AutoConfig to the RDBMS ORACLE_HOME
Update the RDBMS ORACLE_HOME file system with the AutoConfig files by performing the following steps:
 On the application tier (as the APPLMGR user):
o Log in to the APPL_TOP environment (source the environment file)
o Create appsutil.zip file
perl <AD_TOP>/bin/admkappsutil.pl
o This will create appsutil.zip in <INST_TOP>/admin/out
 On the database tier (as the ORACLE user):
o Copy or FTP the appsutil.zip file to the <RDBMS ORACLE_HOME>
cd <RDBMS ORACLE_HOME>
unzip -o appsutil.zip
15. Run AutoConfig on the database tier
Follow the steps under section "Run AutoConfig on the Database Tier" in My Oracle Support Knowledge
Document 387859.1 to run AutoConfig on the database tier nodes.

$ sh <RDBMS_ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME>/adautocfg.sh
 16. Prepare the source system database tier for cloning
Log on to the source system as the ORACLE user, and run the following commands:
$ cd [RDBMS ORACLE_HOME]/appsutil/scripts/[CONTEXT_NAME]
$ perl adpreclone.pl dbTier

17. Maintain snapshot information

Log in to each application tier node as the APPLMGR user, and run "Maintain Snapshot information" in AD
Administration. Refer to Oracle Applications Maintenance Utilities for more information (this is the Release 12.1
version; versions for earlier releases are also available from the Oracle E-Business Suite Online Documentation
Library).

Migration
The migration of the E-Business Suite system from the 32-bit environment to the 64-bit environment is a two steps
process of migrating the database using the process documented in Using Oracle E-Business Suite Release 12 with a
Database Tier Only Platform on Oracle 10g Release 2 and migrating the application tier using the process documented in
Cloning Oracle Applications Release 12 with Rapid Clone .

Migrate the Database

Refer to Section 3: Migration Procedure of Using Oracle E-Business Suite Release 12 with a Database Tier Only Platform on
Oracle 10g Release 2 and perform the following steps.
1. Shut down the application tier services
2. De-register the original database
3. Create a .trc file to use as template to recreate the control files on the target machine
4. Shut down the original (source) database
5. (Option A) Migrate Linux 32-bit database to Linux Itanium
Note: Option A also applies to database migrations from Linux 32-bit to Linux 64-bit.
6. Migrate OLAP analytical workspaces

Install Operating System Linux 64bit

1. Partition detail as follows:
o / 48GB
o SWAP 20GB
o /boot 100MB
o /oradata 500GB
Note : change ownership of /STAGER12 to oracle user
#chown oracle(userid):oinstall(groupid) /statger12
#chown oracle(userid):oinstall(groupid) /oradata
Follow these below steps After completion OS installation:
2. Operating Systems Requirements
Oracle E-Business Suite R12 is supported on Linux 64-bit operating systems running on the x86-64 hardware
architecture.
3. Operating System Supported Versions
The following table lists the supported operating system versions.
Operating System Name Supported Version
o Oracle Linux o 4 - Update 4 or higher (64-bit)
o Oracle Linux o 5 - Update 1 or higher (64-bit)
o Red Hat Enterprise Linux o 4 - Update 4 or higher (64-bit)
o Red Hat Enterprise Linux o 5 - Update 1 or higher (64-bit)
o SUSE Linux Enterprise Server o 9 - SP3 or higher (64-bit)*
 o SUSE Linux Enterprise Server o 10 - GA, SP1 or higher (64-bit)
*: only supported on the application (or middle) tier for upgrade customers in a multi-node system, or for both
application and database tiers if the customer is on 10gR2. This OS is not supported for a new installation of
12.1.1 because 11gR1 of the Database is delivered with Rapid Install and is not supported on these OS'es.

4. Kernel Requirements
The following table lists the required minimum kernel versions (to determine version, enter: $ uname -r):
Operating System Kernel
o Oracle Linux 4 o 2.6.9-42.0.0.0.1.EL

o Oracle Linux 5 o 2.6.18-53.1.4.EL51

o Red Hat Enterprise Linux AS/ES 4 o 2.6.9-42.EL

o Red Hat Enterprise Linux AS/ES 5 o 2.6.18-53.1.4.EL51

o SUSE Linux Enterprise Server 9 o 2.6.5-7.244

o SUSE Linux Enterprise Server 10 o 2.6.16.21-0.8

1
: The Oracle Unbreakable Enterprise Kernel (UEK) version 2.6.32 is supported as well as the default kernel

5. Oracle Linux 5*
Red Hat Enterprise Linux 5* (base and Advanced Platform)
Update 1 (5.1) or higher of Oracle Linux 5 is required
Update 1 (5.1) or higher of Red Hat Enterprise Linux (RHEL) 5 is required
The following packages (or versions of packages) are not part of the OS distribution media and must be
downloaded separately (from http://oss.oracle.com/projects/compat-oracle/files/Enterprise_Linux/ for both Oracle
Linux 5 and RHEL 5) and installed manually:
o openmotif21-2.1.30-11.EL5.i3861
o xorg-x11-libs-compat-6.8.2-1.EL.33.0.1.i386
For Update 1 or 2:
o binutils-2.17.50.0.6-6.0.1.x86_642
For Update 3:
o binutils-2.17.50.0.6-9.0.1.x86_642
For Update 4 (5.4) or higher, see workaround listed below in the 'After Installing or Upgrading' section.

6. Relink Advanced Supply Chain Planning executables (for SLES 10 and Oracle Linux/RHEL 5.4 or
higher only)
During the relink phase of the installation of EBS Release 12 (12.1.1) on SLES 10 or Oracle Linux/RHEL 5.4
(Update 4 or higher), failures will result while relinking the Advanced Supply Chain Planning (ASCP) executables
MSO, MSC, MSR and FEM. To fix this problem, users are required to replace the following line under the Linux
section of the $AD_TOP/bin/adrelinknew.sh:
CPP_LDFLAGS=' -L$(ORACLE_HOME)/lib -L$(ORACLE_HOME)/lib/stubs -lclntsh'
with
CPP_LDFLAGS=' -L$(ORACLE_HOME)/lib -L$(ORACLE_HOME)/lib/stubs -lclntsh -Wl,--noinhibit-exec'
After making this change, users are then required to run the adadmin utility and relink application executables.

Additional Information:
The application of an EBS Release Update Pack (RUP) or AD family pack could over-write the adrelinknew.sh file - users
must then re-edit and make changes to the above file in order to avoid relinking failures.
 The following packages must be installed from the Oracle Linux 5 or RHEL 5 distribution media:
o gcc-4.1.2-14.el5.x86_64
o gcc-c++-4.1.2-14.el5.x86_64
o glibc-2.5-18.i686 (32-bit)
o glibc-2.5-18.x86_64
o glibc-common-2.5-18.x86_64
o glibc-devel-2.5-18.i386 (32-bit)
o glibc-devel-2.5-18.x86_64
o libgcc-4.1.2-14.el5.i386
o libgcc-4.1.2-14.el5.x86_64
o libstdc++-devel-4.1.2-14.el5.i386
o libstdc++-devel-4.1.2-14.el5.x86_64
o libstdc++-4.1.2-14.el5.i386
o libstdc++-4.1.2-14.el5.x86_64
o make-3.81-1.1.x86_64
o gdbm-1.8.0-26.2.1.i386
o gdbm-1.8.0-26.2.1.x86_64
o libXp-1.0.0-8.1.el5.i386
o libXp-1.0.0-8.1.el5.x86_64
o libaio-0.3.106-3.2.i386
o libaio-0.3.106-3.2.x86_64
o libgomp-4.1.2-14.el5.x86_64
o sysstat-7.0.0-3.el5.x86_64
o util-linux-2.13-0.45.el5.x86_64
o compat-libstdc++-296-2.96-138.i386
o compat-libstdc++-33-3.2.3-61.i386
Additionally, the following RPMs are required for an 11gR1 Database (which is bundled with the 12.1.1 release) on
the database tier:
o compat-libstdc++-33-3.2.3-61.x86_64
o elfutils-libelf-devel-0.125-3.el5.x86_64
o elfutils-libelf-devel-static-0.125-3.el5.x86_64
o libaio-devel-0.3.106-3.2.x86_64
o unixODBC-2.2.11-7.1.i386
o unixODBC-devel-2.2.11-7.1.i386
o unixODBC-2.2.11-7.1.x86_64
o unixODBC-devel-2.2.11-7.1.x86_64
o kernel-headers-2.6.18-8.el5.x86_64

Note: After installing these patches

run $ ldconfig -v
Note:
1
: The openmotif package version must be 2.1.30 (for example, openmotif-2.2.3-10.RHEL4.5 is not supported).
2
: This GNU linker (ld) version 2.17 provided by Oracle is required for relinking the modules in Advanced Planning
& Scheduling (MSC, MSO, MSR) and Profitability Manager (FEMCCE)

7. JDK 6.0 Requirements

JDK 6 is bundled with Oracle E-Business Suite version 12.1.1.
Additional Information: Check the Sun Web site for any updates to the JDK 6 requirements for Linux (64-bit):
http://java.sun.com/javase/6/webnotes/install/jdk/install-linux.html#requirements
8. Software Requirements
The following maintenance tools must be installed on all machines, and their locations specified both in the PATH
of the account that runs Rapid Install and in the PATH of the accounts that will own the database tier and
application tier file systems.
o ar
o gcc
o g++
o ksh
o ld
o linux32
o make
o X Display Server

9. Kernel Settings
Edit the /etc/sysctl.conf file to configure your kernel settings. After editing the file, use the "sysctl -p" command or
restart the system to invoke the new settings.
Parameter Value

o kernel.semmsl o 2561

o kernel.semmns o 320001

o kernel.semopm o 1001

o kernel.semmni o 1421

o kernel.shmall o 2097152

o kernel.shmmax o Half the size of the physical memory (in bytes), and at least
21474836482
o kernel.shmmni o 4096

o kernel.msgmax o 8192

o kernel.msgmnb o 65535

o kernel.msgmni o 2878

o fs.file-max o 131072

o net.ipv4.ip_local_port_range o 10000 650003

o net.core.rmem_default o 262144

o net.core.rmem_max o 4194304

o net.core.wmem_default o 262144

o net.core.wmem_max o 262144
1
: set using the following entry in the /etc/sysctl.conf file: kernel.sem = 256 32000 100 142
2
: On the server running the EBS Database, this kernel parameter must be the lesser of half the size of the
physical memory (in bytes) and 4294967295
3
: values recommended for the local port range may need to be adjusted according to the specific needs of the
user's environment in order to avoid port conflicts.
On SUSE Linux Enterprise Server 9 and 10, ensure that you set the following kernel parameter:
disable_cap_mlock = 1
10. Domain Name System (DNS) Resolver Parameters
Two Domain Name System (DNS) resolver parameters (timeout and attempts) are set by default to low values
when the operating system is installed. These low values may cause attempted network connections to an Oracle
database to fail. If this happens, add or update the following entries to these minimum settings in the
/etc/resolv.conf file on each server node:
options attempts:5
options timeout:15
11. Verifying Host Names
Use the following to verify host name settings:
For Oracle Linux 4 and 5, and Red Hat Enterprise Linux AS/ES 4 and 5:
o Verify that the /etc/hosts file is formatted as follows:
localhost.localdomain localhost
[ip_address] [node_name].[domain_name] [node_name]
o Verify that the /etc/sysconfig/network file is formatted as follows:
HOSTNAME=[node_name].[domain_name]
If the /etc/sysconfig/networking/profiles/default/network file exists, remove it.
o If you changed any files in the previous steps, restart the system.
For SUSE Linux SLES 9 and 10:
o Verify that the /etc/hosts file is formatted as follows:
127.0.0.1 localhost.localdomain localhost
[ip_address] [node_name].[domain_name] [node_name]
o If you changed any files in the previous step, restart the system.
12. Modifying the Number of Open File Descriptors
Open the /etc/security/limits.conf file and change the existing values for "hard" and "soft" parameters as
follows. Restart the system after making changes.
Note: If the current value for any parameter is higher than the value listed in this document, then do not change the value
of that parameter.
* hard nofile 65535
* soft nofile 4096
* hard nproc 16384
* soft nproc 2047

13. OS Library Patch for Oracle HTTP Server (on Oracle Linux 5 and RHEL 5 only)
Download and apply the patch 6078836 from My Oracle Support to fix an issue with the Oracle HTTP Server
(missing libdb.so.2) bundled with the E-Business Suite technology stack.
Note that this patch (which includes a required operating system library) must be applied before installing Oracle
E-Business Suite.

14. Link to Motif library in Oracle Application Server 10.1.2 (on Oracle Linux 5 and RHEL 5 only)
Perform the following command (as root on your system) to update a required link to a Motif library prior to
relinking or patching the 10.1.2 Application Server Oracle Home:
# unlink /usr/lib/libXtst.so.6
# ln -s /usr/X11R6/lib/libXtst.so.6.1 /usr/lib/libXtst.so.6
Without this updated link, you may see the following errors during a relink of the 10.1.2 Oracle Home:
/usr/lib/libXtst.so.6: undefined reference to `__stack_chk_fail@GLIBC_2.4'
/usr/lib/libXtst.so.6: undefined reference to `__fprintf_chk@GLIBC_2.3.4'
/usr/lib/libXtst.so.6: undefined reference to `__sprintf_chk@GLIBC_2.3.4'
Since the ldconfig command overrides this link, the above link command (ln) will have to be re-issued after
running the ldconfig command.

15. OPMN port conflict

Attention: By default, the OPMN service of the Application Server technology stack listens on port 6000 when started up
during Rapid Install. This can conflict with the X11 port used for the graphics console on Linux servers and prevent Rapid
 Install from completing.

To address this issue, perform the following steps before installing or upgrading:
o Check if the port 6000 is being used ("netstat -a | grep 6000")
o If so, you should disable the graphics console login process on the Linux server. This can be accomplished
by logging in as root and issuing the following commands:
o Find the process that uses port 6000 by the command "lsof -i TCP:6000".
o Use "kill -9" to abort the process found in the previous step
o Confirm that nothing is listening at port 6000 ("netstat -a | grep 6000")
o Modify /etc/inittab by changing "id:5:initdefault:" to "id:3:initdefault:"
o Run "/sbin/init 3" to restart dtlogin

16. Unset environment variable before installing (for SLES 10 only)

Unset the ENV environment variable prior to installing (to avoid failure of the registration of the 10.1.2 Oracle
Home during install):
$ unset ENV

17. LD_LIBRARY_PATH Environment Variable

Dynamic libraries are used as part of the relinking and execution processes. The LD_LIBRARY_PATH environment
variable is used by Oracle E-Business Suite to locate the required dynamic libraries at runtime - this variable is set
by the Rapid Install wizard during the installation of EBS as well as by the Rapid Clone script (adcfgclone) when
configuring the target system.
If you need to change these values, use the Edit Parameters function of the OAM AutoConfig tool (by logging in as
'System Administrator' responsibility, clicking on 'System Administrator', selecting 'AutoConfig' under 'Oracle
Applications Manager', and clicking on the 'Environments' tab):
18. On each application tier server node:
LD_LIBRARY_PATH is set in three places:
o $APPL_TOP/admin/adovars.env
o $ORA_CONFIG_HOME/10.1.2/[CONTEXT_NAME].env, in the 10.1.2 Oracle home directory
o $ORA_CONFIG_HOME/10.1.3/[CONTEXT_NAME].env, in the 10.1.3 Oracle home directory
In the AutoConfig interface, this corresponds to:
Location Parameter
LD_LIBRARY_PAT
adovars
H
LD_LIBRARY_PAT
tools_home (10.1.2)
H
LD_LIBRARY_PAT
web_home (10.1.3)
H
19. On the database server node:
LD_LIBRARY_PATH is set in $ORACLE_HOME/[CONTEXT_NAME].env which corresponds in the AutoConfig
interface to:
Location Parameter
LD_LIBRARY_PAT
db_home
H
After making these changes, run AutoConfig (adautocfg.sh) to implement the changes on the application and
database tiers.
Additional Information: See AutoConfig in Oracle E-Business Suite Maintenance Utilities for more information on
AutoConfig.
20. Net Service Listeners in Multi-user Installations
Net Service Listeners use the /var/tmp.oracle directory to store temporary files. To give all users in a multi-user
installation write privileges, update /var/tmp/.oracle with 777 permissions:
$ chmod 777 /var/tmp/.oracle

 Install the R12 10.2.0 Oracle home

Use the R12 Rapid Install to install the 10.2.0 database Oracle home on the target Linux 64-bit machine. See the
Installing Technology Stack Components chapter of the Oracle Applications Installation Guide: Using Rapid Install .

Note: The source and target database versions must be the same.

Create the RDBMS ORACLE_HOME on the target machine

Install Oracle 11g Database Release 11.2.0.1 or later on the target machine. Perform all steps in the Database
Installation subsection of Section 1 in My Oracle Support Note 1058763.1, Interoperability Notes: Oracle E-
Business Suite Release 12 with Oracle 11g Release 2 (11.2.0) .
Attention: A full backup of the Oracle E-Business Suite system should be made before carrying out the migration to the
target machine.

Attention: A full backup of the Oracle E-Business Suite system should be made before carrying out the migration
to the target machine.

$ tar –cvzf oradata_data&time.tar.gz ?/oradata

Starting Rapid Install

$ cd /u01/stager12/startCD/disk1/rapidwiz
$ . /rapidwiz –techstak
RDBMS installation completed……………………….
Section 3: Migration Procedure
Perform the steps below to migrate the Applications database from the original platform to the target platform.

Note: The Oracle E-Business Suite system will be unavailable during the migration process.

a. Shut down the application tier services

Log on to each machine in the application tier and stop the Oracle E-Business Suite services.
$ cd [COMMON_TOP]/admin/scripts/[CONTEXT_NAME]
$ adstpall.sh apps/[APPSpwd]

b. Create a .trc file to use as template to re-create the control files on the target machine.
Run the following command on the source database to create a .trc file, which you will use to recreate the
control files on the target machine in a later step.
$ sqlplus /nolog
SQL> connect / as sysdba
SQL> alter database backup controlfile to trace

c. Shut down the original (source) database.

Perform a SHUTDOWN NORMAL on the source database, and stop the database listener.

Perform a full offline database backup.

 (Option B) Migrate Linux 32-bit database to Linux x86-64

Perform the following steps to move the Linux 32-bit database to Linux x86-64:
a. Copy the database (.dbf) files from the source machine to the target machine
b. Copy the database configuration files init.ora and ifilecbo.ora
c. Modify configuration files on target machine to reflect the new environment. Also, set
_system_trig_enabled=false
d. Start up the database in nomount mode
e. Recreate the database control files
Sql> shutdown immediate;

Sql> startup upgrade;

SQL> Spool mig64.lst

f. Run $ORACLE_HOME/rdbms/admin/utlirp.sql to invalidate the PL/SQL modules

Running olap.sql before running utlrp.sql will resolve the issue [ORA-03113, ORA-03114]
Sql> @?/olap/admin/olap.sql SYSAUX TEMP;
g. Install OLAP by performing the detailed step 6 as documented in My Oracle Support Note 352306.1, Upgrading
OLAP from 32 to 64 bits.
h. Upgrade the database from 32-bit to 64-bit (recompile pl/sql modules and change the word size) by running
$ORACLE_HOME/rdbms/admin/utlrp.sql. Refer to the usage and notes sections in the script for instructions on
how to run it.
Note: After completion utlrp.sql no of invalid object must be equal to production database invalid object.

i. Import OLAP analytical workspaces by performing the detailed steps 7-8 as documented in My Oracle Support
Note 352306.1 to import the OLAP analytical workspaces that were previously exported from the source
machine.
j. Perform Step 11 of Appendix C.6.2.1 of Oracle Database Administrator's Reference 11g Release 2 (11.2) for
Linux and UNIX-based Operating Systems to re-create the java system.
Sql> connect /as sysdba
Sql> create or replace java system;

k. Remove _system_trig_enabled=false from init.ora

l. Shutdown and restart the database normally

Post-Migration
Perform the following steps to configure the target system and synchronize the application tier with the database tier.
Database Tier
Refer to Section 4: Post-Migration tasks of Using Oracle E-Business Suite Release 12 with a Database Tier Only Platform on
Oracle 10g Release 2 and perform the following steps.
1. Natively recompile PL/SQL code
2. Start the new database listener
3. Implement and run AutoConfig on the database server node
4. Re-create custom database links

Section 4: Post-Migration Tasks

If you performed Option A or B in step 6 of Section 3 above, perform these additional interoperability steps on the
new database.
1. Natively recompile PL/SQL code (optional)
If you are on a UNIX/Linux platform, you can choose to run Oracle E-Business Suite Release 12 PL/SQL
database objects in natively compiled mode with Oracle Database 11g. See the "Compiling PL/SQL Code
for Native Execution" section of Chapter 12 of Oracle Database PL/SQL Language Reference 11g Release 2
(11.2).
 When modifying the initialization parameters pertaining to the PL/SQL native compilation, use document
216205.1, on My Oracle Support as a guideline.
Sql> $oracle_home/rdbms/admin/dbmsupgnv.sql /as sysdba
Sql> shutdown normal/immediate
Sql> startup normal

2. Start the new database listener

If the Oracle Net listener for the database instance in the new Oracle home has not already been started,
you must start it now. Since AutoConfig has not yet been implemented, start the listener with the lsnrctl
executable (UNIX/Linux) or the Services applet (Windows). See the Oracle Database Net Services
Administrator's Guide 11g Release 2 (11.2) for more information.
3. De-register the original database server machine
De-register the original database server machine from the AutoConfig repository in the Applications
database.

Use SQL*Plus to connect to the database as APPS and run the following command:
$ sqlplus apps/[APPS password]
SQL> exec fnd_conc_clone.setup_clean;

4. Implement and run AutoConfig on the database server node

Implement and run AutoConfig in the new Oracle home on the database server node. If the database
listener of the new Oracle home is defined differently than the old Oracle home, you must also run
AutoConfig on each application tier server node to update the system with the new listener.
See Using AutoConfig to Manage System Configurations with Oracle E-Business Suite Release 12 on My
Oracle Support for instructions on how to implement and run AutoConfig. Section 3.2 explains how to
generate a context file on the database tier.
Shut down all processes, including the database and the listener, and restart them to load the new
environment settings.
5. Re-create custom database links
a. If the Oracle Net listener in the 11.2.0 Oracle home is defined differently than the one used by the
old Oracle home, you must re-create any custom self-referential database links that exist in the E-
Business Suite database instance. To check for the existence of database links, use SQL*Plus on
the database server node to connect to the E-Business Suite database instance as APPS and run
the following query:
$ sqlplus apps/[apps password]
SQL> select db_link from dba_db_links;

 Migrate the Application Tier

Refer to Section 2: Clone Oracle Applications Release 12 of Cloning Oracle Applications Release 12 with Rapid
Clone and perform the following steps.
1. Prepare the source system
 Prepare the source system application tier for cloning
Note: All completed above prerequisite in this document.

2. Copy the source system to the target system

 Copy the application tier file system
Note: In the copying tasks below, UNIX/Linux users should ensure that the symbolic links (soft links) are
preserved when copying. On most UNIX platforms, this can be accomplished with the cp -RH command. Consult
the UNIX man page for the cp command to check the parameters available on your platform.

For example: cd /target_dest_dir/db cp -rh /source_dir/db/*

Alternatively, the tar command can be used to compress the directories into a temporary staging area. UNIX/Linux
users should ensure that the symbolic links (soft links) are preserved when compressing. On most UNIX platforms,
this is the default behavior of tar command. Consult the UNIX man page for the tar command to check the
parameters available on your platform

Additionally, verify the permissions of the executables under ORACLE_HOME/bin that can potentially be owned by
root (i.e. nmo, nmhs, nmb, etc).

Copy the application tier file system

Log on to the source system application tier nodes as the APPLMGR user and shut down the application tier server
processes. Copy the following application tier directories from the source node to the target application tier node:
 [APPL_TOP]
 [COMMON_TOP]
 Applications Technology Stack:
 [OracleAS Tools ORACLE_HOME]
 [OracleAS Web IAS_ORACLE_HOME]

Update the Target System

1. Update environment variable
On the target system, set the environment variable LDEMULATION to elf_i386.
2. Update CTXORIG.xml
Update the the value of the s_platform parameter in CTXORIG.xml from Linux to LINUX_X86-64. The
CTXORIG.xml file is located in the <COMMON_TOP>/clone/context/apps directory of the target system. A
sample entry is shown below:
<platform oa_var="s_platform" osd="LINUX_X86-64">LINUX_X86-64</platform>

Post-Migration
Perform the following steps to configure the target system and synchronize the application tier with the database
tier.

Application Tier
Refer to Section 2: Clone Oracle Applications Release 12 of Cloning Oracle Applications Release 12 with Rapid
Clone and perform the following steps.
 Configure the target system
Configure the target system application tier server nodes
Log on to the target system as the APPLMGR user and enter the following commands:
$ cd [COMMON_TOP]/clone/bin
$ perl adcfgclone.pl appsTier

Refer to Oracle Applications Maintenance Procedures and perform the following steps using AD Administration.
1. Relink AD executables (Use AD Relink for this step)
2. Relink Applications programs
3. Generate message files
4. Generate form files
5. Generate report files
6. Generate product JAR files
Refer to Section 3: Finishing Tasks of Cloning Oracle Applications Release 12 with Rapid Clone and perform the
following steps.
1. Update profile options
Rapid Clone updates only site level profile options. If any other profile options are set to instance specific
values, you must update them manually.
2. Update printer settings
 If the new cloned system needs to utilize different printers, update the target system with the new
printer settings now.
3. Update Workflow configuration settings
Cloning an Oracle Applications instance will not update the host and instance-specific information used
by Oracle Workflow. Review the tables and columns listed in Table 4 to check for any instance-specific
data in the Workflow configuration on the target system.

Table 4: Workflow configuration settings

Table Name Column Name Column Value Details
Value starts with http://[old web host]: Update to new
o WF_NOTIFICATION_ATTRIBUTES TEXT_VALUE
web host.
Value starts with "http://[old web host]: Update to new
o WF_ITEM_ATTRIBUTE_VALUES TEXT_VALUE
web host.
Using the Workflow Administrator Web Applications
o WF_SYSTEMS GUID responsibility, create a new system defined as the new
global database name.
o WF_SYSTEMS NAME Replace value with the database global name.
Update database link with the new database global
o WF_AGENTS ADDRESS
name.
o FND_FORM_FUNCTIONS WEB_HOST_NAME Update with the new web host name.
o FND_FORM_FUNCTIONS WEB_AGENT_NAME Update to point at the new PL/SQL listener name.
o FND_CONCURRENT_REQUESTS LOGFILE_NAME Update with the correct path to the logfile directory.
Update with the new directory path on the target
o FND_CONCURRENT_REQUESTS OUTFILE_NAME
system.

4. Verify APPLCSF variable setting

Source the APPS environment and review that the variable APPLCSF (identifying the top-level directory
for concurrent manager log and output files) points to a suitable directory. To modify it, change the value
of the s_applcsf variable in the context file and then run AutoConfig.
5. Update the SESSION_COOKIE_DOMAIN value in ICX_PARAMETERS
If the target system is in a different domain name than the source system and SESSION_COOKIE_DOMAIN
was not null in the source system, update that value to reflect the new domain name.
6. Re-Implement SSL and SSO configuration
If the Source System was SSL or SSO enabled, and the Target is wished to be SSL or SSO enabled, then
reconfigure the Target by following the SSL/SSO documentation. Otherwise, if the Target is wished to be
non-SSL or non-SSO, then follow the same SSL/SSO documentation to undo the SSL/SSO setup.

We have two options to complete the Application Tier Migration

Option one is briefly discussed above section and Option two can be execute Section:2 Migration Task of the
following documents:

Application Tier Platform Migration with Oracle E-Business Suite Release 12 [ID 438086.1]
Contents
Section 1: Prerequisites: Must be completed prior to using the migration utility.
Section 2: Migration Tasks : Tasks to migrate an application tier to a new platform.
Section 3: Finishing Tasks: Tasks that need to be performed after the migration.

Application Tier Platform Migration with Oracle E-Business Suite Release 12 [ID 438086.1]
Vs.
Cloning Oracle Applications Release 12 with Rapid Clone [ID 406982.1]
Prerequisites of above both documents are same but only

Identify Technology Stack Updates

If you have applied any patches on the Oracle E-Business Suite Technology Stack you must apply them on the Target
System after the migration. At this point, you must identify all the patches applied to the Oracle Application Server 10.1.2
and 10.1.3 ORACLE_HOMEs on the Source System, so they can be applied to the Target System in a later step.
1. Verify the patch level on the ORACLE_HOMEs by executing the Technology Stack Inventory Utility. This utility will
produce an HTML report (or text report if desired). Review any required actions before proceeding with the
Applications Technology updates.
2. Establish the needed environment parameters by sourcing the Applications environment file as the owner of the
application tier file system.
3. Ensure the "APPLRGF" variable is set in environment. If not, set it to the same value as "APPLTMP".
4. Navigate to [FND_TOP]/patch/115/bin. Run the utility as follows:
Operating
Command Line
System
$ perl $FND_TOP/patch/115/bin/TXKScript.pl
-script=$FND_TOP/patch/115/bin/txkInventory.pl
UNIX/Linux -txktop=$APPLTMP -contextfile=$CONTEXT_FILE
-appspass=apps
-outfile=$APPLTMP/Report_Inventory.html
C:\>perl %FND_TOP%\patch\115\bin\TXKScript.pl
-script=%FND_TOP%\patch\115\bin\txkInventory.pl
Windows -txktop=%APPLTMP% -contextfile=%CONTEXT_FILE%
-appspass=apps
-outfile=%APPLTMP%/Report_Inventory.html
5.
6. Where:
Parameter Usage
txktop Temporary working directory use by Perl Modules. Should not be an empty string.

contextfile Location of the context file. If not passed, default is picked from the environment.

appspass APPS schema password. If not passed, default password is used.

outfile Location for the report being generated. If not passed, the default location is [APPLTMP]/TXK.

To generate the report in text format, the parameter -reporttype=text needs to be passed to the above commands. For
example:
$ outfile=$APPLTMP/Report_Inventory.html -reporttype=text

Section 2: Migration Tasks

1. Generate and upload the manifest of customer-specific files
a. Generate customer-specific manifest file:
Log in to your Source System application tier node as the applmgr user and Source the APPL_TOP
environment file. Execute the following command to generate the customer-specific file manifest:
$ cd [AD_TOP]/bin
$ perl adgenpsf.pl
The above command will generate the file adgenpsf.txt under [APPL_TOP]/admin/[TWO_TASK]/out. This
step should take about a minute.
b. Upload Manifest File for generation to target UNIX/Linux platform:
Go to https://updates.oracle.com/PlatformMigration, log in with your My Oracle Support username and
password, then follow the instructions on the screen to upload the manifest file previously generated.
 2. Copy the Source System to the Target System
Copy the application tier file system from the Source Oracle E-Business Suite system to the Target Node by
executing the following steps in the order listed. Make sure the applmgr user owns the files copied to the Target
System.
o [APPL_TOP]
o [COMMON_TOP]/clone
o [COMMON_TOP]/java
o [COMMON_TOP]/_pages
o [COMMON_TOP]/webapps
o [COMMON_TOP]/util
Copy only the directories listed, not the full COMMON_TOP.
If you want the migrated system to have a new digital signature, remove the file [APPL_TOP]/admin/appltop.cer from the
Target System.
3. Install JDK and InfoZip utilities on the Target System
If not already installed, the following utilities must be installed on the Target System:
o JDK 1.5 or higher, in the JDK_HOME
o InfoZip UNZIP version 5.52
o InfoZip ZIP version Zip 2.30
4. Copy the Source System Context File to the Target System
5. Clone the Applications Context File on the Target System
Log in to the Target System as the applmgr user and run the following commands:
a. Create a pairsfile (text file) with the following values:
s_systemname=[SID]
s_dbSid=[SID]
s_jdktop=[JDK_HOME]
s_jretop={JDK_HOME]
b. Generate the Target System Context File:
cd [COMMON_TOP]/clone/bin
perl adclonectx.pl migrate \
java=[JDK_HOME] \
pairsfile=[pairsfile] \
contextfile=[Source Applications Context File]
Where:
Parameter Meaning
[SID] Database Name
[JDK_HOME] Complete $PATH where JDK is installed
[pairsfile] Complete $PATH to the pairsfile created in Step a.
[Source Applications Context Complete $PATH to the Source System Context File copied to the Target
File] System

Note: The Clone Context tool will ask for all the new mount points on the Target System migration node.

Note: If SQL*Net security is being used, the Target System should be allowed to make incoming connections to
the database before running the Clone Context utility.

2. Install the Application Tier Technology Stack

Run the Rapid Install Wizard with the -techstack option to install the Oracle E-Business Suite Technology Stack.
Use the Target System context file created in the previous step:
$ cd [Stage12]/startCD/Disk1/rapidwiz
$ ./rapidwiz -techstack
 Refer to the Oracle E-Business Suite Installation Guide for more details.
Note: Use the latest startCD available. Patch 6796703 For details of the latest startCD Patch for Release 12.0.4 or
12.1.1, refer to the "Current Version of Rapid Install" section in the relevant Oracle E-Business Suite Release Notes
available My Oracle Support Knowledge Documents 549389.1 (12.0.4) and 798258.1 (12.1.1).

3. Run AutoConfig setup phase on the Target System

Execute the INSTE8_SETUP phase of AutoConfig with the new context file. This will create the environment files
required for the AutoPatch session:
$ cd [AD_TOP]/bin
$ ./adconfig.sh run=INSTE8_SETUP contextfile=[Target System Context File]
Note: This command does not require the environment to be sourced.

Note: If you have chosen to create a new digital signature for the Target System, the above AutoConfig session
may complete with errors: specifically, the adgenjky.sh script fails to generate the appltop.cer file. This can occur
because the adjkey executable that this script calls is still specific to Source system. However, the adgenjky script
will be executed correctly on the last step of the migration.

10. Review Component Versions and Technology Stack patch level

In Section 1, Step 11 you identified updates applied to your Source System Technology Stack. If any, apply these
patches to the Target System technology stack now.
Note: If you upgraded the Technology Stack components to higher versions than those included with the Oracle
E-Business Suite Release 12.0.4 or 12.1.1 install media, they should be upgraded on the Target System now.
Examples could include Oracle Application Server 10.1.3.3 or JDK 1.6. Refer to My Oracle Support Knowledge
Document 380482.1 for a list of relevant documents.

11. Regenerate File System Objects

Source the APPL_TOP environment file and perform the following tasks to regenerate the platform dependent files
on the Target System:
a. If migrating an application tier that starts Forms, run the following commands:
$ cd [AD_TOP]/bin
$ ./adgensgn.sh [Apps User]/[Apps Password]
b. Run adadmin to generate messages, forms, reports and product jar files.
Note: If you have languages other than American English already installed in your Release 12.1 system,
you must generate messages, forms and reports for each active language.

12. Clean Nodes (Conditional)

If you are migrating into a different machine name, you will need to recreate the Node configuration by
completing the following two steps:
a. Run afcpclean.sh in the Target Application Tier.
$ cd [INST_TOP]/admin/install
$ ./afcpclean.sh [Apps User] [Apps Password]
Warning: This step will remove the Nodes from the current system. It only applies if the source and
target hostnames have changed. Before running this step, shut down all the application tier service
processes.

b. Log into the Source Database Tier and run Autoconfig

13. Run AutoConfig to complete the Target System configuration

$ cd [AD_TOP]/bin
$ ./adconfig.sh contextfile=[Target System Context File]
Note: On this last step, the database will be updated to reflect the new Target System profile. Ensure any users
log off the system, then shut down the Source System application tier service processes. After this, the Source
System application tier will no longer be available.
Section 3: Finishing Tasks
This section lists tasks that may be necessary, depending on your implementation and the intended use of the migrated
system.
1. Review and update Target System Application Tier Settings and Customizations
Recompile any custom code (forms, C) in the Target System APPL_TOP.

If you were using Oracle Discoverer 10.1.2, OID, SSO or Portal 10g on the Source System, refer to the
corresponding documentation to complete the migration:
Product Documentation
Oracle Discoverer 10.1.2 My Oracle Support Knowledge Document 373634.1.
Oracle Internet Directory (OID) and Oracle Single Sign-
My Oracle Support Knowledge Document 376811.1.
On (SSO)
Oracle Portal 10g My Oracle Support Knowledge Document 380484.1.

Note: Refer to My Oracle Support Knowledge Document 380482.1 for documents relating to other Technology Stack
components.

2. Update printer settings

If the newly migrated system needs to utilize different printers, update the target system with the new
printer settings now.
3. Update Oracle Workflow configuration settings
Migrating an Oracle E-Business Suite instance will not update the host and instance specific
information used by Oracle Workflow. Review the following tables and columns to verify there is no
instance specific data in the Workflow configuration on the Target System.
Affected
Table Name Column Value Action Needed
Column(s)
Value starts with http://[old web host] : Update to new
o WF_NOTIFICATION_ATTRIBUTES TEXT_VALUE
web host
Value starts with http://[old web host] : Update to new
o WF_ITEM_ATTRIBUTE_VALUES TEXT_VALUE
web host
Create a new system defined as new global database
GUID name, via Workflow Administrator Web Applications
o WF_SYSTEMS responsibility.
NAME Replace value with database global name
o WF_AGENTS ADDRESS Update database link with new database global name.

WEB_HOST_NAME Update with new web host name

o FND_FORM_FUNCTIONS
WEB_AGENT_NAME Update to point to new PL/SQL listener name

LOGFILE_NAME Update with the correct path to logfile directory

o FND_CONCURRENT_REQUESTS
OUTFILE_NAME Update with the new directory path on Target System

4. Verify the APPLCSF variable setting

Source the APPS environment and review that the variable APPLCSF (identifying the top-level directory
for concurrent manager log and output files) points to a suitable directory. To modify it, change the
value of the s_applcsf variable in the context file and then run AutoConfig.
5. Update the SESSION_COOKIE_DOMAIN value in ICX_PARAMETERS
If the Target System is in a different domain name than the Source System and
SESSION_COOKIE_DOMAIN was not null in the Source System, update that value to reflect the new
domain name.
 6. Start all services on the Target System
Start all services by running the script:
$ cd [INST_TOP]/admin/scripts
$ ./adstrtal.sh [Apps User] / [Apps Password]

Syntax:
To Tar:
tar –cvzf tarfilename foldername

Untar:
tar –xvzf tarfilename

Example:
tar –cvzf abc.tar.gz abc
- This will zip [tar] the abc folder with the name abc.tar.gz

tar –xvzf filename.tar.gz

- This will unzip [untar] the file as abc folder.