Re: Force users to use Active DG for reporting
- From: Neil Chandler <neil_chandler@xxxxxxxxxxx>
- To: "ricard.martinez@xxxxxxxxx" <ricard.martinez@xxxxxxxxx>
- Date: Mon, 31 Mar 2014 18:18:27 +0100
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
Other related posts:
