Logo Background

Concurrent Manager Error – Name Not Registered

  • By on April 23, 2009 | 1 Comment

    I have perform Oracle cloning on RAC environment using Rapid Clone. When starting up the Oracle Concurrent Manager, the error “Concurrent Manager cannot find error description for CONC-System Node Name not Registered” was in the concurrent manager log at $APPLCSF/$APPLLOG/*.mgr

    ==========================================
    Error when starting up Concurrent Manager
    ==========================================
     
    Starting ORACLE_0423@ORACLE Internal Concurrent Manager -- shell process ID 9142
     
    logfile=oracle/common/admin/log/ORACLE_gvu2734/ORACLE_0423.mgr
    PRINTER=noprint
    mailto=applcrp
    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. : 23-APR-2009 10:45:54 -
     
    Shutting down Internal Concurrent Manager : 23-APR-2009 10:45:54
     
    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 ORACLE_0423@ORACLE internal concurrent manager 
    has terminated with status 1 - giving up

    As a workaround, we can change the profile option “Concurrent:GSM Enabled” from Y to N and startup the concurrent, but only certain concurrent manager can be started up and not all. When “Concurrent:GSM Enabled” set to N, concurrent queue such as Workflow Agent Listener Service, Workflow Mailer Service and Workflow Document Web Services Service could not be started up.

    For permanent solution, you need to setup and configure the entry in FND_NODES. 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

    But I do not recommend that you change the node name, at least you should know what are you doing. I am facing this error because my application server virtual name was the only entry in FND_NODES. You have to add the entry of your application server physical name which was ‘uname -a’ in UNIX to the FND_NODES

    You can do this add the entry from the steps below:

    1. Verify correct node name is registered.
    Go to System Administrator responsibility > Install > Nodes

    2. Enter correct name and save the change.

    3. Restart concurrent managers

    If the problem still doesn’t solve, please use the steps as below to total refresh your FND_NODES configuration: –

    1. Shutdown your applications

    2. Run cmclean.sql (obtain the script from Oracle Metalink)

    3. Run the script as below to clean the entry in FND_NODES by logging as apps in sqlplus(to remove entry from cloning)

    EXEC FND_CONC_CLONE.SETUP_CLEAN; 
    COMMIT; 
    EXIT;

    3. Run the autoconfig in DB Tier and Apps Tier.

    4. Startup all the Oracle Application services except Oracle Concurrent Manager.

    5. Verify correct node name is registered.
    Go to System Administrator responsibility > Install > Nodes

    6. Enter correct name and save the change (remember to add in your physical server name and not only virtual server name)

    7. Create FNDSM_’servername’ for all of the Nodes that exists in the table: FND_NODES by executing the script below

    cd $FND_TOP/patch/115/sql
    sqlplus apps/<password> @afdcm037.sql

    8. Startup the Oracle concurrent manager

    $COMMON_TOP/admin/scripts/$CONTEXT_NAME/adcmctl.sh start apps/<password>
    Previous
    Next
    » Unix IP Configuration Using ifconfig
  1. #1 Nathans_IV
    October 21, 2010 5:41 am

    Hello

    I had the same problem, and on looking up Metalink, I came across patch 6834168. This patch did not resolve the problem. I’ll test the advise you gave me and I’ll update you it here ASAP. Thank you.

    Nathan

    Post ReplyPost Reply
Leave a Comment