Debezium从入门到精通系列之：百篇系列文章汇总之研究Debezium技术遇到的各种错误的解决方法

打通Debezium技术的过程中，遇到了一系列的问题，博主会持续总结运用Debezium过程中遇到的错误，现在把各种错误的解决方法汇总到下面的表格中：

文章名称	文章链接
Debezium报错处理系列一：The db history topic is missing	Debezium报错处理系列一：The db history topic is missing
Debezium报错处理系列二：Make sure that the same history topic isn‘t shared by multiple connector instances	Debezium报错处理系列二：Make sure that the same history topic isn‘t shared by multiple connector instances
Debezium报错处理系列三：Access denied； you need (at least one of) the SUPER, REPLICATION CLIENT privilege(s)	Debezium报错处理系列三：Access denied； you need (at least one of) the SUPER, REPLICATION CLIENT privilege(s)
Debezium报错处理系列四：Caused by: java.net.SocketException: Connection reset	Debezium报错处理系列四：Caused by: java.net.SocketException: Connection reset
Debezium报错处理系列五：Authentication failed: Invalid username or password	Debezium报错处理系列五：Authentication failed: Invalid username or password
Debezium报错处理系列六：A slave with the same server_uuid/server_id as this slave has connected to the maste	Debezium报错处理系列六：A slave with the same server_uuid/server_id as this slave has connected to the maste
debezium报错处理系列七：The database history couldn’t be recovered. Consider to increase the value for database.	debezium报错处理系列七：The database history couldn’t be recovered. Consider to increase the value for database.
debezium报错处理系列八：DDL statement couldn‘t be parsed.	debezium报错处理系列八：DDL statement couldn‘t be parsed.
debezium报错处理系列九：“ddl“ : “# Dummy event replacing event type 160 that slave cannot handle.“	debezium报错处理系列九：“ddl“ : “# Dummy event replacing event type 160 that slave cannot handle.“
Debezium报错处理系列十：Could not find existing binlog information while attempting schema only recovery snashot	Debezium报错处理系列十：Could not find existing binlog information while attempting schema only recovery snashot
Debezium报错处理系列十一：Data row is smaller than a column index, internal schema representation is probably out of sync with real database schema	Debezium报错处理系列十一：Data row is smaller than a column index, internal schema representation is probably out of sync with real database schema
Debezium报错处理系列十二：Cannot enlarge string buffer containing 1073740820 bytes by 1704 more bytes.	Debezium报错处理系列十二：Cannot enlarge string buffer containing 1073740820 bytes by 1704 more bytes.
Debezium报错处理系列十三：Caused by: java.io.EOFException	Debezium报错处理系列十三：Caused by: java.io.EOFException
Debezium报错处理系列十四： Invalid Java object for schema type INT64: class java.lang.String for field: “null	Debezium报错处理系列十四： Invalid Java object for schema type INT64: class java.lang.String for field: “null
debezium报错处理系列之十五：no longer available on the server. Reconfigure the connector to use a snapshot when neede	debezium报错处理系列之十五：no longer available on the server. Reconfigure the connector to use a snapshot when neede
Debezium报错处理系列之十六：Caused by: java.io.EOFException: Failed to read remaining 7 of 23 bytes from	Debezium报错处理系列之十六：Caused by: java.io.EOFException: Failed to read remaining 7 of 23 bytes from
Debezium报错处理系列之十七：Caused by: javax.management.InstanceAlreadyExistsException	Debezium报错处理系列之十七：Caused by: javax.management.InstanceAlreadyExistsException
Debezium报错处理系列之十八：解决无法获取表结构问题	Debezium报错处理系列之十八：解决无法获取表结构问题
Debezium报错处理系列之十九：The replication sender thread cannot start in AUTO_POSITION mode	Debezium报错处理系列之十九：The replication sender thread cannot start in AUTO_POSITION mode
Debezium报错处理系列之二十：task failed to create new topic.Ensure that the task is authorized to create topics	Debezium报错处理系列之二十：task failed to create new topic.Ensure that the task is authorized to create topics
Debezium报错处理系列之二十一： Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server	Debezium报错处理系列之二十一： Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server
Debezium报错处理系列之二十二：SchemaBuilderException: Cannot create field because of field name duplication	Debezium报错处理系列之二十二：SchemaBuilderException: Cannot create field because of field name duplication
Debezium报错处理系列之二十三：Caused by: java.lang.IndexOutOfBoundsException: No group 2	Debezium报错处理系列之二十三：Caused by: java.lang.IndexOutOfBoundsException: No group 2
Debezium报错处理系列之二十四：Caused by: org.postgresql.util.PSQLException: ERROR: replication slot \“debezium\“	Debezium报错处理系列之二十四：Caused by: org.postgresql.util.PSQLException: ERROR: replication slot \“debezium\“
Debezium报错处理系列之二十五：Client requested master to start replication from impossible position	Debezium报错处理系列之二十五：Client requested master to start replication from impossible position
Debezium报错处理系列之二十六：Caused by: io.debezium.DebeziumException: Failed to read next byte from position	Debezium报错处理系列之二十六：Caused by: io.debezium.DebeziumException: Failed to read next byte from position
Debezium报错处理系列之二十七：io.debezium.DebeziumException: Failed to deserialize data of EventHeaderV4	Debezium报错处理系列之二十七：io.debezium.DebeziumException: Failed to deserialize data of EventHeaderV4
Debezium报错处理系列之二十八： Expiring 1 record(s) for test-ts-0:120001 ms has passed since batch creation	Debezium报错处理系列之二十八： Expiring 1 record(s) for test-ts-0:120001 ms has passed since batch creation
Debezium报错处理系列之二十九：Make sure that an instance of SQL Server is running on the host and accepting TCP	Debezium报错处理系列之二十九：Make sure that an instance of SQL Server is running on the host and accepting TCP
Debezium报错处理系列之三十：SQLServerException: 服务器主体 \“dwCDC\“ 无法在当前安全上下文下访问数据库 \“dw\“。	Debezium报错处理系列之三十：SQLServerException: 服务器主体 \“dwCDC\“ 无法在当前安全上下文下访问数据库 \“dw\“。
Debezium报错处理系列之三十一：Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: 为过程或函数 cdc.fn_cdc	Debezium报错处理系列之三十一：Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: 为过程或函数 cdc.fn_cdc
Debezium报错处理系列之三十二：Unable to connect: Public Key Retrieval is not]	Debezium报错处理系列之三十二：Unable to connect: Public Key Retrieval is not
Debezium报错处理系列之三十三：Unexpected error while connecting to MySQL and looking at BINLOG_FORMAT	Debezium报错处理系列之三十三：Unexpected error while connecting to MySQL and looking at BINLOG_FORMAT
Debezium报错处理系列之三十四：io.debezium.DebeziumException: The db history topic or its content is fully or partially missing. Please check database history topic configuration and re-execute the snapshot	Debezium报错处理系列之三十四：io.debezium.DebeziumException: The db history topic or its content is fully or partially missing. Please check database history topic configuration and re-execute the snapshot
Debezium报错处理系列之三十五：ERROR WorkerSourceTask{id=mysql-nus_chat_prod-dd_ods_nus_chat_prod_1h-connector-0} Failed to flush, timed out while waiting for producer to flush outstanding 195 messages (org.apache.kafka.connect.runtime.WorkerSourceTask)	Debezium报错处理系列之三十五：ERROR WorkerSourceTask{id=mysql-nus_chat_prod-dd_ods_nus_chat_prod_1h-connector-0} Failed to flush, timed out while waiting for producer to flush outstanding 195 messages (org.apache.kafka.connect.runtime.WorkerSourceTask)
Debezium报错处理系列之三十六：Task threw an uncaught and unrecoverable exception. Task is being killed and will not recover until manually restarted	Debezium报错处理系列之三十六：Task threw an uncaught and unrecoverable exception. Task is being killed and will not recover until manually restarted
Debezium报错处理系列之三十七：Error configuring an instance of KafkaSchemaHistory；	Debezium报错处理系列之三十七：Error configuring an instance of KafkaSchemaHistory；
Debezium报错处理系列之三十八：Timeout expired while fetching topic metadata	Debezium报错处理系列之三十八：Timeout expired while fetching topic metadata
Debezium报错处理系列之三十九：Debezium Server实际应用报错No resolvable bootstrap urls given in bootstrap.servers	Debezium报错处理系列之三十九：Debezium Server实际应用报错No resolvable bootstrap urls given in bootstrap.servers
Debezium报错处理系列之四十：Debezium Server实际应用报错“message“:“JAAS config entry not terminated by semi-colon“	Debezium报错处理系列之四十：Debezium Server实际应用报错“message“:“JAAS config entry not terminated by semi-colon“
Debezium报错处理系列之四十一：Debezium实际应用报错Unable to configure and start connect.storage.FileOffsetBackingStor	Debezium报错处理系列之四十一：Debezium实际应用报错Unable to configure and start connect.storage.FileOffsetBackingStor
Debezium报错处理系列之四十二：Debezium Server应用报错Error configuring an instance of KafkaSchemaHistory	Debezium报错处理系列之四十二：Debezium Server应用报错Error configuring an instance of KafkaSchemaHistory
Debezium报错处理系列之四十三：Debezium Server实际应用报错“message“:“Could not find a ‘KafkaClient‘ entry in the JAAS	Debezium报错处理系列之四十三：Debezium Server实际应用报错“message“:“Could not find a ‘KafkaClient‘ entry in the JAAS
Debezium报错处理系列之四十四：The request included a message larger than the max message size the server will accept.	Debezium报错处理系列之四十四：The request included a message larger than the max message size the server will accept.
Debezium报错处理系列之四十五：org.apache.kafka.connect.errors.DataException: booking is not a valid field name	Debezium报错处理系列之四十五：org.apache.kafka.connect.errors.DataException: booking is not a valid field name
Debezium报错处理系列之四十六：The server selected protocol version TLS10 is not accepted by client preferences [TLS13, TLS12]	Debezium报错处理系列之四十六：The server selected protocol version TLS10 is not accepted by client preferences [TLS13, TLS12]
Debezium报错处理系列之四十七：Read only connection requires GTID_MODE to be ON	Debezium报错处理系列之四十七：Read only connection requires GTID_MODE to be ON
Debezium报错处理系列之四十八：Debezium Server实际应用报错User does not have the ‘LOCK TABLES‘ privilege required	Debezium报错处理系列之四十八：Debezium Server实际应用报错User does not have the ‘LOCK TABLES‘ privilege required
Debezium报错处理系列之四十九：this version of the Java Runtime only recognizes class file versions up to 52.0	Debezium报错处理系列之四十九：this version of the Java Runtime only recognizes class file versions up to 52.0
Debezium报错处理系列之五十：Flush of EmbeddedEngine{id=kafka} offsets threw an unexpected exception: “,“	Debezium报错处理系列之五十：Flush of EmbeddedEngine{id=kafka} offsets threw an unexpected exception: “,“
Debezium报错处理系列之五十一：Port 8080 seems to be in use by another process. Quarkus may already be running or the port is used by another application.	Debezium报错处理系列之五十一：Port 8080 seems to be in use by another process. Quarkus may already be running or the port is used by another application.
Debezium报错处理系列之五十二：解决Sql Server数据库安装后修改主机名导致sqlserver数据库实例名称没有修改从而无法设置CDC的问题	Debezium报错处理系列之五十二：解决Sql Server数据库安装后修改主机名导致sqlserver数据库实例名称没有修改从而无法设置CDC的问题
Debezium报错处理系列之五十三：Caused by: io.debezium.transforms.partitions.ComputePartitionException: Unable to validate config. partition.data-collections.partition.num.mappings and partition.data-collections.field.mappings has different tables defined	Debezium报错处理系列之五十三：Caused by: io.debezium.transforms.partitions.ComputePartitionException: Unable to validate config. partition.data-collections.partition.num.mappings and partition.data-collections.field.mappings has different tables defined
Debezium报错处理系列之五十四：kafka.connect.errors.DataException: Cannot list fields on non-struct type	Debezium报错处理系列之五十四：kafka.connect.errors.DataException: Cannot list fields on non-struct type
Debezium报错处理系列之五十五：it contains a character other than ASCII alphanumerics, ‘.‘, ‘_‘ and ‘-‘	Debezium报错处理系列之五十五：it contains a character other than ASCII alphanumerics, ‘.‘, ‘_‘ and ‘-‘
Debezium报错处理系列之五十六：common.errors.TimeoutException: Topic not present in metadata after 10000 ms	Debezium报错处理系列之五十六：common.errors.TimeoutException: Topic not present in metadata after 10000 ms
Debezium报错处理系列之五十七：Can‘t compare binlog filenames with different base names	Debezium报错处理系列之五十七：Can‘t compare binlog filenames with different base names
Debezium报错处理系列之五十八：The \‘database.names\‘ value is invalid: Cannot be empty	Debezium报错处理系列之五十八：The \‘database.names\‘ value is invalid: Cannot be empty
Debezium报错处理系列之五十九：The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer SSL encryption	Debezium报错处理系列之五十九：The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer SSL encryption
Debezium报错处理系列之六十：WARN Configuration option ‘event.deserialization.failure.handling.mode’ is renamed to ‘event.processing.failure.handling.mode’	Debezium报错处理系列之六十：WARN Configuration option ‘event.deserialization.failure.handling.mode’ is renamed to ‘event.processing.failure.handling.mode’
Debezium报错处理系列之六十一：Caused by: java.sql.SQLNonTransientConnectionException: Too many connections	Debezium报错处理系列之六十一：Caused by: java.sql.SQLNonTransientConnectionException: Too many connections
Debezium报错处理系列之六十二：Debezium2.1.4版本报错An exception occurred in the change event producer.	Debezium报错处理系列之六十二：Debezium2.1.4版本报错An exception occurred in the change event producer.
Debezium报错处理系列之六十三：FATAL ERROR in native method: processing of -javaagent failed	Debezium报错处理系列之六十三：FATAL ERROR in native method: processing of -javaagent failed
Debezium报错处理系列之六十四： SQL Server Agent running status query must return exactly one value	Debezium报错处理系列之六十四： SQL Server Agent running status query must return exactly one value
Debezium报错处理系列之六十五：Debezium JDBC connector无法支持mysql字段默认值为DEFAULT CURRENT_TIMESTAMP的解决方法	Debezium报错处理系列之六十五：Debezium JDBC connector无法支持mysql字段默认值为DEFAULT CURRENT_TIMESTAMP的解决方法
Debezium报错处理系列之六十六： java.sql.SQLException: Incorrect string value:‘\xE5\x80\xA9\xE5\x80\xA9…’ for column ‘name’ at row 1	Debezium报错处理系列之六十六： java.sql.SQLException: Incorrect string value:‘\xE5\x80\xA9\xE5\x80\xA9…’ for column ‘name’ at row 1
Debezium报错处理系列之六十七：TopicAuthorizationException: Not authorized to access topics	Debezium报错处理系列之六十七：TopicAuthorizationException: Not authorized to access topics
Debezium报错处理系列之六十八：No resolvable bootstrap urls given in bootstrap.servers	Debezium报错处理系列之六十八：No resolvable bootstrap urls given in bootstrap.servers
Debezium报错处理系列之六十九：Can‘t compare binlog filenames with different base names	Debezium报错处理系列之六十九：Can‘t compare binlog filenames with different base names
Debezium报错处理系列之七十：Postgres server wal_level property must be ‘logical‘ but is: ‘replica‘\n	Debezium报错处理系列之七十：Postgres server wal_level property must be ‘logical‘ but is: ‘replica‘\n
Debezium报错处理系列之七十一：Creation of replication slot failed Caused by: org.postgresql.util.PSQLException: FATAL: must be superuser or replication role to start walsender	Debezium报错处理系列之七十一：Creation of replication slot failed Caused by: org.postgresql.util.PSQLException: FATAL: must be superuser or replication role to start walsender
Debezium报错处理系列之七十二：Caused by: org.postgresql.util.PSQLException: ERROR: could not access file “decoderbufs”: No such file or directory	Debezium报错处理系列之七十二：Caused by: org.postgresql.util.PSQLException: ERROR: could not access file “decoderbufs”: No such file or directory
Debezium报错处理系列之七十三：ERROR: must be superuser to create FOR ALL TABLES publication	Debezium报错处理系列之七十三：ERROR: must be superuser to create FOR ALL TABLES publication
Debezium报错处理系列之七十四：com.microsoft.sqlserver.jdbc.SQLServerException: 对象名 ‘dw.cdc.lsn_time_mapping’ 无效	Debezium报错处理系列之七十四：com.microsoft.sqlserver.jdbc.SQLServerException: 对象名 ‘dw.cdc.lsn_time_mapping’ 无效
Debezium报错处理系列之七十五：WARN Cannot query the status of the SQL Server Agent : 拒绝了对对象 ‘server’ 数据库 'master’的 VIEW SERVER STATE 权限。	Debezium报错处理系列之七十五：WARN Cannot query the status of the SQL Server Agent : 拒绝了对对象 ‘server’ 数据库 'master’的 VIEW SERVER STATE 权限。
Debezium报错处理系列之七十六：errors.ConnectException: Tolerance exceeded in error handler	Debezium报错处理系列之七十六：errors.ConnectException: Tolerance exceeded in error handler
Debezium报错处理系列之七十七：Unable to find class io.debezium.storage.jdbc.history.JdbcSchemaHistory	Debezium报错处理系列之七十七：Unable to find class io.debezium.storage.jdbc.history.JdbcSchemaHistory
Debezium报错处理系列之七十八：Client SASL mechanism ‘SCRAM-SHA-256’ not enabled in the server, enabled mechanisms are [PLAIN]	Debezium报错处理系列之七十八：Client SASL mechanism ‘SCRAM-SHA-256’ not enabled in the server, enabled mechanisms are [PLAIN]
Debezium报错处理系列之七十九：Error registering AppInfo mbean javax.management.InstanceAlreadyExistsException	Debezium报错处理系列之七十九：Error registering AppInfo mbean javax.management.InstanceAlreadyExistsException
Debezium报错处理系列之八十：ERROR: requested WAL segment 0000000100000216000000DE has already been removed	Debezium报错处理系列之八十：ERROR: requested WAL segment 0000000100000216000000DE has already been removed
Debezium报错处理系列之八十一：PSQLException: ERROR: all replication slots are in use	Debezium报错处理系列之八十一：PSQLException: ERROR: all replication slots are in use
Debezium报错处理系列之八十二：Could not execute heartbeat action query…SQLException: No database selected	Debezium报错处理系列之八十二：Could not execute heartbeat action query…SQLException: No database selected
Debezium报错处理系列之八十三：heartbeat action query报错Column count doesn‘t match value count at row 1	Debezium报错处理系列之八十三：heartbeat action query报错Column count doesn‘t match value count at row 1
Debezium报错处理系列之八十四：cassandra数据库报错Caused by: org.apache.cassandra.exceptions.ConfigurationException: Invalid yaml. Those properties [thrift_prepared_statements_cache_size_mb	[Debezium报错处理系列之八十四：cassandra数据库报错Caused by: org.apache.cassandra.exceptions.ConfigurationException: Invalid yaml. Those properties thrift_prepared_statements_cache_size_mb
Debezium报错处理系列之八十五：cassandra数据库报错Invalid yaml. Please remove properties [start_rpc, rpc_server_type, rpc_port, thrift_framed_transport_size_in_mb, request_scheduler	[Debezium报错处理系列之八十五：cassandra数据库报错Invalid yaml. Please remove properties start_rpc, rpc_server_type, rpc_port, thrift_framed_transport_size_in_mb, request_scheduler
Debezium报错处理系列之八十六：cassandra数据库报错hints_directory is missing and -Dcassandra.storagedir is not set	Debezium报错处理系列之八十六：cassandra数据库报错hints_directory is missing and -Dcassandra.storagedir is not set
Debezium报错处理系列之八十七：cassandra数据库报错‘Unable to connect to any servers‘ Connection refused	Debezium报错处理系列之八十七：cassandra数据库报错‘Unable to connect to any servers‘ Connection refused
Debezium报错处理系列之八十八： Caused by: java.sql.SQLNonTransientConnectionException: Got timeout reading communication packets	Debezium报错处理系列之八十八： Caused by: java.sql.SQLNonTransientConnectionException: Got timeout reading communication packets
Debezium报错处理系列之八十九：Caused by: javax.script.ScriptException: org.apache.kafka.connect.errors.DataException: op is not a valid field name	Debezium报错处理系列之八十九：Caused by: javax.script.ScriptException: org.apache.kafka.connect.errors.DataException: op is not a valid field name
Debezium报错处理系列之九十：使用debezium消息过滤filter报错ClassNotFoundException: io.debezium.DebeziumException	Debezium报错处理系列之九十：使用debezium消息过滤filter报错ClassNotFoundException: io.debezium.DebeziumException
Debezium报错处理系列之九十一：Caused by: java.lang.NullPointerException: Cannot get property ‘s‘ on null object	Debezium报错处理系列之九十一：Caused by: java.lang.NullPointerException: Cannot get property ‘s‘ on null object
Debezium报错处理系列之九十二：io.debezium.DebeziumException: Error while attempting to read from change stream on ‘cmgo-7cq6t9fn_0’，Caused by: com.mongodb.MongoCommandException: Command failed with error 40415: ‘BSON field ‘$changeStream.fullDocumentBeforeChange’ is an unknown field.’ on server	Debezium报错处理系列之九十二：io.debezium.DebeziumException: Error while attempting to read from change stream on ‘cmgo-7cq6t9fn_0’，Caused by: com.mongodb.MongoCommandException: Command failed with error 40415: ‘BSON field ‘$changeStream.fullDocumentBeforeChange’ is an unknown field.’ on server
Debezium报错处理系列之九十三：设置东八区时区报错Invalid timezone format. Please specify either a geographic timezone	Debezium报错处理系列之九十三：设置东八区时区报错Invalid timezone format. Please specify either a geographic timezone
Debezium报错处理系列之九十四： javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake	Debezium报错处理系列之九十四： javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake
Debezium报错处理系列之九十五：Caused by: com.mysql.cj.exceptions.InvalidConnectionAttributeException: The server time zone value ‘?й???׼ʱ?’ is unrecognized or represents more than one time zone.	Debezium报错处理系列之九十五：Caused by: com.mysql.cj.exceptions.InvalidConnectionAttributeException: The server time zone value ‘?й???׼ʱ?’ is unrecognized or represents more than one time zone.
Debezium报错处理系列之九十六：The message is 388798167 bytes when serialized which is larger than 40960000	Debezium报错处理系列之九十六：The message is 388798167 bytes when serialized which is larger than 40960000
Debezium报错处理系列之九十七：The message is xxxx bytes when serialized which is larger than the total memory	Debezium报错处理系列之九十七：The message is xxxx bytes when serialized which is larger than the total memory
Debezium报错处理系列之九十八：io.debezium.DebeziumException: Supplemental logging not properly configured	Debezium报错处理系列之九十八：io.debezium.DebeziumException: Supplemental logging not properly configured
Debezium报错处理系列之九十九：Database table ‘ORCLPDB1.C##DBZUSER.TEST_TABLE’ not configured with supplemental logging	Debezium报错处理系列之九十九：Database table ‘ORCLPDB1.C##DBZUSER.TEST_TABLE’ not configured with supplemental logging
Debezium报错处理系列之第100篇：Redo logs may be sized too small using the default mining strategy, consider increasing redo log sizes to a minimum of 500MB.	Debezium报错处理系列之第100篇：Redo logs may be sized too small using the default mining strategy, consider increasing redo log sizes to a minimum of 500MB.
Debezium报错处理系列之第101篇：DebeziumException: Unable to find schema_only_recovery snapshotter	Debezium报错处理系列之第101篇：DebeziumException: Unable to find schema_only_recovery snapshotter
Debezium报错处理系列之第102篇：解决Flink CDC报错The db history topic or its content is fully or partially missing	Debezium报错处理系列之第102篇：解决Flink CDC报错The db history topic or its content is fully or partially missing

未完待续，博主会持续更新Debezium相关的技术文章，大家的支持是我不断创作的动力，欢迎与博主交流Debezium技术，一起加油。

• Debezium技术专栏
• 欢迎私信博主交流数据库和Debezium相关技术，如有需要可以私信加博主微信沟通交流技术