Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!uwm.edu!wuarchive!usc!apple!uokmax!occrsh!occrsh.ATT.COM!srm From: srm@occrsh.ATT.COM Newsgroups: comp.databases Subject: Re: Using auto-login feature of Oracle Message-ID: <143900010@occrsh.ATT.COM> Date: 9 Dec 90 03:25:00 GMT References: <911@attc.UUCP> Lines: 36 Nf-ID: #R:attc.UUCP:-91100:occrsh.ATT.COM:143900010:000:1662 Nf-From: occrsh.ATT.COM!srm Dec 8 21:25:00 1990 On Dec 4, 1990, scolev@attc.UUCP writes: >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. >-- >SCOTT LEVIN >scolev@auto-trol.COM Auto-trol Technology Corporation >{...}ncar!ico!auto-trol!scolev 12500 North Washington Street >(303) 252-2865 Denver, CO 80241-2404 Yes, this is a problem that I have to deal with constantly. The problem turns out that "CONNECT /" causes the background oracle process to go to the operating system for info on your user id. No problem yet. When you attempt to connect through the network, the background oracle process must do the same thing (as before) __ONLY__ on the remote machine. Apparently, either the TCP driver "orasrv" spawns off your background process to run as "someone else" (probably root if orasrv runs under root user id) or it looks for an entry in /etc/utmp both of which are failing. The only work-around to this problem (that I and Oracle have found) is to connect via the following: CONNECT OPS$USERNAME/PASSWORD@T:machine_name:SID This will work although PASSWORD will have to be in source code. This creates a security problem! But it does work. -- Steven R. McMaster UNIX(R) mail: ...!uunet!att!occrsh!srm AT&T Network Systems Oklahoma City Works Any opinions expressed in the message above are srm@occrsh.att.com mine, and not necessarily AT&T's.