Re: How do I trace hanging "connect / as sysdba"?

DR wrote:
> > The network error is a ORA-12560: TNS:protocol adapter error.
> > This indicates a networking error where
> > in fact no network substrate is in use (no tcp/ip).
> > I demonstrate in the (partial) trace below.
>
> It says "protocol adapter error", reporting that an error occurred in the
> transport layer, not network error!
>
> > Some firewalls stop programs from acting as server. Check if
> > that's the case. Microsofts firewall just gets in, and starts
> > blocking without *any* conformation. Zonealarm will ask for
> > confomation and does block "outgoing" traffic.
>
> How could this be releated to your local bequeath/piped connection?
>
>
> Regards,
> Dimitre

w2k server was notorious for having issues with not supporting bequeath connections via terminal services.
w2k3 server supports bequeathed connections via an RDP session.

We still don't know how the OP is connecting to the server:

• locally on the server console
• locally via ssh
• remotely via vnc
• remotely via terminal services

Until that is known, everything else is just speculation. Posting a copy of the sqlnet.ora would certainly help, as well as the oradim.log, the alert log (someone has already asked for the listener.log above).

-bdbafh Received on Sat Feb 18 2006 - 12:02:24 CST