RE: Service registration after listener restart
- From: D'Hooge Freek <Freek.DHooge@xxxxxxxxx>
- To: "mschmitt@xxxxxxxxxxxx" <mschmitt@xxxxxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 27 Jan 2011 21:03:11 +0100
Mike,
Since you are already on 11.2, I would suggest that you install grid
infrastructure for a standalone server (aka oracle restart).
This will allow you to use srvctl to register the database in the GI and to
specify services in the GI for that database. Roles can then be attached to
these services so they will for example only be started when the database has
the primary role.
regards,
Freek D'Hooge
Uptime
Oracle Database Administrator
email: freek.dhooge@xxxxxxxxx
tel +32(0)3 451 23 82
http://www.uptime.be
disclaimer: www.uptime.be/disclaimer
________________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx [oracle-l-bounce@xxxxxxxxxxxxx] On Behalf
Of Michael Schmitt [mschmitt@xxxxxxxxxxxx]
Sent: 27 January 2011 19:54
To: oracle-l@xxxxxxxxxxxxx
Subject: Service registration after listener restart
Hi All,
We have setup Dataguard with a physical standby running 11.2. We created a
service that we want to run on the primary for the users to connect to. We
have a system trigger that will register the service with the listener for the
primary after the database opens. I am registering the service with
dbms_service.start_service('<SERVICE>','<INSTANCE>')
This seems to work fine, but if the listener is ever shutdown and restarted,
the service will no longer be configured and we need to execute dbms_service
again.
Is there a way where I can get that service to run on the primary through a
listener restart? I was just going to write a script to monitor it, but was
wondering if there was a different way. I can't configure it in the
listener.ora since I do not want it to run if the database ever becomes the
standby.
Thanks,
Mike
--
//www.freelists.org/webpage/oracle-l--
//www.freelists.org/webpage/oracle-l
Other related posts:
