Monthly Archives: May 2010

Cloning Multi Node to Single Node


Description :
With Oracle Applications 11.5.10 the ability to clone from a multi node to a single node system using rapid clone has now been certified.
This is accomplished by the Shared APPL_TOP and Merging APPL_TOP features.
The information mentioned here is the steps which i have used and found them to be successful for a more elaborate explanation you might want to refer to the Metalink notes mentioned at the end of this document.

Source System here refers to the multi node Production system to be cloned Target System refers to the newly to be created T&D single node system
Applications Version 11.5.10.2
Database Version 10.2.0.4.0
Operating System RedHat Enterprise Linux Advance Server 5 update 4

Source Setup Information:

192.168.200.2 Database
192.168.200.2 Concurrent Manager & Report (Admin Node)
192.168.200.3 Forms & Apache (Web Node)

Step 1: Check OS configuration and utilities
Red Hat Enterprise Linux 5* (base and Advanced Platform) Update 1 (RHEL 5.1) or higher is
required.
The following packages are not part of the OEL 5 or RHEL 5 distribution media and must be installed
manually:
• compat-libstdc++-egcs-1.1.2-11
• compat-libcwait-2.1-11
• compat-oracle-el5-1.0-51
• openmotif21-2.1.30-11.EL51
• binutils-2.152
The following packages must be installed from the OEL 5 or RHEL 5 distribution media:
• libXp-1.0.0-8.1.el5
• compat-libgcc-296-2.96-138
• compat-libstdc++-33-3.2.3-61
• compat-db-4.2.52-5.1
Note :
1: Download from http://oss.oracle.com/projects/compat-oracle/files/Enterprise_Linux/ (for both OEL 5 and RHEL 5)
2: GNU linker (ld) version 2.15 is required for relinking the modules in Advanced Planning &
Scheduling (MSC, MSO, MSR) – download binutils-2.15 from http://oss.oracle.com/projects/compat oracle/files/Enterprise_Linux/ (for both OEL 5 and RHEL 5)
glibc Requirements  Oracle Enterprise Linux 5 2.3.4-2.26

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

Net Service Listeners in Multi-user Installations
Give all users in a multi-user installation write privileges to the .oracle directory:
$ chmod 777 /var/tmp/.oracle

Verifying Host Names
Use the following to verify host name settings:
For Oracle Enterprise Linux 4 and 5, Red Hat Enterprise Linux 3, 4 and 5:
1. Verify that the /etc/hosts file is formatted as follows:
127.0.0.1 localhost.localdomain localhost
.
2. Verify that the /etc/sysconfig/network file is formatted as follows:
HOSTNAME=.
3. If the /etc/sysconfig/networking/profiles/default/network file exists, remove it.
4. If you changed any files in the previous steps, restart the system.

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.
For Oracle Enterprise Linux 4 and 5, Red Hat Enterprise Linux 3, 4 and 5 and SUSE Linux Enterprise
Server 9 and 10:
* hard nofile 65535
* soft nofile 4096
Modifying the Port Range Values
Open the /etc/sysctl.conf file and change the value of net.ipv4.ip_local_port_range as follows. Restart the system after making changes.
net.ipv4.ip_local_port_range = 10000 65000
Please note that this range is a recommended range, and may need to be adjusted according to the specific needs of the user’s environment in order to avoid port conflicts.

Setting the Environment
Perform the following tasks to set the environment before you run Rapid Install.
1. Create symbolic links For Oracle Enterprise Linux 5 and Red Hat Enterprise Linux 5 only :
# ln -s /usr/bin/ld215 /usr/bin/ld
Download and apply the OS library patch 6078836 from Oracle MetaLink and create the following symbolic link:
# ln -s /usr/lib/libdb.so.2 /usr/lib/libdb.so.3
2. Verify that the host name setting is correct. The command should return a fully qualified hostname.
For example: ..
# hostname -f

