after upgrade msserver version from 4v to 5v...it used to work cdcd at 4v

Incumbent CDC state is invalid, reason: io.airbyte.cdk.ConfigErrorException: CDC is not available for the following table(s)

Thinking completed CDC State Invalid After Upgrading source-mssql from v4 to v5 The error you're seeing:

Incumbent CDC state is invalid, reason: io.airbyte.cdk.ConfigErrorException: CDC is not available for the following table(s)

This is a known issue related to how the catalog is configured when running CDC with the MSSQL connector. [PR #85752] What's happening When the connector runs with a full refresh catalog (instead of incremental), the CDC feed still runs and emits a cold-start STATE in the first sync. On the second sync,

validateConfiguredStreamsAreAccessible

filters the catalog to

INCREMENTAL

streams, gets an empty set, and

validateLsnStillAvailable

returns

false

— triggering the misleading "CDC is not available" error, even though the saved LSN is actually valid. [PR #85752] Additionally, there is a known issue where

dbo.systranschemas

(a CDC system table) may be discovered as a user stream and cause this error. [PR #85752] How to fix 1. Ensure your streams are configured as

INCREMENTAL

(not

FULL_REFRESH

) in your connection settings. CDC requires incremental sync mode. 2. Set the

cursor_field

to

_ab_cdc_cursor

— this is the source-defined cursor for CDC streams. Using any other name (including

_ab_cdc_lsn

) will cause issues. [MSSQL Contributing] 3. Exclude system tables like

dbo.systranschemas

from your configured streams, as these should not be treated as user streams. [PR #85752] 4. Reset the CDC state if the state is now invalid: ◦ Go to your connection in the Airbyte UI ◦ Navigate to stream settings ◦ Use the "Clear data and reset" option for the affected streams ◦ Re-run the sync Summary The root cause is likely that after the upgrade, your streams are being treated as full refresh instead of incremental, or system tables are being included. Reconfiguring the streams to use

sync_mode: incremental

with

cursor_field: _ab_cdc_cursor

and excluding

dbo.systranschemas

should resolve the issue. [PR #85752] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.