Oracle connection string with primary & Secondary database details in Devtest

Products

• Service Virtualization

Issue/Introduction

Our team is planning to migrate the DB data to Cloud Exadata services. But requested that applications to be able to switch over from Primary and Secondary DB in case of DB is switched over. 

Is there any mechanism that we can leverage for Oracle DB's ?

For their application, they are getting 2 DB instances with separate connection strings for primary and backup. Primary will get replicated with backup. And during pathing activities, the primary will be switched from one site to another, then application should be able to connect to backup on timeout on primary connection.

In Devtest, currently using the below connection string format:

jdbc\:oracle\:thin\:@//<hostname>\:1521/<DB_name>

 

Can we use below connection string in Devtest to avoid changes in Devtest when there is a database failover?

jdbc:oracle:thin:@(DESCRIPTION=
  (ADDRESS_LIST=
    (LOAD_BALANCE=OFF)
    (FAILOVER=ON)
    (ADDRESS=(PROTOCOL=TCP)(HOST=<primary-host.local>)(PORT=1521))
    (ADDRESS=(PROTOCOL=TCP)(HOST=<standby-host.local>)(PORT=1521))
  )
  (CONNECT_DATA=
    (SERVICE_NAME=<service_name>)
  )
)

Environment

Devtest 10.8.4

Oracle 19c

Resolution

DevTest uses JDBC to commnicate with Database. In this case, the underlying Oracle JDBC driver should support such a configuration and you can modify the connection string with primary and secondary server details.