Starting R12 Apache errors
with status 204 after Cloning SSO Enabled E-Business Suite Instance [ID
730982.1]
script fails with the following error :
...
adapcctl.sh: exiting with status 204
...
Consequently, the Login page cannot be accessed.
The issue persists even after the following script is run in the Target instance, to remove references to the SSO configuration of the Source instance:
Applies to:
Oracle Applications Technology Stack - Version 12.0.1 to
12.1.3 [Release 12.0 to 12.1]
Information in this document applies to any platform.
***Checked for relevance on 17-Apr-2012***
Information in this document applies to any platform.
***Checked for relevance on 17-Apr-2012***
Symptoms to:
After cloning an SSO enabled Oracle E-Business Suite Instance
on the target the starting of the Apache Service via
$INST_TOP/admin/scripts/adapcctl.sh
script fails with the following error :
...
adapcctl.sh: exiting with status 204
...
Consequently, the Login page cannot be accessed.
The issue persists even after the following script is run in the Target instance, to remove references to the SSO configuration of the Source instance:
txkrun.pl -script=SetSSOReg
-removereferences=yes
Changes
Oracle E-Business Suite Instance was cloned from a SSO
enabled Oracle E-Business Suite instance.
This issue is caused due to residual references to SSO
configuration in the <SID_hostname>.xml context file.
The "s_mod_osso_conf_comment" variable enables or disables mod_osso for R12. This variable is updated by the SSO registration utility for R12.
This variable should have a value "#" if the instance is not SSO enabled.
Diagnosis
----------
The following example error message is found in the log file ($LOG_HOME/appl/admin/log/adapcctl.txt) for adapcctl.sh script:
...
Process (index=1,uid=675047098,pid=2461)
failed to start a managed process after the maximum retry limit
Log:
<$INST_TOPY/apps/VIS_at3/logs/ora/10.1.3/opmn/HTTP_Server~1
...
The HTTP_Server~1 log file shows the following message:
...
<$INST_TOP>/apps/VIS_at3/ora/10.1.3/Apache/Apache/bin/apachectl startssl: execing httpd
Syntax error on line 17 of <$INST_TOP>/apps/<SID>_<hostname>/ora/10.1.3/Apache/Apache/conf/mod_osso.conf:
Unable to open <$INST_TOP>/apps/<SID>_<hostname>/ora/10.1.3/Apache/Apache/conf/osso/<SID>_<hostname>_osso.conf.
...
The above error message implies the Apache is still looking for the SSO config file for the instance even when the newly cloned Oracle E-Business Suite instance is not SSO enabled.
Apache looks for the SSO config file based on the context file variable "s_mod_osso_conf_comment". If the value for this variable is not "#", it looks for the file.
Since it cannot find the <SID>_<hostname>_osso.conf, it fails to start.
The "s_mod_osso_conf_comment" variable enables or disables mod_osso for R12. This variable is updated by the SSO registration utility for R12.
This variable should have a value "#" if the instance is not SSO enabled.
Diagnosis
----------
The following example error message is found in the log file ($LOG_HOME/appl/admin/log/adapcctl.txt) for adapcctl.sh script:
...
Process (index=1,uid=675047098,pid=2461)
failed to start a managed process after the maximum retry limit
Log:
<$INST_TOPY/apps/VIS_at3/logs/ora/10.1.3/opmn/HTTP_Server~1
...
The HTTP_Server~1 log file shows the following message:
...
<$INST_TOP>/apps/VIS_at3/ora/10.1.3/Apache/Apache/bin/apachectl startssl: execing httpd
Syntax error on line 17 of <$INST_TOP>/apps/<SID>_<hostname>/ora/10.1.3/Apache/Apache/conf/mod_osso.conf:
Unable to open <$INST_TOP>/apps/<SID>_<hostname>/ora/10.1.3/Apache/Apache/conf/osso/<SID>_<hostname>_osso.conf.
...
The above error message implies the Apache is still looking for the SSO config file for the instance even when the newly cloned Oracle E-Business Suite instance is not SSO enabled.
Apache looks for the SSO config file based on the context file variable "s_mod_osso_conf_comment". If the value for this variable is not "#", it looks for the file.
Since it cannot find the <SID>_<hostname>_osso.conf, it fails to start.
1. Backup the $CONTEXT_FILE
2. Edit the parameter "s_mod_osso_conf_comment" in the $CONTEXT_FILE using editContext utility, or manually using a text editor
3. Set the value for the above parameter to "#"
4. Save the changes and run Autoconfig
5. Start the Apache service to re-test the issue
6. Migrate the solution as appropriate to other environments
2. Edit the parameter "s_mod_osso_conf_comment" in the $CONTEXT_FILE using editContext utility, or manually using a text editor
3. Set the value for the above parameter to "#"
4. Save the changes and run Autoconfig
5. Start the Apache service to re-test the issue
6. Migrate the solution as appropriate to other environments
No comments:
Post a Comment