Oracle HTTP Server Fails to Start after Applying Patch 29794278(12.2.1.3.190517) with "SEVERE: ServerName directive is not configured in admin.conf of component_name"
(Doc ID 2569295.1)
Last updated on JULY 01, 2024
Applies to:
Oracle HTTP Server - Version 12.2.1.3.0 to 12.2.1.3.0 [Release 12c]Information in this document applies to any platform.
Symptoms
-This document has been created to supplement '<Document 2568225.1> Cumulative README Post-Install Steps for Oracle HTTP Server 12.2.1.3+ Bundle Patches' for the specific issue of error "SEVERE: ServerName directive is not configured in admin.conf of component_name."
-Patch 29794278 no longer exists. It was replaced with Patch 30158713 which has been superseded. Please obtain the latest patches from the current Critical Patch Update Advisory.
-Patch 29794278 no longer exists. It was replaced with Patch 30158713 which has been superseded. Please obtain the latest patches from the current Critical Patch Update Advisory.
After applying the Oracle HTTP Server (OHS) CPU Bundle Patch 12.2.1.3.190517 <Patch 29794278>, OHS fails to start with the following errors in nodemanager log.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |