Skip to content
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

Feature: create agent to run on database host #102

Open
bersler opened this issue Jan 28, 2024 · 3 comments
Open

Feature: create agent to run on database host #102

bersler opened this issue Jan 28, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@bersler
Copy link
Owner

bersler commented Jan 28, 2024

Is your feature request related to a problem? Please describe.
In some environments it is not possible to provide external access to database redo log files. Running OpenLogReplicator on the database host is not an option. It is however possible to run a small agent that would just push the redo log files to an external location.

Describe the solution you'd like
Create a small agent that would just read database redo log files in real time and copy them so some external location. On that location OpenLogReplicator could be running and reading them and processing in real time.

Describe alternatives you've considered
Running OpenLogReplicator on the database host which is sometimes not possible. Connecting to the database host using SSH which is also sometimes not possible.

Additional context
This option could allow greater adoption of OpenLogReplicator.l

@bersler bersler added the enhancement New feature or request label Jan 28, 2024
@bersler
Copy link
Owner Author

bersler commented Jan 28, 2024

This feature is complicated to implement.. If there is a demand from users more focus could be given here.

@marlon-costa-dc
Copy link

Regarding the feature request to create an agent capable of operating on the database host, I'd like to propose an alternative approach that could simplify the implementation and enhance compatibility across different infrastructure configurations. Instead of developing an agent to externally transfer redo log files, why not leverage the native connection interfaces of the Oracle database to access the archive log files directly?

Utilizing a directory object within Oracle itself or accessing directly via the ASM instance are feasible techniques that could allow for efficient file reading. This approach would simplify data transfer and pave the way to support more complex topologies in the future, such as Grid Infrastructure and Oracle RAC. I believe this solution could offer significant flexibility and potentially ease implementation challenges, aligning with the needs of users facing restrictions on direct access to redo log files.

Given the importance of adapting OpenLogReplicator to diverse environments and the current limitations on external file access, this proposal could represent an important step towards a more universal and accessible solution. I am open to discussing this possibility further and exploring how this integration could be technically achieved, aiming to maximize the adoption of OpenLogReplicator across a wider range of scenarios.

@bersler
Copy link
Owner Author

bersler commented Jan 28, 2024

Thank you very much @marlon-costa-dc for a valid point. Indeed this is a must have for any cdc source replication tool. But this approach is different and deserves a separate ticket. I have created #103.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants