Path: utzoo!attcan!uunet!peregrine!elroy.jpl.nasa.gov!ncar!ico!attc!toncha
From: toncha@attc.UUCP (Tony Chang)
Newsgroups: comp.databases
Subject: Using auto-login feature of Oracle
Message-ID: <912@attc.UUCP>
Date: 5 Dec 90 20:19:11 GMT
Reply-To: toncha@auto-trol.COM ()
Organization: Auto-trol Technology, Denver
Lines: 86

In article <911@attc.UUCP> Scott Levin writes:
|> ----- News saved at 4 Dec 90 22:05:57 GMT
|> I am trying to use the auto-login feature of Oracle in
|> combination with SQL*NET. Without SQL*NET the following
|> connect command works fine.
|>
|>         CONNECT /
|>
|> However, as soon as I add the syntax to access Oracle across
|> a Sun network, I am unable get the auto-login feature to work.
|>
|> Following are the two commands I used when trying to connect across
|> the network.
|>
|>          CONNECT /@T:oracle_server:TEST_DB
|>
|>          ERROR: ORA-01017: invalid username/password; logon denied
|>
|>          CONNECT / @T:oracle_server:TEST_DB
|>
|>          ERROR: ORA-01005: null password given; logon denied
|>
|>
|>
|> Has anyone had any success in using the auto-login feature
|> of Oracle in conjunction with SQL*NET. The versions of Oracle
|> RDBMS, SQL*Plus, and SQL*NET I am using are V6.0.26.8.1,
|> Version 3.0.6.1.1, and Version 1.1.4 respectively.
|>
|>


This is to follow up the problem Scott is having with the
auto-login feature of ORACLE.

Our environment is as the following:

	SUN Sparc station 1
	SUN OS 4.1
	Ethernet - TCP/IP
	ORACLE RDBMS 6.0.26.8.1
	ORACLE SQL*Plus 3.0.6.1.1
	ORACLE SQL*Net TCP/IP 1.1.4

Our ORACLE setup is as the following:

	oracle_server is the host name of the ORACLE server.
	oracle_client1 is the host name of the ORACLE client.
	TEST_DB is the ORACLE system id.
	user1 is a SUN OS user account.
	OPS$user1 is created by ORACLE DBA with the password 
	user1password for automatic login purposes.

The problem was that when connecting TEST_DB on oracle_server
as auto-login account OPS$user1, it worked fine. However, while
connecting from a client node as the same account, it did NOT.

	I've logged on "oracle_server" as user1,

	SQL> CONNECT /

	SQL> CONNECT OPS$user1/user1password

	Both of the above commands worked fine.


	I've logged on "oracle_client" as user1,

	SQL> CONNECT /@T:oracle_server:TEST_DB

	SQL> CONNECT OPS$user1/user1password@T:oracle_server:TEST_DB

	The first command did not work while the second one did.

I was wondering if anyone who has a similar setup could try the 
same commands and find out if this is an ORACLE bug. I have heard
that they work on VAX/VMS and DEC/ULTRIX platforms.

I would like to thank Dale Cook who replied to Scott's original
request. Dale's response has inspired some thoughts that lead to
a clearer picture of thie problem. Thanks a lot!

I would like to use this feature in PRO*C applications eventually. 
If anyone has information about this problem and potential traps
on PRO*C development, I would appreciate you send them to either
me or Scott through E-mail.