Re: TWO_TASK

From: Lloyd E Vancil <lev_at_ipxed5.nswses.navy.mil>
Date: 8 Mar 93 17:05:34 GMT
Message-ID: <27368_at_suned1.Nswses.Navy.MIL>


In article <1993Feb16.043613.6976_at_oracle.us.oracle.com> rmanalac_at_oracle.com writes:
>
>The TWO_TASK environment variable is a Unix specific variable used
>by Oracle to append a database connect string to the end of a
>username/password combination. When it is not set, it defaults
>to 'P:' and uses the pipe driver protocol to connect to a local
>database as specified by the ORACLE_SID environment variable.
>
>If this variable is set to something like 'T:hostname:SID' then
>the command "sqlplus scott/tiger" is automatically interpreted
>as "sqlplus scott/tiger_at_T:hostname:SID" and one is connected to
>the SID database on hostname via SQL*Net TCP/IP.
>

An additional little tidbit.. In the unix world if you have a mix of users, some remote and some windowing the server where Oracle lives, this parameter must be tested an enabled or disabled as necessary.

For example, as dba I access sqldba over an rsh session to the server. In that login I do not need TWO_TASK. While as myself I access the Oracle application from my desktop worksation, during this use I need TWO_TASK. The solution is a simple test in the .cshrc file for the user that goes like this:

setenv TWO_TASK T:server:SID

if ( `hostname` == server ) then

        unsetenv TWO_TASK
endif

--
|suned1!lev_at_elroy.JPL.Nasa.Gov|lev_at_suned1.nswses.navy.mil|sun!suntzu!suned1!lev|
|S.T.A.R.S. The revolution has begun!|  My Opinions are Mine mine mine hahahah!|
Received on Mon Mar 08 1993 - 18:05:34 CET

Original text of this message