When you set SQLNET.AUTHENTICATION_SERVICES to NONE on SQLNET.ora file on windows you will get ORA-01031 when you try to connect with the strings belowfor SQL*Plus
| C:\Documents and Settings\cgundogar>sqlplus / as sysdba
SQL*Plus: Release 10.2.0.1.0 – Production on Cum Nis 27 10:47:42 2007Copyright (c) 1982, 2005, Oracle. All rights reserved.ERROR: C:\Documents and Settings\cgundogar>sqlplus /nolog SQL*Plus: Release 10.2.0.1.0 – Production on Cum Nis 27 10:48:00 2007 Copyright (c) 1982, 2005, Oracle. All rights reserved. idle> connect / as sysdba idle> connect “/ as sysdba” Enter password: ERROR: ORA-01017: invalid username/password; logon denied –password is not accepted Warning: You are no longer connected to ORACLE. |
for RMAN
| C:\Documents and Settings\cgundogar>rman target /
Recovery Manager: Release 10.2.0.1.0 – Production on Cum Nis 27 10:58:09 2007 Copyright (c) 1982, 2005, Oracle. All rights reserved.RMAN-00571: =========================================================== C:\Documents and Settings\cgundogar>rman Recovery Manager: Release 10.2.0.1.0 – Production on Cum Nis 27 10:58:12 2007 Copyright (c) 1982, 2005, Oracle. All rights reserved. RMAN> connect target /RMAN-00571: =========================================================== RMAN> |
To solve this problem you can must connectby giving valid username username and password
for SQL*Plus
| sys@XE> connect sys as sysdba Enter password: Connected. sys@XE> connect sys/passwd as sysdba Connected. sys@XE> connect sys@passwd as sysdba Enter password: Connected. sys@ORACOS> connect sys/passwd@oracos as sysdba –over listenerConnected. Connected. C:\Documents and Settings\cgundogar>sqlplus sys as sysdba SQL*Plus: Release 10.2.0.1.0 – Production on Cum Nis 27 11:08:57 2007 Copyright (c) 1982, 2005, Oracle. All rights reserved.Enter password:Connected to: sys@XE>exit C:\Documents and Settings\cgundogar>sqlplus sys/passwd as sysdba SQL*Plus: Release 10.2.0.1.0 – Production on Cum Nis 27 11:09:09 2007 Copyright (c) 1982, 2005, Oracle. All rights reserved. Connected to:Oracle Database 10g Express Edition Release 10.2.0.1.0 – Production C:\Documents and Settings\cgundogar>sqlplus sys/passwd@oracos as sysdba SQL*Plus: Release 10.2.0.1.0 – Production on Cum Nis 27 11:09:15 2007 Copyright (c) 1982, 2005, Oracle. All rights reserved. Connected to:Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 – Production |
for RMAN
| C:\Documents and Settings\cgundogar>rman
Recovery Manager: Release 10.2.0.1.0 – Production on Cum Nis 27 10:56:17 2007 Copyright (c) 1982, 2005, Oracle. All rights reserved.RMAN> connect target sys target database Password: RMAN> exit Recovery Manager complete. C:\Documents and Settings\cgundogar>rman Recovery Manager: Release 10.2.0.1.0 – Production on Cum Nis 27 10:56:17 2007 Copyright (c) 1982, 2005, Oracle. All rights reserved. RMAN> connect target sys/passwdconnected to target database: XE (DBID=2496353564) RMAN> exit Recovery Manager complete. C:\Documents and Settings\cgundogar>rman target sys Recovery Manager: Release 10.2.0.1.0 – Production on Cum Nis 27 10:56:28 2007 Copyright (c) 1982, 2005, Oracle. All rights reserved. target database Password: connected to target database: XE (DBID=2496353564)RMAN> exit Recovery Manager complete. C:\Documents and Settings\cgundogar>rman target sys/passwd Recovery Manager: Release 10.2.0.1.0 – Production on Cum Nis 27 10:56:38 2007 Copyright (c) 1982, 2005, Oracle. All rights reserved. connected to target database: XE (DBID=2496353564) |
Edit (03/07/2009) : Check also
Metalink Note ID:730067.1
Metalink Note ID:114384.1
Hi
very nice look to the blog. You will only be able to log on as sysdba with a password if you have set one up – using the orapwd utility. no passwordfile, no non os authenticated logons – which on windows means nts.
Comment by Niall Litchfield — May 29, 2007 @ 2:46 pm
Hi,
When I do connect target sys/passwd
I type any password, like passpwd, like senha, like anything.
Why can I put any password for user sys?
Comment by Tadeu — June 21, 2007 @ 6:57 pm
The password file needs to be created using orapwd with the file name as ‘orapw$ORACLE_SID’.
we need to export the oracle_sid, down the database, create the password file and bring up the database.
once db is up, check the v$pwfile_users. For ‘SYS’ user, the value should be TRUE, TRUE.
just say ‘rman target sys/xxx@targetsid’
you should be able to login.
I noticed, that even if the file name has lower case oracle_sid in the ORAPW file, the database wouldn’t pick up the value.
HTH
Comment by freebirds — August 28, 2007 @ 2:16 am
Hi,
It helped me a lot…
thanks a lot…
Comment by Ritesh — February 11, 2008 @ 2:12 pm
I have changed the sqlnet.ora and removed ‘none’ and I was able to connect. However, I get another error “ora-01506: missing or illegal database name” when shutdown and startup the database.
How can I sort this one out.
Thanks in advance
Comment by Munyendo — August 25, 2008 @ 12:49 pm
Hi
my ARCHIVELOG Mode in Configure Recovery Settings
is Disable Please Help Me.
Comment by shaho — September 25, 2008 @ 8:38 am
Tamam da, ben OS autentication yapmak istiyorum!
)
sen bana yapma demisin! bu cozum degildir ki!
seni Oguz abiye sikayet edecem!
Comment by Bekir Birden — December 17, 2008 @ 8:50 am
Thanks for the solution, it solved my problem!!!!
Comment by cepguill — January 21, 2009 @ 10:00 pm
Just a heads up for everybody:
There is a bug in SQLNET.AUTHENTICATION_SERVICES=NTS on Windows.
If the machine name and the user name are the same, then “sqlplus / as sysdba” will fail with ORA-12638 “credential retrieval failed” even if you’ve done all the other setup correctly (i.e., the user is a member of the local “ora_dba” group).
As my network guy explains it, when Oracle is querying Active Directory to authenticate the user, apparently it is not setting the appropriate flag to select just user accounts. Since the machine account is returned first(?) by Active Directory, the authentication fails.
Workaround is to change either the machine name or the user name. This is now recognized as an Oracle “feature” (Tech Note 782419.1). Probably won’t be fixed until at least 11.2.
Comment by Richard Holmes — May 1, 2009 @ 6:14 pm
Thanks a lot Team..
this really helped me sort out my issue..
Thanks for ur valuable support
Comment by Abdul Kalam Asath — June 29, 2009 @ 10:02 am
I thought I know, how to deal with orapwd, did it many times in different environment, but now on Linux I can’t get over ORA-01031: insufficient privileges, when login as sysdba.
I work on Oracle 10.2.0.1 on Linux.
Ican login local without password, but I can’t login remotely as sysdba.
I shutdown instance, recreate passwd liek this:
$ORACLE_HOME/bin/orapwd file=$ORACLE_HOME/dbs/pwkcub.ora password=’password’ force=y
- start instance
- sqlplus ‘sys@KCUB as sysdba’
Enter password:
ERROR:
ORA-01031: insufficient privileges
could have something to do with group for user ‘oracle’ ? he is memebr of oinstall as first group and dba as 2nd group !
thanks for any tip.
Comment by laode — July 3, 2009 @ 3:59 pm
Hi Laode
What is SQLNET.AUTHENTICATION_SERVICES parameter setting ?
It needs to be ALL
Comment by coskan — July 3, 2009 @ 4:15 pm
Hi coskan,
thanks for the tip, it looks like that the problem is in deed somewhere in the sql*net settings.
before I posted my 1st question, there was no sqlnet.ora at all, so I created on with only this entry:
NAMES.DIRECTORY_PATH=(TNSNAMES)
Now I added your hint:
SQLNET.AUTHENTICATION_SERVICES=(ALL)
and I get a different error:
ORA-12641: Authentication service failed to initialize
I intend to setup only a basic instance to become able to run other Oracle-gui-tools from windows-PC, but this requires remote login as sysdba.
laode
Comment by laode — July 3, 2009 @ 6:49 pm
Can you also try with NONE setting ?
http://arjudba.blogspot.com/2008/06/ora-12641-authentication-service-failed.html
Comment by coskan — July 3, 2009 @ 7:29 pm
i am creating an oracle DB manually on a Windows XP SP2 machine.
I have created the required SID(service) using, oradim command. I have also created the initialization parameter file in the default location.
$sqlplus /nolog
SQL>startup nomount;
ORA-01031: insufficient privileges
I am getting this error
. Please help
Comment by nagashree — November 19, 2010 @ 11:11 am
sqlplus /nolog
means you are not logged in
sqlplus / as sysdba
or
sqlplus sys as sysdba
means you are in logged in
Comment by coskan gundogar — November 19, 2010 @ 11:14 am
hai,
i have written a procedure on scott/tiger but at the compilation time i got error as insufficient privileges plz tell about how to solve it.
Comment by vijay — January 22, 2011 @ 3:18 pm