Resources can be added automatically on the client side or manually by adding them to the dblist.cfg or via the Portal. The ProTop Portal and syncdblist.sh[bat] try to keep all these approaches in sync.
One challenge is using the same custid across multiple servers. This means all resources across all servers are in the dblist on every server as well as on the portal.
Deleting a resource from the portal forces an update to the dblist on the resource's source server. The trouble is that the other servers don't get this update, so the deleted resource remains in the dblist.cfg on the other servers. When a syncdblist is run on those servers, it sends the deleted resource back to the portal, and not being found there it gets recreated.
This conundrum will be addressed with a planned change to the portal where resources are created only on the portal and no longer on the client side.
In the meantime, here are a couple of approaches to address the issue:
1. Mark the resource as inactive and forget about it. This comes at the expense of cluttering your resource list.
2. Use this coordinated approach to clean up across all servers and the portal:
NOTE: Be sure you are on the latest version of ProTop.
a. stop your dbmonitor service from being invoked on all affected servers sharing the same custid. On UNIX, comment out the crontab entry. Stop the ProTop3 DB Monitor service on Windows and change it from automatic to manual
b. delete all [your protop dir]/tmp/*flg files on all servers to shut protop down completely
c. edit one of the etc/dblist.cfg files and remove the lines for the resource(s) you want to delete
d. copy that etc/dblist.cfg to all servers using the same custid
e. remove the same resources from the portal
f. restart your dbmonitor service by reversing step a. above
g. verify the deleted resources remain deleted from the dblist.cfg and the portal