Re: connect with internal user in oracle 8.0.5

On Sat, 22 Dec 2007 11:37:13 -0800 (PST), EdStevens <quetico_man_at_yahoo.com> wrote:

>On Dec 22, 3:58 am, Frank van Bortel <frank.van.bor..._at_gmail.com>
>wrote:
>> EdStevens wrote:
>> > I remember there being an issue with connecting internal via Windows
>> > Terminal Services on older versions of Oracle (well, it would have to
>> > be an older version to have 'connect internal'). Check note MetaLink
>> > note 66397.1, and search MetaLink for 'terminal services'.
>>
>> Actually - terminal services messes with environment variables; it
>> does not always make the correct distinction between local (where
>> you run the remote terminal from - *your* workstation) and remote
>> environment variables.
>> --
>> Regards,
>> Frank van Bortel
>>
>> Top-posting is one way to shut me up...
>
>I don't remember that specific issue, but that could have been part of
>it. I do remember that there were problems supporting IPC protocol
>under Terminal Services with the particular version of Windows and
>Oracle I was dealing with at the time. You'd think I'd remember it
>better. I do remember having to present the issue several times to
>our management and SA's who were trying to push us into an unsupported
>configuration. I've just now tried searching MetaLink for the
>definitive documents I had thenk, but cant' find them

Remote Desktop doesn't support BEQueath. Set oracle_sid=<literal> implies BEQ.

The workaround is
- do not use Remote Desktop but Dameware or
- use
set local=<TNS Alias>

As far as I know this problem persists until this day.

-- 

Sybrand Bakker
Senior Oracle DBA