Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
.png "Former Employee"){kind=icon}
Introduction: I encountered this error message recently in a logstream child task log and wanted to reproduce with an example.
Test Case:
1. Start Parent/Staging task with a reload (1:04pm)
2. Start Child/ Replication task with a reload (1:04pm)
3. Make a few changes on source table and see reflected in the monitor tab (1:09pm)
4. Stop the child/Replication task
5. Try a restart from timestamp from before the reload (1:03pm). This will throw the error:
00028524: 2022-09-07T13:09:55 [SOURCE_CAPTURE ]I: Starting processing from context 'timestamp:2022-09-07T17:03:45' (ar_cdc_channel.c:821)
00028524: 2022-09-07T13:09:55 [SOURCE_CAPTURE ]E: Cannot start processing from timestamp '2022-09-07 13:03:45.000000', the logstream only contains records with timestamp greater than or equal to '2022-09-07 13:04:23.329281' [1002510] (ar_cdc_channel.c:946)
This means the Logstream timeline started from '2022-09-07 13:04:23.329281'.
The log message is telling us to start the replicate task using timestamp '2022-09-07 13:04:23.329281' which is equivalent to the time which the staging(Logstream) task started.
6. Start from timestamp the value listed in the log.
Oops this did not work!
00028996: 2022-09-07T13:20:16 [SOURCE_CAPTURE ]E: Cannot start processing from timestamp '2022-09-07 13:04:23.000000', the logstream only contains records with timestamp greater than or equal to '2022-09-07 13:04:23.329281' [1002510] (ar_cdc_channel.c:946)
Need to go 1 second higher.
7. Start from timestamp the value listed in the log, rounded up 1 second.
Task able to process the changes.
*Note*- this is purely an example to display the error message and what it means. Please proceed with caution when doing a restart from timestamp on child/replication task to avoid duplicate or missing records (depends on task settings, target endpoint, etc.)
Environment
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
