sys can not logon as sysdba

I applied two patches to my base 8.1.6 (8i) last night to bring it to 8.1.6.3.8 Now, when entering the database I can't connect sys or internal as sysdba - only as normal. The error tells me that it is an invalid username or password but I can use the same username and password to connect as normal. What is the best way to remedy this? I am on a windows 2000 platform.

Quote:

---

Originally posted by ratfink
I applied two patches to my base 8.1.6 (8i) last night to bring it to 8.1.6.3.8 Now, when entering the database I can't connect sys or internal as sysdba - only as normal. The error tells me that it is an invalid username or password but I can use the same username and password to connect as normal. What is the best way to remedy this? I am on a windows 2000 platform.

---

Strange , what does contents of v$pwfile_users say?

try recreate the password file

I tried recreating the password file, rebooting but it didn't help. We have a DBA consultant that is comming in tonight. I will finish this thread tomorrow with the results. Thank you for your input.

While you're at it, did you try connecting as
connect internal/pwd@string as sysdba
That shud have worked.
Interesting note:
I ended up similarly with a rather unexplainable situation. I had a pwd veify fxn ran on my test db, after a certain period of time ,which was today i was prompted in my sql*plus to change pwd of user sys, so i did.
Now within the sql*plus i did again
connect sys/newpwd@string as sysdba
no luck!
then i did
internal/pwd@string as sysdba
ok!
and then i said hey let's try
connect sys/oldpwd@string as sysdba.
OK!!!?
I for now don't have a clue but i'll prod on..............;)

So far nothing has worked. Tried the v$pwfile_users and it returned no rows! Tried your connect internal trick - nada! Tried changing the internal password using oradim - nothing. Recreated the password file multiple times - rebooted - nothing! We are tearing our hair out now.... sys will logon fine as sysoper or normal but not sysdba. Internal can't logon as all. System still will work with normal. Any more ideas??? Nothing that I have gotten from metalink has worked.

Make sure that the parameter REMOTE_LOGIN_PASSWORDFILE is set to EXCLUSIVE?

Sanjay

We finally figured it out. Thank you everyone for your help. As you read this you will see how everyone's contribution fit in. We had the correct stuff - just the wrong order of things and I hadn't shut down the db and services. This is what we did and it worked - I have two sids that I had to do this with.

To change the password for “internal”
Stop the database and all services first.
at the command line:
Make sure you are in the correct SID by first typing
SET ORACLE_SID=
Then SET ORACLE_SID to make sure that it worked

oradim –edit –sid –intpwd

Also – while the services are still off – rename or remove the password file for the sid located in InstallDrive:/Oracle/Ora81/DATABASE.
at the command line (make sure that Oracle/Ora81/BIN is in path):

InstallDrive:/Oracle/Ora81/DATABASE /orapw file=PWD.ORA password= entries=5

Now check the init.ora file located in Oracle/Ora81/Admin/Orcl/pfile and make sure that remote_login_passwordfile=exclusive. Do not comment out.
Start up the database and all services.

To change the password for “sys”
In SQL*Plus :

Alter user sys identified by
Both the internal and sys password should be the same.

How much did you pay for this? I could have told you this for free.

Now you tell me!!! Tee Hee! It's alright, he was a good friend of mine

Hi, guys, I've got some questions on this topic.

First, why do you use ORAPWD to create a new password file and then alter sys user's password after that? Is it a duplicated job? I mean is it that doing either one can achieve the aim?

Second, you have more than one user in the password file. So when you create another password file for sys user, all the other user password information will be lost, right?

Third, what's the useage of oradim -edit -sid -intpwd command? What if I don't execute this command?

The ORAPWD is to set the password for internal, not sys. You change the sys password with the alter user command. I used the oradim to also set the internal password because I was having trouble getting it to work. The only password I had in my password file was for internal.

The Password Utility has nothing to do with SYS user . It's to create the SYSDBA's password . Note: Sysdba is different from DBA . It's much higher priviledge and basically he can do everything in the oracle ( shutdown , recovery etc )
DBA user's job scope is much narrow .

So SYSDBA's password is stored in password file and DBA's password is stored in the system table .

Only one password can be used . You have to delete the previous one I think .