-
Notifications
You must be signed in to change notification settings - Fork 297
RDSC-4297: Update RDI Oracle XStream setup steps and clarify them #2584
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
RDSC-4297: Update RDI Oracle XStream setup steps and clarify them #2584
Conversation
ZdravkoDonev-redis
commented
Dec 26, 2025
- I added a few very important notes in the SQL scripts
- I added the last step, without which nothing will work - actually making RDI to use the custom Debezium image.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR enhances the Oracle XStream setup documentation for RDI by adding critical setup instructions and clarifications. The updates ensure users can properly configure RDI to use custom Debezium images for Oracle XStream connectivity, which was previously missing and would prevent the setup from working.
Key changes:
- Added important SQL script comments warning users to check if
ARCHIVELOGmode is already enabled before executing database shutdown commands - Clarified that database commands should be run as
sysdbauser instead oforacleuser - Added the critical step 5 documenting how to configure RDI to use the custom Debezium image via the
rdi-operatorconfigmap
Comments suppressed due to low confidence (1)
content/integrate/redis-data-integration/data-pipelines/prepare-dbs/oracle.md:652
- The subsection is labeled "5.1. For VM installation" which implies there should be other subsections (e.g., 5.2 for other installation types), but no additional subsections are provided. Consider either removing the "5.1" numbering and just using a descriptive heading like "For VM installation:", or adding subsections for other installation types if they exist.
```bash
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
content/integrate/redis-data-integration/data-pipelines/prepare-dbs/oracle.md
Show resolved
Hide resolved
content/integrate/redis-data-integration/data-pipelines/prepare-dbs/oracle.md
Show resolved
Hide resolved
content/integrate/redis-data-integration/data-pipelines/prepare-dbs/oracle.md
Show resolved
Hide resolved
…es for RAC and non-CDB Oralce databases. Add FAQ section
andy-stark-redis
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ZdravkoDonev-redis I've implemented some fixes: the Copilot stuff, renumbering the sections, and replacing the ASCII art with Mermaid diagrams (AI finds these easier to parse). The text otherwise LGTM, but you might want to have a quick check that my changes are OK.