Hi,
Happy New Year to all readers!
Recently I was cloning an R12 instance. After the cloning part was done using rapid clone, the apache failed to come up and was reporting the following error:
adapcctl.sh: exiting with status 204
However, there were no errors in error_log or in the adapcctl.txt log file that is generated as part of the startup script. Further digging into the issue revealed the following error in the HTTP_Server~1 log file under $LOG_HOME/ora/10.1.3/opmn:
Syntax error on line 17 of /apps/local/FIEST1/inst/apps/FIEST1_iftg-01/ora/10.1.3/Apache/Apache/conf/mod_osso.conf:Unable to open /apps/local/FIEST1/inst/apps/FIEST1_iftg-01/ora/10.1.3/Apache/Apache/conf/osso/FIEST1_iftg-01_osso.conf.
It turns out that this issue is because the source is SSO enabled and the target was not yet SSO enabled. Running $FND_TOP/bin/txkrun.pl -script=SetSSOReg -removereferences=Yes in target instance did not help either.
Fix:
Run detailed steps to deregister OID/SSO registration. This will run autoconfig as part of the deregistration process, which will generate the correct mod osso files. Basically, the s_mod_osso_conf_comment should have # (comment) in xml file before running autoconfig (which will be the result of running deregistration steps).
The apache came up fine subsequently.
- Aravind Kamath Posral
Subscribe to:
Post Comments (Atom)
Posts
3 comments:
Hi Aravind,
I am ur old friend Sridhar.
Your expaination helped me in finding root cause of this Problem.But I resolved in a different way.Work around is in httpd.conf,
#include “$inst_top/ora/10.1.3/Apache/Apache/conf/mod_osso.conf"
Comment the above line so that it won’t look for this file.
Cheers,
Sridhar Nagarajaswamy.
Hi Aravind,
I am your old friend Sridhar Nagarajaswamy.
Your explaination helped me in finding the root cause.
We can comment the below line in httpd.conf do that Apache will not look for this file
#include “$inst_top/ora/10.1.3/Apache/Apache/conf/mod_osso.conf"
This is a work around :-).
Cheers,
Sridhar Nagarajaswamy
Hi Sridhar,
The next time you run autoconfig, your httpd.conf file will get overwritten. The fix I have mentioned to put a # in the xml and close the tag does exactly that when you run autoconfig and that is preserved across autoconfig runs as well..
-Aravind
Post a Comment