I had tried to suggest in my previous email also that you need to work with your password file. Save your current password file with a different name and create a new one with orapwd utility and the password that you will mention in this new file would become the sys password when connect as sysdba.
Besides, try pay attention to this. There is a file that oracle creates when oracle is installed. In this file oracle keeps a record of the oracle user and oracle group for os authentication purpose. When you connect as internal it is assumed that you are connecting with the os authentication permissions. Now, think of a situation (this is realistic - I have gone through it) in which the database is copied from one machine to another by way of copying the files physically including the password file in $ORACLE_HOME/dbs [in unix] directory. The name of this file in windows might be $ORACLE_HOME/database - I am not sure. But either of the two informations, namely oracle user or oracle group is different on the machine where the database is being copied. You are likely to have a problem with your sysdba password here. If possible to know what was the original oracle user and/or oracle group in original database then you can create that group and user in the current environment also and come out of your problem. If it is not possible to get this information for you then you need to resort to the first suggestion of making the new password file. Try paying attention to what name you are giving to the new password file. Keep it as close to original naming as possible.
Use following as the syntax for making new password file:
orapwd file=<fname> password=<password> entries=<users>
Or, type orapwd help in your $ORACLE_HOME directory. The above command is from unix. In windows I think it will show you a few extra parameters than 3. Make sure you keep the entries parameter high to 3 at least. The password that you will mention here would become the password for sys and system when connecting as sysdba.
I hope this will help you. Good luck,
Gurmohan
www.freemath.info - The ultimate tool for learning and teaching math.
-----Original Message-----
From: Chris Wrigley
[mailto:oracledba-ezmlmshield-x77475851.[Email address protected]
Sent: Wednesday, August 31, 2005 6:31 AM
To: LazyDBA Discussion
Subject: Re: Permissions issue for SYS connect as sysdba on Windows 2000
Server?
Sorry, this still does not resolve this problem.
I tried without the quotes and had the same problem, insufficient privileges.
As someone else privately suggested, I tried exporting the SID (using "set" as we're in windows here), but no cookie.
Anyone have any other ideas? I'm out of options here!
Thanks for any help.
>>> "Chris Wrigley " <oracledba-ezmlmshield-x99032990.[Email address protected] 30/08/2005 12:26 >>>
Can any of you bright sparks help me out with this legacy database I've just acquired.
Some background:
1. It's on a Windows2000 Server.
2. I am a member of the Administrators Group (has control over ORA_DBA group)
3. I am connecting via Proxy Master.
So I open up SQLplus on the server (from Proxy Master), knowing that I'm an Admin and should be able to connect ok...
SQL> connect sys/foopwrd
Connected.
SQL> connect 'sys/foopwrd as sysdba'
Enter password:
Enter password:
ERROR:
ORA-01005: null password given; logon denied
Warning: You are no longer connected to ORACLE.
--- Huh? It's asking me for a password? But I'm in the administrators group on Win2000!!
SQL> connect sys/foopwrd
Connected.
SQL> show parameter password;
NAME TYPE VALUE
------------------------------------ ------- ----------
remote_login_passwordfile string SHARED
SQL> select * from v$pwfile_users;
USERNAME SYSDB SYSOP
------------------------------ ----- -----
INTERNAL TRUE TRUE
SYS TRUE TRUE
SQL> connect internal
Enter password: ********
Connected.
SQL>
Okay, so I'm lucky I can connect as internal because the "DBA" left the password something simple, even though I should be able to connect as internal without a password, right?
My problem is, I *cannot* recreate the password file because the application software connects internally to the DB.
My question: How can I reset SYS to connect as sysdba without:
1. recreating the password file.
2. changing from "shared" to "exclusive"
Thanks to any bright person who can help me out here.
Chris.
---------------------------------------------------------------------------
This email and any attachment(s) is intended for and confidential to the
addressee. If you are neither the addressee nor an authorised recipient
for the addressee please notify us of receipt, delete this message from
your system and do not use, copy or disseminate the information in, or
attached to it, in any way.
Our messages are checked for viruses but please note that we do not accept
liability for any viruses which may be transmitted in or with this message.
---------------------------------------------------------------------------
The College of Law of England and Wales. Registered charity No 271297
---------------------------------------------------------------------------
--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com
By using this list you agree to these terms:http://www.lazydba.com/legal.html
Oracle LazyDBA home page