OEBS RA core agent to connect with primary / standby OEBS DB using 2 connection objects

Discussion created by Tran-Hoang_Hau_348 on Mar 16, 2017
This question has been asked so far.

Currently OEBS RA core agent is using a connection object to connect with primary OEBS DB instance. 
We are planning to create a ADG standby OEBS DB which will be in sync with primary OEBS DB instance and will be used in case of primary DB failure. All the existing triggers and objects created by OEBS RA core agent into primary OEBS DB will be copied to standby OEBS DB. 

To support the connectivity between OEBS RA core agent and standby OEBS DB instance, we will create another connection object for standby OEBS DB instance. In case of primary DB failure, we will just edit the OEBS RA core agent to use the 2nd connection object for standby OEBS DB. 

Please let us know if there is any product limitation for OEBS RA core agent to support connecting with standby OEBS DB for OEBS jobs scheduling. 


I would say there is no problem with other connection object (for standby DB), please remember to restart the agent each time you change the connection object.

On the other hand I would suggest to use the agent group, and you can control which agent should be used in your job