000033293 - All collected objects are showing as new in RSA Via Lifecycle and Governance

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000033293
Applies ToRSA Product Set: RSA Via Lifecycle and Governance (RSA Via L&G)
RSA Version/Condition: 6.8.1, 6.9, 6.9.1

 
IssueAll objects and/or references in a collection run's raw data are showing as new.
 
User-added image
CauseThere are two reasons an item should show up as new in the raw data. Either:
  1. The object did not exist in the previous collection run, or
  2. The collector definition/reference resolution was altered.
If all items are showing as new outside of the above scenarios, there may be a database setting that is incorrectly configured to run what is known as a full refresh.
To validate if this is the case, check the database logs (Admin > Monitoring > Runfor the entry "Forcing full collector refresh." It will typically look like:
      

5758067--Account_Data_CollectorSave_Change_LogINFO4/20/2016 16:51Forcing full collector refresh
5758065--Account_Data_CollectorSave_Run_DataINFO4/20/2016 16:514876 rows copied
5758064--Account_Data_CollectorSave_Run_DataSQLTEXT4/20/2016 16:51Copying table data
57580631Account_Data_CollectorSave_Run_DataBEGIN4/20/2016 16:51 

ResolutionEdit the value of column REQUIRES_FULL_REFRESH on the table T_DATA_COLLECTORS, associated with the collector in question and set it to null. The query to do so should look something like this:
UPDATE T_DATA_COLLECTORS SET REQUIRES_FULL_REFRESH = NULL WHERE NAME = '<COLLECTOR_NAME>';
COMMIT;

Replace <COLLECTOR_NAME> with the actual name of your collector.

Attachments

    Outcomes