RE: Concurrent Manager Issue

Hello Mamta,

are your managers showing the correct node names when checking? Log into 
Apps as system administrator, then go to Concurrent - Manager - Define




My machine name in this example is ro04la04. So each manager has to show 
correct machine name. Just double-check. This is one of the steps we are 
doing manually after each clone.



Cheers,
Helmut








"NEELI-SC, Mamta" <Mamta.NEELI@xxxxxxxxxxxxxx> 
Sent by: ora-apps-dba-bounce@xxxxxxxxxxxxx
01/04/2009 09:15 PM
Please respond to
ora-apps-dba@xxxxxxxxxxxxx


To
<ora-apps-dba@xxxxxxxxxxxxx>
cc

Subject
RE: Concurrent Manager Issue






Helmut thanks for your prompt response.
 
I?m beginner to this field could you please tell me what do you mean by CM 
definition are ok?
 
 
 

From: ora-apps-dba-bounce@xxxxxxxxxxxxx 
[mailto:ora-apps-dba-bounce@xxxxxxxxxxxxx] On Behalf Of 
HDaiminger@xxxxxxxxxxxxx
Sent: Monday, 5 January 2009 12:33
To: ora-apps-dba@xxxxxxxxxxxxx
Subject: Re: Concurrent Manager Issue
 

Hi Mamta, 

I assume the CM definitions are ok. Then try this: 

1) Run db autoconfig 
2) as APPS (in SQL*Plus): EXEC FND_CONC_CLONE.SETUP_CLEAN; 
3) Run apps autocfg 
       4) restart apps, CM will start up

Regards, 
Helmut



"NEELI-SC, Mamta" <Mamta.NEELI@xxxxxxxxxxxxxx> 
Sent by: ora-apps-dba-bounce@xxxxxxxxxxxxx 
01/04/2009 08:25 PM 


Please respond to
ora-apps-dba@xxxxxxxxxxxxx



To
<ora-apps-dba@xxxxxxxxxxxxx> 
cc
 
Subject
Concurrent Manager Issue
 


 
 




Hi DBA?s 
  
My internal concurrent manger is starting but all the other managers are 
not starting.they are showing target processes but no actual processes. 
The log file is as follows 


Check that your system has enough resources to start a concurrent manager 
process. 
  
Any one please help me in resolving this issue. 
  
Regards 
Mamta

GIF image

GIF image

Other related posts: