Description
Solution
The following CLI commands can be used to verify and correct certain database integrity errors:
#diagnose dvm check-integrity
#diagnose cdb check objcfg-integrity
#diagnose cdb check policy-assignment
#diagnose pm2 check-integrity all
Not all integrity problems can be detected and corrected by these commands.
If a database correction is attempted, it is recommended to run the command a second time in order to confirm that the changes were correctly done.
#diagnose dvm check-integrity
#diagnose cdb check objcfg-integrity
#diagnose cdb check policy-assignment
#diagnose pm2 check-integrity all
Not all integrity problems can be detected and corrected by these commands.
If a database correction is attempted, it is recommended to run the command a second time in order to confirm that the changes were correctly done.
Solution
The FortiManager database can also be checked using the SQLite Studio application from sqlitestudio.pl. Here is the procedure to use it:
1) Rename the FortiManager Backup with a .tgz extension and unarchive to disk. Locate the /var/pm2/global.db files.
2) Open these files with the SQLite Studio application.
3) Perform an Integrity check as per the following screenshots. The results should indicate "ok" if the FortiManager database is in good state.
1) Rename the FortiManager Backup with a .tgz extension and unarchive to disk. Locate the /var/pm2/global.db files.
2) Open these files with the SQLite Studio application.
3) Perform an Integrity check as per the following screenshots. The results should indicate "ok" if the FortiManager database is in good state.
