Re: SQL*NET error on remote connection attempt

An ORA-1017 would indeed be generated if the password were incorrect.

However, a 3113 is generated when the server dies and the SQL*Net connection is closed. I suggested in a private message to Mike that he check for core dumps and trace files on the server side.

If the protocol is not available, then a 6401 error would be generated.

To clear up a common misconception, Oracle always come with SQL*Net, either V1 or V2 or both.

                                    Rick
                                    Rick Wessman
				    Server Techologies - Network Products
				    Oracle Corporation
                                    rwessman_at_us.oracle.com

In article <Cottsz.18t_at_world.std.com> lparsons_at_world.std.com (Lee E Parsons) writes:

>Newsgroups: comp.databases.oracle
>Path: oracle!gatekeeper.us.oracle.com!decwrl!hookup!swrinde!cs.utexas.edu!howland.reston.ans.net!europa.eng.gtefsd.com!MathWorks.Com!news.kei.com!world!lparsons
>From: lparsons_at_world.std.com (Lee E Parsons)
>Organization: The World Public Access UNIX, Brookline, MA
>References: <1994Apr19.120918_at_suned1.nswses.navy.mil> <2pger1$oo4_at_blkbox.blkbox.COM>
>Date: Mon, 25 Apr 1994 17:55:46 GMT
>Lines: 25
>
>swhatley_at_blkbox.COM (Steven Whatley) writes:
>>grape_at_suned1.nswses.navy.mil (Mike Grapevine) writes:
>>
>>> sqlplus /_at_t:{SUN machine}:{SUN Oracle SID}
 

>>>ERROR: ORA-03113: end-of-file on communication channel
>>
>>If I remembor right, the OPS$ login only works if you are logged into the
>>system account that owns the Oracle account. When using SQL*Net you must
>>give the username and password. A '/' is not sufficant.
>
>This is true depending on how orasrv is setup but if that where the case
>here he would get an:
>
>ERROR: ORA-01017: invalid username/password; logon denied
>
>I think this is a case of Sqlnet Not being compiled into the oracle
>kernel.
>
>
>--
>Regards,
>
>Lee E. Parsons
>Systems Oracle DBA lparsons_at_world.std.com
Received on Tue Apr 26 1994 - 16:52:34 CEST