Opmn Reloads Cause Opmn Managed Processes To Go Into NONE Or Init Status
(Doc ID 553442.1)
Last updated on APRIL 16, 2021
Applies to:Oracle Fusion Middleware - Version 10.1.3.3.0 to 10.1.3.3.0 [Release AS10gR3]
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on SPARC (32-bit)
HP-UX PA-RISC (64-bit)
HP-UX ItaniumSun Solaris SPARC (64-bit)Sun Solaris SPARC (32-bit)HP-UX PA-RISC (64-bit)
Checked for relevance on 29-May-2009
Whenever "opmnctl reload" command is called, whether from adding/removing an
OC4J container (Using Application Server Control or command line) or running "opmnctl reload" manually,
"opmnctl reload" is attempting to start up components without taking into account
that those components are already up and running.
The startup will hang since the components are already up, and resulting in the components cannot be used at this point.
This can affect the OC4J containers and the HTTP Server.
"opmnctl status" shows components in a status of "NONE" or "Init" states and the only way
to fix it is to kill the processes manually using kill -9 from the command line.
At this point, the components become unusable.
This has only shown to occur once the instance is patched to 10.1.3.3
10.1.3.2 and previous 10.1.3.x versions do not display this problem
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