ICM Not Starting: Node Name not Registered
Error:
ICM does not start and the following error is reported:
Shutting down Internal Concurrent Manager
Concurrent Manager cannot find error description for CONC-System Node
Name not Registered
Contact your support representative.
Cause:
wrong host name defined
Solution:
The Concurrent Managers start up and call to the UNIX executable to determine the node name of the machine. This call is 'uname -a' and returns information about the operating system and the name of the node.
Each and every request that runs, takes this node name, time, absolute path to the output file and other information and puts an entry into the FND_CONCURRENT_REQUESTS table with the request ID.
This node name can be an alias but it should be something that the domain name server will resolve.
This node name value can be changed by running the UNIX command setuname or the hostname command. An example of this would be:
setuname -n newnodename
Once you change the node name, be sure to bring down the concurrent managers (if they are not already) and bring them back up. Go to the Concurrent Manager Administer screen to see the new node name on the row with the Internal Manager information.
Reference metalink Doc ID 602942.1
Error:
ICM does not start and the following error is reported:
Shutting down Internal Concurrent Manager
Concurrent Manager cannot find error description for CONC-System Node
Name not Registered
Contact your support representative.
Cause:
wrong host name defined
Solution:
The Concurrent Managers start up and call to the UNIX executable to determine the node name of the machine. This call is 'uname -a' and returns information about the operating system and the name of the node.
Each and every request that runs, takes this node name, time, absolute path to the output file and other information and puts an entry into the FND_CONCURRENT_REQUESTS table with the request ID.
This node name can be an alias but it should be something that the domain name server will resolve.
This node name value can be changed by running the UNIX command setuname or the hostname command. An example of this would be:
setuname -n newnodename
Once you change the node name, be sure to bring down the concurrent managers (if they are not already) and bring them back up. Go to the Concurrent Manager Administer screen to see the new node name on the row with the Internal Manager information.
Reference metalink Doc ID 602942.1
No comments:
Post a Comment