Re: Oracle Client not passing Windows Domain portion of connect info ?
Date: Thu, 18 Feb 2010 11:03:16 -0800
On Thu, Feb 18, 2010 at 10:34 AM, Taylor, Chris David < ChrisDavid.Taylor_at_ingrambarge.com> wrote:
> 1.) Well, the crux of the issue is that “Domain” isn’t being passed to
> the Oracle database from the client. The Oracle connect info is constructed
> of the following (when using OS Authentication): OS_AUTHENT_PREFIX,
> Domain/Machine Name, Username. Our db server does not have
> OS_AUTHENT_PREFIX set, yet my coworker beside me connects fine and his
> audited connection shows DOMAIN\Username. My INITIAL connection (1stattempt) fails, and shows Username only (instead of DOMAIN\Username).
Has the registry entry OSAUTH_PREFIX_DOMAIN been set on the DB server? if TRUE (default) then the domain name will be required to be part of the database account name
for OS authenticated accounts.
eg. the account name for a scott_at_somedomain.com would be SOMEDOMAIN\SCOTT
If set to FALSE then the oracle account name would be SCOTT. This is assuming that OS_AUTHENT_PREFIX is '' as you stated. If set to OPS$ then the account names would be OPS$SOMEDOMAIN\SCOTT and OPS$SCOTT respectively.
So on a Windows network using an OS authenticated account, the only way to
having an account name like SOMEDOMAIN\SCOTT is to explicitly set the registry
variable for Oracle OSAUTH_PREFIX_DOMAIN=FALSE.
At least in my experience anyway.
What are the actual account names in the database?
> 2.) This is a Windows AD network. Relevant to those who might have
> experienced similar issues on an AD network.
> It's only relevant for ORA-1017 if you are using OS authenticated accounts,
which is why I asked.
> 3.) The INITIAL connect means, I can type SQL> connect /_at_db_name and
> it fails, and then type SQL> connect /_at_db_name again and it works.
Yes, that is strange.
You may want to to set SQLnet admin and client tracing to level 16 and open an SR.Received on Thu Feb 18 2010 - 13:03:16 CST