Re: Force users to use Active DG for reporting
- From: Andrew Kerber <andrew.kerber@xxxxxxxxx>
- To: neil_chandler@xxxxxxxxxxx
- Date: Mon, 31 Mar 2014 12:27:36 -0500
I would create a read only service accessible only on the standby, and
modify their tnsnames to connect to the RO service, and then setup typical
failover entry listing both servers, but specifying the RO service, so that
if for some reason the standby goes down they will connect to the primary
once you switch the service back. I wrote a trigger for this a couple of
times, basically if the database is open RW you start the rw service and if
it is open read only you start the RO service.
On Mon, Mar 31, 2014 at 12:18 PM, Neil Chandler
<neil_chandler@xxxxxxxxxxx>wrote:
> You could always write an on-login trigger which identifies the user
> logging on, checks against the db_unique_name and raises a nice exception
> if the user is in an inappropriate db.
>
> Don't kill them, just don't let them in with a nice raised error message
> telling them where they went wrong.
>
> Regs
>
> Neil Chandler
> @chandlerDBA
> >
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
--
Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'
Other related posts:
