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.

LVL 2
CallumTAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

vishal68Commented:
One way of handling it can be to use two listeners on the primary site. One listener is the main trade_t listener on which the users login. Create another listener (maybe called trade_t2) and register the trade_t_xpt service with the new listener. This way during the SWITCHOVER, you can shutdown the trade_t listener, no user will be able to login, but keep the second listener (trade_t2) up and runnig, so that the logs can be shipped back to the new standby.

HTH
Vishal
 
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
CallumTAuthor Commented:
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.
0
vishal68Commented:
Local listener in the DG should point to the Secondary Listener

HTH
Vishal
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Oracle Database

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.