nigel@cnw01.storesys.coles.oz.au (Nigel Harwood) (10/16/90)
Can someone please provide some information regarding SQL*NET for ORACLE 6. Firstly, what transports can SQL*NET run over. i.e. X.25, Ethernet, Token Ring. Also can it handle one or more transports concurrently ? For example a system which is part of a TCP/IP over Ethernet LAN and an X.25 WAN. Will it allow a process on system-A to have a table(s) open on system-A and system-B simultaneously ? Can the remote table(s) be open for update ? Finally, someone mentioned that it required NFS, is this true ? Also, any other comments concerning this product would be appreciated. Regards -- <<<<<<<<<<<<<<<<<<<<<<<<< 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 >> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Ron_E_Wolf@cup.portal.com (10/22/90)
>Can someone please provide some information regarding >SQL*NET for ORACLE 6. > >Firstly, what transports can SQL*NET run over. > >i.e. X.25, Ethernet, Token Ring. > There's another question here, what systems do you wish to use SQL*Net over? For example, DOS SQL*Net can speak the three 'transports' you mention plus Async & IBM Coax. Actually, except in the case of Async, SQL*Net interfaces w/3rd party comm. packages such as FTP Software and so SQL*Net's capabilities are really the capabilities of the 3rd party package. >Also can it handle one or more transports concurrently ? > >For example a system which is part of a TCP/IP over Ethernet >LAN and an X.25 WAN. > Again, this is more a matter of the comm. support inherent in the system or 3rd party comm. package. >Will it allow a process on system-A to have a table(s) >open on system-A and system-B simultaneously ? > Yes. >Can the remote table(s) be open for update ? > Yes. But, be careful here. If Oracle distributed data base is involved, then update capabilities are not supported for all databases downstream of the distribution server. SQL*Net users look like clients, not distributed servers. >Finally, someone mentioned that it required NFS, is this true ? > Not necessarily, this is merely one of the comm. providers that is supported. >Also, any other comments concerning this product would be >appreciated. We've found this to be a good product. Fairly reliable and straight forward to use. Good range in terms of connectivity options. The APIs are the same whether using a local server or a remote server through SQL*Net. Good luck, Ron Wolf, Gupta Technologies, Menlo Park, CA US 415-321-9500