Re: I have the same problem, but why?

I don't believe Oracle SQL-net is the problem.

After having installed Oracle 8.1.7 and having created a database instance, I finally thought I could leave the noisy server room and finish my job from my own desktop.

I used to work with programs like VNC, Netop, PCAnywhere, Laplink but the customer didn't install one of these. Instead terminal server was available.
I opened my terminal client box, loggod on to the server (with the same account as I installed the software and created the databaseinstance) opened a command prompt and tried to start srvmgrl. But, no way to connect to the database. Afterwards I went back to the server room and doing exactly the same as with terminal client did work.

My conclusion: as DBA, don't use terminal server, install instead one of the REAL remote programs.

Bart

"Billy Verreynne" <vslabs_at_onwe.co.za> wrote in message news:<9k85sj$s12$1_at_ctb-nnrp2.saix.net>...
> Li Lin" <tb_lin_at_hotmail.com> wrote
>
>
> > I'm having exactly the same problem here, install Oracle on Win2K
> > using terminal service ... and finally 'ORA-12560: TNS:protocol
> > adapter error'. I think I've found the answer here that I need to
> > install locally, but why? What caused that error message?
>
> Oracle uses a software protocol adapter interface or layer, between actual
> protocol stack and the upper layers of the Oracle call interface. Much like a
> networking API (application programming interface) that sits between the
> protocol and the application software.
>
> In order for Oracle's SQL*Net to "access" the network (i.e. send and receive via
> the network), it needs to have a protocol adapter installed that provides the
> interface into whatever protocol stacks you have on that machine, e.g. IP, IPX,
> LU6, etc. Without a protocol adapter, Oracle on that platform can not use the
> network.
>
> The details on the error:
> 12560, 00000, "TNS:protocol adapter error"
> // *Cause: A generic protocol adapter error occurred.
> // *Action: Check addresses used for proper protocol specification. Before
> // reporting this error, look at the error stack and check for lower level
> // transport errors.For further details, turn on tracing and reexecute the
> // operation. Turn off tracing when the operation is complete.
>
> I think the suggested actions speak for itself. Turn on tracing (see the
> SQLNET.ORA file for details). You should also check the NT event log.
>
> Hopefully this one is easy to solve. I've run into some weird network bugs in
> the past with Oracle, though no real fault of Oracle, but problems in the
> operating system protocol stack (Unix) and network device drivers (Windows).
Received on Thu Aug 02 2001 - 09:51:02 CDT