11/15/1995 Oracle 7.x Quick Reference (16bit client) 1. Client connection drivers Srvr Net Protocol/Client App. Windows (Sql*Net1) DOS (Sql*Net1) Dec Pathworks DecNET ORA7WIN.DLL, COREWIN.DLL, SQLDNT.DLL SQLDNT.EXE NamedPipe OS/2 ORA7WIN.DLL, COREWIN.DLL, SQLNMP.DLL SQLNMP.EXE Novell Netware SPX ORA7WIN.DLL, COREWIN.DLL, SQLSPX.DLL SQLSPX.EXE Banyan / Vines ORA7WIN.DLL, COREWIN.DLL, SQLVIN.DLL SQLVIN.EXE NetBIOS ORA7WIN.DLL, COREWIN.DLL, SQLNTB.DLL SOLNTB.EXE IBM APPCA.U6.2 ORA7WIN.DLL, COREWIN.DLL, SQLAPPC.DLL SQLAPPC.EXE TCPIP ->3Com 3+Open ORA7WIN.DLL, COREWIN.DLL, SQLTCP.DLL SQLTCP.EXE TCPIP ->HP Arpa Services ORA7WIN.DLL, COREWIN.DLL, SQLTCP.DLL SQLTCP.EXE TCPIP ->Interlan ORA7WIN.DLL, COREWIN.DLL, SQLTCP.DLL SQLTCP.EXE TCPIP ->Ungerman Bass ORA7WIN.DLL, COREWIN.DLL, SQLTCP.DLL SQLTCP.EXE TCPIP ->Novell Lan Workplace ORA7WIN.DLL, COREWIN.DLL, SQLTCP.DLL SQLTCP.EXE TCPIP ->Sun PC/NFS ORA7WIN.DLL, COREWIN.DLL, SQLTCP.DLL SQLTCP.EXE TCPIP ->Wollongong ORA7WIN.DLL, COREWIN.DLL, SQLTCP.DLL SQLTCP.EXE 1-a) Oracle's SQL*Net 2.0 uses a different set of files that is too extensive to outline here. Use the Oracle Installer (ORAINST.EXE) to verify the version and installation of SQL*Net. 2. Connection files to be loaded: To establish a Windows connection: The Windows connection to Oracle 7 uses only Windows DLLs where the DOS connection relies on a combination of TSR'S and DLL’s for a Windows connection. The connection DLLs must be in the system's path and only one copy of a specific DLL can exist in the path. The user should not have both the ORA6WIN.DLL and the ORA7WIN.DLL in the path. If they do, they may be unable to connect (SQL Link 2.0 has an Oracle driver option for setting the specific DLL that should be loaded). The user must also have the network API DLLs installed. These are provided by Microsoft and vary from network to network. Example of network API DLL’s for Novell networks: NWNETAPI.DLL NWIPXSPX.DLL To establish a DOS connection: *For DOS level configuration refer to the Quick Reference sheet for Oracle 6.0. 3. Required configuration settings: To establish a Windows connection: The connection requires that there be an [Oracle] section declared in the WIN.INI and an entry for ORA_CONFIG which refers to the location of the ORAWIN.INI file. Example WIN. INI file entry: [Oracle] ORA_CONFIG=C:\ORACLE7\BIN\ORAWIN.INI The ORAWIN.INI holds the default settings for a server connection. Example ORAWIN.INI (6.0/7.0) file entries: ORACLE-HOME=C:\ORACLE MACHINE-TYPE=0 WIN_REMOTE_SESSIONS=4 When connecting through Windows an an entry for WIN_REMOTE_SESSIONS should exist. The WIN_REMOTE_SESSIONS parameter must be set equal to a value greater than or equal to 4. * If the WIN_REMOTE_SESSIONS setting is too low it can cause problems with remote table closure, opening Cursors, cursors becoming undefined, and SQL Pass-through. Depending on the users Windows configuration he/she may need to use the Oracle Windows utility NETINIT7.EXE before attempting to establish a connection. NETINIT7.EXE sets aside stack space within Windows for the connection to the remote database. *Verify your PC's connection to the server using Oracle's Net Test (NETTEST.EXE) and/or SQL Plus (PLUS31.EXE).* ------------------------------------------------------------------------------- Can I connect to Oracle using SQLNet 2.x ------------------------------------------------------------------------------- Yes, you can connect using the 2.0 Oracle SQL*Net with v2.0/2.5 of the SQL Link . In cases all you need to do is make sure that the 'Network Protocol' entry is blank in the alias manager. Also make sure that the SQL Link Oracle driver's (not just the alias) "Net Protocol" is blank (do this through the Idapi config utility). Enter: TNS:myservername ('myservername' represents the your server's "alias" entry in the SQL*Net 2.x TNSNAMES.ORA file located in the \ORAWIN\NETWORK\ADMIN directory) into the 'Server Name' setting - also in the alias manager (if your only configured for one server it might only be necessary to type in 'TNS' for the 'Server Name') SQL*Net 2.0 requires that a different connection string be passed to the server. Using SQL*Net 1.x the string would usually be something like '@x:jolly' where 'x' represents the network protocol being used, the 'jolly' is the server name and the ':' is a separator between the two (you should see a similar scheme when connecting to an InterBase 4.0 server - ':' for TCP/IP, '@' for SPX and '\' for NetBeui.) The 2.x version of SQL*Net uses something called TNS (Transparent Network Substrate) that can subsitute for both the net protocol and the server name. The pieces are put together by both the server and the oracle configuration file on the local client machine. TNS is meant to make server administration and local configuration easier. *Verify your PC's connection to the server using Oracle's Net Test (NETTEST.EXE) and/or SQL Plus (PLUS31.EXE).* ------------------------------------------------------------------------------- Oracle 6.0 Quick Reference 1. Client connection drivers Srvr Net Protocol/Client App. Windows DOS Dec Pathworks DecNET ORA6WIN.DLL, SQLDNT.EXE SQLDNT.EXE NamedPipe OS/2 ORA6WIN.DLL, SQLNMP.EXE SQLNMP.EXE Novell Netware SPX ORA6WIN.DLL, SQLSPX.EXE SQLSPX.EXE Banyan / Vines ORA6WIN.DLL, SQLVIN.EXE SQLVIN.EXE NetBIOS ORA6WIN.DLL, SQLNTB.EXE SQLNTB.EXE IBM APPC/LU6.2 ORA6WIN.DLL, SQLAPPC.EXE SQLAPPC.EXE TCPIP -> 3Com 3+Open ORA6WIN.DLL, SQLTCP.EXE SQLTCP.EXE TCPIP -> HP Arpa Services ORA6WIN.DLL, SQLTCP.EXE SQLTCP.EXE TCPIP -> Interlan ORA6WIN.DLL, SQLTCP.EXE SQLTCP.EXE TCPIP -> Ungerman Bass ORA6WIN.DLL, SQLTCP.EXE SQLTCP.EXE TCPIP -> Novell Lan Workplace ORA6WIN.DLL, SQLTCP.EXE SQLTCP.EXE TCPIP -> Sun PC/NFS ORA6WIN.DLL, SQLTCP.EXE SQLTCP.EXE TCPIP -> Wollongong ORA6WIN.DLL, SQLTCP.EXE SQLTCP.EXE 2. Connection files to be loaded: To establish a Windows connection: The Windows connection to Oracle 6 uses a combination of DOS TSRs and Windows DLLS. The SQL*.EXE file must be loaded before entering Windows. To establish a DOS connection: The DOS level connection requires only the SQL*. EXE file to be loaded. 3. Required configuration settings: To establish a Windows connection: The connection requires that the environment variable CONFIG be set to refer to the location of the CONFIG.ORA file. Example batch file entry: SET CONFIG=C:\ORACLE6\BIN\CONFIG.ORA The CONFIG.ORA holds the default settings for a server connection. Example CONFIG. ORA file entrys: ORACLE HOME=C:\ORACLE MACHINE TYPE=0 When connecting through Windows an entry for WIN_REMOTE_SESSIONS must exist. The WIN_REMOTE_SESSIONS parameter must be set equal to a value greater than or equal to 4. Example CONFIG.ORA file entry: WIN_REMOTE_SESSIONS=4 When connecting through Windows an an entry for WIN_REMOTE_SESSIONS should exist. The WIN_REMOTE_SESSIONS parameter must be set equal to a value greater than or equal to 4. * If the WIN_REMOTE_SESSIONS setting is too low it can cause problems with remote table closure, opening Cursors, cursors becoming undefined, and SQL Pass-through. Depending on the users Windows configuration he/she may need to use the Oracle Windows utility NETINIT6.EXE before attempting to establish a connection. NETINIT6.EXE sets aside stack space within Windows for the connection to the remote database. Depending on the users Windows config they may need to use the Oracle Windows utility NETINIT7.EXE before attempting to establish a connection. NETINIT7.EXE * Verify your PC's connection to the server using Oracle's Net Test (NETTEST.EXE) and/or SQL Plus (PLUS31.EXE).* ID:CSxxxx