Printable View
I just took over this database about 2 weeks ago and it's been a big mess. Any way, I have a quick question, I try to bounce this database but I have no password for INTERNAL when I tried to log in through SVRMGRL. this is Oracle 8.1.6.0.0
I have the password for SYSTEM so I tried to log in as SYSTEM from SVRMGRL and I tried to shutdown the database and it's telling me that Insufficient privileges.
Please let me know any other way to shutdown this database and startup.
Thanks
You can only connect as internal if you are logged on as an administrator in NT or part of the DBA group in Unix.
I am sorry, but I am not clear. Please help!!!
so you are saying that I can't connect INTENRAL if I am not an administrator ??? So I need to the admin guy give me the administrator privilege to log in ???
Please help
First of all can you say which OS are you using ? If it is unix, then all u need to do is login as oracle user.
I'm not sure if you can do much unless you know the sys/internal password when on NT.
Yes Mike,
If you are running NT, then your logon account must be a system administrator. So you either need the admin logon OR your network administrator can give YOUR username admin priviledges.
Then connect internal will not ask for a password. (in my experience)
If you are running on UNIX then like vinit says, logon as Oracle. Or YOUR logon name must be added to the DBA group. Your unix administrator can do this.
Either way it's your OS user account that doesn't have the privileges you need.
Can someone help me to understand why sometime when I connect INTERNAL@SVRMGRL, it does not ask me for password and sometimes it does ???
I still have problem with the issue above. please correct me if I am wrong, so if I am logged in windows as a administrator I should log in the database with INTERNAL user with no problem ???
Please help me understand.
If you're running on Windows, you can change the Internal password. Here is what you need to do:
1) get the exact path of the pwd.ora file (i.e:pwddata.ora)
2) Using command line, type
ORAPWD FILE=PASSWORD= ENTRIES=
For example:
orapwd file=e:\oracle\ora81\database\pwddata.ora password=oracle entries=5
I ran into this problem a week ago while working on a client's database whose DBA did not want to give out the Internal pswd. I found this on Metalink and it took care of the problem.
Try it yourself. Good luck.
John
Can you be a little clear on this, I am confused
sorry and thanks for your help, what is entries=5 for
I did try it but it gave me this error
OPW-00005: File with same name exists - please delete or rename
Please advise
[Edited by mike73 on 11-01-2001 at 05:59 PM]
first delete the default pwd file and thn recrete it.
that it.
you will be able to connect internal
First delete the existing file then it will allow u to create the new file.
entries=5 means atmost u can give 5 users sysdba privileges.
by default it is only with internal.
to give the privilge to a user say mike
create a database use mike . the using internal
sql> grant sysdba to mike;
so next time u can log in as
sqlplus mike/as sysdba
then u will be able to startup and shutdown database as mike also
entries=5 means other than internal any 4other users can be given sysdba privilege
regards
Amit Tandon
Because of your OS permissions.Quote:
Originally posted by mike73
Can someone help me to understand why sometime when I connect INTERNAL@SVRMGRL, it does not ask me for password and sometimes it does ???
Read my previous
If your an admin you won't get asked.
Hi Mike:
Sorry for the late response. Like Saurabh said, first thing to do is to delete the existing pwd.ora file. Most of the time, this file is found under the 'drive:\oracle\ora81\database\' path. For example, if the the database is Oracle, you would see the pwd file as 'drive:\oracle\ora81\database\pwdoracle.ora'. A note of caution, however. Please make a copy of this file first using simple Copy/Paste command.
Once you delete this file, create a new pwd file using the afore-mentioned command. i.e:
orapwd file=C:\oracle\ora81\database\pwdoracle.ora password=newpsd entries=pick a number.
The 'entries' option is optional. When I did mine, I did not include this option yet it worked out fine.
Let's give it a try and good luck.
John
NT or Unix? Sometimes how? On NT you can regulate this via sqlnet.ora. In Unix, if you are in the DBA group, you will not be prompted for a password.Quote:
Originally posted by UNIX DBA
Because of your OS permissions.Quote:
Originally posted by mike73
Can someone help me to understand why sometime when I connect INTERNAL@SVRMGRL, it does not ask me for password and sometimes it does ???
Read my previous
If your an admin you won't get asked.
Hi Mike:
One more thing I forgot to include. My answer is based on the assumption that you're running on NT. And yes you have to log in as administrator user to that local machine (server) in order to change the pwd file (and creating a new Internal pswd.)
I hope this helps. Good luck.