My Oracle Support Banner

Failback To The Primary Concurrent Node Does Not Startup Authomatically (Doc ID 1088081.1)

Last updated on DECEMBER 23, 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

On the Primary Node, the Node field is changed back to the Primary Node in the Administer Concurrent Managers form for the Internal Concurrent Manager and Internal Monitor, but cannot start up. The Applications 806 listener doesn't start up automatically on the just re-booted node.

Failback is not happening and the following was found in the Internal Concurrent Manager log file
<NODENAME> is unavailable to migrate. REASON: Service Manager currently unreachable by TNS

Changes

 

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!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.