Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!samsung!munnari.oz.au!bruce!labtam!cnw01!nigel
From: nigel@cnw01.storesys.coles.oz.au (Nigel Harwood)
Newsgroups: comp.databases
Subject: SQL*NET Summary Of Responses
Message-ID: <1112@cnw01.storesys.coles.oz.au>
Date: 17 Oct 90 21:12:56 GMT
Organization: Coles Myer Ltd., Melbourne, Australia
Lines: 35

Thanks to those that replied to my request for information
about SQL*NET, following is a summary :

---------------

SQL*NET doesn't run on the transport layer but on the higher layers.
So it will run on TCP/IP (with whatever hardware/transport your hardware
vendor supports), on DECNET, on LU6.2, etc.

For SQL*NET to run on X.25, you need some protocol on top of it,
such as TCP/IP.

SQL*NET will allow a process on system-A to have a table(s)
open on system-A and system-B simultaneously.
But there is no way to do a commit concurrently on the two systems.

SQL*NET does not require NFS.

---------------

SQL*NET runs over TCP/IP and Towernet if you're using Unix V.2.

On V.3, it runs over TCP/IP for certain, I'm not sure about some of the
other options you mentioned.

SQL*NET does not require NFS, and in fact  Oracle specifically recommends 
that you not keep data base files on a remote NFS filesystem.  This
restriction is, I believe, due to concerns about reliability of disk writes.

---------------
-- 
<<<<<<<<<<<<<<<<<<<<<<<<<  Nigel Harwood  >>>>>>>>>>>>>>>>>>>>>>>>>>>
<< Post:  Coles Myer Ltd, PO Box 2000 Tooronga 3146, Australia     >>
<< Phone: +61 3 829 6090  E-mail: nigel@cnw01.storesys.coles.oz.au >>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>