Introduction:
During an adop apply cycle in an Oracle E-Business Suite (R12.2) environment, the patching process failed during the AutoConfig phase on the application tier. The patch could not proceed because AutoConfig terminated with a template version conflict.
After investigation, it was found that a custom Auto Config template under the custom/ directory was outdated when compared to the Oracle-delivered template. This mismatch caused Auto Config to fail while validating template versions.
Error Summary :
During adop apply, the following messages were seen:
[UNEXPECTED] Error occurred running “sh …/adconfig.sh …”
[UNEXPECTED] Error occurred while executing AutoConfig on current node.
[UNEXPECTED] Apply phase has failed.
The AutoConfig log displayed a template version mismatch:
[ 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.
This confirms a version conflict between the standard and custom AutoConfig templates.
Root Cause (RCA)
The AutoConfig failure occurred due to the following reasons:
A customized template file oacore_web_xml_FMW.tmp existed inside the custom directory.
The version of this custom template was older (31) than the version shipped by the latest Oracle patch (33).
AutoConfig strictly checks template version alignment. Any mismatch causes AutoConfig to fail immediately.
During the patching process, AutoConfig expected the updated template from the patch but instead found an outdated version inside custom/.
In short, the custom template was never updated to match the new Oracle-delivered template version, resulting in failure.
Solution Steps
1. Take a Backup of the Template Directory
cp -pr template template_ori_171125
2. Copy the Latest Oracle-Shipped 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 the Template Versions
Ensure both standard and custom files now have the same version (33).
ls -ltr oacore_web_xml_FMW.tmp*
4. Continue with the Patching Cycle
After correcting the custom template version:
Restart the patch session
Continue with adop apply
The patch proceeded successfully.
5. No Need to Re-run AutoConfig Manually
Since AutoConfig inside adop apply completed successfully, no manual AutoConfig run was required.
Patch application completed successfully
AutoConfig executed without errors
Custom template version now matches the Oracle-delivered version
Environment returned to a stable state
Conclusion
Version mismatches in custom AutoConfig templates are a common issue in Oracle E-Business Suite R12.2 during adop patching cycles. Even minor discrepancies in template versions can cause AutoConfig to fail, halting the entire patching process.Keeping templates aligned helps ensure smooth patching, minimal downtime, and stable environments.
