Bug report

For bug reports, provide this information, please:

What Debezium connector do you use and what version?

DB2 Connector 

What is the connector configuration?

It does not depend on the configuration. 

If snapshot.mode is set to initial, after a connector restart, it fails.

If snapshot.mode is set to when_needed, after a connector restart, it does create a new snapshot. 

What is the captured database version and mode of deployment?

quay.io/rh_integration/dbz-db2-cdc:latest deployed in OCP

What behavior do you expect?

I expect that the connector is able to recover from a restart correctly.

What behavior do you see?

The connector fails to detect the LSN offset and fails with the following exception, not being able to recover automatically. 

throw new DebeziumException("The connector is trying to read change stream starting at " + offset.getSourceInfo() + ", but this is no longer "
        + "available on the server. Reconfigure the connector to use a snapshot mode when needed."); 

Do you see the same behaviour using the latest released Debezium version?

Yes. 

Do you have the connector logs, ideally from start till finish?

Attached. kafka_connect.logs

How to reproduce the issue using our tutorial deployment?

If you run the system test, it will fail all the time. 

Implementation ideas (optional)

The fix Chris did solved the problem in the test side here