For Oracle Enterprise Linux 5, Red Hat Enterprise Linux 5 and SUSE Linux Enterprise Server 10 customers, the LD_ASSUME_KERNEL environment variable should be unset before starting the installation. The installation fails when the LD_ASSUME_KERNEL variable is set by the adgetlnxver.sh file during the course of the installation. Patch 6365595 contains the fix for adgetlnxver.sh file. The procedure below is a guideline for replacing the adgetlnxver.sh file in the
Oracle Applications 11i ship home.

Merging existing APPL_TOPs into a single APPL_TOP
In preparation for sharing a file system in an existing system with multiple APPL_TOPs, you can use the Rapid Clone utility to merge the multiple APPL_TOP (and COMMON_TOP) file systems into a single APPL_TOP file system. See Oracle MetaLink Doc ID: 230672.1 for more information. Oracle
recommends that the different APPL_TOPs should be merged into a completely new APPL_TOP to facilitate rollback incase of merge failure.
Note : We have considered Web Node ie 192.168.200.3 as our primary node (Node A mentioned in below steps)

Step 2: Maintain snapshot information
Log in to each application tier node as the APPLXXX user and run the maintain snapshot task in AD Administration.

Step 3: Merge existing APPL_TOPs
I) Prepare the source system application tier for merging
Choose one of the source system nodes to be the primary node. This document refers to it as “Node A”.
o Log in to Node A as the APPLXXX (applprod in our case) user and run:
$ cd /admin/scripts/
$ perl adpreclone.pl appsTier merge
This will create clone directory under $COMMON_TOP on 192.168.200.3

o Log in as the APPLMGR user to each of the secondary nodes being merged and run:
$ cd /admin/scripts/
$ perl adpreclone.pl appltop merge

This will create clone directory under $COMMON_TOP on 192.168.200.2

Step 4: Perform Backup of Source System
II) Copy the Source System to the Target System
Copy the application tier file system from the source Applications system to the target node by executing the following steps in the order listed. Ensure the application tier files copied to the target system are owned by the target APPLXXX user, and that the database tier files are owned by the ORAXXX user.

III) Create a copy of Node A (preferred)
If you want to place the merged APPL_TOPs in a new location instead of using an existing APPL_TOP location, create a copy of Node A (the other nodes in the system do not need to be copied). Include the following directories from Node A:

Step 5: Restore the backup on Target Node

IV) Copy the database tier file system
Log on to the source system database node as the ORACLE user.
• Perform a normal shutdown of the source system database
• Copy the database (DBF) files from the source to the target system
• Copy the source database ORACLE_HOME to the target system
• Start up the source Applications system database and application tier processes

V) Copy the required files for merging
Log in as the APPLMGR user to each source node and recursively copy:
directory /clone/appl
– to –
directory /clone/appl on Node A (or the copy of Node A).

VI) Configure target Database and Application
f. Configure the Target System
Execute the following commands to configure the target system.
You will be prompted for the target system specific values (SID, Paths, Ports, etc)
o Configure the target system database server
Log on to the target system as the ORACLE user and type the following commands
to configure and start the database:
cd /appsutil/clone/bin
perl adcfgclone.pl dbTier
o Configure the application tier server nodes
Log in to the merged APPL_TOP node as the APPLMGR user and execute the
following commands:
$ cd /clone/bin
$ perl adcfgclone.pl appsTier

Step 6: Finishing tasks
• Log in to the target system application tier node as the APPLMGR user.
• Run the following tasks in adadmin for all products:
o generate JAR files
o generate message files
o relink executables
o copy files to destination
• Depending on which tier you chose as the primary node, certain files may be missing. Run
adadmin to verify files required at runtime. If any files are listed as missing files, you must
manually copy them to the merged APPL_TOP.
• Remove the temporary directory /clone/appl to reduce disk space usage.
• Update Profile options
• Update Printer Settings
• Update the workflow configuration settings
• Verify the APPLCSF variable setting
• Update the session_cookie_domain value in icx_parameters

Reference Metalink Note :
316806.1 – Oracle Applications Installation Update Notes, Release 11i (11.5.10.2)
233428.1 – Sharing the Application Tier File System in Oracle Applications 11i
230672.1 – Cloning Oracle Applications Release 11i with Rapid Clone