how to stop failing snapshot

[Joseph Vonášek]

ello, I tried to sent a signal to create increamental snapshot using signal topic to debezium, but debezium adjusted the query adding there surrogateKey= null. The connector try to run this incorect query and it fails again and again . How is possible to stop it ? org.apache.kafka.connect.errors.RetriableException: An exception occurred in the change event producer. This connector will be restarted.

at io.debezium.pipeline.ErrorHandler.setProducerThrowable(ErrorHandler.java:63)

at io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:150)

at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)

at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)

at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)

at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

at java.base/java.lang.Thread.run(Thread.java:829)

Caused by: io.debezium.DebeziumException: Database error while executing incremental snapshot for table 'DataCollection{id=SLTRS_ISU.dbo.ISU_EPROFVAL15, additionalCondition=(SELECT * FROM SLTRS_ISU.dbo.ISU_EPROFVAL15 WHERE MANDT='130' AND VALUEDAY IN ('20250810','20250809','20250812','20250813','20250807','20250806','20250805')), surrogateKey=}'

at io.debezium.pipeline.source.snapshot.incremental.AbstractIncrementalSnapshotChangeEventSource.readChunk(AbstractIncrementalSnapshotChangeEventSource.java:345)

at io.debezium.pipeline.source.snapshot.incremental.AbstractIncrementalSnapshotChangeEventSource.init(AbstractIncrementalSnapshotChangeEventSource.java:232)

at io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$initStreamEvents$7(ChangeEventSourceCoordinator.java:329)

at java.base/java.util.Optional.ifPresent(Optional.java:183)

at io.debezium.pipeline.ChangeEventSourceCoordinator.initStreamEvents(ChangeEventSourceCoordinator.java:329)

at io.debezium.connector.sqlserver.SqlServerChangeEventSourceCoordinator.executeChangeEventSources(SqlServerChangeEventSourceCoordinator.java:101)

at io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:143)

... 5 more

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Column name or number of supplied values does not match table definition.

at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:259)

at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1695)

at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:648)

at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:567)

at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7675)

at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:4137)

at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:272)

at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:246)

at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.execute(SQLServerPreparedStatement.java:544)

at io.debezium.jdbc.JdbcConnection.prepareUpdate(JdbcConnection.java:786)

at io.debezium.pipeline.source.snapshot.incremental.SignalBasedIncrementalSnapshotChangeEventSource.emitWindowOpen(SignalBasedIncrementalSnapshotChangeEventSource.java:69)

at io.debezium.pipeline.source.snapshot.incremental.AbstractIncrementalSnapshotChangeEventSource.readChunk(AbstractIncrementalSnapshotChangeEventSource.java:258)

... 11 more

[jiri.p...@gmail.com]

Hi,

what Debezium version are we tlaking about? What exact signal have you sent? Could you please also change the source table and change table and confirm that the schema matches?

Thanks

Jiri

[jiri.p...@gmail.com]

WRT stopping the snapshot I'd recommend just to disable the source channel and then re-enable it later.

Jiri

On Thursday, September 11, 2025 at 8:40:42 PM UTC+2 von...@gmail.com wrote:

[Joseph Vonášek]

Debezium version is  2.7,

Where debezium stores the signals ? How can I delete it ?

There is a command that I see in connect-sqlserver-offsets topik

{
"incremental_snapshot_correlation_id": null,
"event_serial_no": 1,
"incremental_snapshot_maximum_key": "aced000570",
"commit_lsn": "00032cf8:0000ad03:0017",
"change_lsn": "00032cf8:0000ad03:0016",
"incremental_snapshot_collections": "[{\"incremental_snapshot_collections_id\":\"SLTRS_ISU.dbo.ISU_EPROFVAL15\",\"incremental_snapshot_collections_additional_condition\":\"((((SELECT * FROM SLTRS_ISU.dbo.ISU_EPROFVAL15 WHERE MANDT='130' AND VALUEDAY IN ('20250810','20250809','20250812','20250813','20250807','20250806','20250805')))))\",\"incremental_snapshot_collections_surrogate_key\":null}]",
"incremental_snapshot_primary_key": "aced000570"
}

Dne pátek 12. září 2025 v 7:57:42 UTC+2 uživatel jiri.p...@gmail.com napsal:

[Chris Cranford]

Hi Joseph -

You would set `signal.enabled.channels` to an empty string in your configuration to disable all signal channels.

-cc

--
You received this message because you are subscribed to the Google Groups "debezium" group.
To unsubscribe from this group and stop receiving emails from it, send an email to debezium+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/debezium/d544614b-485a-4d15-b64f-4e0e769d24c9n%40googlegroups.com.