Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> Re:SQLNet V1 issue to support Dynacomm 16-bit app.

Re:SQLNet V1 issue to support Dynacomm 16-bit app.

From: <Val_Gamerman/>
Date: Wed, 28 Jun 2000 09:28:34 -0400
Message-Id: <>


Did you actually get it to work on a Win'95 machine? When you say you were using the "client32" DOS drivers what do you mean?

The only reason I am asking is that the only way we could get it to work was on a DOS machine (Win 3.1). I did not try to hard setting it up on Win'95 pretty much because I assumed that a DOS application will not have a way of using a 32 bit IP stack.

Please shed the light on this as I would like to move all this Win'95.


To:       Multiple recipients of list ORACLE-L <>
cc:        (bcc: Val Gamerman/Victoria Financial)
From:     "Eric D. Pierce" <> @ NOTES NET
Date:     06/28/2000 02:14:06 AM GMT

Subject: Re:SQLNet V1 issue to support Dynacomm 16-bit app.

FWIW, don't forget that Oracle's extended memory manager for DOS ("sqlpme.exe") is also required (NOT COMPATIBLE WITH A DOS BOX IN WIN9x!!!).
Ahhh, remember the "good old days" when you had to fit your network drivers and all that sh*t into 640K RAM? Anyways, per the appended SQL*Net v2-lite documentation, the TCP/IP vendors supported are:

OWS>                a) FTP
OWS>                b) Novell
OWS>                c) PCNFS

(we used it with Novell's "client32" DOS drivers and Netware 3.1x) example connect string syntax:
OWS>                SQLFORMS SCOTT/TIGER_at_t: -C BIOS
have fun,

> ... I believe Oracle (somewhere in the deep dark back room)
> may have a version of SQL*Net V2 Lite that may save your bacon. Whether
or not
> it will support your protocol may be a sticky point. I've a copy
> for TCP/IP but it required a specific vendors TCP stack to work.

Return-path: <>
Date: Tue, 09 Sep 1997 10:29:14 -0600
Organization: Oracle WWS Networking
Content-Disposition: inline; filename="readme.txt"
                          SQL*NET V2-Lite
        SQL*NET is the Oracle communications component that allows you to
        share information stored in different ORACLE databases. With
        SQL*NET, you can run an ORACLE tool or another application on one
        machine and be able to find, manipulate, and store data in an
        database located on another machine.
        SQL*NET also allows applications to connect to multiple ORACLE
        databases across a network, using a variety of communication
        protocols and application program interfaces (APIs) to establish
        a distributed processing and distributed database environment.
        For more information on SQL*NET please refer to SQL*NET TCP/IP
        User's Guide version 1.2.

        DOS users till now had the option of using SQL*NET V1. The
        advantages of SQL*NET V2 server of ORACLE ( Ver 6 & Ver 7 )
        were not available due to the constraints of the operating system
        itself. To get around the problem of memory limitations of DOS,
        SQL*NET V2-Lite has been developed.
        SQL*NET V2-Lite gives you the flexiblity to connect to SQL*NET V1
        server as well as to SQL*NET V2 server, with added advantages.
        SQL*NET V2-Lite is a scaled down version of SQL*NET V2. It is
        essentially a SQL*NET V1 client simulating SQL*NET V2 client.
        While the features of SQL*NET V2 like Auto-Detection are now
        available through SQL*NET V2-Lite, multi-protocol support provided
        by SQL*NET V2 is not available due to the limitations of the
        operating system.

  1. Connecting to SQL*NET V2 server
  2. Auto-Detection feature to connect to SQL*NET V1 or SQL*NET V2 server.
  3. Forcible connection to SQL*NET V1 or SQL*NET V2 if required.
  4. Available for various vendors of TCP/IP
  5. FTP
  6. Novell
    SQL*NET V2-Lite is available for FTP, Novell & PCNFS TCP/IP drivers. To work with SQL*NET V2-Lite, the TCP/IP driver corresponding to your installation should be present in your system. The executable you will be using will depend on the vendor of your TCP/IP software as given below: TCP/IP VENDOR Executable required
    • ------------------- FTP SQLTCPF.EXE Novell SQLTCPN.EXE PCNFS SQLTCPS.EXE COMMON PXE SQLTCP.PXE Copy the respective *.exe and sqltcp.pxe to the ORACLE-HOME/bin directory. Set the following parameters in config.ora, TCP_HOST_FILE ---> specifies host ip addresses. TCP_SERVICES_FILE----> specifies port numbers of the services e.g TCP_HOST_FILE=\pctcp\hosts TCP_SERVICES_FILE=\pctcp\services Also ensure that the following entries are present in the services file, orasrv <V1 port number>/tcp tnslsnr <V2 port number>/tcp For example, if your V1 port number is 1525 and V2 port number is 1521, the entries would be: orasrv 1525/tcp tnslsnr 1521/tcp For more information on working with SQL*NET V2-Lite refer to the Using SQL*NET TCP/IP section of SQL*NET TCP/IP for MS-DOS chapter of the SQL*NET TCP/IP User's Guide Version 1.2. SQL*NET V2-LITE LOGIN PARAMETERS
      You can use SQL*NET V2-Lite to connect to remote database when you run any ORACLE application that accepts a username and password in the command line. For example, SQL*Plus, SQL*Forms, and SQL*Calc all accept a username and password on the command line. The general syntax for running an application program from command line is: application username/password_at_connect string where application Is the command that invokes the Oracle application. username Specifies the username to be used to connect to the remote database. password Specifies the password associated with username. connect string Specifies the network prefix, the target host for the remote database, and the system ID(SID) of the remote database that is the target of your connection request. Note: If you are using an ORACLE application that requires its own parameters, place those parameters after the SQL*NET V2-Lite specific parameters. For example, if you running SQL*Forms with the parameters -C BIOS and your username and password are SCOTT and TIGER respectively, and the connect string is t:, your command would be: SQLFORMS SCOTT/TIGER_at_t: -C BIOS CONNECT STRING SYNTAX
      The syntax for connect string is same as SQL*NET V1 connect string. V2-Lite does not require tnsnames.ora like SQL*NET V2. The syntax is: net prefix:hostname[/port number]:SID[,buffer size][/Listener version] net prefix For tcp it is always T. hostname Address or alias name of remote host. port number TCP port number of Server listener. ( If not given default would be considered). SID System ID of server database. buffer size The size of context area used by driver. Listener version Optional forcible version number V1 or V2 depending on Server listener version. For example, if the address of your host is, the server listener port number is 1521 and the SID is ora, your connect string would be: t:


        This product has been designed to work with all the platforms
        running ORACLE server.
        This release has been tested succesfully with ORACLE server running
        on the following platforms:
                  1) Windows NT
                  2) NetWare
                  3) SunOS
                  4) Ultrix
                  5) IUS
                  6) SCO

  1. If you are unable to connect to any server, you can use Forcible V1/V2 option.
  2. Timeout option should be enabled on the server and the value for timeout should be greater than zero. LIMITATIONS
    Since V2-Lite is basically a sql*net v1 simulating sql*net v2, the limitations sql*net v1 exists in sql*net v2-lite also. V2-Lite PCNFS version may not work continously after 500 connections. The workaround is to restart PCNFS.
    • end of appended material ------------------------------------------
      -- Author: Eric D. Pierce INET: Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists
      To REMOVE yourself from this mailing list, send an E-Mail message to: (note EXACT spelling of 'ListGuru') and in
Received on Wed Jun 28 2000 - 08:28:34 CDT

Original text of this message