FortiManager
FortiManager supports network operations use cases for centralized management, best practices compliance, and workflow automation to provide better protection against breaches.
sinanalshoker
Article Id 425037
Description This article describes how to use a new debug command 'diagnose cdb upgrade check invalid-visibility' which has been introduced to identify and fix inconsistencies, which helps deleting invalid visibility entries from the Global ADOM. 
Scope FortiManager.
Solution

In the scenario, which may occur after the upgrade, the object appears to have no references when checked using the 'Where used' option. However, FortiManager returns the following error:  

 

Global Database - Could not change assigned objs - object is assigned to ADOM X. which indicates that the object still in use in ADOM X.

 

The recommended solution is to initially backup the FortiManager, then execute the command 'diagnose cdb upgrade check invalid-visibility' to remove the invalid visibility entries. Once this is completed, the object can be deleted successfully as follows:

 

FMG-VM64 # diagnose cdb upgrade check invalid-visibility

Checking: Remove invalid visibility entries from global ADOM

 

[] error(s) found.

The above changes will be made to the database, however it is recommended to perform a backup first.
Do you want to continue? (y/n)y

error(s) fixed.


Database upgrade complete.

After confirming with 'y', the affected entries should be fixed and the objects should be possible to delete.