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@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Viktor Sent: Tuesday, December 08, 2009 9:11 PM To: oracle-l@xxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxx> wrote: From: Johnson, William L (TEIS) <WLJohnson@xxxxxxxxxxxxxxxxxxx> Subject: RE: Mistakenly changes db users passwords To: "robertgfreeman@xxxxxxxxx" <robertgfreeman@xxxxxxxxx>, "stant_98@xxxxxxxxx" <stant_98@xxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx> 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...