AWS RDS Oracle CDB support clarification for Debezium Oracle Connector with LogMiner
35 views
Skip to first unread message
Maf.K
May 11, 2026, 5:52:56 AM (2 days ago) May 11
to debezium
Hello Debezium team,
I would like to ask for a clear clarification regarding support for standard AWS RDS Oracle CDB with the Debezium Oracle Connector using LogMiner.
We are testing Debezium Oracle Connector against AWS RDS for Oracle 19c Standard Edition 2 in a CDB/PDB configuration, using the LogMiner adapter.
From the documentation and past forum discussions, my understanding is that in CDB mode Debezium requires access to both:
- the PDB context for the snapshot phase
- the CDB root context for the streaming phase
However, in standard AWS RDS Oracle CDB, it appears that the required root-container privileges cannot be granted in the same way as in self-managed Oracle environments. In our testing, this results in ORA-01031 errors when Debezium attempts operations that appear to require root-container level access.
Because the documentation includes AWS RDS-specific setup steps, it is difficult to determine whether those steps also apply to standard AWS RDS Oracle CDB, or whether they are intended only for non-CDB deployments.
Could you please clarify the following explicitly?
1. Is standard AWS RDS Oracle CDB officially supported by the Debezium Oracle Connector when using LogMiner for CDC streaming?
2. If yes, what is the exact supported setup and required grants/steps on standard AWS RDS Oracle CDB?
3. If not, is there any plan or roadmap to support AWS RDS Oracle CDB in the future?
4. If not, are there any recommended alternatives or workarounds for this use case?
A clear yes/no answer on current support status would be greatly appreciated so that we do not misunderstand the documentation.
Best regards,
I would like to ask for a clear clarification regarding support for standard AWS RDS Oracle CDB with the Debezium Oracle Connector using LogMiner.
We are testing Debezium Oracle Connector against AWS RDS for Oracle 19c Standard Edition 2 in a CDB/PDB configuration, using the LogMiner adapter.
From the documentation and past forum discussions, my understanding is that in CDB mode Debezium requires access to both:
- the PDB context for the snapshot phase
- the CDB root context for the streaming phase
However, in standard AWS RDS Oracle CDB, it appears that the required root-container privileges cannot be granted in the same way as in self-managed Oracle environments. In our testing, this results in ORA-01031 errors when Debezium attempts operations that appear to require root-container level access.
Because the documentation includes AWS RDS-specific setup steps, it is difficult to determine whether those steps also apply to standard AWS RDS Oracle CDB, or whether they are intended only for non-CDB deployments.
Could you please clarify the following explicitly?
1. Is standard AWS RDS Oracle CDB officially supported by the Debezium Oracle Connector when using LogMiner for CDC streaming?
2. If yes, what is the exact supported setup and required grants/steps on standard AWS RDS Oracle CDB?
3. If not, is there any plan or roadmap to support AWS RDS Oracle CDB in the future?
4. If not, are there any recommended alternatives or workarounds for this use case?
A clear yes/no answer on current support status would be greatly appreciated so that we do not misunderstand the documentation.
Best regards,
Chris Cranford
May 12, 2026, 9:56:41 AM (24 hours ago) May 12
to debe...@googlegroups.com
Hi -
I'm afraid we do not test Debezium against any managed database service provider, but you're right that with AWS RDS with a multitenant setup, the normal DBMS_LOGMNR package is not available, and so you are unable to stream changes without an ORA-01013 exception. When using RDS without a CDB setup, there should be no issue as the restricted-model is not applied there by AWS.
However, even if we patched Debezium to use the RDS-specific APIs for LogMiner, there is no guarantee there won't be other issues related to access to a variety of performance views (V$) that are required for Debezium to operate. In addition, the PDB model used by AWS directly contradicts the standard PDB used by non-AWS environments, so there would need to be extensive testing to verify that we don't break backward compatibility for non-RDS users, too.
I have raised a issue [1] about supporting AWS RDS with CDB deployments.
As for a workaround, are you in a position where you can use a non-CDB database or must it use CDB?
-cc
[1]: https://github.com/debezium/dbz/issues/1925
I'm afraid we do not test Debezium against any managed database service provider, but you're right that with AWS RDS with a multitenant setup, the normal DBMS_LOGMNR package is not available, and so you are unable to stream changes without an ORA-01013 exception. When using RDS without a CDB setup, there should be no issue as the restricted-model is not applied there by AWS.
However, even if we patched Debezium to use the RDS-specific APIs for LogMiner, there is no guarantee there won't be other issues related to access to a variety of performance views (V$) that are required for Debezium to operate. In addition, the PDB model used by AWS directly contradicts the standard PDB used by non-AWS environments, so there would need to be extensive testing to verify that we don't break backward compatibility for non-RDS users, too.
I have raised a issue [1] about supporting AWS RDS with CDB deployments.
As for a workaround, are you in a position where you can use a non-CDB database or must it use CDB?
-cc
[1]: https://github.com/debezium/dbz/issues/1925
Best regards, --
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/68c2c96b-05ae-47fe-ab7c-561a13c7ae84n%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages