Hi,
There is custom attribute named "Service ID" on our entitlement object.
According to SQL script in entitlement collector, below rows' service id should be null.
We don't understand why entitlement collector does not nullify previously collected data.
Note that we are able to see correct result when we execute the script directly in database.
Hi Ece.. What script are you talking about and what is it doing exactly?
Hi Venkata,
Script is like that, i want to clear serviceid attribute of roles. because they dont comply the case.
,case when RoleName like 'SRV%' then substr(....bla bla...)
else null end serviceid
FROM
Thanks,
Please look at the RAW data of the collection run. This can be seen in collection data run detail page from Admin->Monitoring->Data Runs. Look for the same application roles in the raw data there and see what value they are collecting. That would tell whether the issue is on the collection side or the data processing side.
Hi again,
Yes i see the serviceIDs in that page as below:
So why they dont rebound to what access page at applicaiton?
If you are seeing NULL value on Raw data but some other value on the actual entitlement/app role, you have hit some bug with the delta processing part. While a jira should be filed for that (there might be some fixed already), use you can use below query to set the collector for full refresh (adjust collector name if required and commit update). Rerunning the collector after that should fix your data.
update t_data_collectors set requires_full_refresh = 'B' where name = 'ENT_COL_DATABASE_EBS'
Hello,
After executing below script and running collection again, we have observed data is nullified successfully.
update t_data_collectors set requires_full_refresh = 'B' where name = 'ENT_COL_DATABASE_EBS'
Below ticket has been raised as well.
case 00821626 - Entitlement Collector Does Not Nullify Previously Collected Data
I am trying to determine from your last comment if your issue is resolved or if you still need assistance?
Hello Ian,
I suppose we are not expected to run such a script manually at our end.
It needs investigation (from RSA Support Service) on why, during collection, we are not able to nullify previously collected data.
Waiting for your response.
Based on the symptoms and the work around that resolved this for you I believe this matches a known issue that has been addressed, and will be patched in the upcoming RSA Via Lifecycle and Governance P04 patch release.
Hello Ian,
For the sake of tracebility, may I request issue number for the known issue you were referring to.
If you are seeing NULL value on Raw data but some other value on the actual entitlement/app role, you have hit some bug with the delta processing part. While a jira should be filed for that (there might be some fixed already), use you can use below query to set the collector for full refresh (adjust collector name if required and commit update). Rerunning the collector after that should fix your data.
update t_data_collectors set requires_full_refresh = 'B' where name = 'ENT_COL_DATABASE_EBS'