-
Bug
-
Resolution: Unresolved
-
Major
-
3.2.0.Final
-
None
-
False
-
-
False
-
Critical
PostgreSQL DB was converted from Oracle using AWS Schema Conversion Tool, and it has Oracle compatibility extensions installed. This created 40K+ custom types .
When I try to run Debezium, the connector gets stuck during startup because it's processing all of these types. The logs keep filling up with messages like:
WARN Type [oid:316992, name:some_oracle_type] is already mapped WARN Type [oid:337428, name:another_type] is already mapped
It's been churning on this for hours.
conversation link
Connector and Version
- Connector: io.debezium.connector.postgresql.PostgresConnector
- Debezium version: 3.2.0.Final
- Kafka version: 3.9.0
- JDK version: 17
Connector Configuration
{ "name": "dp-source-debezium-pg-ban2020-faismgr-rtvbgrp", "config":
{ "connector.class": "io.debezium.connector.postgresql.PostgresConnector", "database.hostname": "host.docker.internal", "database.port": "5433", "database.user": "postgres", "database.password": "****", "database.dbname": "ban2020", "database.server.name": "alen_postgres_ban2020_production", "plugin.name": "pgoutput", "slot.name": "debezium_pg_slot_ban2020_rtvbgrp", "table.include.list": "faismgr.rtvbgrp", "tombstones.on.delete": "true", "heartbeat.interval.ms": "10000", "poll.interval.ms": "30000", "tasks.max": "1", "topic.creation.enable": "true", "topic.prefix": "alen-pg-ban2020", "topic.creation.default.replication.factor": "2", "topic.creation.default.partitions": "1", "key.converter": "org.apache.kafka.connect.json.JsonConverter", "value.converter": "org.apache.kafka.connect.json.JsonConverter", "key.converter.schemas.enable": "false", "value.converter.schemas.enable": "false", "publication.name": "dbz_publication_ban2020", "publication.autocreate.mode": "filtered", "snapshot.mode": "initial", "include.unknown.datatypes": "true", "schema.include.list": "faismgr", "skip.messages.without.change": "true", "provide.transaction.metadata": "false", "message.key.columns": "faismgr.rtvbgrp:rtvbgrp_code", "transforms": "unwrap", "transforms.unwrap.type": "io.debezium.transforms.ExtractNewRecordState", "transforms.unwrap.drop.tombstones": "false", "transforms.unwrap.delete.handling.mode": "rewrite", "transforms.unwrap.add.fields": "op,ts_ms,source.ts_ms", "errors.tolerance": "all", "errors.log.enable": "true", "errors.log.include.messages": "true", "errors.deadletterqueue.topic.name": "dlq-alen-pg-ban2020-rtvbgrp", "column.propagate.source.type": ".*", "decimal.handling.mode": "double", "database.tcpKeepAlive": "true", "datatype.propagate.source.type": "aws_oracle_ext.rowid" }}
Captured Database Version and Deployment
- Database: Aurora PostgreSQL
- Engine version: 16.4
- Deployment: AWS Aurora (managed Postgres cluster)
Expected Behavior
- Connector should start successfully.
- Type registry should uniquely identify types by (namespace, typname, typmod) (or OID as fallback).
- Different namespaces with the same type name should not collide.
Actual Behavior
- Connector fails to start.
- Logs show repeated "Type is already mapped" warnings for Oracle compatibility types.
- Because Debezium ignores the namespace, multiple same-named types collapse into one, causing type registry conflicts and preventing task startup.
Logs (excerpt)
[2025-09-09 15:43:51,335] WARN [ban2020-optimized-postgres-connector|task-0]
Type [oid:553455, name:_agrakex] is already mapped (io.debezium.connector.postgresql.TypeRegistry:145)
[2025-09-09 15:43:51,336] WARN [ban2020-optimized-postgres-connector|task-0]
Type [oid:553456, name:agrakex] is already mapped (io.debezium.connector.postgresql.TypeRegistry:145)
[2025-09-09 15:43:52,012] WARN [ban2020-optimized-postgres-connector|task-0]
Type [oid:553464, name:agrakgt] is already mapped (io.debezium.connector.postgresql.TypeRegistry:145)
[2025-09-09 15:43:52,359] WARN [ban2020-optimized-postgres-connector|task-0]
Type [oid:553468, name:agrakpc] is already mapped (io.debezium.connector.postgresql.TypeRegistry:145)
... (repeated for other Oracle compatibility types)
Behavior on Latest Release
-
- Issue confirmed on 3.2.0.Final.
- Not yet tested with Alpha/Beta builds.
Steps to Reproduce
Deploy Aurora PostgreSQL 16.4 with Oracle compatibility extension enabled (creates thousands of compatibility types across schemas).
Configure Debezium Postgres connector (see config above).
Start the connector.
Task fails with type mapping warnings → connector never transitions to RUNNING.
- relates to
-
-
- Open
-
