RE: Oracle Client not passing Windows Domain portion of connect info ?

From: Taylor, Chris David <>
Date: Thu, 18 Feb 2010 12:34:29 -0600
Message-ID: <>

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 (1st attempt) fails, and shows Username only (instead of DOMAIN\Username).

2.) This is a Windows AD network. Relevant to those who might have experienced similar issues on an AD network.

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. Strange.

HTH Chris Taylor
Sr. Oracle DBA
Ingram Barge Company
Nashville, TN 37205
Office: 615-517-3355
Cell: 615-354-4799

CONFIDENTIALITY NOTICE: This e-mail and any attachments are confidential and may also be privileged. If you are not the named recipient, please notify the sender immediately and delete the contents of this message without disclosing the contents to anyone, using them for any purpose, or storing or copying the information on any medium. From: Jared Still [] Sent: Thursday, February 18, 2010 11:34 AM To: Taylor, Chris David
Cc: oracle-l-freelists
Subject: Re: Oracle Client not passing Windows Domain portion of connect info ?

On Thu, Feb 18, 2010 at 9:20 AM, Taylor, Chris David <<>> wrote: Anyone know how the Oracle Client (10.2) passes the DOMAIN portion of the client info to the remote DB server?  It appears that my Oracle client (nor are passing the DOMAIN portion. I'm on an AD network.  I've turned on auditing and verified that the username passed in is "TAYLORCD" without the domain portion and receives ORA-01017 invalid username/password. Only the initial connect attempt experiences this behavior.

There really isn't enough information here to work with.

You mention AD for instance. How is that relevant? Is the Oracle account using OS authentication?

What does "Only the initial connect attempt experiences this behavior" actually mean. I can immediately think of at least two interpretations of this.

Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist Oracle Blog: Home Page:

Received on Thu Feb 18 2010 - 12:34:29 CST

Original text of this message