asked on

Dataguard Configuration for XPT Services

Hi,
I am attempting to configure a Dataguard environment which utilises connect time failover, so during a Switchover scenario, clients are able to connect to the New Primary without the need for reconfiguring DNS or change TNSNAMES.ORA on client-side. However in doing so, we can't ship logs back to the Old primary (see below)

So, in the TNSNAMES.ora file we have :

TRADE_T.CONTACT-ENERGY.CO.NZ =
(DESCRIPTION =
(ADDRESS_LIST =
(FAILOVER=on) (LOAD_BALANCE=off)
(ADDRESS = (PROTOCOL = TCP)(HOST = trade_t)(PORT = 1563))
(ADDRESS = (PROTOCOL = TCP)(HOST = trade_t_stby)(PORT = 1563))
)
(CONNECT_DATA =
(SERVICE_NAME = TRADE_T.contact-energy.co.nz)
)
)

The idea being that during a SWITCHOVER situation we close the old Primary Listener, therefore closing all connections to the OLD Primary (trade_t). However, as the trade_t_xpt service has registered with the TRADE_T listener, it can't ship logs back from the new primary (trade_t_stby) to the new standby (trade_t).

The actual switchover (and failovers) are working fine.It's just that I want a configuration taht requires a change to DNS or mods to the client tnsnames.ora during any switchover.

ASKER CERTIFIED SOLUTION

vishal68

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

CallumT

ASKER

Thanks That did the trick. Although having a few issues with the DataGuard Broker, should the locallistener paremeter in a DG Database configuration point to the Main Listener or the Secondary (XPT) listener.

vishal68

Local listener in the DG should point to the Secondary Listener

HTH
Vishal