Suggest an Idea

[Airbus]

Hello everyone,

Hope you're all fine.

Actually, Replicate is able to handle Oracle DB dataguard switches. We just need to create a connexion string following this pattern : 

(DESCRIPTION=(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=TCP)(HOST=primary_dataguard)(PORT=primary_dataguard_port))
(ADDRESS=(PROTOCOL=TCP)(HOST=secondary_dataguard)(PORT=secondary_dataguard_port))
)
(CONNECT_DATA=(SERVICE_NAME=<service_name>)))

This way, the task is able to connect to the first dataguard and switch to the second one if necessary.

But Replicate is unable to automatically switch the ASM instance between first and secondary dataguard.

As ASM is going to be a standard for us, we need it to be implemented to Replicate.

Actually, our workaround is a powershell script monitoring the tasks logs, and detecting the ASM errors. When an error occurs, we're able to change the connexion string and recover the data.

We already tried to build a connexion string with a similar pattern as DB connexion string (see above). The task works but the switch is not handled automatically.

In summary : 

We propose that Replicate implements a way to automatically switch the ASM dataguard instance to ensure the robustness and continuity of Oracle-ASM tasks.

Many thanks

Bastien

[bobvecchione]

We will review with R&D and report back as soon as we have feedback.

--bobv--

[DanielRuta]

Hello @Airbus & Bastien,

thank you for the insights.
We are facing the same problems.
We would like to see this solution be implemented in Replicate.
@bobvecchione Please consider that some customers would profit from this solution.

Thanks and regards
Daniel Ruta

[Meghann_MacDonald]

From now on, please track this idea from the Ideation portal. 

Link to new idea

Meghann

NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.