1. Verify that the missing data can be found in the User Console search but does not appear in the Analyzer report.
2. Understand why this happens:
   • The last modified date of the data entry is earlier than the application’s last catalog ETL date. 
   • Catalog ETL loads incremental or delta data from BDNA_PUBLISH into Analyzer tables.
   • Incremental data calculation uses the last modified date of the catalog data and the last ETL date. 
   • Initially, the last ETL date is set to 1969-12-31 to load all data. 
   • If catalog data changes occur earlier than the current ETL, those entries may not import into Analyzer.
3. To resolve this and reload all data, reset the last ETL date manually:
   For SQL Server:
   

   --USE BDNA_PUBLISH
   UPDATE BDNA_A_PROPERTIES$ SET VALUE_DATE = '1969-12-31' WHERE VALUE_DATE IS NOT NULL

   For Oracle Database:
   

   UPDATE BDNA_A_PROPERTIES$ SET VALUE_DATE = TO_DATE('1969-12-31','YYYY-MM-DD') WHERE VALUE_DATE IS NOT NULL;

4. After resetting the ETL date:
   • Rerun the Catalog Sync on the next day when new data is available, or
   • Run the following command on the User Console server:
   

   Analyze.exe /ETL=Catalog

This procedure forces a full ETL reload, ensuring all data, including previously missed entries, appears in Analyzer reports.