Stopping Node Manager Causes Whole Server Migration
(Doc ID 1667639.1)
Last updated on MARCH 05, 2019
Applies to:Oracle Fusion Middleware High Availability - Version 18.104.22.168.0 and later
Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.
Customer has an OSB environment where Whole Server Migration has been configured. Customer's environment is:
- two RAC Database (DB) nodes.
- two managed servers configured on two hosts to use Whole Server Migration with the DB nodes controlled by a node manager (NM) on each host in an OSB cluster.
When the customer stops the managed server from the console and then stops the corresponding NM, then a whole server migration is performed for the considered managed server.
Problem has been checked in the server migration table provided by the customer : the number of rows in it always stay constant, meaning that a whole server migration will be triggered.
After comparing a lab setup logs in debug mode and customer's logs, the difference is that a thread dump is generated while the managed server is shutdown. The interesting stack is:
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