Loading ...Oracle Application Server (OAS) Error on apachemoduleossl.dll During or After Patch Sets
The issue is actually related to OPatch, the utility to install one-off patches. Patch 5907304 needs to be applied in order to supply 10.1.0.5 networking libraries. This is referred to 10.1.0.5 Bundle 13, and is intended to be automatically installed with the Oracle Application Server 10g Patch Sets. These libraries may have networking objects various other components may use, especially the Oracle HTTP Server when using SSL, and hence the implication with apachemoduleossl.dll.
milly 1:07 pm on May 18, 2010
It appears OPatch may have failed to apply Patch 5907304 as an earlier action before the Configuration Assistant which redeploys applications and issues dcmctl updateconfig. There is usually a One-Off Patch Configuration Assistant which makes a call to OPatch. There may not be an error reported back to the OUI (Installer) when there is a problem, and it can say “Run One-off OPatches” succeeded. This is because the OUI installer and OPatch utility operate independently.
In any case, if Patch 5907304 is not applied, then the newer modossl functionality will not work.
You can check for Patch 5907304 in your inventory using this method:
set ORACLE_HOME=
%ORACLE_HOME%\OPatch\opatch lsinventory
(5907304 or newer 10.1.0.5 bundle patch should be listed if you have just applied the Patch Set)
To troubleshoot why it failed, check the ORACLE_HOME\.patch_storage\5907304 to see if anything exists. It not clear what happened because it was behind the OUI Installer. There may be nothing in the opatch logs unless the opatch utility is manually run yourself. By seeing the .patch_storage as being empty, something happened with the opatch apply.
Certain 10.1.0.5 networking files need to be in place before the running of the Configuration Assistant because it is running ‘dcmctl updateconfig’, which checks syntax or starting the Oracle HTTP Server, just like the above manual command.
Note this issue does not always occur, and circumstances may differ resulting in the loss of 5907304 or newer 10.1.0.5 bundle patch.
- Applied the Oracle Application Server 10g Release 2 (10.1.2.3) or Release 3 (10.1.3.3, 10.1.3.4, 10.1.3.5) Patch Sets on Windows platform
- Configuration Assistants fail after issuing a “dcmctl updateconfig” command, which checks syntax and updates the repository. It is failing on a syntax check with the HTTP_Server component saying it could not load the apachemoduleossl.dll module.
- Issuing “opmnctl startproc process-type=HTTP_Server” fails and upon checking the ORACLE_HOME/Apache/Apache/logs/error_log, it could not load the apachemoduleossl.dll module.
- If editing the opmn.xml and httpd.conf files to disable SSL and the ApacheModuleOSSL.dll module from loading, the HTTP_Server will then start.
- Manual “dcmctl updateconfig” results on version 10.1.2.3
Our solution:
In our situation, we tried reinstalling OAS several times using different AS instance name and OC4J name, and it actually went through without the error fine. OAS is very strange when it comes to naming convention and it seems flaky and picky about certain combination of names.
Other Solutions:
Manually apply Patch 5907304, (or newer), which means all Oracle processes (including the OUI installer) on the machine should be down to avoid potential issues. If this occurs during a Patch Set installation, disable SSL for the HTTP_Server and re-run the Configuration Assistant from the session you are currently using. Otherwise you may run configToolCommands to get the Configuration Assistant to run again in another session. The below steps consider these two options:
1. Opening the opmn.xml file and disable SSL for the HTTP_Server:
- Open ORACLE_HOME\opmn\conf\opmn.xml in a text editor.
- In the entry, if required, change the start mode from “ssl-enabled” to “ssl-disabled”. After modification is made, the entry should look like the following:
<data id="start-mode" value="ssl-disabled"/>- Save and close opmn.xml. Reload OPMN using the following command:
% opmnctl reload- Open the ORACLE_HOME\Apache\Apache\conf\httpd.conf and comment out the following lines to prevent it from loading and syntax checked:
- Save and close the httpd.conf. Use updateconfig if on version 10.1.2.3 and confirm no issue:
% dcmctl updateconfig2. Finish the Patch Set installation by clicking retry on the failed Configuration Assistant. If problem occurred during installation and you no longer have the session available, execute the ORACLE_HOME\cfgtoollogs\configToolCommands.pl to re-run all skipped or failed Configuration Assistants. (There is more information about configToolCommands in the original Installation Guide)
3. Stop all Oracle Services and processes on the machine, as is the requirement for most one-off patching on Windows to avoid potential lock issues.
4. Download Patch 5907304 from My Oracle Support. Note that this is superseded by Critical Patch Updates (CPU), and thus you may choose to install the newest one available:
Critical Patch Updates (CPU) and Security Alerts
– Check for latest CPU, then look for an associated Patch Availability Document
5. Install Patch 5907304 (or newer) following the readme, “opatch apply” when in the patch directory. (Note that the newer CPUs use the “opatch napply” command)
6. Enable SSL again if it was disabled during this process, uncomment out the lines in the httpd.conf, and restart the HTTP_Server (and all other processes as normal).