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

pcroft wrote:
> Frank,
> Thank you for your reply.
>

>> How long did you  allow it to hang?

Ok - that's a hang, for sure.
(Some folks allow it 10, 15 seconds max, and sometimes it may take just that long for services to start)

[snip]

OK - as for what happens:
- the client (sql*plus) tries to open a session to the instance, using OS authentication. - that implies you should be logged on to the system, with the same account you installed Oracle with (that account "owns" the software, and thus the processes)
- that again, implies a local account, as during a reboot, when services start, network authentication may not be available (even the network may be down). Many windows sysadmins fail to see this point, and will install using network accounts.
- you do need administrative right on the machine.

As you have done installations before, also on Windows, this should not be unfamiliar to you.

The whole point is, there's not much to trace. 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?
- what happens when you try sqlplus /nolog and then connect / as sysdba?
- you could add sqlnet.trace_level_client=admin in sqlnet.ora and see if it results in any .trc files.

-- 
Regards,
Frank van Bortel

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