Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: How do I trace hanging "connect / as sysdba"?

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

From: Frank van Bortel <frank.van.bortel_at_gmail.com>
Date: Sat, 25 Feb 2006 13:46:46 +0100
Message-ID: <dtpirt$kf3$1@news2.zwoll1.ov.home.nl>


pcroft wrote:
> Here's a summary of what I've found so far:
> The server is running W2k sp4, and I installed the software for Oracle
> 9.2
> Active Directory is NOT installed.
> I am logged on as a local OS user who is in groups Administrators and
> ORA_DBA.
> With SQLNET.AUTHENTICATION_SERVICES= (NTS) in sqlnet.ora
> sqlplus "/ as sysdba" hangs,
> but with sqlnet.authentication_services=(none)
> sqlplus "sys/CHANGE_ON_INSTALL as sysdba" works.
>

You change two things at once here. Try both "/ as sysdba" and "sys/pswd as sysdba" with authentication_services=NTS. Both ought to work.
Only "sys/pswd as sysdba" should work with with authentication_services=none (or remotely - not the case).

It merely suggests the installation was done not as local admin, and verification of the ORA_DBA group fails against some domain.

> When I put TRACE_LEVEL_SERVER=support into sqlnet.ora I got some
> interesting output
> in the trace file:
> The Bequeath protocol is mentioned; I know this can be a problem with
> w2k

What do you mean - there *no* problem with bequeath connecttions on w2k.

> [21-FEB-2006 12:12:30:015] nioqper: error from niotns: nsaccept
> failed...
> [21-FEB-2006 12:12:30:015] nioqper: nr err code: 0
> [21-FEB-2006 12:12:30:015] nioqper: ns main err code: 12637
> [21-FEB-2006 12:12:30:015] nioqper: ns (2) err code: 12537
> [21-FEB-2006 12:12:30:015] nioqper: nt main err code: 0
> [21-FEB-2006 12:12:30:015] nioqper: nt (2) err code: 0
> [21-FEB-2006 12:12:30:015] nioqper: nt OS err code: 0

12637, 00000, "Packet receive failed"

// *Cause:  A process was unable to receive a packet from another process.
//          Possible causes are:
//          1. The other process was terminated.
//          2. The machine on which the other process is running went down.
//          3. Some other communications error occurred.
// *Action: If the cause is not obvious, contact Oracle Customer Support.

oerr tns 12537
12537, 00000, "TNS:connection closed"
// *Cause: "End of file" condition has been reached; partner has disconnected.
// *Action: None needed; this is an information message.

But, as your problem is solved, we'll leave it here. You can connect sys/pswd as sysdba, and startup, shutdown, migrate, upgrade and create the database.

-- 
Regards,
Frank van Bortel

Top-posting is one way to shut me up...
Received on Sat Feb 25 2006 - 06:46:46 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US