AutoConfig Failure Due to Custom Template Version Mismatch in Oracle E-Business Suite R12.2
Introduction
During online patching in Oracle E-Business Suite (R12.2), the AutoConfig phase plays a criticalrole in validating and applying configuration changes across the application tier.This blog explains a real-time issue encountered during an adop apply cycle, where AutoConfig failed due to a custom template version mismatch, along with the root cause and resolution steps.
Environment Details
· Application: Oracle E-Business Suite R12.2
· Patching Method: adop (Online Patching)
· Phase: apply
· Node: Application Tier
Issue Summary
During the adop apply phase, the patching process failed while executing AutoConfig.
Observed Errors
[UNEXPECTED] Error occurred running "sh .../adconfig.sh ..."
[UNEXPECTED] Error occurred while executing AutoConfig on current node.
[UNEXPECTED] Apply phase has failed.
Error Details from AutoConfig Log
The AutoConfig log clearly indicated a template version conflict:
[ VERSION CONFLICTS INFORMATION ]
Template shipped by Oracle :
.../template/oacore_web_xml_FMW.tmp (version: 120.17.12020000.33)
Custom template :
.../template/custom/oacore_web_xml_FMW.tmp (version: 120.17.12020000.31)
Please resolve the differences between the two templates or refer to the Oracle E-Business Suite Setup Guide.
Understanding the Issue
Oracle EBS allows DBAs to maintain custom AutoConfig templates under:
template/custom/
During patching:
· Oracle delivers updated standard templates
· AutoConfig validates version consistency
· Any mismatch between standard and custom templates leads to failure AutoConfig enforces strict version control to prevent configuration inconsistencies.
Root Cause Analysis (RCA)
The failure occurred due to the following:
· A custom template file oacore_web_xml_FMW.tmp existed in the custom directory
· The custom version (120.17.12020000.31) was outdated
· Oracle patch delivered a newer version (120.17.12020000.33)
· AutoConfig detected the mismatch and terminated execution
In short:
Outdated custom template caused AutoConfig to fail during validation
Resolution Steps
1. Backup Existing Templates
cp -pr template template_ori_171125
2. Copy Latest Oracle Template to Custom Directory
cp /u01/oracle/PRETEST/fs2/EBSapps/appl/fnd/12.0.0/admin/template/oacore_web_xml_FMW.tmp
/u01/oracle/PRETEST/fs2/EBSapps/appl/fnd/12.0.0/admin/template/custom/oacore_web_xml_FMW.tmp
3. Verify Template Version
ls -ltr oacore_web_xml_FMW.tmp*
Ensure both files reflect the same version (120.17.12020000.33)
4. Resume Patching Cycle
· Restart the patch session
· Continue with adop apply AutoConfig executed successfully after version alignment
5. AutoConfig Execution
No manual AutoConfig run required adop internally completed AutoConfig
Post-Fix Outcome
· Patch applied successfully
· AutoConfig completed without errors
· Template versions synchronized
· Application environment stabilized
Key Takeaways
· AutoConfig strictly validates template versions
· Custom templates must always match Oracle-delivered versions
· Even minor version differences can break patching
· Always review custom directory during patching cycles
Best Practices
· Maintain version control for all custom templates
· Compare standard vs custom templates after every patch
· Document all template customizations
· Backup template directories before patching
· Periodically clean unused custom templates
Conclusion
Custom template management is a critical aspect of maintaining Oracle E-Business Suite environments. Version mismatches, even minor ones, can disrupt AutoConfig and halt patching activities.By ensuring proper alignment between standard and custom templates, DBAs can avoid unexpected failures and ensure smooth patching cycles.
No comments:
Post a Comment