Single OTD Node in SOACS Environment (Doc ID 2433480.1)

Last updated on DECEMBER 19, 2023

Applies to:

Java Cloud Service - Version N/A and later
Information in this document applies to any platform.

Goal

Qn1:Currently we run an architecture where we have a single OTD node in our production environment. We want to understand what would happen if that node failed e.g. underlying hardware failure, corruption, or just a general service issues. What is the maximum amount of downtime we could suffer, and how long would need to happen to bring the service back online?

Qn2:OTD---->SOACS Cluster---->DBCS RAC (Active Gridlink to DR)

He would like to know the best way to minimize downtime should they loose existing OTD node. Do we support, OTD Active/Passive failover, meaning create another OTD node and make a DNS change point to Passive node in the event of the failure of the Active node.

Solution

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Goal

Solution

References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

Single OTD Node in SOACS Environment (Doc ID 2433480.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!