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
delete a agent which is in discovering state
- rahulsehgal
- Nouveau
- Posts: 148
- Joined: 19 Mar 2009 12:00
- Location: Delhi
- Contact:
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
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
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
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
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.
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).
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France