| ORA-01031: insufficient privileges [message #69278] |
Mon, 03 December 2001 02:10  |
Io Gemeni
Messages: 1
Registered: December 2001
|
Junior Member |
|
|
When I try to connect as sysdba to a oracle 8.1.7 database from a client I get following error:
SQL> connect system@lem as sysdba
ERROR:
ORA-01031: insufficient privileges
but from sqlplus on the server I can connect as sysdba.
Were could be the problem?
I have the following os groups on the server:
dba,osdba,osoper,osinstall.
Oracle user is part of dba,osdba,osinstall,osoper groups.
Thank you!
----------------------------------------------------------------------
|
|
|
|
| Re: ORA-01031: insufficient privileges [message #69279 is a reply to message #69278] |
Mon, 03 December 2001 03:32  |
Chella
Messages: 25
Registered: September 2000
|
Junior Member |
|
|
I found this somewhere thought might help you;
"You need to give the execute privilege on DBMS_SQL directly to the user. If it is given through role then oracle does not allow to execute this package."
HTH
Chella
----------------------------------------------------------------------
|
|
|
|
| Re: ORA-01031: insufficient privileges [message #69281 is a reply to message #69278] |
Mon, 03 December 2001 05:04 |
Suresh Vemulapalli
Messages: 624
Registered: August 2000
|
Senior Member |
|
|
check init.ora parameter values of REMOTE_LOGIN_PASSWORDFILE
select name,value from v$parameter
where name like 'remote_login_p%';
value should be NONE if you want to access from remote machine.
----------------------------------------------------------------------
|
|
|
|
| Re: ORA-01031: insufficient privileges [message #69430 is a reply to message #69278] |
Fri, 04 January 2002 09:04 |
Varad Cancheepuram
Messages: 1
Registered: January 2002
|
Junior Member |
|
|
Hi ,
This solution is one of the possibilities.
If you have used ORADIM or ORAPWD to create a new password file then by default the new password file was created for SYS and INTERNAL.
So check v$pwfile_users, only SYS and INTERNAL will available.
So granted the privilies to SYSTEM too.
GRANT SYSDBA TO SYSTEM;
GRANT SYSOPER TO SYSTEM;
Now try after connecting using connect internal;
Select * from v$pwfile_users;
You will find entry for SYS,SYSTEM and INTERNAL with SYSDBA and SYSOPER priviliges to TRUE.
Hope this may help.
Regards,
Varad
----------------------------------------------------------------------
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
