🔷 Introduction
Step by Step Guide to Add Secondy Node in Oracle EBS R12.2 | Oracle E-Business Suite (EBS) R12.2 supports a multi-node
architecture that allows organizations to scale application tier services such
as web, forms, and concurrent processing. Adding a new node is a common
requirement for load balancing, performance improvement, or environment
expansion.
This guide provides a complete, accurate, and
production-ready procedure to add and configure a new application tier node in
Oracle EBS R12.2 using Rapid Clone.
🔷 Prerequisites
Before proceeding, ensure the following requirements are
met:
- ✅
Oracle EBS R12.2 environment is up and running
- ✅
Same OS version and patches installed on target node
- ✅
Application user (applmgr) and database user (oracle) exist
- ✅ Change shared_file_system to true on run and patch file system context file
- ✅
Passwordless SSH configured between source and target nodes
- ✅
Shared Application Tier File System (via NFS or shared storage)
- ✅
Adequate disk space and memory on the new node
- ✅
Source environment context file backup taken
🔷 Architecture Overview
(R12.2)
Oracle EBS R12.2 uses a dual file system:
- fs1
(Run File System)
- fs2
(Patch File System)
Both file systems must be properly configured on the new
node.
🔷 Step 1: Prepare the
Target Node
On the new node:
- Install
required OS packages
- Create
users and groups:
groupadd dba
useradd -g dba applmgr
- Create directory structure identical to the source system
🔷 Step 2: Configure
Shared File System (NFS)
On Source Node:
Edit exports file:
vi /etc/exports
Add:
/u01/appl_top 192.168.1.20(rw,sync,no_root_squash)
Apply changes:
exportfs -ra
systemctl restart nfs-server
On Target Node:
Mount the shared file system:
mount -t nfs source_host:/u01/appl_top /u01/appl_top
Verify mount:
df -h
🔷 Step 3: Copy Required
Files
Ensure the following are available on the target node:
- Application
tier file system
- Context
files
- Rapid
Clone utility
🔷 Step 4: Run Rapid Clone
(Important Step)
Start weblogic admin server on run and patch file system.
Run fs.
$sh adadminsrvctl.sh start
Patch fs.
$sh adadminsrvctl.sh start forcepatchfs
Then run adpreclone on run and patch file system.
Navigate to clone directory:
cd $COMMON_TOP/clone/bin
Run the cloning utility:
perl adclonectx.pl addnode contextfile=/u01/app/run/UAT_s2uatebs01.xml pairsfile=/u01/app/run/UAT_s2uatebs01_run.txt dualfs=yes
🔹 Provide Required
Inputs:
- Target
hostname
- Domain
name
- Base
directory path
- Port
pool (choose unique port pool)
🔷 Step 5: Run AutoConfig
After cloning completes, run AutoConfig:
cd $ADMIN_SCRIPTS_HOME
./adautocfg.sh
✅ This step:
- Creates
configuration files
- Registers
node automatically
- Synchronizes
system settings
🔷 Step 6: Verify Node
Registration
Connect to database and run:
SQL>SELECT node_name, support_cp, support_web, support_forms FROM fnd_nodes;
Ensure the new node is listed.
🔷 Step 7: Start
Application Services
Start services on new node:
cd $ADMIN_SCRIPTS_HOME
./adstrtal.sh apps/apps
✅ Verify Services:
- Apache
→ Running ✅
- WebLogic
→ Running ✅
- Forms
Services → Running ✅
🔷 Best Practices
- ✅
Always take full backup before changes
- ✅
Ensure time synchronization between nodes
- ✅
Maintain consistent patch levels
- ✅
Regularly monitor logs and services
- ✅
Validate NFS performance for production environments
🔷 FAQ
✅ Q1: Is downtime required to add
a new node?
👉 Minimal downtime may be
required depending on environment setup.
✅ Q2: Can I add multiple nodes in
R12.2?
👉 Yes, Oracle EBS fully
supports multi-node architecture.
✅ Q3: What is the role of
AutoConfig?
👉 AutoConfig synchronizes
configuration and registers the node automatically.
✅ Q4: Is NFS mandatory?
👉 Yes, for shared
application tier file system in most setups.
🔚 Conclusion
Adding a new node in Oracle EBS R12.2 is a
straightforward process when using the correct tools and approach. By
leveraging Rapid Clone and AutoConfig, you can efficiently scale your
environment while maintaining system consistency and stability.
No comments:
Post a Comment