Re: Force users to use Active DG for reporting
From: Neil Chandler <neil_chandler_at_hotmail.com>
Date: Mon, 31 Mar 2014 18:18:27 +0100
Message-ID: <BLU0-SMTP193F4D5DED643739808E8E685630_at_phx.gbl>
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.
Date: Mon, 31 Mar 2014 18:18:27 +0100
Message-ID: <BLU0-SMTP193F4D5DED643739808E8E685630_at_phx.gbl>
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
_at_chandlerDBA
>
-- http://www.freelists.org/webpage/oracle-lReceived on Mon Mar 31 2014 - 19:18:27 CEST