I have delta aggregation configured for a few JDBC sources. We maintain a table in our database for each source that is populated with the necessary ‘Insert’/’Update’/’Delete’ records. It is my understanding that when a change is processed, it is supposed to be deleted from this table, but I’m finding that not all the records are removed. Over time, the table size grows. Are there any situations under which ISC doesn’t remove the record from the delta table of a JDBC source?
If we are talking about aggregation, why would ISC remove the record from source? Can you add more context or flow to the process here.
It doesn’t remove the record from the source. I think it is supposed to remove the record from the delta change table. As per the doc [1]:
CREATE TABLE USER_DELTA (USER_ID VARCHAR2(20), ACTION VARCHAR2(10));
That’s the table I’m talking about. Over time the number of records grows, even after doing aggregations on the source in ISC. My expectation would be that the number of records in that table should be 0 after an aggregation (race conditions aside).
Hi Matt, for the delta records that get left behind, can you see if the actual record exists in the view (based on the user_ID as a key).
My guess is that the delta record stayed because of a broken / incomplete lookup of the actual record entry.
I think that was it. Thanks Terry!