https://linen.dev logo
Join Slack
Powered by
```2026-06-01 16:15:28 platform INFO main i.a.c.i....
# replication-ask-ai
r
Copy code
2026-06-01 16:15:28 platform INFO main i.a.c.i.b.s.SshTunnel$Companion(getInstance):424 Starting connection with method: NO_TUNNEL
2026-06-01 16:15:28 platform INFO main c.z.h.HikariDataSource(<init>):79 HikariPool-1 - Starting...
2026-06-01 16:15:28 platform INFO main c.z.h.HikariDataSource(<init>):81 HikariPool-1 - Start completed.
2026-06-01 16:15:28 platform INFO main i.a.c.i.s.j.AbstractJdbcSource(getCheckOperations$lambda$6):343 Attempting to get metadata from the database to see if we can connect.
2026-06-01 16:15:28 platform INFO main i.a.i.s.m.MssqlSource(lambda$assertCdcEnabledInDb$14):328 Checking that cdc is enabled on database 'interactdbData4BI' using the query: 'SELECT name, is_cdc_enabled FROM sys.databases WHERE name = ?'
2026-06-01 16:15:28 platform INFO main i.a.c.d.j.s.AdaptiveStreamingQueryConfig(initialize):24 Set initial fetch size: 10 rows
2026-06-01 16:15:28 platform INFO main i.a.i.s.m.MssqlSource(lambda$assertCdcSchemaQueryable$15):360 Checking user 't2t_admin' can query the cdc schema and that we have at least 1 cdc enabled table using the query: 'USE [interactdbData4BI]; SELECT * FROM cdc.change_tables'
2026-06-01 16:15:28 platform INFO main i.a.c.d.j.s.AdaptiveStreamingQueryConfig(initialize):24 Set initial fetch size: 10 rows
2026-06-01 16:15:28 platform INFO main i.a.c.d.j.s.AdaptiveStreamingQueryConfig(initialize):24 Set initial fetch size: 10 rows
2026-06-01 16:15:28 platform INFO main i.a.i.s.m.MssqlSource(lambda$assertSqlServerAgentRunning$16):388 Checking that the SQL Server Agent is running using the query: 'SELECT status_desc FROM sys.dm_server_services WHERE [servicename] LIKE 'SQL Server Agent%' OR [servicename] LIKE 'SQL Server 代理%' '
2026-06-01 16:15:28 platform INFO main i.a.c.d.j.s.AdaptiveStreamingQueryConfig(initialize):24 Set initial fetch size: 10 rows
2026-06-01 16:15:28 platform INFO main c.z.h.HikariDataSource(close):349 HikariPool-1 - Shutdown initiated...
2026-06-01 16:15:28 platform INFO main c.z.h.HikariDataSource(close):351 HikariPool-1 - Shutdown completed.
2026-06-01 16:15:28 platform INFO main i.a.c.i.b.IntegrationRunner(runInternal):224 Completed integration: io.airbyte.cdk.integrations.base.ssh.SshWrappedSource
2026-06-01 16:15:28 platform INFO main i.a.i.s.m.MssqlSource(main):599 completed source: class io.airbyte.integrations.source.mssql.MssqlSource
2026-06-01 16:15:28 platform INFO Checking for optional control message...
2026-06-01 16:15:28 platform INFO Writing output of b5ea17b1-f170-46dc-bc31-cc744ca984c1_778185_0_check to the doc store
2026-06-01 16:15:28 platform INFO Marking workload b5ea17b1-f170-46dc-bc31-cc744ca984c1_778185_0_check as successful
2026-06-01 16:15:28 platform INFO 
2026-06-01 16:15:28 platform INFO Deliberately exiting process with code 0.
2026-06-01 16:15:28 platform INFO ----- END CHECK -----
2026-06-01 16:15:28 platform INFO
k
Looking at your logs, the connection check completed successfully — the workload was marked as successful and exited with code 0. All three CDC prerequisite checks passed: 1. CDC enabled on the database — 
interactdbData4BI
was queried and passed. 2. CDC schema queryable — the user 
t2t_admin
can query 
cdc.change_tables
and at least one CDC-enabled table exists. 3. SQL Server Agent running — the agent status check completed without error. The log sequence ending with 
Marking workload ... as successful
and 
Deliberately exiting process with code 0
confirms the check operation succeeded normally. If you are seeing an issue despite this successful check, here are some things to consider based on known MSSQL CDC behaviors: • LSN validation issues: If syncs fail after the check passes, it could be related to LSN availability or permission issues on specific capture instances. A fix for unauthorized CDC capture instances causing LSN validation failures was shipped in source-mssql 
4.4.3
. [LSN fix PR] • Tables without primary keys: If you have CDC-enabled tables without a primary key, CDC discovery was broken prior to 
4.4.8
. [PK-less CDC fix] • Adding columns to CDC tables: If you've added columns to existing CDC-tracked tables, those columns won't be captured automatically — you need to disable and re-enable CDC on the table. [CDC troubleshooting] Could you clarify what specific problem you're experiencing? The logs you shared show a successful connection check, so if there's an issue, it may be occurring during the actual sync rather than the check phase. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
11 Views
Open in Slack
PreviousNext
Powered by