Concurrent Manager Node Name Issue

Hi All,
Recently one of EBS 11i (11.5.10.2 + RHEL 4.7) Node (VM Node) has been cloned to another node. So i had to change the Host name for the cloned application. I followed the meta link note 338003.1 and 341322.1. I am successfully changed the host name and able to access the application as well. When i check the Concurrent manager process's status, its showing Actual-1 and Target -1. B*ut the problem is some of process's node name is showing the previous node name (the name of the node from where cloned).* For example Output Post Processor's node name is showing the previous one and its status showing Actual - 0 and Target - 1. Please let me know why this has happened and also how can i solve this issue?
Thanks,
Mani

Please run cmclean.sql script as per (Concurrent Processing - CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables [ID 134007.1]) and check then.
If you still have the same issue, update FND_CONCURRENT_QUEUES table (TARGET_NODE column) -- Troubleshooting the "Error Occurred While Attempting to Establish an Applications File Server Connection" [ID 117012.1]
Please also see (Concurrent Processing - CCM.sql Diagnostic Script to Diagnose Common Concurrent Manager Issues [ID 171855.1]).
Thanks,
Hussein

Similar Messages

  • Concurrent manager failed to start on win2k3,

    hi,
    this is seems to be common issue, i have search so many forums but unable to bring up concurrent managers.pls help me resolve the issue.
    APPS: 11i (11.5.10.2 ) on win2k3.
    //An error occurred while attempting to establish an Applications File Server connection with the node FNDFS_APPS. There may be a network configuration problem, or the TNS listener on node FNDFS_APPS may not be running. Please contact your system administrator.//
    SQL> SELECT concurrent_queue_name
    2 FROM fnd_concurrent_queues
    3 WHERE concurrent_queue_name LIKE 'FND%';
    CONCURRENT_QUEUE_NAME
    FNDCPOPP
    FNDCRM
    FNDICM
    FNDIM_APPS
    FNDIM_AUTHENTICATION
    FNDSCH
    FNDSM_APPS
    FNDSM_AUTHENTICATION
    FNDTMTST
    9 rows selected.
    D:\oracle\visora\8.0.6\NET80\ADMIN\VIS_apps>tnsping80 FNDFS_APPS
    TNS Ping Utility for 32-bit Windows: Version 8.0.6.3.0 - Production on 27-MAY-2010 14:22:00
    (c) Copyright 1997 Oracle Corporation. All rights reserved.
    Attempting to contact (ADDRESS=(PROTOCOL=tcp)(HOST=APPS.ora.com)(PORT=1626))
    OK (20 msec)
    FNDFS.exe is available at FND_TOP/bin DIRECTORY.
    i have run autoconfig on both the tire also. but issue is still there.
    i have gone through from Standard Concurrent Manager is not running.
    Note: 735148.1 - How to Troubleshoot Concurrent Manager Start Up Issue Related to Service Manager
    Note: 423170.1 - Concurrent Manager Fails to Start Because of a 'Could not start Service Manager FNDSM__' Error
    kindly help me to resolve this issue.
    Regards,
    sandeep.

    Hi;
    It was working before? Did you apply any patch or something else?
    Those note which u mention in your post didnt help?
    Did you try to Maintain Applications Files >> Relink Applications programs ?
    Regard
    Helios

  • How to clean Concurrent Managers Nodes on Cloned instances.

    Hi,
    We have PCP on PROD environment, when we do cloning to test instances, after running exec FIND_CONC_CLONES on test instances , TEST instance concurrent managers nodes are still pointing to PROD CM nodes, Please let me know how to change to test concurrent manager nodes, I know we can do it manually its all time taken process to change all managers one by one.
    Thanks

    Hi;
    Please check below thread;
    Re: Standard Manager still pointing to PROD after Clone
    EXEC FND_CONC_CLONE.SETUP_CLEAN;
    If its not help please update thread

  • Concurrent Manager Issue in Oracle Apps 11i on MS Windows 2003

    Hi,
    We have Oracle Apps 11i (11.5.10) on Windows 2003 running Oracle Financilas and Supply Chain.
    From this morning onwards, concurrent requests are not getting completed. All requests are showing Running Normally. I checked the server (Single Node 4 GB Memory) and CPU usage is more than 90%. Task Manager is showing 50% CPU usage for SYSTEM (Image Name). Once the CPU usage for SYSTEM(image name) goes beyond 40% then the server is becoming slow and the problem starts.
    When I stop the Concurrent Manager it does not stop and I have to End Process the FNDLIBR process manually.
    I have recreated the concurrent manager using CCMSETUP and also ran cmclean.sql. Nothing is helping.
    System is Live since 2006 and the issue started only today.
    Please suggest any solutions as this is happening in our Production system.
    Thanks.
    Thiru

    Thiru,
    Which concurrent manager consumes the CPU usage? Are you able to identify it?
    Any errors in the CM log file? Did you try to start the CM with diag=y and see if any errors are reported in the log files?
    What happen to the CPU usage when you stop the CM?
    I assume that you are running Purge Concurrent Manager/Requests on regular basis, so this should not be an issue here.
    Please review the following notes, and see if it helps.
    Note: 114380.1 - Concurrent Manager Processes Taking Lots of CPU
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=114380.1
    Note: 264752.1 - FNDLIBR Consuming Memory Causing CPU Utilization To Increase Daily
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=264752.1
    System is Live since 2006 and the issue started only today.I assume no changes have been done recently, correct?
    Regards,
    Hussein

  • Concurrent Manager cannot find error description for CONC-System Node

    Hi friends,
    I m facing a problem while doing clustering for oracle EBS.i m using hpux11i with veritas cluster server for oracle DataBase cluster.i am doing 2 node cluster.i have installed oracle 11i apps with 9i DB.thru veritas i am able to do a db cluster failover.now i want to run oracle apps 11i too from both nodes(active/passive).so i configured a virtual IP address with a Virtual Hostname which will move along with the cluster failover.when i configure ora apps tier thru giving it virtual hostname concurrent manager dies with error--Concurrent Manager cannot find error description for CONC-System Node. i tried many things but unable to come up with a solution. pls help.
    regs
    Satish

    Please post the contents of your hosts file here.
    Is FND_NODES table populated correctly? Please run AutoConfig and make sure it completes successfully.
    Why are the Concurrent Managers Failing with 'CONC-System Node Name not Registered" Error After Applying Patch 6461517? [ID 1108452.1]
    OPP and SFM Managers do not Start [ID 1425409.1]
    Thanks,
    Hussein

  • Issue when opening a report from concurrent manager

    Hi all,
    Our EBS instance worked well and stable. But two days ago, we met a strange issue as below description:
    When user clicks "View Output" or "View log" from concurrent manager, they see the error in the pop-up: "Authentication failed" or "File server could not identify source file". The link in the pop-up is in "http://hostname/OA_CGI/FNDWRR.exe?temp_id=<number>" format.
    After some attempts to refresh this pop-up page or close pop-up - re-click "View output" our user can see the correct output as normal. Sometimes, they click view output once and get the correct output immediately. The messages we've got is not same during these attempts, it could be authentication failed or "File server could not identify source file" randomly.
    We've tried to find the solutions from metalink and from some threads in this forum but nothing can help. It's our production system.
    Hope to see the solution from you
    Our environment: Oracle EBS 11.5.10.2 on RHEL 4.6 32bit, Database Oracle 10.2.0.4 on RHEL 4.6 64bit

    When user clicks "View Output" or "View log" from concurrent manager, they see the error in the pop-up: "Authentication failed" or "File server could not identify source file". The link in the pop-up is in "http://hostname/OA_CGI/FNDWRR.exe?temp_id=<number>" format.
    Have you checked "File Server Could Not Identify Source File [ID 1073863.1]"?
    After some attempts to refresh this pop-up page or close pop-up - re-click "View output" our user can see the correct output as normal. Sometimes, they click view output once and get the correct output immediately. The messages we've got is not same during these attempts, it could be authentication failed or "File server could not identify source file" randomly.Any changes have been done recently?
    Can you find any errors in the CM/Database/OS log files?
    Can you confirm that the concurrent requests output/log files have been generated successfully at the OS level? Does this issue happen with all concurrent requests or specific ones only?
    We've tried to find the solutions from metalink and from some threads in this forum but nothing can help. What solutions have you tried?
    Did you run AutoConfig?
    It's our production system.For production issues, please log a SR.
    Thanks,
    Hussein

  • Widows XP - Concurrent Manager - Target node/queue unavailable!

    Dear All,
    Need help to run concurrent Manager, all services are up, started, but all request are inactive, no manager, I tried my best to solve this problem thru metalink, updating FND......, its activating and suddenly status changing to target node/queue unavailable.
    Please give me some idea how to sort this problem, when intalling 11i there is some error came memory error and i cancelled, then it proceeded and completed installation.
    Regards,
    Williams.

    Hi All,
    I am also facing same problem and did you got the any soluation.
    I am getting below problem, while trying to install E-Business suite on Windows server XP,
    RW-50011 :ERROR:- Operating system patch/version test has returned an error:1
    Moreover I have prox 92 GB disk space free, but it's giving errors, there is no enough free space on disk...
    Warm regards
    raags INDIA
    [email protected]

  • Issue in Concurrent manager

    Hi All,
    Last week I faced one issue related with concurrent manager.From the development side,they said submitted concurrent requests(which is normally run by standard manager) were in pending& normal status. I checked the standard manager .It shows actual: 1 and target: 8. In standard manager one request was running.I have deactivated and activated the standard manager.It solved the problem.But I didn't check the status of those request which were in pending&normal stage.
    I know that when we deactivate standard manager it will alllow the running requests to complete.But what will happen to those requests in
    pending&normal(which needs to be run asap) status?
    and also why suddenly there was a difference between actual and target process?
    Thanks,
    RajaSekar

    Pending requests will be processed with the priority given.
    In concurrent manager,
    Actual Processes: The number of operating system processes that means the processes that are actually running.
    Target Processes: The max number of service processes that can be active for this service.
    Usually both actual and target are same.
    Refer: Concurrent Processing - Concurrent Manager Generic Platform Questions and Answers [ID 105133.1]
    Cherrish Vaidiyan

  • Concurrent Manager encountered an error while running Oracle*Report for you

    hi
    our team is running a report.but encountered
    +-----------------------------
    | Starting concurrent program execution...
    +-----------------------------
    Arguments
    P_DELV_ID='8022'
    Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
    American_America.US7ASCII
    Enter Password:
    REP-0069: Internal error
    REP-57054: In-process job terminated:Terminated with error:
    REP-1401: '': Fatal PL/SQL error occurred.
    Report Builder: Release 10.1.2.0.2 - Production on Mon Jun 21 11:26:16 2010
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    +---------------------------------------------------------------------------+
    Start of log messages from FND_FILE
    +---------------------------------------------------------------------------+
    +---------------------------------------------------------------------------+
    End of log messages from FND_FILE
    +---------------------------------------------------------------------------+
    Program exited with status 1
    Concurrent Manager encountered an error while running Oracle*Report for your concurrent request 451508.
    Review your concurrent request log and/or report output file for more detailed information.
    +---------------------------------------------------------------------------+
    Executing request completion options...
    +------------- 1) PUBLISH -------------+
    Beginning post-processing of request 451508 on node DEMO at 21-JUN-2010 11:26:17.
    Post-processing of request 451508 failed at 21-JUN-2010 11:26:17 with the error message:
    One or more post-processing actions failed. Consult the OPP service log for details.
    +--------------------------------------+
    Finished executing request completion options.
    +---------------------------------------------------------------------------+
    Concurrent request completed
    Current system time is 21-JUN-2010 11:26:17
    +---------------------------------------------------------------------------+how to solve it?when i am searching in this error in cmctl log there is nothing for it.
    i have lnched a SR on this they told to run it by appsrwrun.sh.how to run this report by appsrwrun.sh??
    rgrds
    Edited by: new2appsdba on Jun 21, 2010 4:19 AM

    Hi,
    how do you suspect its a OPP related issue??what is OPP?
    Enter value for request_id: 451508
    old   5: AND fcpp.concurrent_request_id = &&request_id
    new   5: AND fcpp.concurrent_request_id = 451508
        REQ_ID NODE_NAME
    LOGFILE_NAME
        451508 DEMO
    /t01/demoap/inst/apps/DEMO_demo/logs/appl/conc/log/FNDOPP94508.txt
    [demoap@demo ~]$ vi /t01/demoap/inst/apps/DEMO_demo/logs/appl/conc/log/FNDOPP94508.txt
    [6/20/10 1:37:36 PM] [main] Starting GSF service with concurrent process id = 94508.
    [6/20/10 1:37:36 PM] [main] Initialization Parameters: oracle.apps.fnd.cp.opp.OPPServiceThread:2:0:max_threads=5
    [6/20/10 1:37:37 PM] [Thread-16] Service thread starting up.
    [6/20/10 1:37:37 PM] [Thread-15] Service thread starting up.
    [6/21/10 11:12:00 AM] [OPPServiceThread0] Post-processing request 451495.
    [6/21/10 11:12:00 AM] [94508:RT451495] Executing post-processing actions for request 451495.
    [6/21/10 11:12:00 AM] [94508:RT451495] Starting XML Publisher post-processing action.
    [6/21/10 11:12:00 AM] [94508:RT451495]
    Template code: WILPACKSLIP
    Template app:  ONT
    Language:      en
    Territory:     00
    Output type:   PDF
    [6/21/10 11:12:00 AM] [UNEXPECTED] [94508:RT451495] java.io.FileNotFoundException: /t01/demoap/inst/apps/DEMO_demo/logs/appl/conc/out/o451495.out (No such file or directory)
            at java.io.FileInputStream.open(Native Method)
            at java.io.FileInputStream.<init>(FileInputStream.java:106)
    at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:241)
            at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:172)
    [6/21/10 11:12:00 AM] [94508:RT451495] Completed post-processing actions for request 451495.
    [6/21/10 11:22:27 AM] [OPPServiceThread0] Post-processing request 451505.
    [6/21/10 11:22:27 AM] [94508:RT451505] Executing post-processing actions for request 451505.
    [6/21/10 11:22:27 AM] [94508:RT451505] Starting XML Publisher post-processing action.
    [6/21/10 11:22:27 AM] [94508:RT451505]
    Template code: WILPACKSLIP
    Template app:  ONT
    Language:      en
    Territory:     00
    Output type:   PDF
    [6/21/10 11:22:27 AM] [UNEXPECTED] [94508:RT451505] java.io.FileNotFoundException: /t01/demoap/inst/apps/DEMO_demo/logs/appl/conc/out/o451505.out (No such file or directory)
            at java.io.FileInputStream.open(Native Method)
            at java.io.FileInputStream.<init>(FileInputStream.java:106)
    at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:241)
            at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:172)
    [6/21/10 11:22:27 AM] [94508:RT451505] Completed post-processing actions for request 451505.
    [6/21/10 11:26:17 AM] [OPPServiceThread1] Post-processing request 451508.
    [6/21/10 11:26:17 AM] [94508:RT451508] Executing post-processing actions for request 451508.
    [6/21/10 11:26:17 AM] [94508:RT451508] Starting XML Publisher post-processing action.
    [6/21/10 11:26:17 AM] [94508:RT451508]
    Template code: WILPACKSLIP
    Template app:  ONT
    Language:      en
    Territory:     00
    Output type:   PDF
    [6/21/10 11:26:17 AM] [UNEXPECTED] [94508:RT451508] java.io.FileNotFoundException: /t01/demoap/inst/apps/DEMO_demo/logs/appl/conc/out/o451508.out (No such file or directory)
            at java.io.FileInputStream.open(Native Method)
            at java.io.FileInputStream.<init>(FileInputStream.java:106)
                                                                  at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:241)
            at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:172)
    [6/21/10 12:00:59 PM] [94508:RT451533] Completed post-processing actions for request 451533.
    [6/21/10 12:17:51 PM] [OPPServiceThread0] Post-processing request 451573.
    [6/21/10 12:17:51 PM] [94508:RT451573] Executing post-processing actions for request 451573.
    [6/21/10 12:17:51 PM] [94508:RT451573] Starting XML Publisher post-processing action.
    [6/21/10 12:17:51 PM] [94508:RT451573]
    Template code: XXWEBB_EXP_INV
    Template app:  ONT
    Language:      en
    Territory:     00
    Output type:   PDF
    [6/21/10 12:17:51 PM] [UNEXPECTED] [94508:RT451573] java.io.FileNotFoundException: /t01/demoap/inst/apps/DEMO_demo/logs/appl/conc/out/o451573.out (No such file or directory)
            at java.io.FileInputStream.open(Native Method)
            at java.io.FileInputStream.<init>(FileInputStream.java:106)
    at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:241)
            at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:172)
    [6/21/10 12:17:51 PM] [94508:RT451573] Completed post-processing actions for request 451573.
    [6/21/10 12:19:19 PM] [OPPServiceThread0] Post-processing request 451577.
    [6/21/10 12:19:19 PM] [94508:RT451577] Executing post-processing actions for request 451577.
    [6/21/10 12:19:19 PM] [94508:RT451577] Starting XML Publisher post-processing action.
    [6/21/10 12:19:19 PM] [94508:RT451577]
    Template code: WILEXINVREP
    Template app:  ONT
    Language:      en
    Territory:     00
    Output type:   PDF
    [062110_121919525][][EXCEPTION] [DEBUG] ------- Preferences defined PreferenceStore -------
    [062110_121919526][][EXCEPTION] [DEBUG] ------- Environment variables stored in EnvironmentStore -------
    [062110_121919526][][EXCEPTION] [DEBUG]  [FND_JDBC_IDLE_THRESHOLD.LOW]:[-1]
    [062110_121919526][][EXCEPTION] [DEBUG]  [FND_JDBC_IDLE_THRESHOLD.LOW]:[-1]
    [062110_121919526][][EXCEPTION] [DEBUG]  [SECURITY_GROUP_ID]:[0]
    [062110_121919526][][EXCEPTION] [DEBUG]  [FND_JDBC_BUFFER_DECAY_INTERVAL]:[300]
    [062110_121919526][][EXCEPTION] [DEBUG]  [NLS_CHARACTERSET]:[US7ASCII]
    [062110_121919526][][EXCEPTION] [DEBUG]  [RESP_APPL_ID]:[-1]
    [062110_121919526][][EXCEPTION] [DEBUG]  [NLS_LANGUAGE]:[AMERICAN]
    [062110_121919526][][EXCEPTION] [DEBUG]  [FND_JDBC_BUFFER_MIN]:[1]
    [062110_121919526][][EXCEPTION] [DEBUG]  [FND_JDBC_BUFFER_MAX]:[2]
    [062110_121919526][][EXCEPTION] [DEBUG]  [NLS_NUMERIC_CHARACTERS]:[.,]
    [062110_121919526][][EXCEPTION] [DEBUG]  [APPS_JDBC_URL]:[jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES)(ADDRESS=(PROTOCOL=tcp)(HOST=demo.webbindia.com)(PORT=1527)))(CONNECT_DATA=(SID=DEMO)))]
    [062110_121919527][][EXCEPTION] [DEBUG]  [RESP_ID]:[-1]
    [062110_121919527][][EXCEPTION] [DEBUG]  [FND_MAX_JDBC_CONNECTIONS]:[500]
    [062110_121919527][][EXCEPTION] [DEBUG]  [FND_JDBC_USABLE_CHECK]:[false]
    [062110_121919527][][EXCEPTION] [DEBUG]  [USER_ID]:[-1]
    [062110_121919527][][EXCEPTION] [DEBUG]  [NLS_TERRITORY]:[AMERICA]
    [062110_121919527][][EXCEPTION] [DEBUG]  [FND_JDBC_PLSQL_RESET]:[false]
    [062110_121919527][][EXCEPTION] [DEBUG]  [FND_JDBC_CONTEXT_CHECK]:[true]
    [062110_121919527][][EXCEPTION] [DEBUG]  [NLS_DATE_FORMAT]:[DD-MON-RR]
    [062110_121919527][][EXCEPTION] [DEBUG]  [FND_JDBC_BUFFER_DECAY_SIZE]:[5]
    [062110_121919527][][EXCEPTION] [DEBUG]  [FND_JDBC_IDLE_THRESHOLD.HIGH]:[-1]
    [062110_121919527][][EXCEPTION] [DEBUG]  [NLS_SORT]:[BINARY]
    [062110_121919527][][EXCEPTION] [DEBUG]  [NLS_DATE_LANGUAGE]:[AMERICAN]
    [062110_121919527][][EXCEPTION] [DEBUG]  [LOGIN_ID]:[-1]
    [062110_121919528][][EXCEPTION] [DEBUG] ------- Properties stored in Java System Properties -------
    [062110_121919528][][EXCEPTION] [DEBUG]  [APPLTMP]:[/t01/demoap/inst/apps/DEMO_demo/appltmp]
    [062110_121919528][][EXCEPTION] [DEBUG]  [java.runtime.name]:[Java(TM) 2 Runtime Environment, Standard Edition]
    [062110_121919528][][EXCEPTION] [DEBUG]  [sun.boot.library.path]:[/t01/demoap/apps/tech_st/10.1.3/appsutil/jdk/jre/lib/i386]
    [062110_121919528][][EXCEPTION] [DEBUG]  [java.vm.version]:[1.5.0_08-b03]
    [062110_121919528][][EXCEPTION] [DEBUG]  [OVERRIDE_DBC]:[true]
    [062110_121919528][][EXCEPTION] [DEBUG]  [dbcfile]:[/t01/demoap/inst/apps/DEMO_demo/appl/fnd/12.0.0/secure/DEMO.dbc]
    [062110_121919528][][EXCEPTION] [DEBUG]  [java.vm.vendor]:[Sun Microsystems Inc.]
    [062110_121919528][][EXCEPTION] [DEBUG]  [java.vendor.url]:[http://java.sun.com/]
    [062110_121919528][][EXCEPTION] [DEBUG]  [path.separator]:[:]
    [062110_121919528][][EXCEPTION] [DEBUG]  [APPLCSF]:[/t01/demoap/inst/apps/DEMO_demo/logs/appl/conc]
    [062110_121919528][][EXCEPTION] [DEBUG]  [java.vm.name]:[Java HotSpot(TM) Server VM]
    [062110_121919528][][EXCEPTION] [DEBUG]  [file.encoding.pkg]:[sun.io]
    [062110_121919528][][EXCEPTION] [DEBUG]  [user.country]:[US]
    [062110_121919529][][EXCEPTION] [DEBUG]  [sun.os.patch.level]:[unknown]
    [062110_121919529][][EXCEPTION] [DEBUG]  [java.vm.specification.name]:[Java Virtual Machine Specification]
    [062110_121919529][][EXCEPTION] [DEBUG]  [user.dir]:[/t01/demoap/inst/apps/DEMO_demo/logs/appl/conc/log]
    [062110_121919529][][EXCEPTION] [DEBUG]  [java.runtime.version]:[1.5.0_08-b03]
    [062110_121919529][][EXCEPTION] [DEBUG]  [CLIENT_PROCESSID]:[30369]
    [062110_121919529][][EXCEPTION] [DEBUG]  [java.awt.graphicsenv]:[sun.awt.X11GraphicsEnvironment]
    [062110_121919529][][EXCEPTION] [DEBUG]  [java.endorsed.dirs]:[/t01/demoap/apps/tech_st/10.1.3/appsutil/jdk/jre/lib/endorsed]
    [062110_121919529][][EXCEPTION] [DEBUG]  [os.arch]:[i386]
    [062110_121919529][][EXCEPTION] [DEBUG]  [JTFDBCFILE]:[/t01/demoap/inst/apps/DEMO_demo/appl/fnd/12.0.0/secure/DEMO.dbc]
    [062110_121919529][][EXCEPTION] [DEBUG]  [java.io.tmpdir]:[/tmp]
    [062110_121919529][][EXCEPTION] [DEBUG]  [line.separator]:[
    [062110_121919529][][EXCEPTION] [DEBUG]  [java.vm.specification.vendor]:[Sun Microsystems Inc.]
    [062110_121919529][][EXCEPTION] [DEBUG]  [os.name]:[Linux]
    [062110_121919529][][EXCEPTION] [DEBUG]  [FND_JDBC_BUFFER_MIN]:[1]
    [062110_121919530][][EXCEPTION] [DEBUG]  [cpid]:[94508]
    [062110_121919530][][EXCEPTION] [DEBUG]  [sun.jnu.encoding]:[UTF-8]
    [062110_121919530][][EXCEPTION] [DEBUG]  [oracle.apps.fnd.common.Pool.leak.mode]:[stderr:off]
    [062110_121919530][][EXCEPTION] [DEBUG]  [java.library.path]:[/t01/demoap/apps/tech_st/10.1.3/appsutil/jdk/jre/lib/i386/server:/t01/demoap/apps/tech_st/10.1.3/appsutil/jdk/jre/lib/i386:/t01/demoap/apps/tech_st/10.1.3/appsutil/jdk/jre/../lib/i386:/t01/demoap/apps/tech_st/10.1.3/lib32:/t01/demoap/apps/tech_st/10.1.3/lib:/t01/demoap/apps/apps_st/appl/cz/12.0.0/bin:/t01/demoap/apps/apps_st/appl/iby/12.0.0/bin:/t01/demoap/apps/apps_st/appl/pon/12.0.0/bin:/t01/demoap/apps/apps_st/appl/sht/12.0.0/lib]
    [062110_121919530][][EXCEPTION] [DEBUG]  [java.specification.name]:[Java Platform API Specification]
    [062110_121919530][][EXCEPTION] [DEBUG]  [java.class.version]:[49.0]
    [062110_121919530][][EXCEPTION] [DEBUG]  [sun.management.compiler]:[HotSpot Server Compiler]
    [062110_121919530][][EXCEPTION] [DEBUG]  [queue_appl_id]:[0]
    [062110_121919530][][EXCEPTION] [DEBUG]  [os.version]:[2.6.18-164.11.1.el5xen]
    [062110_121919530][][EXCEPTION] [DEBUG]  [LONG_RUNNING_JVM]:[true]
    [062110_121919530][][EXCEPTION] [DEBUG]  [user.home]:[/t01/demoap]
    [062110_121919530][][EXCEPTION] [DEBUG]  [user.timezone]:[GMT+05:30]
    [062110_121919530][][EXCEPTION] [DEBUG]  [java.awt.printerjob]:[sun.print.PSPrinterJob]
    --------------------------------------------------------------------------------lots of lines ----------------------------------------
    [GC 17474K->10837K(24648K), 0.0037890 secs]
    [GC 17685K->11057K(24648K), 0.0035530 secs]
    [GC 17905K->11271K(24648K), 0.0029030 secs]
    [GC 18119K->11488K(24648K), 0.0024650 secs]
    [GC 18336K->11702K(24648K), 0.0023940 secs]
    [GC 18550K->11919K(24648K), 0.0025010 secs]
    [GC 18767K->12133K(24648K), 0.0024460 secs]
    [GC 18981K->12344K(24648K), 0.0024020 secs]
    [GC 19192K->12575K(24648K), 0.0024790 secs]
    [GC 19423K->12781K(24648K), 0.0025650 secs]
    [GC 19629K->12991K(24648K), 0.0024010 secs]
    [GC 19839K->13212K(24648K), 0.0024430 secs]
    [GC 20060K->13427K(24648K), 0.0024160 secs]
    [GC 20275K->13641K(24648K), 0.0024440 secs]
    [GC 20489K->13857K(24648K), 0.0024410 secs]
    [GC 20705K->14073K(24648K), 0.0024570 secs]
    [GC 20921K->14284K(24648K), 0.0024340 secs]
    [GC 21132K->14504K(24648K), 0.0024580 secs]
    [GC 21352K->14719K(24648K), 0.0024620 secs]
    [GC 21567K->14935K(24648K), 0.0024600 secs]
    [GC 21783K->15151K(24648K), 0.0024360 secs]
    [GC 21999K->15365K(24648K), 0.0024180 secs]
    [GC 22213K->15004K(24648K), 0.0204220 secs]rgrds
    Edited by: new2appsdba on Jun 22, 2010 1:43 AM
    Edited by: new2appsdba on Jun 22, 2010 2:12 AM
    Edited by: new2appsdba on Jun 22, 2010 5:37 AM

  • CONCURRENT MANAGER SETUP AND CONFIGURATION REQUIREMENTS IN AN 11I RAC ENVIR

    제품 : AOL
    작성날짜 : 2004-05-13
    PURPOSE
    RAC-PCP 구성에 대한 Setup 사항을 기술한 문서입니다.
    PCP 구현은 CM의 workload 분산, Failover등을 목적으로 합니다.
    Explanation
    Failure sceniro 는 다음 3가지로 구분해 볼수 있습니다.
    1. The database instance that supports the CP, Applications, and Middle-Tier
    processes such as Forms, or iAS can fail.
    2. The Database node server that supports the CP, Applications, and Middle-
    Tier processes such as Forms, or iAS can fail.
    3. The Applications/Middle-Tier server that supports the CP (and Applications)
    base can fail.
    아래부분은 CM,AP 구성과
    CM과 GSM(Global Service Management)과의 관계를 설명하고 있습니다.
    The concurrent processing tier can reside on either the Applications, Middle-
    Tier, or Database Tier nodes. In a single tier configuration, non PCP
    environment, a node failure will impact Concurrent Processing operations do to
    any of these failure conditions. In a multi-node configuration the impact of
    any these types of failures will be dependent upon what type of failure is
    experienced, and how concurrent processing is distributed among the nodes in
    the configuration. Parallel Concurrent Processing provides seamless failover
    for a Concurrent Processing environment in the event that any of these types of
    failures takes place.
    In an Applications environment where the database tier utilizes Listener (
    server) load balancing is implemented, and in a non-load balanced environment,
    there are changes that must be made to the default configuration generated by
    Autoconfig so that CP initialization, processing, and PCP functionality are
    initiated properly on their respective/assigned nodes. These changes are
    described in the next section - Concurrent Manager Setup and Configuration
    Requirements in an 11i RAC Environment.
    The current Concurrent Processing architecture with Global Service Management
    consists of the following processes and communication model, where each process
    is responsible for performing a specific set of routines and communicating with
    parent and dependent processes.
    아래 내용은 PCP환경에서 ICM, FNDSM, IM, Standard Manager의 역활을 설명하고
    있습니다.
    Internal Concurrent Manager (FNDLIBR process) - Communicates with the Service
    Manager.
    The Internal Concurrent Manager (ICM) starts, sets the number of active
    processes, monitors, and terminates all other concurrent processes through
    requests made to the Service Manager, including restarting any failed processes.
    The ICM also starts and stops, and restarts the Service Manager for each node.
    The ICM will perform process migration during an instance or node failure.
    The ICM will be
    active on a single node. This is also true in a PCP environment, where the ICM
    will be active on at least one node at all times.
    Service Manager (FNDSM process) - Communicates with the Internal Concurrent
    Manager, Concurrent Manager, and non-Manager Service processes.
    The Service Manager (SM) spawns, and terminates manager and service processes (
    these could be Forms, or Apache Listeners, Metrics or Reports Server, and any
    other process controlled through Generic Service Management). When the ICM
    terminates the SM that
    resides on the same node with the ICM will also terminate. The SM is ?hained?
    to the ICM. The SM will only reinitialize after termination when there is a
    function it needs to perform (start, or stop a process), so there may be
    periods of time when the SM is not active, and this would be normal. All
    processes initialized by the SM
    inherit the same environment as the SM. The SM environment is set by APPSORA.
    env file, and the gsmstart.sh script. The TWO_TASK used by the SM to connect
    to a RAC instance must match the instance_name from GV$INSTANCE. The apps_<sid>
    listener must be active on each CP node to support the SM connection to the
    local instance. There
    should be a Service Manager active on each node where a Concurrent or non-
    Manager service process will reside.
    Internal Monitor (FNDIMON process) - Communicates with the Internal Concurrent
    Manager.
    The Internal Monitor (IM) monitors the Internal Concurrent Manager, and
    restarts any failed ICM on the local node. During a node failure in a PCP
    environment the IM will restart the ICM on a surviving node (multiple ICM's may
    be started on multiple nodes, but only the first ICM started will eventually
    remain active, all others will gracefully terminate). There should be an
    Internal Monitor defined on each node
    where the ICM may migrate.
    Standard Manager (FNDLIBR process) - Communicates with the Service Manager and
    any client application process.
    The Standard Manager is a worker process, that initiates, and executes client
    requests on behalf of Applications batch, and OLTP clients.
    Transaction Manager - Communicates with the Service Manager, and any user
    process initiated on behalf of a Forms, or Standard Manager request. See Note:
    240818.1 regarding Transaction Manager communication and setup requirements for
    RAC.
    Concurrent Manager Setup and Configuration Requirements in an 11i RAC
    Environment
    PCP를 사용하기위한 기본적인 Setup 절차를 설명하고 있습니다.
    In order to set up Setup Parallel Concurrent Processing Using AutoConfig with
    GSM,
    follow the instructions in the 11.5.8 Oracle Applications System Administrators
    Guide
    under Implementing Parallel Concurrent Processing using the following steps:
    1. Applications 11.5.8 and higher is configured to use GSM. Verify the
    configuration on each node (see WebIV Note:165041.1).
    2. On each cluster node edit the Applications Context file (<SID>.xml), that
    resides in APPL_TOP/admin, to set the variable <APPLDCP oa_var="s_appldcp">
    ON </APPLDCP>. It is normally set to OFF. This change should be performed
    using the Context Editor.
    3. Prior to regenerating the configuration, copy the existing tnsnames.ora,
    listener.ora and sqlnet.ora files, where they exist, under the 8.0.6 and iAS
    ORACLE_HOME locations on the each node to preserve the files (i.e./<some_
    directory>/<SID>ora/$ORACLE_HOME/network/admin/<SID>/tnsnames.ora). If any of
    the Applications startup scripts that reside in COMMON_TOP/admin/scripts/<SID>
    have been modified also copy these to preserve the files.
    4. Regenerate the configuration by running adautocfg.sh on each cluster node as
    outlined in Note:165195.1.
    5. After regenerating the configuration merge any changes back into the
    tnsnames.ora, listener.ora and sqlnet.ora files in the network directories,
    and the startup scripts in the COMMON_TOP/admin/scripts/<SID> directory.
    Each nodes tnsnames.ora file must contain the aliases that exist on all
    other nodes in the cluster. When merging tnsnames.ora files ensure that each
    node contains all other nodes tnsnames.ora entries. This includes tns
    entries for any Applications tier nodes where a concurrent request could be
    initiated, or request output to be viewed.
    6. In the tnsnames.ora file of each Concurrent Processing node ensure that
    there is an alias that matches the instance name from GV$INSTANCE of each
    Oracle instance on each RAC node in the cluster. This is required in order
    for the SM to establish connectivity to the local node during startup. The
    entry for the local node will be the entry that is used for the TWO_TASK in
    APPSORA.env (also in the APPS<SID>_<HOSTNAME>.env file referenced in the
    Applications Listener [APPS_<SID>] listener.ora file entry "envs='MYAPPSORA=<
    some directory>/APPS<SID>_<HOSTNAME>.env)
    on each node in the cluster (this is modified in step 12).
    7. Verify that the FNDSM_<SID> entry has been added to the listener.ora file
    under the 8.0.6 ORACLE_HOME/network/admin/<SID> directory. See WebiV Note:
    165041.1 for instructions regarding configuring this entry. NOTE: With the
    implementation of GSM the 8.0.6 Applications, and 9.2.0 Database listeners
    must be active on all PCP nodes in the cluster during normal operations.
    8. AutoConfig will update the database profiles and reset them for the node
    from which it was last run. If necessary reset the database profiles back to
    their original settings.
    9. Ensure that the Applications Listener is active on each node in the cluster
    where Concurrent, or Service processes will execute. On each node start the
    database and Forms Server processes as required by the configuration that
    has been implemented.
    10. Navigate to Install > Nodes and ensure that each node is registered. Use
    the node name as it appears when executing a nodename?from the Unix prompt on
    the server. GSM will add the appropriate services for each node at startup.
    11. Navigate to Concurrent > Manager > Define, and set up the primary and
    secondary node names for all the concurrent managers according to the
    desired configuration for each node workload. The Internal Concurrent
    Manager should be defined on the primary PCP node only. When defining the
    Internal Monitor for the secondary (target) node(s), make the primary node (
    local node) assignment, and assign a secondary node designation to the
    Internal Monitor, also assign a standard work shift with one process.
    12. Prior to starting the Manager processes it is necessary to edit the APPSORA.
    env file on each node in order to specify a TWO_TASK entry that contains
    the INSTANCE_NAME parameter for the local nodes Oracle instance, in order
    to bind each Manager to the local instance. This should be done regardless
    of whether Listener load balancing is configured, as it will ensure the
    configuration conforms to the required standards of having the TWO_TASK set
    to the instance name of each node as specified in GV$INSTANCE. Start the
    Concurrent Processes on their primary node(s). This is the environment
    that the Service Manager passes on to each process that it initializes on
    behalf of the Internal Concurrent Manager. Also make the same update to
    the file referenced by the Applications Listener APPS_<SID> in the
    listener.ora entry "envs='MYAPPSORA= <some directory>/APPS<SID>_<HOSTNAME>.
    env" on each node.
    13. Navigate to Concurrent > Manager > Administer and verify that the Service
    Manager and Internal Monitor are activated on the secondary node, and any
    other addititional nodes in the cluster. The Internal Monitor should not be
    active on the primary cluster node.
    14. Stop and restart the Concurrent Manager processes on their primary node(s),
    and verify that the managers are starting on their appropriate nodes. On
    the target (secondary) node in addition to any defined managers you will
    see an FNDSM process (the Service Manager), along with the FNDIMON process (
    Internal Monitor).
    Reference Documents
    Note 241370.1

    What is your database version? OS?
    We are using VCP suite for Planning Purpose. We are using VCP environment (12.1.3) in Decentralized structure connecting to 3 differect source environment ( consisting 11i and R12). As per the Oracle Note {RAC Configuration Setup For Running MRP Planning, APS Planning, and Data Collection Processes [ID 279156]} we have implemented RAC in our test environment to get better performance.
    But after doing all the setups and concurrent programs assignment to different nodes, we are seeing huge performance issue. The Complete Collection which takes generally on an avg 180 mins in Production, is taking more than 6 hours to complete in RAC.
    So I would like to get suggestion from this forum, if anyone has implemented RAC in pure VCP (decentralized) environment ? Will there be any improvement if we make our VCP Instance in RAC ?Do you PCP enabled? Can you reproduce the issue when you stop the CM?
    Have you reviewed these docs?
    Value Chain Planning - VCP - Implementation Notes & White Papers [ID 280052.1]
    Concurrent Processing - How To Ensure Load Balancing Of Concurrent Manager Processes In PCP-RAC Configuration [ID 762024.1]
    How to Setup and Run Data Collections [ID 145419.1]
    12.x - Latest Patches and Installation Requirements for Value Chain Planning (aka APS Advanced Planning & Scheduling) [ID 746824.1]
    APSCHECK.sql Provides Information Needed for Diagnosing VCP and GOP Applications Issues [ID 246150.1]
    Thanks,
    Hussein

  • Internal Concurrent Manager deactivated.

    Hi
    Iam working on setting up R12 instances on Amazon Cloud Virtual machines.
    After running post clone steps when I check the concurrent managers - manage screen I see old node name. How to update this with the new node name.
    Also after changing the node name the internal concurrent manager is in deactivated state, How to get this activated.
    Pls let me know how to resolve the issue.
    Sree

    After running post clone steps when I check the concurrent managers - manage screen I see old node name. How to update this with the new node name. You can update TARGET_NODE column in FND_CONCURRENT_QUEUES table from the backend.
    Also after changing the node name the internal concurrent manager is in deactivated state, How to get this activated. From the application (as mentioned above by Taher) or stop/start the CM using adcmclt.sh script.
    Thanks,
    Hussein

  • Concurrent Manager not starting after cloning

    Hi,
    I am not able to start concurrent manager after cloning the CM tier. I am gettiing below error in the manager log file,
    Could not initialize the Service Manager FNDSM_<Node name>_<Env>. Verify that <Node Name> has been registered for concurrent processing.
    Routine AFPEIM encountered an error while starting concurrent manager RCVOLTM with library /u01/app/hl.../...appl/po/11.5.0/bin/RCVOLTM.
    What might be cause of the error?
    Thanks,
    Prasad

    Hi Prasad,
    Using normal hostsnames or virtual hostsnames? Also did you experience issues during the dbTier clone (check all log files created even if the cloning did not error out)
    Possible the hostsnames in FND_NODES are not cleared properly during the DB clone
    Running the following might give a better result:
    1 - SQL> EXEC FND_CONC_CLONE.SETUP_CLEAN;
    COMMIT;
    EXIT;
    2 - Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers,
    3 - check if the concurrent managers are starting.
    Regards,
    Ronald

  • Concurrent manager problem on Cloud

    Hi
    I did the clone on cloud machine.
    Iam getting issues with concurrent manager.Below is the error in the log file.
    establish_icm - Unable to insert ICM record
    Call to establish_icm failed
    The Internal Concurrent Manager has encountered an error.
    Review concurrent manager log file for more detailed information. : 07-MAY-2011 03:29:04 -
    Shutting down Internal Concurrent Manager : 07-MAY-2011 03:29:04
    List of errors encountered:
    _ 1 _
    Routine AFPCSQ encountered an ORACLE error. .
    Review your error messages for the cause of the error. (=<POINTER>)
    APP-FND-01564: ORACLE error 12899 in insert_icm_record
    Cause: insert_icm_record failed due to ORA-12899: value too large for column "APPLSYS"."FND_CONCURRENT_PROCESSES"."NODE_NAME" (actual: 31, maximum: 30).
    The SQL statement being executed at the time of the error was: INSERT INTO FND_CONCURRENT_PROCESSES (CONCURRENT_PROCESS_ID, LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, ORACLE_PROCESS_ID, QUEUE_APPLICATION_ID, CONCURRENT_QUEUE_ID, OS_PROCESS_ID, SESSION_ID, PROCESS_START_DATE, PROCESS_STATUS_CODE, MANAGER_TYPE, NODE_NAME, DB_NAME, DB_DOMAIN, SQLNET_STRING, DB_INSTANCE, Instance_Number) VALUES (:cpid, SYSDATE, SYSDATE, :mgrusrid, :mgrusrid2, :opid, :qappid, :qid, :ospid, :osid, SYSDATE, 'A', 0, :node, :dbname, :dbdomain, :dbinst, (Select instance_name from v$instance), (Select instance_number from v$instance)) and was executed from the file &ERRFILE.
    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.
    sh: line 63: mail: command not found
    The DEMO_0507@DEMO internal concurrent manager has terminated with status 1 - giving up.
    [root@domU-12-q1-39-1A-05-F3 log]# hostname
    domU-12-3q-39-1A-05-F3.compute-1.internal
    SQL> select node_name from fnd_nodes;
    NODE_NAME
    AUTHENTICATION
    RDCORACLEAPP
    RDCORACLEDB
    Where does this get the hostname or node name from.
    Pls help.
    Sree

    Where does this get the hostname or node name from.From the hosts file and from the source instance that you have cloned from -- Concurrent Managers Fail To Start After New Install of Release 12 [ID 413164.1]
    Please purge FND_NODES table as per (Concurrent Processing - Steps To Clean Nonexistent Nodes or IP Addresses From FND_NODES [ID 260887.1]) and after correcting all the entries in the hosts file, and check then (make sure you run AutoConfig on the database/application tier nodes).
    Thanks,
    Hussein

  • 11.5.10.2 Windows XP installation - Concurrent Manager not working

    I have completed the 11.5.10.2 installation on windows XP without any issues. However, concurrent manager even though it starts but when I submit any request, "no active manager" displays in the requests window.
    I tried if anyone had issues in this forum and found that I need to run autoconfig but that has not helped.
    The following steps are being already tried but with no luck:
    1. Stopped all application tier services (apache, fulfillment, forms etc)
    2. Ran \oracle\viscomn\admin\scripts\<VIS_Server>\adautocfg.cmd - it completed successfully
    3. One of the threads in this forum said "OracleVISOra806_2TNSListener80APPS_VIS" must be running in order for CM to work - it was not running and attempted to start but could not.
    Here is the log file info for "OracleVISOra806_2TNSListener80APPS_VIS" service:
    System parameter file is E:\oracle\visdb\9.2.0\network\admin\<VIS_Server>\listener.ora
    Log messages written to E:\oracle\visora\8.0.6\NET80\log\apps_vis.log
    TNS-01151: Missing listener name, APPS_VIS, in LISTENER.ORA
    Thanks in advance..

    As I ran autoconfig, it has set the service to start automatically...this is the service name I'm referring to: OracleVISOra806_2TNSListener80APPS_VIS
    8.0.6 listner.ora
    APPS_VIS =
    (ADDRESS_LIST =
    (ADDRESS= (PROTOCOL= TCP)(Host= pravdhir)(Port= 1626))
    SID_LIST_APPS_VIS =
    (SID_LIST =
    ( SID_DESC = ( SID_NAME = FNDSM )
    ( ORACLE_HOME = E:\oracle\visora\8.0.6 )
    ( PROGRAM = E:\oracle\visappl\fnd\11.5.0\bin\fndsm.exe )
    ( ARGV0 = FNDSM_VIS_pravdhir )
    ( envs='MYAPPSORA=E:\oracle\visappl\APPSVIS_pravdhir.cmd,FNDSM_SCRIPT=E:\oracle\viscomn\admin\scripts\VIS_pravdhir\gsmstart.cmd' )
    ( SID_DESC = ( SID_NAME = FNDFS )
    ( ORACLE_HOME = E:\oracle\visora\8.0.6 )
    ( PROGRAM = E:\oracle\visappl\fnd\11.5.0\bin\fndfs.exe )
    ( ARGV0 = VIS_pravdhir )
    ( envs='EPC_DISABLED=TRUE,NLS_LANG=American_America.UTF8,APPLFSTT=VIS_BALANCE;VIS;VIS_806_BALANCE;VIS_FO,APPLFSWD=E:\oracle\visappl\admin;E:\oracle\viscomn\temp;E:\oracle\viscomn\html\oam\nonUix\launchMode\restricted')
    STARTUP_WAIT_TIME_APPS_VIS = 0
    CONNECT_TIMEOUT_APPS_VIS = 10
    TRACE_LEVEL_APPS_VIS = OFF
    LOG_DIRECTORY_APPS_VIS = E:\oracle\visora\8.0.6\net80\admin
    LOG_FILE_APPS_VIS = APPS_VIS
    TRACE_DIRECTORY_APPS_VIS = E:\oracle\visora\8.0.6\net80\admin
    TRACE_FILE_APPS_VIS = APPS_VIS
    IFILE = E:\oracle\visora\8.0.6\network\admin\VIS_pravdhir\VIS_pravdhir_listener_ifile.ora
    9.2.0 Listner.ora
    VIS =
    (ADDRESS_LIST =
    (ADDRESS= (PROTOCOL= IPC)(KEY= EXTPROCVIS))
    (ADDRESS= (PROTOCOL= TCP)(Host= pravdhir.dp.com )(Port= 1521))
    SID_LIST_VIS =
    (SID_LIST =
    (SID_DESC =
    (ORACLE_HOME= E:\oracle\visdb\9.2.0)
    (SID_NAME = VIS)
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = E:\oracle\visdb\9.2.0)
    (PROGRAM = extproc)
    STARTUP_WAIT_TIME_VIS = 0
    CONNECT_TIMEOUT_VIS = 10
    TRACE_LEVEL_VIS = OFF
    LOG_DIRECTORY_VIS = E:\oracle\visdb\9.2.0/network/admin
    LOG_FILE_VIS = VIS
    TRACE_DIRECTORY_VIS = E:\oracle\visdb\9.2.0/network/admin
    TRACE_FILE_VIS = VIS
    ADMIN_RESTRICTIONS_VIS = OFF
    IFILE=E:\oracle\visdb\9.2.0\network\admin\VIS_pravdhir\listener_ifile.ora
    As the system parameter is set to 9.2.0 directory and it is trying to find APPS_VIS entry which is not found in 9.2.0 Listner.ora file and hence erroring out.
    I tried the following:
    1. I copied the contents from 8.0.6 listner.ora file and added into 9.2.0 listner.ora file.
    2. Rebooted
    3. OracleVISOra806_2TNSListener80APPS_VIS > service started successfully
    4. Started 9.2.0 listner service (OracleVIS_db920_RDBMSTNSListenerVIS) and Oracle Service manually
    5. I ran autoconfig
    6. I started all the application services manually
    It worked but I don;t know where else the application will fail. So far so good. But is this the right procedure?
    one more question? Do I need to run autoconfig after every reboot?

  • Request set not getting picked up by concurrent manager.

    Hi All
    We have an issue today where the daily scheduled request set did not run and status for which remained at "Pending Scheduled". Concurrent Manager did not pick up this and status remained:
    This request is waiting to be processed by the Conflict Resolution Manager.
    This request cannot yet begin execution because other requests may conflict with it. The Conflict Resolution Manager will determine when this request may begin execution.
    User <user_ name> submitted this request on 06-MAR-2011 23:17:33.
    No action required. This is a normal condition.
    This request may have to wait on one or more of the following requests to complete before it can begin execution:
    I checked all the 'incompatibilities" of the programs for request set and none of them were running.
    We did the below, but no success:
    1. Restarted the concurret manager
    2. Cancelled the scheduled run and submitted request set again.
    Still the status remained at "Pending Scheduled" with above message.
    When we tried to run the individaul programs for that request set it all worked fine. So I would like to know what could be the issue and how to overcome this. I think the issue could be with request set as the individual program is working fine.
    Any pointers will be highly appriciated.
    Many Thanks,
    -Shashank

    which manager is Processing that request.. if it is Custom manager Then U should excllude this concurrent program from the concurrent manager.
    otherwise both the Standard manager or custom manager both are not going to pickup the process..
    he
    Please Check The Cocnurrent Manager which is going to process and check wether its included in the respective manager.
    Thanks
    Reddy
    http://11iapps.wordpress.com

Maybe you are looking for