| Insufficient privileges when using SYSDBA,SYSOPER connect [message #97389] |
Tue, 09 April 2002 12:14  |
sheela
Messages: 66
Registered: March 2002
|
Member |
|
|
Hi,
I've been working with oracle for quite a while. I've oracle 8.1.6 and 8.1.7 and having trouble because sometimes you have to login as 'SYSDBA' or 'SYSOPER' instead of 'NORMAL' to get some jobs done.
However everytime I tried to logon to the database as SYSDBA or SYSOPER I get an error "Insufficient privileges". I'm using system/manager logon and password for this. If I try 'NORMAL' connect, it works (I mean, I can logon, but I cannot do certain jobs). Why do I get this error? How to avoid that? Please Help!.
Thx
Paul
|
|
|
|
| Re: Insufficient privileges when using SYSDBA,SYSOPER connect [message #97390 is a reply to message #97389] |
Tue, 09 April 2002 12:43  |
Grant
Messages: 578
Registered: January 2002
|
Senior Member |
|
|
Basically you need to look at the remote_login_passwordfile (initSID.ora parameter) and the orapwd command for unix.
In a nutshell when I create a database I set remote_login_passwordfile = exclusive and run orapwd (on one line):
orapwd file=/oradb/kham/u1/app/oracle/product/8.1.7/dbs/orapwdev password=manager entries=10
file parameter is required and has to go in $ORACLE_HOME/dbs (full path as shown) in the format orapwSID. When you change the SYS password this also changes the INTERNAL password. This forces oracle to look if this schema has SYSDBA or SYSOPER and it matches the password in the password file (external) and lets them in. I do not use OS authentication. If you have any further problems check out the oracle docs.
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
