RE: Concurrent Manager Issue

That should be ok. Only the managers that are actually needed should have 
the node information there. We have tons of managers without node info 
since they are not started, since we don't use that functionality/module. 
So we don't need them. Should be the same for you then.

So I would suggest you just try the 4 steps I gave you at the beginning:

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



Helmut Daiminger
Ritchie Bros. Auctioneers
Phone: (604) 304-5039
Cell: (604) 377-8686
Fax: (604) 304-5031
mailto: hdaiminger@xxxxxxxxxxxxx
http://www.rbauction.com




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


To
<ora-apps-dba@xxxxxxxxxxxxx>
cc

Subject
RE: Concurrent Manager Issue






Hi Helmut,
 
Thanks for your interest in my issue?
 
I tried to check this only few managers have the node and platform 
information.But for the reset the tab is blank.
 
How should I do the setting? After going Install-Node what should I do.
 
Could you please help me in that.
 
Thanks in advance.
 
Mamta
 

From: ora-apps-dba-bounce@xxxxxxxxxxxxx 
[mailto:ora-apps-dba-bounce@xxxxxxxxxxxxx] On Behalf Of 
HDaiminger@xxxxxxxxxxxxx
Sent: Monday, 5 January 2009 14:22
To: ora-apps-dba@xxxxxxxxxxxxx
Subject: 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: