Running startComponent.sh Script Fails With "Invalid instance ohs1" Error When Using Multiple Domains on Same Server
(Doc ID 2149629.1)
Last updated on AUGUST 13, 2020
Applies to:Oracle HTTP Server - Version 22.214.171.124.0 and later
Oracle Forms - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
When trying to start the the OHS component with the startComponent.sh script, it fails with this error:
Error Starting server ohs1: weblogic.nodemanager.NMException:
Received error message from Node Manager Server: [Server start command for OHS server 'ohs1' failed due to: [Invalid instance ohs1].
This error may occur for various reasons, but the instance is invalid for some reason.
Leading to the cause of this problem is a multi-homed installation on the same machine. This is usually performed on separate machines. Oracle HTTP Server (OHS) 12c is a standalone installation, it is not registered with an Oracle WebLogic (WLS) domain. OHS and Forms & Reports (F&R) 12.2.1 are purposely installed on the same server but in different ORACLE_HOME directories to provide an environment where OHS will be later configured to provide a remote proxy to WLS/F&R. The Forms & Reports domain is running on this server. The problem here is with the OHS configuration at installation time.
Before the actual issue outline occurs, the Configuration Assistant of the OHS home was executed to install an OHS standalone component and it ended successfully. However, the NodeManager fails to start because port 5556 was already in used by the Forms & Reports domain. The nodemanager.properties file was edited and the port number was changed from 5556 to 5557 and the NodeManager started successfully. This is common for this type of multi homed environment, but related to this issue for another reason.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!