If analytic logs are needed in the new ADOM, what should be done?

To ensure that analytic logs are present in a new ADOM (Administrative Domain) on FortiAnalyzer, rebuilding the SQL database using a special command is the proper course of action. This process involves initializing or refreshing the database structure, which is essential for incorporating and ensuring the integrity of the analytic logs within the new ADOM.

When you create a new ADOM, it does not automatically inherit the logs or data from existing ADOMs, meaning the logs must be explicitly managed. By using the special command to rebuild the SQL database, you are essentially setting up the appropriate data structure required for the analytic logs to be stored and processed correctly in that specific ADOM. This action guarantees that any historic logs or data relevant to the analytic functions are integrated into the new setup.

The other options may seem viable but do not adequately address the need for a robust setup of analytic logs in the new ADOM context. For instance, simply copying logs manually or exporting them from an old ADOM may lead to potential inconsistencies or data integrity issues. Relying on an automatic transfer process would not be effective since logs do not migrate without intervention after an ADOM is created. Thus, the most reliable and systematic method is to rebuild the SQL database.