Concurrent Manager requires physical hostname to start??

Hi,
We are planning to setup HP Service Guard Clustering for our Oracle R12.0.6 instance.
After going thourgh HP documentation(http://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA1-2863ENW&cc=us&lc=en)
, i understood that Serviceguard uses virtual hostname concept for failover.
The HP document suggests to use PCP, which is a complex setup for us as per our existing envirtonment.
But Oracle says CM requires physical hostname to start.
CM will not failover with virtual hostname according to oracle.
Could anybody kindly explain why CM need physical hostname?
how can i use Note: 734506.1 - Virtual Hostnames For Concurrent Managers with the above HP document to setup a succesfull HA E-Business Suite R12.
Please suggest me for better.
Thanks.

Hi user;
Please check
How To Configure Autoconfig For Hp Service Guard [ID 790123.1]
Implementing Virtual Host, Concurrent Managers and EM DBconsole on Oracle Applications R12 [ID 603883.1]
Also see:
http://oracleappstechnology.blogspot.com/2009/06/concurrent-managers-require-physical.html
Hope it helps
Regard
Helios

Similar Messages

  • Concurrent manager problem i.e not starting

    Hai everyone ,
    while iam running the concurrent program iam getting the following problem...
    1>No concurrent manager is defined to process this request, so it cannot be processed.
    I have been facing this problem from 1 week,even i have tried to shut down the conurrent manager and up the manager but unable to slove the problem.pls can anyone help me to get rid of the problem and iam unable run the cmclean.sql script file.can anyone tell where to run it..waiting for reply...
    Thanks
    srinivas

    Srini,
    Is this custom concurrent program ?
    If this is standard Oracle Request could you share name of request so that I can check to which manager its assigned to so that you can check if that manager is Up or not .
    Looking at your message it seems this is custom request which is not assigned to any manager & by default it should have been picked up by Standard Manager but their might be some incompatibilities
    Atul
    http://teachmeoracle.com/forum

  • Concurrent Manager not starting

    Platform: "Windows 2003 R2 32-bit"
    EBS: "11.5.10.2"
    Database: "10.2.0.4"
    Just applied patch 6241631 and then successfully completed autoconfig on both database and application. When trying to start the application services concurrent manager service is not being started and giving error:
    ECHO is off.
    ECHO is off.
    Thu 08/18/2011 09:53 AM
    ECHO is off.
    ECHO is off.
    Thu 08/18/2011 09:53 AM
    ECHO is off.
    ECHO is off.
    Setting environment for using Microsoft Visual C++ tools.
    APPSORA.cmd exiting with status 0
    Starting concurrent manager for PROD ...
    The OracleConcMgrPROD_apps11i service is starting.
    adcmctl.cmd exiting with status 2
    .end std out.
    The OracleConcMgrPROD_apps11i service could not be started.
    A system error has occurred.
    System error 1067 has occurred.
    The process terminated unexpectedly.
    .end err out.
    The patch completed succesfully but I am wondering why its is behaving abnormally. I have run cmclean.sql and even rebooted the machine but in vain.
    Please guide me to get rid out of this.
    In the "08180953.log" at the end I see the following report:
    [Service Control Execution Report]
    The report format is:
    <Service> <Script> <Status>
    Oracle Apache Server PROD_apps11i adapcctl.cmd Started
    OraclePRODOra806_2TNSListener80APPS_PROD adalnctl.cmd Started
    OracleConcMgrPROD_apps11i adcmctl.cmd Started
    OracleFormsServer-Forms60PROD_apps11i adfrmctl.cmd Started
    OracleReportServer-Rep60_PROD adrepctl.cmd Started
    Oracle Metrics Client PROD_apps11i adfmcctl.cmd Started
    Oracle Metrics Server PROD_apps11i adfmsctl.cmd Started
    Oracle Fulfillment Server PROD_apps11i jtffmctl.cmd Already Started
    Oracle Restricted Apache Server PROD_apps11i adaprstctl.cmd Disabled
    Oracle Apache Server PROD_apps11i for PL/SQL adapcctl.cmd Disabled
    Oracle TCF SocketServer PROD_apps11i adtcfctl.cmd Disabled
    Oracle ICSM PROD_apps11i ieoicsm.cmd Disabled
    Oracle iProcurement Bulk Loader PROD_apps11i icxblkctl.cmd Disabled
    Oracle MWA Service PROD_apps11i mwactlwrpr.cmd Disabled
    ServiceControl is exiting with status 0
    Edited by: user12194837 on Aug 17, 2011 10:19 PM

    The OracleConcMgrPROD_apps11i service is starting.
    adcmctl.cmd exiting with status 2
    .end std out.Please check the CM log file for details about the error.
    The OracleConcMgrPROD_apps11i service could not be started.
    A system error has occurred.
    System error 1067 has occurred.
    The process terminated unexpectedly.Please check the Event Viewer for details about the error.
    Thanks,
    Hussein

  • Concurrent Manager Not Started after RUP7

    Hi All,
    After applying patch (6241631) 11.ATG_RUP7 concurrent manager showing status as not started in OAM.
    The patch Installation completed succesfully with no issues.
    All the concurrent managers are running and all application is running fine. Only the issue is with OAM
    Thanks in advance for any inputs.

    Hi,
    Note: 858801.1 - Known Issues On Top of 11i.ATG_PF.H.delta.7 (RUP7) - 6241631Doesn't contains any Information.Save this document for future reference as I expect bugs and.issues to be reported later.
    I will try to regenerate all JAR files with force option. For this do we need to bounce web server?Yes.
    Regards,
    Hussein

  • Internal concurrent manager is 0

    After completion of cloning, internal manager is 0.,but other managers are 1and 1.,can anyone help me?

    vaaru wrote:
    After completion of cloning, internal manager is 0.,but other managers are 1and 1.,can anyone help me?Please do the following:
    - Stop the CM
    - Purge FND_NODES table then run AutoConfig on all tier nodes -- How to get a clean Autoconfig Environment ? [ID 391406.1]
    - Run cmclean.sql script -- Concurrent Processing - CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables [ID 134007.1]
    - Start the CM
    If you still have the same issue, please check the contents of the CM log file.
    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]

  • 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

  • Adobe Application Manager, required to start your trial, is missing or damaged

    I have just bought Adobe CC years membership, i have downloaded CC application manager, i have also downloaded InDesign.... when i click to open the application manager it says that the application manager required to start the trial is missing or damaged? one its not a trial and two how can i fix it? I had re installed creative cloud as that is the application manager but still no luck? any ideas guys ...... PLEASE HELP!!

    did you download application manager from that link?
    if yes, did you install application manager after downloading?

  • Concurrent Manager service cant be started

    Good day
    -I installed Apps 11i 11.5.0 on my PC for learning purpose , My OS is (Win XP SP2) .
    -The Concurrent Manager service in windows cant be started although it was fine directly after installation ( i tried to submit request for one report and it worked ) .
    -If i start the service manually it returns the error :
    Error 1065 : the database specified is dose not exist .
    -In the event viewer i find two errors :
    Cannot connect to database (APPS/_‚ ?ٹ„‚•ٹگڈ”@VIS). ORA-error:1033.
    OR
    Cannot connect to database (APPS/_‚ ?ٹ„‚•ٹگڈ”@VIS). ORA-error:1017.
    -I didn’t change any database password .
    -I can log on to the application using (operation/welcome) .
    Any idea …
    Thanx in advance .
    Edited by: Hassan Abazid on Jan 21, 2009 6:45 AM

    Source the application env file (envshell.cmd) under %APPL_TOP%, and run the following script to remove the existing Concurrent Manager Service:
    adsvcm.cmd -deinstallTo create a new Concurrent Manager Service:
    adsvcm.cmd apps <appspassword>Oracle® Applications Maintenance Procedures
    http://download.oracle.com/docs/cd/B11454_01/11.5.9/acrobat/11iadproc.pdf

  • Oracle Fulfillment server does not start and also my concurrent manager is

    The oracle Fulfillment server does not start and also my concurrent manager is down, when ever iam trying to start them i getting error.
    even i restarted my laptop many times
    Iam using WINXP on my laptop.
    Pls help someone
    hsawwan
    Posts: 11,859
    Registered: 03/13/06
    Re: oracle Fulfillment server and concurrent manager problem
    Posted: Oct 13, 2008 9:26 AM in response to: user578071 Reply
    What is the error?
    What does CM log file say?
    Please run cmclean.sql and try to start the CM then.
    Note: 134007.1 - CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables
    https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=134007.1
    where should i run in apps schema or some other schema, where can i find the log
    as iam using r12

    Duplicate thread ..
    oracle Fulfillment server and concurrent manager problem
    Re: oracle Fulfillment server and concurrent manager problem

  • Concurrent Manager start/stop EBS R12

    Hi all,
    I am starting all the processes/services in my EBS R12 as APPLMGR user,
    using the shell script:
    $ adstrtal.sh apps/apps
    and to stop it with:
    $ adstpall.sh apps/apps
    But when I run the stop script, I still see the Concurrent Manager process active
    (ps -ef|grep FNDLIBR).
    Does adstpall.sh do not contain the script to stop CM?
    Thanks a lot

    I just get paranoid when it keeps emailing the APPLMGR user that the CM died -giving up What is the message you get? If it says "successfully" then you can ignore the message.

  • 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 not starting automatically with adstrtal.sh apps/apps

    I am facing an issue with ICM, its not starting automatically when I start the application with help of
    /d01/oracle/viscomn/admin/scripts/VIS_oracleapps/adstrtal.sh apps/apps
    But, I am able to start it manually with adcmctl.sh start apps/apps - any clue why its not starting automatically?
    Pls let me know if any suggestions to troubleshoot...
    CM log file snip -
    Shutting down Internal Concurrent Manager : 26-JUN-2008 11:06:13
    List of errors encountered:
    _ 1 _
    Routine AFPCMT encountered an ORACLE error. ORA-01012: not logged on
    Review your error messages for the cause of the error. (=<POINTER>)
    _ 2 _
    Routine AFPCSQ encountered an ORACLE error. ORA-01017: invalid
    username/password; logon denied
    Review your error messages for the cause of the error. (=<POINTER>)
    The VIS_0626@VIS internal concurrent manager has terminated with status 1 - giving up.
    Thanks,
    Ambi

    This issue has been fixed, it was due to (apps) password was misspelt in the script calling the adstrtal.sh script.

  • CS6 not starting says "Adobe Application Manager Required" but I already have it AND I reinstalled.

    CS6 not starting says "Adobe Application Manager Required" but I already have it AND I reinstalled. All I know is that I have CS5 on my computer and it's not a permission error. Please help

    We are not ignoring you...we are checking into it! Sorry for the delay.
    Pattie

  • Concurrent Manager not starting after patching/ cloning

    Hi,
    We have an issue where after cloning and/or patching an environment the concurrent manager doesn't start. Our steps to resolve this problem have thus far been as follows:
    1. Apply 3830807
    2. Run autoconfig
    3. Run cmclean.sql on environment
    4. Check the libc* files in 8.0.6 ORACLE_HOME/lib/stubs
    We had an instance after a patch was applied where the conc mgr did not start and we applied all of the above, in that order. No success. We then decided to apply the 3830807 patch again and run autoconfig- basically re- run steps 1 and 2. Success. In another instance, running the cmclean.sql resolved the error. In some instances, simply shutting down the application and DB and restarting will be enough.
    Our problem is that the resolution to this error always seems random. What may work in one instance almost never works in another. Additionally, the problem has started since we've applied ATG RUP 6 to our LIVE environment and our clones. Coincidence?
    We have logged an SR but I feel like we're being spun in circles- I'm not getting a direct answer or resolution path from them.
    If someone could provide some guidance on a proper resolution path for this conc mgr issue I would very much appreciate it.
    Thanks,
    Lia.

    Basically the approach we're now taking (and that's working) is that after applying a patch, or set of patches, we apply patch 3830807 and then run autoconfig on the db and apps tier. We then shut down the application (if not already down) and the database and then bring everything back up.
    Thanks to all for their assistance.
    Lia.

Maybe you are looking for