ORA-01031: insufficient privileges message

Hi

I have installed Oracle 9 and it has generated the initial db without any problems. The db is running but when I attempt to perform the following

sqlplus /nolog

connect / as sysdba
or
connect system/@DB AS systdba

I get the ORA-01031: insufficient privileges message.

I understand that this may be a groups issue but the Oracle9 user is assigned to the dba group although the Primary group is orainventory.

I have just investigated this further and can do a

conn sys/ as sysdba

I am missing something here. Apologies for the dumb questions but I haven't touched DBA work for 2-3 years so a little rusty !!

Kevin

authentication mode?

open your sqlnet.ora file and uncomment "SQLNET.AUTHENTICATION_SERVICES" parameter

Kevin
Check remote_login_passwordfile init.ora parameter.
If it is "exclusive", then u need to create a password file.
use the orapwd utility to create it
$orapwd file=orapwtest password=pwd entries=5
I suggest u create another user with DBA privileges and create the password file, and set the remote_login_passwordfile=exclusive.
SQL>create user dbmon identified by ...
SQL>grant connect, resource, dba, sysdba to dbmon;

Now on any client machine u can connect as sysdba.

c:\>>sqlplus /nolog
SQL>connect dbmon@ as sysdba
Enter password: -- enter the pwd
Connected.
SQL>

Hope this helps.

Quote:

---

Originally posted by nagarjuna
open your sqlnet.ora file and uncomment "SQLNET.AUTHENTICATION_SERVICES" parameter

---

There is no sqlnet.ora. I am doing that on the server.

Quote:

---

Originally posted by suhasd75
Kevin
Check remote_login_passwordfile init.ora parameter.
If it is "exclusive", then u need to create a password file.
use the orapwd utility to create it
$orapwd file=orapwtest password=pwd entries=5
I suggest u create another user with DBA privileges and create the password file, and set the remote_login_passwordfile=exclusive.
SQL>create user dbmon identified by ...
SQL>grant connect, resource, dba, sysdba to dbmon;

Now on any client machine u can connect as sysdba.

c:\>>sqlplus /nolog
SQL>connect dbmon@ as sysdba
Enter password: -- enter the pwd
Connected.
SQL>

Hope this helps.

---

remote_login_passwordfile=exclusive and of course I have the password file. And moreover, I am running the command on the server side.

Quote:

---

Originally posted by julian
There is no sqlnet.ora. I am doing that on the server.

---

What if u r doing on server.. sqlnet.ora has no role here?? .. :confused:

Quote:

---

Originally posted by abhaysk
What if u r doing on server.. sqlnet.ora has no role here?? .. :confused:

---

Gee, I answered the wrong thread. Sorry :-)

I had the following problem:

SQL> conn / as sysdba
Connected.
SQL> exec dbms_stats.gather_fixed_objects_stats('ALL');
BEGIN dbms_stats.gather_fixed_objects_stats('ALL'); END;

*
ERROR at line 1:
ORA-20000: Insufficient privileges to analyze an object in Fixed Ob
ORA-06512: at "SYS.DBMS_STATS", line 11802
ORA-06512: at "SYS.DBMS_STATS", line 12085
ORA-06512: at "SYS.DBMS_STATS", line 12599
ORA-06512: at line 1

SQL> select * from v$version;

BANNER
----------------------------------------------------------------
Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - 64bi
PL/SQL Release 10.1.0.2.0 - Production
CORE 10.1.0.2.0 Production
TNS for Solaris: Version 10.1.0.2.0 - Production
NLSRTL Version 10.1.0.2.0 - Production

What do you suggest??

Quote:

---

Originally posted by julian
What do you suggest??

---

Open a case with Oracle.. in metalink

Quote:

---

Originally posted by abhaysk
Open a case with Oracle.. in metalink

---

:-( Thanks. Never crossed my mind :-)

Quote:

---

Originally posted by abhaysk
What if u r doing on server.. sqlnet.ora has no role here?? .. :confused:

---

sqlnet.ora plays role if somebody is trying to connect to database using connect string (@dbname).

"NAMES.DIRECTORY_PATH" entry is used for all the cases that connect to database using connect string.

"SQLNET.AUTHENTICATION_SERVICES" is used for all those trying "connect as internal" in 8i or "connect / as sysdba" with a connect string.

Quote:

---

Originally posted by nagarjuna
sqlnet.ora plays role if somebody is trying to connect to database using connect string (@dbname).

"NAMES.DIRECTORY_PATH" entry is used for all the cases that connect to database using connect string.

"SQLNET.AUTHENTICATION_SERVICES" is used for all those trying "connect as internal" in 8i or "connect / as sysdba" with a connect string.

---

Which i know, so was the confused smile over ther ( for Julian's Post )