Comments on: Act as if, temporarily in Oracle http://coskan.wordpress.com/2007/04/23/act-as-if-temporarily-in-oracle/ What I learned about Oracle Tue, 21 May 2013 01:33:22 +0000 hourly 1 http://wordpress.com/ By: Alter user identified by values on 11G without using SYS.USER$ « Coskan’s Approach to Oracle http://coskan.wordpress.com/2007/04/23/act-as-if-temporarily-in-oracle/#comment-3415 Wed, 11 Mar 2009 11:14:59 +0000 http://coskan.wordpress.com/2007/04/23/act-as-if-temporarily-in-oracle/#comment-3415 [...] table, so to change the password temporarily, it is not possible to use the way I explained here [...]

]]> By: coskan http://coskan.wordpress.com/2007/04/23/act-as-if-temporarily-in-oracle/#comment-22 Mon, 23 Apr 2007 21:26:14 +0000 http://coskan.wordpress.com/2007/04/23/act-as-if-temporarily-in-oracle/#comment-22 Thanks a lot for you comment Peter. I think the entry is really complete now

]]> By: Peter K http://coskan.wordpress.com/2007/04/23/act-as-if-temporarily-in-oracle/#comment-21 Mon, 23 Apr 2007 20:10:54 +0000 http://coskan.wordpress.com/2007/04/23/act-as-if-temporarily-in-oracle/#comment-21 It’s a known feature since at least v5 of Oracle. The only thing that I would caution is if you are attempting to lock up the SYS and SYSTEM accounts so that no one can get in w/o having to set a new password.

For example, alter user SYSTEM identified by values ‘Totally Secured’ will prevent anyone from hacking SYSTEM by any password guessing methods since the hashed value will never equal to ‘Totally Secured’. The only way then, is to reset the password if you need to use the SYSTEM account.

The caution is obviously to ensure that you do have another account that is given privilege to reset other users’ passwords otherwise if you set SYS and SYSTEM as above and you don’t have another account with privilege to reset the password, you are locked out of your db although you still can get in via the OS level with “connect / as sysdba” which is deprecated in 10g.

]]>