RE: Logical Standby
- From: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>
- To: <TaftD@xxxxxxxxxxx>, <Smith.Steven@xxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 8 May 2007 13:41:03 -0700
How about a logon trigger that checks the database name and if it's the
production database, automatically terminates their session?
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Taft, David
This means that in order to give a user access to the standby for
ad-hoc reporting, they must first be added to the primary. That night
their UserIDs get applied to the standby. At that point they are on
their honor not to run ad-hocs against the primary.
Privileged/Confidential Information may be contained in this message or
attachments hereto. Please advise immediately if you or your employer do not
consent to Internet email for messages of this kind. Opinions, conclusions and
other information in this message that do not relate to the official business
of this company shall be understood as neither given nor endorsed by it.
Other related posts:
