Applies to: Oracle Applications Technology Stack - Version: 12.0 to 12.0.4 - Release: 12.0 t o 12.0 Information in this document applies to any platform.

Symptoms After cloning an Oracle E-Business Suite instance from an SSO enabled Oracle E-B usiness Suite instance, starting the Apache service using $INST_TOP/admin/script s/ script fails with the following error : 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: -script=SetSSOReg -removereferences=yes Changes Oracle E-Business Suite Instance was cloned from a SSO enabled Oracle E-Business Suite instance. Cause 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 d isables mod_osso for R12. This variable is updated by the SSO registration utili ty for R12. This variable should have a value "#" if the instance is not SSO ena bled. Diagnosis ---------The following example error message is found in the log file ($LOG_HOME/appl/adm in/log/adapcctl.txt) for script: _____________________________ Error --> Process (index=1,uid=675047098,pid=2461) failed to start a managed process after the maximum retry limit Log: /oracle/appsR12/inst/apps/VIS_at3/logs/ora/10.1.3/opmn/HTTP_Server~1 _____________________________ The HTTP_Server~1 log file shows the following message: _____________________________ /oracle/appsR12/inst/apps/VIS_at3/ora/10.1.3/Apache/Apache/bin/apachectl startss l: execing httpd Syntax error on line 17 of /oracle/appsR12/inst/apps/VIS_at3/ora/10.1.3/Apache/A pache/conf/mod_osso.conf: Unable to open /oracle/appsR12/inst/apps/VIS_at3/ora/10.1.3/Apache/Apache/conf/o sso/VIS_at3_osso.conf. _____________________________ The above error message implies the Apache is still looking for the SSO config f ile 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_o sso_conf_comment". If the value for this variable is not "#", it looks for the f

Start the Apache service to re-test the issue 6. or manually using a text editor 3. Edit the parameter "s_mod_osso_conf_comment" in the $CONTEXT_FILE using edit Context utility. Migrate the solution as appropriate to other environments . Set the value for the above parameter to "#" 4. Solution 1. it fails to start.ile. Backup the $CONTEXT_FILE 2. Since it cannot find the VIS_at3_osso. Save the changes and run Autoconfig 5.conf (in the above example).