Concurrent Manager cannot find error description for CONC-System Node

For a new instance, when we failed over through Veritas Cluster, the concurrent manager did not come up and showed these errors:

Starting jupiter2_0516@jupiter2 Internal Concurrent Manager -- shell process ID 25341

logfile=$APPLCSF/$APPLLOG/jupiter2_0516.mgr
PRINTER=noprint
mailto=appesep2
restart=N
diag=N
sleep=60 (default)
pmon=20 (default)
quesiz=1 (default)

The Internal Concurrent Manager has encountered an error.

Review concurrent manager log file for more detailed information. : 16-MAY-2009 09:08:43 -


Shutting down Internal Concurrent Manager : 16-MAY-2009 09:08:43

List of errors encountered:
.............................................................................

_ 1 _
Concurrent Manager cannot find error description for CONC-System Node
Name not Registered

Contact your support representative.
.............................................................................



List of errors encountered:
.............................................................................

_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR

Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
.............................................................................

The jupiter2_0516@jupiter2 internal concurrent manager has terminated with status 1 - giving up.


This issue is described in Metalink Note 375813.1 and 456865.1

This occurs if the failover node is not present in fnd_nodes.

You need to do this to correct:

To implement the solution, please execute the following steps:

1. Verify correct node name is registered.
- Login with sysadmin responsibility

- Navigate to Install > Nodes

2. Enter correct name and save the change.

3. Restart concurrent managers