Oracle EBS 12.2 – Patch File System Validation Checklist
1. Take Backup of Critical Files
Take backup of the following files from all RUN/PATCH nodes and keep them in a shared NAS mount location for easy recovery.
a) Context Files
Backup all context XML files.
Example:
$INST_TOP/appl/admin/*.xml
b) Environment Files
$APPL_TOP/*.env
c) WebLogic Domain Configuration
$FMW_HOME/user_projects/domains/EBS_domain_<SID>/config/config.xml
2. Copy Patch to Shared Mount Point
Copy the required patch files to the extranet/shared mount location.
Example:
/nas/ebs_patches/
3. Run ADOP Validation
Execute validation before starting the patching cycle.
adop phase=validate
Ensure validation completes successfully without errors.
4. Validate Admin Server and Node Manager
Connect to PATCH file system and validate startup/shutdown of:
- Admin Server (Primary Node)
- Node Manager (All Nodes)
Source Patch Environment
cd ~
. ./EBSapps.env patch
Admin Server Start/Stop Validation
$ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start
$ADMIN_SCRIPTS_HOME/adadminsrvctl.sh stop
Node Manager Start/Stop Validation
$ADMIN_SCRIPTS_HOME/adnodemgrctl.sh start
$ADMIN_SCRIPTS_HOME/adnodemgrctl.sh stop
5. Ensure No Patch File System Processes Are Running
Verify no residual PATCH filesystem processes are active across application nodes.
Example:
ps -ef | grep fs2
If any unwanted processes exist, stop them cleanly before proceeding.
6. Validate Node Manager Port Configuration
Ensure:
- RUN filesystem ports are identical across all RUN nodes.
- PATCH filesystem uses a different Node Manager port.
Verify Node Manager Listen Port
grep -i listen-port \
$FMW_HOME/user_projects/domains/EBS_domain_<SID>/config/config.xml
Extract Port Number
grep -i listen-port \
$FMW_HOME/user_projects/domains/EBS_domain_<SID>/config/config.xml \
| sed -n 1p \
| cut -d'>' -f2 \
| cut -d'<' -f1
Recommended DBA Validation Checks
Verify Node Manager Process
ps -ef | grep NodeManager
Check Listening Ports
netstat -an | grep LISTEN | grep <PORT>
Verify WebLogic Admin Connectivity
curl -I http://hostname:port
Important Best Practices
- Always validate PATCH filesystem before
adop prepare. - Ensure no orphan Java/WLS processes exist.
- Maintain backup of
config.xmlbefore changes. - Validate SSH equivalency between nodes.
- Confirm shared filesystem mount availability on all nodes.
- Check free space in:
$PATCH_TOP$NE_BASE$COMMON_TOP
Typical Real-Time Use Cases
This checklist is commonly used before:
adop phase=prepareadop fs_clone- WebLogic recovery
- Node Manager troubleshooting
- Dual filesystem synchronization issues
- Patch filesystem corruption validation
No comments:
Post a Comment