If this still doesn't solve the issue then try paying attention to the passward file that may have been created with orapwd utility and it might have a changed password for the sysdba account for system. I think if this would be the case then you will need to create a new password file with a new password.
Gurmohan
www.freemath.info - The ultimate resource for teaching and learning math.
-----Original Message-----
From: Salee Chris
[mailto:oracledba-ezmlmshield-x27256789.[Email address protected]
Sent: Tuesday, August 30, 2005 8:34 AM
To: LazyDBA Discussion
Subject: RE: Permissions issue for SYS connect as sysdba on Windows 2000
Server?
connect sys/foopwrd as sysdba. Leave out the single quotes.
-----Original Message-----
From: Chris Wrigley
[mailto:oracledba-ezmlmshield-x99032990.[Email address protected]
Sent: Tuesday, August 30, 2005 6:27 AM
To: LazyDBA Discussion
Subject: Permissions issue for SYS connect as sysdba on Windows 2000
Server?
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
--------
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