delete a agent which is in discovering state

Everything about Control-M agents installation or setup.
Post Reply
User avatar
archu
Nouveau
Nouveau
Posts: 18
Joined: 27 Apr 2009 12:00

delete a agent which is in discovering state

Post by archu » 17 Nov 2009 11:54

Hi ,

How to delete a agent which is in discovering status:

I have tried to delete in configuration Manager as wellas in Controlm Server. But still no success.

After Deleting the agent it went to Discovering status.
From then i am not able to delete it.

Please help me in this regard.


Regards

User avatar
markf
Nouveau
Nouveau
Posts: 134
Joined: 13 Jul 2006 12:00
Location: Switzerland
Contact:

Post by markf » 17 Nov 2009 12:01

Depends on the version of Control-M Server that you are using ...

User avatar
rahulsehgal
Nouveau
Nouveau
Posts: 148
Joined: 19 Mar 2009 12:00
Location: Delhi
Contact:

Post by rahulsehgal » 17 Nov 2009 12:03

Hi Archu,

To remove the bad configuration agents, it’s best to shutdown Control-M during this process. In the ~/ctm/data/AGSTAT and ~/ctm/data/AGPRM directories remove all the corresponding bad agents.

To find the jobs that are setup to run on a “bad” agent, run the following from the Control-M database (example=sybase)

select JOBNAME, MEMNAME, NODEID, NODEGRP from CMS_JOBDEF where NODEID = ‘<bad>’
go
NODEGRP = ‘<bad>’ can also be used in place of NODEID and you can also look in the CMS_JOBAJF too. These jobs can need to either be removed on corrected to reflect the appropriate agent.

Regards,
Rahul Sehgal

User avatar
archu
Nouveau
Nouveau
Posts: 18
Joined: 27 Apr 2009 12:00

Post by archu » 17 Nov 2009 1:50

Hi,

Those are Windows servers(i mean Windows Agents)
And my control -M version is 6.4.01 and agent is 6.3.01

Regards


rahulsehgal wrote:Hi Archu,

To remove the bad configuration agents, it’s best to shutdown Control-M during this process. In the ~/ctm/data/AGSTAT and ~/ctm/data/AGPRM directories remove all the corresponding bad agents.

To find the jobs that are setup to run on a “bad” agent, run the following from the Control-M database (example=sybase)

select JOBNAME, MEMNAME, NODEID, NODEGRP from CMS_JOBDEF where NODEID = ‘<bad>’
go
NODEGRP = ‘<bad>’ can also be used in place of NODEID and you can also look in the CMS_JOBAJF too. These jobs can need to either be removed on corrected to reflect the appropriate agent.

Regards,
Rahul Sehgal

Yves31

Post by Yves31 » 17 Nov 2009 2:18

Hi,

Use ctm_menu utility on Control/m server, enter number 9 <enter>, enter number <4> enter.

Yves31.

User avatar
markf
Nouveau
Nouveau
Posts: 134
Joined: 13 Jul 2006 12:00
Location: Switzerland
Contact:

Post by markf » 17 Nov 2009 4:19

archu - with that version of Control-M it is actually easier and 'cleaner' to do this via the CONTROL-M Configuration Manager (highlight the Agent in question and right-click/delete).

User avatar
archu
Nouveau
Nouveau
Posts: 18
Joined: 27 Apr 2009 12:00

Post by archu » 18 Nov 2009 2:52

Hi friends,

Thanks for ur help. I have already tried in ctm_menu and configuration manager which i have return in my first mail.

Any ways my problem is resolved.

markf wrote:archu - with that version of Control-M it is actually easier and 'cleaner' to do this via the CONTROL-M Configuration Manager (highlight the Agent in question and right-click/delete).

User avatar
philmalmaison
Nouveau
Nouveau
Posts: 1148
Joined: 08 Jun 2007 12:00
Location: Ile de France

Post by philmalmaison » 18 Nov 2009 3:37

hy all
don't forget that :
a agent is going to discover status when only one job in ajf in design with concerned agent host.

you must first remove all jobs refering to the agent before !!!

after using CCM in in 6.3 to clean it by delete

regards
philmalmaison

Post Reply