Migration of Internal Manager Back to Primary Node is Failing When Node is Rebooted

(Doc ID 1508694.1)

Last updated on JANUARY 16, 2017

Applies to:

Oracle Concurrent Processing - Version to [Release 11.5]
Information in this document applies to any platform.


When a node is rebooted, migration of Internal manager back to primary node fails and the logfile shows error message 'ICM Migration failed' repeatedly, the FNDLIBR process associated with ICM is still alive on secondary node.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms