Migration of Internal Manager Back to Primary Node is Failing When Node is Rebooted
(Doc ID 1508694.1)
Last updated on NOVEMBER 11, 2023
Applies to:
Oracle Concurrent Processing - Version 11.5.10.2 to 11.5.10.2 [Release 11.5]Information in this document applies to any platform.
Symptoms
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.
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 |
| Cause |
| Solution |
| References |