Re: SqlNet*2.1 Problems

In article <3bmj3p$5nn_at_piaget.moe.ac.sg> eio_at_moe.ac.sg (Jimmy Cheong) writes:

>Path: dcsun4.us.oracle.com!gatekeeper.us.oracle.com!decwrl!legato.com!news.Stanford.EDU!bloom-beacon.mit.edu!usc!howland.reston.ans.net!vixen.cso.uiuc.edu!news.uoregon.edu!ntuix.ntu.ac.sg!raffles.technet.sg!piaget.moe.ac.sg!eio
>From: eio_at_moe.ac.sg (Jimmy Cheong)
>Newsgroups: comp.databases.oracle
>Date: 2 Dec 1994 07:41:45 GMT
>Organization: Ministry of Education
>Lines: 32
>References: <1994Nov22.204408.15094_at_mprgate.mpr.ca>
>NNTP-Posting-Host: piaget.moe.ac.sg
>X-Newsreader: TIN [version 1.2 PL2]
>
>Mathew Tasalloti (tasallot_at_galaxy.mpr.ca) wrote:
>: SQL*Net 2.1 has been nothing but a headache since I installed it on
>: my PC. It not only stopped my client applications from being able
>: to access the server, but also does not allow me to use the
>: old convention of user/pwd_at_t:server:database.
>
>Did u install SQL*NET 2.1 in your server as well ? Incompatible SQL*NET
>versions can't interoperate with each other.

SQL*Net 2.1 uses a different syntax for the connect string - see your documentation for details. If you are using SQL*Net 1.0 on the server, you must upgrade the server to 2.0 or above.

Please note that support for 1.0 will be terminated in the near future, so it is probably in your best interest to use SQL*Net 2.1.

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