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

DR wrote:

>> Usually, this fails with network errors (there's
>> no networking involved, but anyway), which indicate
>> services are not started.
>> Or with authorization failures, indicating you use
>> a different account, or you have sqlnet.ora wrong.
>> Just "hangs" are rare... Some thoughts:
>> - firewall?
> 
> "no networking involved, but anyway" -> "sqlnet.ora" -> "firewall"?
> 
> Could you elaborate?
> 
> Regards,
> Dimitre 
> 
> 

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.

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.

sqlnet.ora trace_level_client will show the *attempt* to set up a connection, in case of services not being started, you will see this:

[18-FEB-2006 16:54:00:640] snlpcss: Unable to spawn Oracle oracle
(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq))) db920, error 2.
[18-FEB-2006 16:54:00:640] sntpcall: exit
[18-FEB-2006 16:54:00:640] ntpcon: exit
[18-FEB-2006 16:54:00:640] nserror: nsres: id=0, op=65, ns=12560, ns2=0;
nt[0]=530, nt[1]=2, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0
[18-FEB-2006 16:54:00:640] nsopen: unable to open transport
[18-FEB-2006 16:54:00:640] nsmfr: 1632 bytes at 0x14eb5d0
[18-FEB-2006 16:54:00:640] nsmfr: 536 bytes at 0x14eb3a8
[18-FEB-2006 16:54:00:640] nladget: entry
[18-FEB-2006 16:54:00:640] nladget: exit
[18-FEB-2006 16:54:00:640] nsmfr: 212 bytes at 0x14ea098
[18-FEB-2006 16:54:00:640] nladtrm: entry
[18-FEB-2006 16:54:00:640] nladtrm: exit
[18-FEB-2006 16:54:00:640] nioqper: error from nscall
[18-FEB-2006 16:54:00:640] nioqper: ns main err code: 12560
[18-FEB-2006 16:54:00:640] nioqper: ns (2) err code: 0
[18-FEB-2006 16:54:00:640] nioqper: nt main err code: 530
[18-FEB-2006 16:54:00:640] nioqper: nt (2) err code: 2
[18-FEB-2006 16:54:00:640] nioqper: nt OS err code: 0

Does that answer your questions?

-- 
Regards,
Frank van Bortel

Top-posting is one way to shut me up...