The meaning of commit_change_records_count in the GetTaskDetails API

[iti-attunity-sup]

I would like answers to the following three questions about the GetTaskDetails API:

1. The commit_change_records_count is described in the documentation as "The number of COMMIT change records."
   Could you please provide more details about this field?
2. I couldn't distinguish between commit_change_records_count and applied_records_comitted_count.
   Could you explain the meaning of applied_records_comitted_count?
3. In what situations could this kind of response result occur?
   'cdc_transactions_counters': {'commit_change_records_count': 16126, 'rollback_transaction_count': 0, 'rollback_change_records_count': 0, 'rollback_change_volume_mb': 0, 'applied_transactions_in_progress_count': 0, 'applied_records_in_progress_count': 0, 'applied_comitted_transaction_count': 0, 'applied_records_comitted_count': 0, 'applied_volume_comitted_mb': 0, 'incoming_accumulated_changes_in_memory_count': 0, 'incoming_accumulated_changes_on_disk_count': 0, 'incoming_applying_changes_in_memory_count': 0, 'incoming_applying_changes_on_disk_count': 0}

          ■What I confirmed by checking the response is:

          ・total_latency is 00:00:00, indicating no latency.
          ・All incoming_XXX values are 0, suggesting no unapplied changes.
          ・commit_change_records_count is 16126, while applied_records_comitted_count is 0, indicating a discrepancy.

          ■The status of the task when this response is returned
          ・The task is running when GetTaskDetails is executed ('state': 'RUNNING').
          ・There are no errors or warnings in the task log.
          ・SAP Application source is used (with SAP HANA as the backend using trigger-based CDC), and no filters are set on the task.

[Heinvandenheuvel]

Well, do you think there were any actual changes to the SAP table being replicate? Can you test this in a controlled (DEV) environment where you know the actual changes count?

Rollback and commit could be expected to have similar counters.

commit_change_records_count  - The number of COMMIT change records.
rollback_tranaction_count -  The number of ROLLBACK transactions.    (TYPO in API guide)
rollback_change_records_count - The number of ROLLBACK change records.

:

applied_committed_transaction_count The number of transactions committed.
applied_records_committed_count The sum of all records/events in all Completed transactions.

It sure looks like there is a missing "committed_transaction_count". Or maybe  'commit_change_records_count' is just the missing count: all the commits being in the log and those commits may be 'empty' for replicate when  they involve tables not being replicated or even transactions with just selects in there.

Perhaps a low priority support case is justified to request an explanation from engineering, and fix the missing s in transaction typo, but it feels like a wasted effort.

Hein.

[iti-attunity-sup]

Hein,

Thank you for your reply.

Could I get answers to the three questions, please?

Best regards

[iti-attunity-sup]

I'd like answers to the three questions I initially mentioned.

Please provide assistance.

[DesmondWOO · Accepted solution]

Hi @iti-attunity-sup ,

I've conducted a test. From my observation,

1. commit_change_records_count is the number of change records that have been committed at the source database.

2. applied_records_comitted_count is the number of committed change records that have been applied to the target database. 

3. Based on the provided numbers, it appears that Replicate has captured 16126 committed records, but it has not yet applied these changes to target. 

I would recommend to open a support ticket to this issue. 

Please also open other support tickets for the following typos:

• User guide: rollback_tranaction_count
• REST API GetTaskDetails: Under cdc_transactions_counters, all instances of the word 'committed' are spelled as 'comitted'. 

Regards,
Desmond

[iti-attunity-sup]

Hi @DesmondWOO 

Thank you for your input.
As you recommended, I have decided to create the case.

Best regards