Resolving OHS Start Up Issues

Note:

• The OHS service depends on the Node Manager. Ensure that the Node Manager is up and running.
• If the Node Manager fails to start, review the logs located under:

  [EPM_ORACLE_INSTANCE]\httpConfig\ohs\nodemanager

OHS Startup Failure Scenarios

Table 11-7 Scenario 1: Startup Failure During Sequential Update

Step	Details
OHS Installation	Ensure that the OHS installation was completed succesfully.
Middleware_Home directory structure	Ensure the Middleware_Home/ohs directory contains all the necessary subfolders, matching a known working environment. If not, copy them from a working environment. Middleware_Home/ohs/lib should have all the required libraries. If startup error points to any missing libraries, copying this folder from a working environment can resolve the issue.
OPatch Version	Verify the OPatch version under Middleware_Home/ohs. It should match the version required for the current release to confirm that the OPatch upgrade was successful.
ApplyUpdate Summary Log	Review the ApplyUpdate Summary Log for any OHS patch failures or conflicts. For more details, refer to the ApplyUpdate details log. If conflicts are found: Rollback the conflicting OPatch. Re-Run ApplyUpdate.

Table 11-8 Scenario 2: Startup Failure During Sequential Update When OHS CPU Patches Were Applied by the User

Step	Details
OHS Installation	Ensure that the OHS installation was completed succesfully. Insufficient TMP space can cause installation failues. Ensure that there is adequate space in TMP durectory On Linux machines, installation may fail if the noexec flag is set on the TMP directory. Remove the noexec flag and reinstall OHS manually.
OPatch Version	Verify the OPatch version under Middleware_Home/ohs. It should match the version required for the current release to confirm that the OPatch upgrade was successful.
ApplyUpdate Summary Log	Review the ApplyUpdate Summary Log for any OHS patch failures or conflicts. For more details, refer to the ApplyUpdate details log. If conflicts are found: Rollback the conflicting OPatch. Re-Run ApplyUpdate.
Manually installed OHS CPU Patches	If the OHS CPU Patches were manually installed, verify if the following sequence was followed: Was OPatch upgraded to the supported version? Was database client upgraded to the required version before applying the the OHS CPU patches? Were all the OHS CPU patches applied after the database client installation, as specified in the Fusion Middleware documentation? FMW.OHS FMW.OHS.DBRU FMW.OHS.OSS FMW.OHS.VS FMW.OHS.OPSS
OHS CPU Patches applied without database client	If the OHS CPU patch was applied without the required database client: Rollback the OHS CPU patch. if Rollback is not possible, check if a backup of the OHS installation exists. If available, restore from backup. If not, copy the ohs folder from another working environment with the same version. If no backup exists and recovery from another system is not possible, contact Oracle support.