Unable to recreate a database agent because agent or instance "is already monitored" (4225903)

A user cannot recreate an Azure SQL, Oracle, SQL Server, or DB2 database agent that was previously deleted and does not appear listed in the Agent Status panel. A popup appears indicating that the agent or database instance is already being monitored, such as: "This database is already monitored by agent null".

This can indicates that either an agent has not yet appeared in the Global View dashboard or an agent was deleted in Agent Status but the configuration settings weren’t completely cleared out from the Clear Agent Data and Clear Agent Model Data sections of the Databases Technical Support dashboard.

WORKAROUND

Delete the old agent topology and recreate the agent using the following steps.

1. Navigate to Databases > Support Dashboard > Databases Technical Support
2. Switch between the DB types tabs (e.g. Oracle or SQL Server accordingly)
3. Click on Clear Agent data
4. Highlight the agent which is missing from Database Dashboard and has topology duplication
5. Click on the Delete button
6. Click on Clear Agent Model Data
7. Highlight the agent which is missing from Database Dashboard and has topology duplication
8. Click on the Delete button
9. Rerun the Database Wizard and add the instance

A restart of the FMS may be required for 7.3 and earlier FMS versions due to a CacheOptimisticLockException error in the log files.

If your system has a lot of database agents seeing the agent in the Global view is not immediate and it can take up to a couple of minutes to appear. Deactivating and reactivating the agent in Agent Status can sometime expedite the agent reappearing.

STATUS

Beginning in the Foglight 8.1 release database agents deleted using the Agent Status dashboard will have their topologies issues addressed. Database agents deleted using a previous FMS and cartridge versions will still require using the workaround.