RE: Logical Standby
- From: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>
- To: "Taft, David" <TaftD@xxxxxxxxxxx>, <Smith.Steven@xxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 9 May 2007 11:37:03 -0700
In that case, you could write the trigger to automatically prompt them
for a new password, modify it - and then terminate their session.
________________________________
From: Taft, David [mailto:TaftD@xxxxxxxxxxx]
Unfortunately, the users still have to log onto the primary to alter
their expired passwords.
From: Allen, Brandon
How about a logon trigger that checks the database name and if it's the
production database, automatically terminates their session?
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:
