Agens is in "Discover" status - how to delete it?

Dilbert · Post by **Dilbert** » 11 Dec 2007 10:41

Hello all!
In my test environment I have the 2 Agents controlled by old CONTROL-M/Server. I changed hostname of the CONTROL-M/EM machine and CONTROL-M/Server machine, changed the Agent logical name, but one of the agent remains with old name, and it is always in "Discovering.." status. I can't delete it, or stop discovering it...
Anybody know how to delete that Agent from environment?

Post by **fyot** » 11 Dec 2007 10:56

Hi Dilbert

You must disabled the agent.
So during the discover, it's not possible.
The only way is to find in [controlm]/data/AGSTAT directory, the file concening that agent and modify AGSTAT parameter to D.

Dilbert · Post by **Dilbert** » 11 Dec 2007 11:31

Thanks, Franck!
I'll check that!

philmalmaison · Post by **philmalmaison** » 11 Dec 2007 5:46

be carefull , first step make a svg of AGSTAT and AGPRM
second DO NOT DO IT IN AG* directories, but copy the file in $HOME before !!!!!!! change it, and put it in AG* after
regards
Philmalmaison

Dilbert · Post by **Dilbert** » 18 Dec 2007 1:18

Hello, guys!

It is impossible to delete Agent.

I don't know how, but it seems that the Agent entry is somehow duplicated in the database.
When I'm using option 4 from Agent Status Menu, it says there is a two Agent with same name in status "Disable".
After deleting Agent entry, it appear again, twice!

I'm going slightly mad about it... maybe I should write to BMC support...

philmalmaison · Post by **philmalmaison** » 18 Dec 2007 1:40

delete all entries in AGPRM / AGSTAT / AG*RJX for any forms pointing to your nodeid
regards
philmalmaison

Dilbert · Post by **Dilbert** » 18 Dec 2007 2:29

Thaks, I deleted it finally.
But, now I can't delete it from CONTROL-M/EM Configuration Manager.

When CM started, message appears:

"Duplicate component was identified".
After that, I can enter into the CM, but can't delete Agent deleted from CTM Server before...

philmalmaison · Post by **philmalmaison** » 19 Dec 2007 2:42

can you explain what did you do at all

Dilbert · Post by **Dilbert** » 20 Dec 2007 1:05

I removed machine with problematic agent from environment.
After that, CONTROL-M/Server always trying to discover that Agent, and, of course, without success.
I deleted the entry from CONTROL-M/Server database as you and fyot suggested before, but CONTROL-M/EM Configuration Manager always show that Agent and trying to discover... after that, that agent appear again in Server database entry...

It will be good idea to implemet mechanism into CONTROL-M/Server to prevent automatic discovering of agent...

philmalmaison · Post by **philmalmaison** » 20 Dec 2007 1:35

what is the result of the following sql command ?

SQL
select count(NODEID) from CMS_NODEID=<you>

?
regards
Philmalmaison

Dilbert · Post by **Dilbert** » 20 Dec 2007 2:03

philmalmaison wrote:what is the result of the following sql command ?

SQL
select count(NODEID) from CMS_NODEID=<you>

?
regards
Philmalmaison

This query didn't work.
Says:
ORA-00933: SQL command not properly ended

philmalmaison · Post by **philmalmaison** » 20 Dec 2007 2:46

select count(NODEID) from CMS_NODID
where
NODEID="you nodeid name"
go

for sybase ...

result should be 1

regards
Philmalmaison

Dilbert · Post by **Dilbert** » 27 Dec 2007 10:43

The result is 0.

Any suggestions?

CONTROL-M/Server is placed o LInux ,achine, Enterprise Manager is on the Windows machine, problematic Agent was Windows Agent (second Win machine).

philmalmaison · Post by **philmalmaison** » 27 Dec 2007 4:28

so no nodeid record in controlm, so do you have in AJF a job recorded with your nodeid ?
regards
Philmalmaison

philmalmaison · Post by **philmalmaison** » 27 Dec 2007 4:42

or a node group in wich your nodeid is record ?
regards
Philmalmaison