Scribd Logo
Upload

Welcome to Scribd!

  • 218 views

    After Clone Concurrent Managers Issues

    Uploaded by

    arun k
    The document describes an issue where concurrent managers were down due to an error inserting data into a table. The error was ORA-01403 no data found. The solution involved updating the node and target names of the concurrent queues to match the hostname, running autoconfig scripts on the database and application tiers, and restarting the application.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    After Clone Concurrent Managers Issues

    Uploaded by

    arun k
    218 views2 pages
    The document describes an issue where concurrent managers were down due to an error inserting data into a table. The error was ORA-01403 no data found. The solution involved updating the node and target names of the concurrent queues to match the hostname, running autoconfig scripts on the database and application tiers, and restarting the application.

    Original Description:

    After clone concurrent managers issues

    Original Title

    After clone concurrent managers issues

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document describes an issue where concurrent managers were down due to an error inserting data into a table. The error was ORA-01403 no data found. The solution involved updating the node and target names of the concurrent queues to match the hostname, running autoconfig scripts on the database and application tiers, and restarting the application.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    218 views2 pages

    After Clone Concurrent Managers Issues

    Uploaded by

    arun k
    The document describes an issue where concurrent managers were down due to an error inserting data into a table. The error was ORA-01403 no data found. The solution involved updating the node and target names of the concurrent queues to match the hostname, running autoconfig scripts on the database and application tiers, and restarting the application.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    You are on page 1of 2

    5/21/2019 Concurrent Managers are down error insert_fcp failed due to ORA-01403 no data found, ORA-06512 | ORACLE DBA

    Concurrent Managers are down error insert_fcp failed due to ORA-01403 no


    data found, ORA-06512

    Hey DBA-Mates, Recently we faced this below error: ORA-01403: no data found
    Scenario:
    We are doing cloning and after all we started Application but we found that all Concurrent Manager is down
    except ICM.
    We checked the Manager log under $ cd $APPLCSF/log then we found the error as shown below:

    Error in CM :
    The SQL statement being executed at the time of the error was: and was executed from the file &ERRFILE.
    Could not initialize the Service Manager FNDSM_host_SID. Verify that host has been registered for
    concurrent processing.

    An error occured in client-side routine afpsmcsm for Service Manager FNDSM_host_SID. The routine
    returned code 126.

    Check for preceding errors and as well as the service manager log file for further details."
    Routine AFPEIM encountered an error while starting concurrent manager POMGR with library
    /apps/sku/apps/apps_st/appl/fnd/12.0.0/bin/FNDLIBR.
    Check that your system has enough resources to start a concurrent manager process. Contact your system
    admin : 17-AUG-2018 04:43:39
    Starting OAMCOLMGR Concurrent Manager : 17-AUG-2018 04:43:39

    ORACLE error 1403 in insert_fcp


    Cause: insert_fcp failed due to ORA-01403: no data found
    ORA-06512: at "APPS.FND_CP_FNDSM", line 177
    ORA-06512: at line 1.

    The SQL statement being executed at the time of the error was: and was executed from the file &ERRFILE.
    Could not initialize the Service Manager FNDSM_ora-data_sku. Verify that ora-data has been registered for
    concurrent processing.

    An error occured in client-side routine afpsmcsm for Service Manager FNDSM_ora-data_sku. The routine
    returned code 126.

    Check for preceding errors and as well as the service manager log file for further details."
    Routine AFPEIM encountered an error while starting concurrent manager OAMCOLMGR with library
    /apps/sku/apps/apps_st/appl/fnd/12.0.0/bin/FNDLIBR.

    Work-around/Solution:

    1. We logged in to front end and we noticed that Host name for ICM is in "Caps letters" like HOSTNAME and
    for others CM hostname was like hostname.

    2. Executed
    SQL> EXEC FND_CONC_CLONE.SETUP_CLEAN;

    SQL>update fnd_concurrent_queues set NODE_NAME='HOSTNAME' where ENABLED_FLAG='Y';

    SQL>update fnd_concurrent_queues set TARGET_NAME='HOSTNAME' where ENABLED_FLAG='Y';


    SQL> commit;
    Commit complete.

    https://ora-data.blogspot.com/2018/09/concurrent-managers-are-down-error-insertfcp-failed-due-to-ora-01403-no-data-found.html 1/2
    5/21/2019 Concurrent Managers are down error insert_fcp failed due to ORA-01403 no data found, ORA-06512 | ORACLE DBA

    SQL> exit

    3. Run autoconfig on DB tier.


    # pwd
    $ORACLE_HOME/appsutil/scripts/SID_hostname
    # ls -ltr adautocfg.sh
    -rwx------ 1 oracle dba 1570 Aug 12 2017 adautocfg.sh
    #

    4. Run autoconfig on APPS tier.


    $cd $APPL_TOP
    $ . ./APPSSID_hostname.env
    $ cd $ADMIN_SCRIPTS_HOME
    $ ls -ltr adautocfg.sh
    -rwx------ 1 applmgr oinstall 1564 Sep 17 08:03 adautocfg.sh
    $

    5. Start the application.


    $cd $ADMIN_SCRIPTS_HOME
    $ ls -ltr adstrtal.sh
    -rwx------ 1 applmgr oinstall 8393 Sep 17 08:03 adstrtal.sh
    $

    https://ora-data.blogspot.com/2018/09/concurrent-managers-are-down-error-insertfcp-failed-due-to-ora-01403-no-data-found.html 2/2

    You might also like

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy