SQL Links - Oracle Connection

Company

SQL LINKS DEVELOPER SUPPORT

SEARCH Borland Online/Developer Support

Tech Notes Index

Personal Oracle Guidelines Configuring 32-bit BDE/SQL Links connection to Oracle servers OEM Install method: Execute \setup.exe from your 32bit SQL*Net 2.x install disk. Select CUSTOM when installing the NT SQLNET client software. (TYPICAL will install the complete Oracle server edition) Under SQL*NET 2.x (hold down shift key and click downarrow) Highlight Oracle Named Pipes Adaptor 2.1.3.0 (or current ver.) Oracle Named Server 1.0.1 (or current ver.) Oracle SPX Adaptor Oracle TCP/IP Adaptor SQL*Net Client Ensure that your SQL*Net 2.x settings are correct (SQLNET.ORA, TNSNAMES.ORA, etc) Please contact your Oracle server administrator for information on the server name(s), user name(s) and password(s) that you will use to connect. Select Control Panel|System|Path (from NT) or just add to your path: Add c:\orant\bin (or the appropriate path string) to your path statement. Shutdown and Restart You may now connect to an Oracle database via SQLNET 2.1. A connection to your Oracle server via SQL*Net 2.x may require that the Oracle BDE DRIVER/ALIAS NET PROTOCOL setting be set to "TNS". The ORACLE Driver "VENDOR INIT" setting in the BDE 3.0 configuration utility should be should be set to "ORANT71". (*Please note*: a 32bit BDE client connection using the Win95/NT version of Oracle's SQL Net client software and/or a connection to PERSONAL ORACLE FOR WINDOWS 95 may require that you change the BDE Oracle driver VENDOR INIT setting to ORA72.DLL) Common errors: (please refer to your Oracle documentation first for specific information) Vendor Initialization failed. Alias: myaliasname File: ORANT71.DLL keywords: oracle, sql links, vendor init, bde, orant71.dll, sql*net, sql net A connection to your Oracle server via SQL*Net 2.x may require that the Oracle BDE DRIVER/ALIAS NET PROTOCOL setting be set to "TNS". The ORACLE Driver "VENDOR INIT" setting in the BDE 3.0 configuration utility should be should be set to "ORANT71.DLL" (or the currently available Oracle database library: ORA72.DLL, ORA73.DLL, etc.). Please note that a 32bit BDE client connection to PERSONAL ORACLE FOR WINDOWS 95 may require that you change the BDE Oracle driver VENDOR INIT setting to ORA72.DLL If the specified VENDOR INIT dll can not be found the the Oracle driver will default to ORANT71.DLL. A common mistake is to leave the ".dll" off of the file name. (PUB, ID:CS1045, BC, 9.6.96) Vendor initialization failed. Cannot load an IDAPI service library. File: ORANT71.DLL Alias: MYALIASNAME The file specified in the SQL Links Oracle driver parameter VENDOR INIT cannot be found in memory or in the DOS path (Win95) or in the SYSTEM Environment Path (WinNT). The Oracle VENDOR INIT file can usually be found in the Oracle \BIN directory. Oracle's Win95 or WinNT SQL Net may not been installed correctly (or completed successfully) or has not been installed yet. PLEASE NOTE: If the Oracle SQL Links driver cannot find the file specified in the VENDOR INIT parameter then it will default to looking for ORANT71.DLL (this was the first 32bit version of Oracle's OCI available to Borland). (BC 6.2.97) ORA-3121 error usually means c:\orant\bin has not been added to your path or the SERVER NAME and/or the NET PROTOCOL have been entered incorrectly for your BDE Oracle alias. Verify it is in your path via the "set" command in a MS-DOS window. Ensure that SERVER NAME is the same as the string used when connecting using Oracle's SQL Plus and that the NET PROTOCOL is "TNS". ORA-12154 error usually means that the Server name was not found in the myoracledir\network\admin\TNSNAMES.ORA file. Entering the full matching entry in the TNSNAMES.ORA file usually solves the problem (i.e. orasrvr_tcp.borland.world) ORA-12203 1)his error can mean that the registry doesn't contain the proper oracle files: \HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE (example registry entries for NT and Win95 can be found at the bottom of this file) OR 2)the SQL Net listener is not loaded on the Oracle server. ORA-12196:received an error from TNS Delphi 2.0 SQL Links 3.0 Oracle driver Oracle SQL Net 2.x for NT MS NT 4.0 w/Explorer shell (beta) Launching DBD 7.0 from a shortcut (.lnk) file on the Start menu Launching Oracle's database manager from the Explorer Info from the SQLNET.TRC file (created by SQL Net and configured via the SQLNET.ORA file) indicated: "Poorly form NS address (DESCRIPTION=CONNECT_DATA=(SID=ORCL) (CID=(PROGRAM=C:\WINNT35.0\profiles\APS\Start Menu\Programs\ Delphi 2.0 (Common)\Database Desktop.lnk)(HOST=Windows NT PC..." Launching DBD from the Explorer (DBD32.EXE) vs. the Start menu (Database Desktop.lnk) corrected this problem. Basic information on configuring the SQL*Net 2.x listener on the Oracle server: (please refer to your Oracle documentation first for specific information) The listener.ora file that resides on the server must match the tnsnames.ora file on the client. A trick for setting the host, port, service and protocol to run lsnrctl at the server and issue the status and the start command to look for errors and to get it going. For an NT server you must make sure this is started up in NT's ControlPanel services. LSNRCTL creates a log file that you can refer too. Client side is SQLNET.ora and TNSNAMES.ora: SQLNET you just have to worry about the default domain and zone. Zone appears to be for the older version 2.0 and domain is for 2.1 SQLNET. TNSNAMES.ORA contains the connection information. The first part can be named anything you like, just that when you refer to it you must refer to it either as the complete name (i.e. orasrvr_spx.borland.world) or everything before the default domain(i.e. orasrvr_spx) because the default domain is added (ie: borland.world). EXAMPLE REGISTRY ENTRIES Example NT registry entries: Key Name: SOFTWARE\ORACLE Class Name: Application Global Data Last Write Time: 8/21/95 - 3:37 PM Value 0 Name: API Type: REG_EXPAND_SZ Data: C:\ORANT\DBS Value 1 Name: NLS_LANG Type: REG_EXPAND_SZ Data: AMERICAN_AMERICA.WE8ISO8859P1 Value 2 Name: ORA_ORCL_PWFILE Type: REG_SZ Data: C:\ORANT\RDBMS71\PWDORCL.ORA Value 3 Name: ORACLE_GROUP_NAME Type: REG_EXPAND_SZ Data: Oracle7 Workgroup Server for Windows NT Value 4 Name: ORACLE_HOME Type: REG_EXPAND_SZ Data: C:\ORANT Value 5 Name: ORACLE_PRIORITY Type: REG_EXPAND_SZ Data: CLASS:normal;DEF:normal Value 6 Name: ORACLE_SID Type: REG_EXPAND_SZ Data: ORCL Value 7 Name: PLSQL21 Type: REG_EXPAND_SZ Data: C:\ORANT\PLSQL21 Value 8 Name: RDBMS71 Type: REG_EXPAND_SZ Data: C:\ORANT\RDBMS71 Value 9 Name: RDBMS71_ARCHIVE Type: REG_EXPAND_SZ Data: C:\ORANT\RDBMS71\ARCHIVE Value 10 Name: RDBMS71_CONTROL Type: REG_EXPAND_SZ Data: C:\ORANT\RDBMS71 Key Name: SOFTWARE\ORACLE\SECURITY Class Name: Application Global Data Last Write Time: 8/21/95 - 3:36 PM Value 0 Name: ORA_ORCL_STARTTYPE Type: REG_DWORD Data: 0x42 Value 1 Name: ORA_ORCL_TCP Type: REG_SZ Data: TRUE Example Win95 registry entries: [HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE] "API"="C:\\ORANT\\DBS" "RDBMS71"="C:\\ORANT\\RDBMS71" "PLSQL21"="C:\\ORANT\\PLSQL21" "ORACLE_HOME"="C:\\ORANT" "ORACLE_GROUP_NAME"="Oracle7 Workgroup Server for Windows NT" "NLS_LANG"="AMERICAN_AMERICA.WE8ISO8859P1" ID:1005 WL,BC 5/2/1995