Re: Oracle 8.1.6 and Terminal Services on Windows 2000

In fact windows terminal services does work but does not support the bequeath (or IPC) protocol. What this means is that the command line utilities won't work if you try the old fashioned

set oracle_sid=<sid>
exp bla/blah etc.

they will however work if you issue

exp bla/blah@<tnsnames enty> and so on.

Having said all that it is usually better to either sit at the console or install a product like PC Anywhere.

--
Niall Litchfield
Oracle DBA
Audit Commission UK

Legal disclaimer required by my employer
****************************************************************************
**
This email contains information intended for the addressee only.
 It may be confidential and may be the subject of legal and/or professional
privilege.
Any dissemination, distribution, copyright or use of this communication
without prior permission of the addressee is strictly prohibited.
****************************************************************************
**
"Paul Moore" <paul.moore_at_uk.origin-it.com> wrote in message
news:d5o2ntsliuasoehml7v1cn48vep8t2u7ae_at_4ax.com...


> On Wed, 8 Aug 2001 03:09:17 +0200 , adamr1000_at_hotmail.com (Adam Rothberg)

> wrote:

>

> >I am running Oracle 8.1.7 on Windows 2000 Advanced Server.

> >When I open a Terminal Services session to the database server, I

> >cannot run any of the command line utilities.

> >

> >For example, via a Terminal Services session to the db server I get

> >the following output...

> >

> >E:\oracle>exp

> >

> >Export: Release 8.1.7.0.0 - Production on Tue Aug 7 21:00:07 2001

> >

> >(c) Copyright 2000 Oracle Corporation.  All rights reserved.

> >

> >

> >Username: manager

> >Password:

> >

> >EXP-00056: ORACLE error 12560 encountered

> >ORA-12560: TNS:protocol adapter error

> >EXP-00000: Export terminated unsuccessfully

> >

>

> It's a restriction. Read the release notes - there's a section on Windows

> Terminal Server, saying that that platform isn't supported. What's not

 100%


> clear (or at least it wasn't to me) was the fact that Terminal Services on

> Windows 2000 Server fall into this category, as well.

>

> Another nasty one is that if you try to shut down an OEM Management Server

> from the Services applet over Terminal Services, that locks up. There's a

> dialog box which appears on the console, but doesn't show over Terminal

> Services... (It took us *many* reboots before we found that one out...)

>

> Paul.

>