Description
This article describes how to delete a Policy Package in the Global Database where it has been unassigned but the error shows it was assigned to local ADOM.
Scope
FortiManager.
Solution
Confirm that it was not assigned to any local ADOM and check the CLI command below if showing any error and rectify it:
FMG # diagnose cdb upgrade check invalid-assign-status
Checking: Invalid assign status entries
ADOM Global:
DELETE: pkg_oid 6191, adom_oid 1454
1 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
Upgrading: Invalid assign status entries
ADOM Global:
DELETE: pkg_oid 6191, adom_oid 1454
1 error(s) fixed.
Database upgrade complete.
The output shows that the policy package was corrupted on the database end where it had been already unassigned and the command rectified it.
Related article:
Troubleshooting Tip: How to troubleshoot error when assigning global policy package
