No question at this time
DBA Top 10
1 A. Kavsek 8600
2 M. Cadot 7000
3 B. Vroman 6100
4 T. Boles 5150
5 J. Schnackenberg 4100
6 P. Wisse 3000
7 T. P 1200
8 G. Lambregts 1100
8 . Lauri 1100
10 R. Pattyn 800
About
DBA-Village
The DBA-Village forum
Forum as RSS
as RSS feed
Site Statistics
Ever registered users48371
Total active users1539
Act. users last 24h2
Act. users last hour0
Registered user hits last week106
Registered user hits last month948
Go up

Unable to connect to database via Windows Level authentication
Next thread: Dataguard: Adding new standby on AWS
Prev thread: system schema object droped

Message Score Author Date
Hi everyone, I'm currently unable to connect to...... Gary Campbell Apr 16, 2019, 14:42
Hi Gary, Did you set, in your init.ora file the...... Score: 400 PtsScore: 400 PtsScore: 400 PtsScore: 400 PtsScore: 400 Pts Joël Péran Apr 16, 2019, 16:00
Hi Joel, Yes- it's set via SPFILE, but the valu...... Gary Campbell Apr 16, 2019, 16:37
Hi Gary, this is usually an OS issue. Of course...... Score: 200 PtsScore: 200 PtsScore: 200 PtsScore: 200 PtsScore: 200 Pts Ales Kavsek Apr 16, 2019, 18:43
Hi again, did you check what's written on th...... Score: 200 PtsScore: 200 PtsScore: 200 PtsScore: 200 PtsScore: 200 Pts Joël Péran Apr 19, 2019, 08:03
Hi Joel, The "Logon as User" is still set as Lo...... Gary Campbell Apr 24, 2019, 17:30
Hi Gary, did you try error stack tracing: <pre...... Ales Kavsek Apr 24, 2019, 18:46

Follow up by mail Click here


Subject: Unable to connect to database via Windows Level authentication
Author: Gary Campbell, Ireland
Date: Apr 16, 2019, 14:42, 33 days ago
Os info: Windows Server 2008 R2
Oracle info: 11.1.0.7
Error info: ORA-12631: Username retrieval failed
ORA-01017: invalid username/password; logon denied
Message: Hi everyone,

I'm currently unable to connect to a database via SQL*Plus or RMAN using windows-level authentication i.e.:

sqlplus / as sysdba
rman target /


I've checked the ora_dba group and the user who runs the Oracle Services (Local System account) is in that group, although I've tried removing/adding/rebooting to no avail.

The SQLNET.AUTHENTICATION_SERVICES was set to NTS, this resulted in a ORA-12631: Username retrieval failed error.

Is there anything else I can check to rule issues in/out?

Thanks
Gary
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: Unable to connect to database via Windows Level authentication
Author: Joël Péran, France
Date: Apr 16, 2019, 16:00, 33 days ago
Score:   Score: 400 PtsScore: 400 PtsScore: 400 PtsScore: 400 PtsScore: 400 Pts
Message: Hi Gary,

Did you set, in your init.ora file the variable REMOTE_LOGIN_PASSWORDFILE to EXCLUSIVE ?
Regards,
Joel
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: Unable to connect to database via Windows Level authentication
Author: Gary Campbell, Ireland
Date: Apr 16, 2019, 16:37, 33 days ago
Message: Hi Joel,

Yes- it's set via SPFILE, but the value for remote_login_passwordfile is EXCLUSIVE.

This won't have changed however- the network team have said they are aware of no AD changes etc., but we were able to authenticate fine until 2 days ago!
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: Unable to connect to database via Windows Level authentication
Author: Ales Kavsek, Slovenia
Date: Apr 16, 2019, 18:43, 33 days ago
Score:   Score: 200 PtsScore: 200 PtsScore: 200 PtsScore: 200 PtsScore: 200 Pts
Message: Hi Gary,

this is usually an OS issue. Of course, workaround of turning off NTS authentication is almost never acceptable.
Nowadays, I rarely hit the error (even in the past error rarely occurred on Windows Server OS, but regularly on XP)...the usual stuff that I did was:

1) check that time discrepancy between member server (on which Oracle is running) is not significant compared to AD DC servers (Kerberos auth. is time sensitive), sync clocks if necessary.

2) restart Oracle service and try login as sysdba with OS auth.

3) if 1 and 2 doesn't help you'll have to reboot Windows Server but with a twist. First change Oracle service starting type from Automatic to Manual. Reboot Windows Server and wait for a minute or two after you login as Admin, so that NTLM is up and running, then start Oracle service (and change Oracle service to start Automatically again).

If even #3 doesn't help, then something more serious happened (check when was the last time updates were applied to the OS, check AV sw logs if you have installed one, check System event log for authentication related errors...)

Regards,
Ales

Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: Unable to connect to database via Windows Level authentication
Author: Joël Péran, France
Date: Apr 19, 2019, 08:03, 30 days ago
Score:   Score: 200 PtsScore: 200 PtsScore: 200 PtsScore: 200 PtsScore: 200 Pts
Message: Hi again,

did you check what's written on this note from MOS : ORA-12631 SQLPLUS / AS SYSDBA (Doc ID 1421456.1)

The problem is caused by database service (in the service panel) Logon as user was changed from "Local System" to domain user "oracle@<domain>"

Ok ... It is related to Failsafe as well (which I am using in 12.1) :)

Regards,

Joel
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: Unable to connect to database via Windows Level authentication
Author: Gary Campbell, Ireland
Date: Apr 24, 2019, 17:30, 25 days ago
Message: Hi Joel,

The "Logon as User" is still set as Local System- Running out of things to check!

Thanks
Gary
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re: Unable to connect to database via Windows Level authentication
Author: Ales Kavsek, Slovenia
Date: Apr 24, 2019, 18:46, 25 days ago
Message: Hi Gary,

did you try error stack tracing:

sql> alter system set events '12631 trace name errorstack level 3; name library_cache level 10';
then try to reproduce the error by connecting:
connect / as sysdba

Check alert log file for the trace log file name and see if information from the error stack can help you.

You can turn off error stack tracing with:

sql> alter system set events '12631 trace name errorstack off; name library_cache off';

regards,
Ales
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here