Concurrent Manager cannot find error description for CONC-System Node
Name not Registered
Name not Registered
Issue : After Installing R12 (12.1.1) On HP-UX 11.31 Itanium .
Error in Concurrent Manager Log file
========================================================================
Starting XXX@XXXInternal Concurrent Manager -- shell process ID 9809
logfile=/u02/ebiz/inst/apps/MAXDEMO_demoserver/logs/appl/conc/log/MAXDEMO_1013.mgr
PRINTER=noprint
mailto=appsvis
restart=N
diag=N
sleep=30
pmon=4
quesiz=1
Reviver is ENABLED
The Internal Concurrent Manager has encountered an error.
Review concurrent manager log file for more detailed information. : 13-OCT-2010 19:42:43 -
Shutting down Internal Concurrent Manager : 13-OCT-2010 19:42: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 XXX@XXX internal concurrent manager has terminated with status 1 - giving up.
Solution :
1st :
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
2nd :
If the above solution doesnt work.
(By default HP-UX can have hostname only 8 characters if you have given more than 8 characters then
increase the lenght of hostname)
Check the node name of sever
# uname -n ( should give you nodename)
# hostname
both the above commands should give same result.
if not same then change the nodename by #set_parms commad
and check once again by the above commands.
Restart concurrent managers and check conc are up and running If not.
3rd :
login to apps tier :
sqlplus apps/apps
check entries in FND_NODES
also check entries in FND_CONCURRENT_REQUESTS.
sql> select LOGFILE_NODE_NAME,OUTFILE_NODE_NAME from fnd_concurrent_requests;
check whether logfile and outfile nodename are same if not
first take backup of the fnd_concurrent_requests then update the logfile and outfile node name with correct nodename.
Issue commit;
and come out.
bounce conc managers and check once again.
(if still issue is there)
4th :
Download cmclean script from metalink.
stop conc managers $INST_TOP/admin/scripts
$./adcmctl.sh stop
copy to the server and sqlplus apps/apps
sql>@cmclean.sql
sql > commit;
come out
start conc managers and check managers are up and running.
if still facing the issue :
5th :
Check OS Kernel Parameters and keep them to maximum.
Restart the server if asked to kernel parameters are static.
bounce the conc manager and check again.
6th :
.....IF THE ISSUE IS STILL THERE THEN PLEASE RAISE SR WITH ORACLE.....
