Missing synchronization between SAM and AM after deleting object in AM

Well,

it should be enough starting a discovery
But you can also delete the objects from SAM using dmctl

dmctl -s INCHARGE-SA delete Node::

cheers

Thank you,
but our goal is maximumly to simplify work of Smarts operator.
My remark is logically correct.

well,

it's indeed correct but ...
well not really but's ... you can optimize the sincro between AM and SAM. By default it's performed every 6 hours if i remember correctly but you can tweak this setting. Don't remember where actually but you can do it and it's in the documentation.
And what is the problem with operators? Alarms won't be raised againts that devide anymore and i don't think he/she will be looking at the topology all the time

cheers

Fernando

Hi

In our environment we detected a problem on the synchronisation once.
The problem could be solved with the following cmdline commands:

In .log you have: Got another sync request to while syncing to the same source. Ignored the new sync request
1. check if a look does exist
dmctl -s invoke GA_StringDictionary::DXA-SyncCheck dump
2. check the dump in the ./local/logs/ .log
if you find " => TRUE" run the command in step 3
3. removing the look
dmctl -s invoke GA_StringDictionary::DXA-SyncCheck remove

After that you can start the synchronization again:
dmctl -s invoke GA_DaemonDriver:: _Topo-Driver start

Hope it helps...