Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
442 posts
|
Hi,
On R12.2.4, DB 11.2.0.4 on Aix, Adop prepare fails with: [UNEXPECTED]Error 1 occurred while Executing txkADOPValidation script [ERROR]: OHS Configuration Files Have Not Been Instantiated From The Latest AutoConfig Templates." I found this(Doc ID 2368793.1) and 2437111.1. Both suggest to edit CONTEXT_FILE and admin.conf to have the same Listen port in them. My problem is that, these two files have correct and same port number for: Listen %s_ohs_adminport% PortDescription %s_ohs_adminport% "OHS Administrator port" in admin.conf and s_ohs_adminport in CONTEXT_FILE. Do have any other suggestion? Thanks and regards. |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
Administrator
5727 posts
|
It seems like you have a version mismatch between the template and the config files that is supposed to be generated from that template..
What are the detailed errors? Did you check the following MOS NOTE -> Oracle E-Business Suite Release 12.2: Validations Performed By the adop Online Patching Utility (Doc ID 1678355.1) 6. Check if instantiate instructions in the readme have been followed correctly That node suggest following corrective action -> Corrective Action: Refer to My Oracle Support Knowledge Document 1617461.1 to apply the latest AD and TXK release update packs. As I already requested the detailed errors, we need to check the exact files that are causing this.. This error may be the same as the one given in the following MOS Note: "[ERROR]: OHS Configuration Files Have Not Been Instantiated From The Latest AutoConfig Templates." When running fs_clone (Doc ID 2368793.1) Note that, it is not the config that is problematic, it is the file versions! So in the note above, you get the config file from the template and you manually edit the template to make the template and the config file be sync in terms of version.. I hope you understand what I mean.. |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
442 posts
|
This post was updated on Aug 11, 2021; 5:10am.
Hi,
Thank you. I followed 2368793.1 and copied template and modified it manually and renamed it admin.config on PATCH and RUN. Then autoconfig. Was it the correct action? And ran adop always the same error. adop_prepare_error.txt Regards. |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
Administrator
5727 posts
|
You did all the things documented in note "[ERROR]: OHS Configuration Files Have Not Been Instantiated From The Latest AutoConfig Templates." When running fs_clone (Doc ID 2368793.1)?
So then your template version is also old.. Check the $FND_TOP/admin/template/admin_conf_FMW.tmp file and see the version written there.. If the template is also old, then as I already recommended, apply the latest AD and TXK release update packs. -- MOS Doc : 1617461.1 |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
442 posts
|
This post was updated on Aug 13, 2021; 8:14pm.
Hi,
In ADOPValidations_detailed.log we have: ================================ ERROR: File versions mismatch. ================================ Template File: /u01/appl_top/dev/fs2/EBSapps/appl/fnd/12.0.0/admin/template/ssl_conf_FMW.tmp 120.5.12020000.2 Target File: /u01/appl_top/dev/fs2/FMW_Home/webtier/instances/EBS_web_dev_OHS1/config/OHS/EBS_web_dev/ssl.conf 120.5.12020000.3 Template File: /u01/appl_top/dev/fs2/EBSapps/appl/fnd/12.0.0/admin/template/admin_conf_FMW.tmp 120.1.12020000.2 Target File: /u01/appl_top/dev/fs2/FMW_Home/webtier/instances/EBS_web_dev_OHS1/config/OHS/EBS_web_dev/admin.conf 120.1.12020000.2 ================================ ERROR: Oracle HTTP service configuration file version does not match corresponding AutoConfig template file. Then we see that admin_conf_FMW.tmp 120.1.12020000.2 and admin.conf 120.1.12020000.2, then why mismatch? They are the same version. As said in 2368793.1 I replaced admin.conf with admin_conf_FMW.tmp,(rename admin_conf_FMW.tmp to admin.conf) and edited and changed: Change the following lines in my new admin.conf file: FROM Listen %s_ohs_adminport% PortDescription %s_ohs_adminport% "OHS Administrator port" TO Listen xxxxx PortDescription xxxxx "OHS Administrator port" Ran autoconfig on RUN and then adop phase=prepare which failed with the same errors (as above)in ADOPValidations_detailed.log. adop_prepare_error_2.txt I cannot apply the latest AD and TXK release because we should keep DEV at the same release of AD and TXK of our other systems. Thanks for help. |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
Administrator
5727 posts
|
We still see version mismatch in the log.
What about mod_wl_ohs.conf ? Is the version of that file same as the its template? The ssl.conf file is also problematic.. Template version 120.5.12020000.2, target file version 120.5.12020000.3.. |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
442 posts
|
This post was updated on Aug 14, 2021; 6:47am.
Hi,
Thank you. strings mod_wl_ohs.conf | grep '$Header' # $Header: mod_wl_ohs_conf_FMW.tmp 120.7.12020000.6 2014/05/09 11:03:18 mmanku ship $ strings $FND_TOP/admin/template/mod_wl_ohs_conf_FMW.tmp | grep '$Header' # $Header: mod_wl_ohs_conf_FMW.tmp 120.7.12020000.6 2014/05/09 11:03:18 mmanku ship $ Regards. |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
Administrator
5727 posts
|
No need.
This is not a binary file . This is a text file. Open it with a text edior such as vi and there you will see the version |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
442 posts
|
Hi,
Thank you. The version of mod_wl_ohs_conf_FMW.tmp 120.7.12020000.6 2014/05/09 11:03:18 mmanku ship $ And the version of mod_wl_ohs.conf is also 120.7.12020000.6 2014/05/09 11:03:18 mmanku ship $ What can we conclude? Does it suggest a workaround? Regards. |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
Administrator
5727 posts
|
The ssl.conf file is also problematic.. Template version 120.5.12020000.2, target file version 120.5.12020000.3..
Do the same trick that you did for admin conf for the ssl conf and retry. |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
442 posts
|
Thank you.
Should we replace ssl.conf and admin.conf on PATCH fs also? Should autoconfig be run on PATCH also? Regards. |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
Administrator
5727 posts
|
Replace in the patch fs as well.
Then retry the failing operation. |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
442 posts
|
This post was updated on Aug 15, 2021; 4:07pm.
Thank you.
I will do the operation on moday. Regards. |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
442 posts
|
Hi,
I did it: replace admin.conf and ssl.conf by their template on RUN and PATCH fs,and modify as should. Ran autoconfig on RUN and PATCH. Start application. Ran adop phase = prepare. Continued with other pahses. It worked fine. Thank you very much Erman. Have a nice they. Regards. |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
Administrator
5727 posts
|
Good :)
|
Free forum by Nabble | Edit this page |