| 
		
			| Reset SYS Account [message #611331] | Tue, 01 April 2014 11:44  |  
			| 
				
				|  | papertiger Messages: 22
 Registered: March 2014
 Location: MD
 | Junior Member |  |  |  
	| To make a long story short -- we change passwords on the sys, system and about 4 other accounts that we have in our Oracle 10g DB.  I changed the password on all of the accounts (had to include "" around the password), but now I'm unable to log on with any of them due to an incorrect password or ID.  I'm basically looking for any other option to log onto the db via sqlplus and change the sys password without logging in. 
 What I've already done:
 checked to make sure my domain account is in the ora_dba group
 altered the sqlnet.authentication_services = (NTS)
 already tried to logon with sqlplus / as sysdba (ORA-01031: insufficient privileges.) even with sqlplus /nolog
 
 I haven't tried deleting the pwd file -- didn't look as if it would've made a difference for me....
 
 Is there any type of back door when unlocking the sys account?
 
 can I restore the db from an RMAN backup to reset the password?
 
 Any help would be greatly appreciated.
 
 |  
	|  |  | 
	| 
		
			| Re: Reset SYS Account [message #611333 is a reply to message #611331] | Tue, 01 April 2014 11:51   |  
			| 
				
				
					| John Watson Messages: 8989
 Registered: January 2010
 Location: Global Village
 | Senior Member |  |  |  
	| I would log on to Windows as a local user (not with a domain account) who is in the ORA_DBA group, and then try Please can you show (with copy/paste) what happens happens when you do. Also, show what happens when you try to connect as another user, such as SYSTEM. |  
	|  |  | 
	|  | 
	|  | 
	|  | 
	|  | 
	| 
		
			| Re: Reset SYS Account [message #611340 is a reply to message #611338] | Tue, 01 April 2014 13:19   |  
			| 
				
				
					| John Watson Messages: 8989
 Registered: January 2010
 Location: Global Village
 | Senior Member |  |  |  
	| OK, your IP address does suggest that you need to be careful. The output of WHOAMI is not right. I think each group should be prefixed with the name of the machine, for instance. Is what you have transcribed what you actually see?
 
 One suggestion: set some environment variables explicitly before attempting to connect, like this:
 
 c:\users\john>
c:\users\john>set ORACLE_HOME=c:\app\oracle\product\12.1.0\dbhome_1
c:\users\john>set PATH=%ORACLE_HOME%\bin;%PATH%
c:\users\john>set ORACLE_SID=orclz
c:\users\john>sqlplus / as sysdba
SQL*Plus: Release 12.1.0.1.0 Production on Tue Apr 1 19:16:07 2014
Copyright (c) 1982, 2013, Oracle.  All rights reserved.
Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
orclz>
 You have still not shown how you attempted to log on a SYSTEM. Can you provide the exact command?
 
 |  
	|  |  | 
	|  | 
	|  | 
	| 
		
			| Re: Reset SYS Account [message #611360 is a reply to message #611349] | Tue, 01 April 2014 15:53   |  
			| 
				
				|  | papertiger Messages: 22
 Registered: March 2014
 Location: MD
 | Junior Member |  |  |  
	| C:\Documents and settings\sys>whoami /all 
 USER INFORMATION
 
 
 user Name	           SID
 =============              ===================================
 <servername>\sys           XXXXXXXXXXXXXX
 
 
 GROUP INFORMATION
 
 Group Name                                   Type               Attributes
 Everyone                                     well-known group   Mandatory group, enabled by default, enabled group
 <servername>\ora_dba                         Alias              Mandatory group, enabled by default, enabled group
 Builtin\administrators                       Alias              Mandatory group, Enabled by default, enabled group, group owner
 Builtin\users                                Alias              Mandatory group, enabled by default, enabled group
 NT authority\Remote Interactive Logon        Alias              Mandatory group, enabled by default, enabled group
 NT Authority\Interactive                     well-known group   Mandatory group, enabled by default, enabled group
 NT Authority\Authenticated Users             well-known group   Mandatory group, enabled by default, enabled group
 NT Authority\This Organization               well-known group   Mandatory group, enabled by default, enabled group
 Local                                        well-known group   Mandatory group, enabled by default, enabled group
 NT Authority\NTLM Authentication             well-known group  Mandatory group, enabled by default, enabled group
 
 PRIVILEGES INFORMATION
 
 Privilege Name                 Description                                  State
 
 SeChangeNotifyPrivilege        Bypass traverse checking                     Enabled
 
 SeBackupPrivilege              back up files and directories                Disabled
 
 SeRestorePrivilege             change the system time                      Disabled
 
 SeSystemTimePrivilege          change the system time                      Disabled
 
 SeShutdownPrivilege            shut down the system                        Disabled
 
 SeTakeOwnerShipPrivilege       Take ownership of files or other objects    Disabled
 
 SeSystemEnvironmentPrivilege   Modify firmware environment va1ues          Disabled
 
 SeSystemProfilePrivilege       Profile system performance                  Disabled
 
 SeProfilesingleProcessPrivilege Profile single process                      Disabled
 
 SeIncreasesBasePriorityPrivilege Increase scheduling priority               Disabled
 
 SeLoadDriverPrivilege            Load and unload device drivers             Disabled
 
 SeCreatePagefilePrivilege        Create a page file                         Disabled
 
 SeIncreaseQuotaPrivilege         Adjust memory quotas for a process         Disabled
 
 SeUndockPrivileg                 Remove computer from docking station       Disabled
 
 SeManageVolume Privilege         Perfomr volume maintenance tasks           Disabled
 
 SeImpersonatePrivilege           Impersonate a client after authentication   Enable
 
 SeCreateGlobalPrivilege           Create global objects                       Enable
 
 
 
 
 
 
 |  
	|  |  | 
	|  | 
	| 
		
			| Re: Reset SYS Account [message #611378 is a reply to message #611360] | Wed, 02 April 2014 01:53   |  
			| 
				
				
					| John Watson Messages: 8989
 Registered: January 2010
 Location: Global Village
 | Senior Member |  |  |  
	| Well, the whoami output looks fine. If your environment variables are right and your OS permissions are right and NTS is enabled in your sqlnet.ora and the service is running under a local system account (it is, isn't it?) then it should work. The only remaining suggestion I have is to delete the Windows service for the instance, and create a new one (use the oradim.exe utility for this). Failing that, install a new Oracle Home and use that to create a service and open the database.
 Perhaps someone else has an idea.
 
 [Updated on: Wed, 02 April 2014 01:57] Report message to a moderator |  
	|  |  | 
	|  | 
	|  | 
	|  | 
	|  | 
	|  | 
	|  | 
	|  | 
	|  | 
	|  | 
	|  |