RE: Mistakenly changes db users passwords

From: Hostetter, Jay M <JHostetter_at_windstream.com>
Date: Thu, 10 Dec 2009 09:38:12 -0500
Message-ID: <D67EB7CEECD4334F9C85759227553BBC0E3D15D0_at_CL-EXCHANGE1.dande.com>

Glad to see that the flashback query worked. Another thing that would have come in handy would be an export. You could imp with show=y to get all your create user statements, which would have the encrypted password.  

Jay

---

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Viktor Sent: Tuesday, December 08, 2009 9:11 PM To: oracle-l_at_freelists.org
Subject: RE: Mistakenly changes db users passwords  

This worked perfectly. Thanks to all!

And, Robert, you're totally right about being a nice guy!

• On Tue, 12/8/09, Johnson, William L (TEIS)
  <WLJohnson_at_tycoelectronics.com> wrote:
  

From: Johnson, William L (TEIS) <WLJohnson_at_tycoelectronics.com> Subject: RE: Mistakenly changes db users passwords To: "robertgfreeman_at_yahoo.com" <robertgfreeman_at_yahoo.com>, "stant_98_at_yahoo.com" <stant_98_at_yahoo.com>, "oracle-l_at_freelists.org"
<oracle-l_at_freelists.org>

Date: Tuesday, December 8, 2009, 8:24 PM

Why wouldn't you just simply run a flashback query against dba_users to gather their password values at a point-in-time prior to your oops? You could create a temp table with the data and then do the updates from there...

create table my_dba_users tablespace mytablespace as select * from dba_users as of timestamp to_timestamp('2007-07-30 06:30:00', 'YYYY-MM-DD HH24:MI:SS'); <-- fill in your own time here...          

--
http://www.freelists.org/webpage/oracle-l

Received on Thu Dec 10 2009 - 08:38:12 CST