you are not hitting a limitation with running two connectors against the same Oracle database. The problem happens because Kafka Connect is timing out during configuration validation.

When you create a connector, the Connect worker performs a full validation step. It tries to connect to the Oracle database and also checks access to Kafka or Event Hubs for the internal schema history topic. If either of these steps is slow or unreachable from the worker, the REST request times out even though the worker is still running the validation in the background.

To fix this, check that the Connect worker can reach both Oracle and the Kafka or Event Hubs endpoints from its network environment. Make sure database service names, listeners, and firewall rules are correct. Also confirm that the schema history topic can be created or accessed with the credentials provided.

If validation still takes too long, you can increase the timeout values for the schema history operations.

When running more than one connector against the same Oracle database, make sure each connector uses a unique topic prefix and its own schema history topic name. This prevents conflicts between connectors and ensures each instance maintains separate metadata.

In short, the timeout does not mean you cannot run multiple connectors. It only indicates that validation could not complete due to a slow or blocked network path. Once connectivity and timeouts are adjusted, the second connector will register normally.