View Revisions: Issue #6959
| Summary | 0006959: SQL-Server log miner goes back to older change version in loop | ||
|---|---|---|---|
| Revision | 2025-06-19 12:59 by elong | ||
| Description | SQL-Server log miner can continue to go back to an older change version to mine changes in a loop. For example, current version is 1, it sees a change waiting at 2, so it mines it and advances to wait for 3, but then logic decreases it back to 1. [LogMinerService] [SQL_target-job-12] Obtained a start ID 3 from sym_context [LogMinerService] [SQL_target-job-12] Decreasing the next ID from 3 to 1 because it's greater than the current ID of 1 [LogMinerService] [SQL_target-job-12] Saving position at ID 1 with 0 open XIDs: The logic appears to have been introduce in issue 0006863. |
||
| Revision | 2025-06-19 12:58 by elong | ||
| Description | SQL-Server log miner can continue to go back to an older change version to mine changes in a loop. For example, current version is 1, it sees a change waiting at 2, so it mines it and advances to wait for 3, but then logic decreases it back to 1. [LogMinerService] [SQL_target-job-12] Obtained a start ID 3 from sym_context [LogMinerService] [SQL_target-job-12] Decreasing the next ID from 3 to 1 because it's greater than the current ID of 1 [LogMinerService] [SQL_target-job-12] Saving position at ID 1 with 0 open XIDs: |
||