Compatibility
Can I mix and match client and server components from different OpenLink versions?
<p>OpenLink Software does not support mixed-version installations. Mismatched client and server software may not hinder a user's ability to connect and query. However, version incompatibility issues will arise over time. In fact, users who mix OpenLink 3.x and OpenLink 4.x software can expect specific problems with stability, transactions, and threading. These problems can only be resolved by upgrading the older component.</p>
Compatibility
Can I run OpenLink 32-bit data access drivers (ODBC or JDBC) on a 64-bit operating system?
<p>OpenLink 32-bit data access drivers (ODBC or JDBC) software runs on 64-bit operating systems. However, OpenLink's 32-bit data access drivers are designed for use with 32-bit applications. Connectivity is possible to 64-bit applications that ship with 32bit libraries. However, OpenLink does not recommend this configuration.</p>
Compatibility
Can I use 64-bit OpenLink ODBC or JDBC Drivers on a 32-bit operating system?
<p>OpenLink Software does not recommend this configuration.</p>
Compatibility
Can I run multiple versions at the same time?
<p>Users like to run multiple driver versions for comparative purposes. Single-Tier users simply install their new drivers to a new directory. Multi-Tier drivers should install their new drivers to different directories, as well. In addition, Multi-Tier users must insure that their Request Brokers use separate TCP/IP Listen ports.</p>
Compatibility
Do I need ODBC or JDBC Drivers?
<p>If you are unsure of whether you require our ODBC or JDBC drivers, please review the questions posed below:</p><p> Do you need to query a database with a 3rd party application? Is your application ODBC- or JDBC- compliant? Does your network environment support the TCP/IP or SPX protocol?</p><p> OpenLink's Data Access Drivers provide ODBC and JDBC connectivity between compliant applications and databases. Moreover, OpenLink's drivers use the TCP/IP network protocol to achieve this connection. Consequently, if your response is YES to the aforementioned questions, you need these drivers.</p><p> If you are still unsure, please consult your Database Administrators, System Administrators, or other knowledgeable staff.</p><p> Users who respond NO to one or more questions must clarify their needs with either a Support Consultant or their Account Manager. We offer other solutions which might be what you require.</p>
Compatibility
Do OpenLink ODBC Drivers work with Oracle Heterogeneous Services?
<p>Our ODBC drivers work in conjunction with Oracle's Heterogeneous Services.</p>
Compatibility
Do OpenLink ODBC Drivers work with SQLServer Linked Servers?
<p>OpenLink's 5.x+ drivers support ODBC API calls made by MS SQLServer's Linked Servers.</p><p> We also provide an alternative OLE DB provider for use with this and similar products.</p>
Compatibility
Does OpenLink ODBC Drivers work with the SQL Server DTS Wizard?
<p>OpenLink's 5.x+ drivers support ODBC API calls made by MS SQLServer's DTS Wizard.</p><p> We also provide an alternative ODBC provider for ADO.NET and OLE.DB for use with this and similar products.</p>
Compatibility
Do you have 16Bit drivers?
<p>OpenLink produced 16Bit 1.x builds. These builds are not available to the general public.</p>
Compatibility
How can I tell if OpenLink produces software for a particular operating system or database?
<p>Go to the OpenLink downloads pages to search for the software for your particular OS.</p><p> If your Operating System or Database is not available in the list of supported platforms, please contact your Product Support consultant or Account Manager as the software might be available internally but not publicly so.</p>
Compatibility
Is Older OS Compatibility Supported?
<p>Consultants will encounter users who possess older builds of popular operating systems. For example, OpenLink may provide software for Solaris 2.5 systems. However, users have Solaris 2.4. In this instance, consultants should not encourage users to download software. OpenLink's software is not backwards compatible and may not function on the older platform.</p>
Compatibility
Is there Older DB Compatibility Supported?
<p>Consultants will encounter users who possess older builds of popular databases. For example, OpenLink may provide software for Informix 7.3 systems. However, users have Informix 5. In this instance, consultants should not encourage users to download software. OpenLink's software is not backwards compatible and may not function with the older platform. Be advised - Progress databases and OpenLink's Progress software are compatible, as long as both products share the same major number. For instance, OpenLink's Progress 8 database agents will connect to most Progress 8 databases. However Progress 8 database agents will not connect to Progress 7 databases.</p>
Compatibility
OpenLink Data Access Drivers Vs iODBC?
<p>iODBC.org offers free installers and instructions for the open-source iODBC Driver Manager and iODBC SDK. The installers are packaged with source code, header files, make files, and other resources of interest to the development community. These products match OpenLink Software's quality and reliability; however, they, and the iODBC.org web site, cater to highly technical individuals who know how to build the iODBC Driver Manager into their own custom solutions.</p><p> OpenLink Software provides commercial quality Data Access Drivers, the Virtuoso Universal Server, diagnostic utilities, and related SDKs. In addition, the iODBC Driver Manager is bundled into the OpenLink SDKs and installers for Data Access Drivers and Virtuoso. This software is intended to service businesses and other entities which need a complete, reliable, out-of-the-box solution.</p><p> OpenLink provides value added components in the OpenLink iODBC variant of the iODBC SDK. This value takes the form of ready-to-run iODBC ports for all supported platforms, and in the case of Mac OS X this currently includes an AQUA and Frameworks based ODBC Administrator.</p>
Compatibility
What Are Your Prerequisites And System Requirements?
<p>Users must install OpenLink's Single-Tier drivers on a supported operating system. Users must install DB2, Informix, Ingres, and Progress drivers on a machine, which contains a functional copy of their database native client. Users must install "ODBC Lite" drivers on a system that contains a 3rd party data source, which connects to the user's database. Users must install OpenLink's Multi-Tier client and server components on one or more supported operating systems. DB2, Informix, Ingres, and Progress users must install the server components on a system, which contains the user's database or database native client. Users must install "Generic ODBC" drivers on a system that contains a 3rd party data source, which connects to the user's database. Users must install Virtuoso Universal Server client and server components on one or more supported operating systems. Users must install the iODBC Driver Manager, OpenLink ODBC Bench, and ODBC Scan on a supported client operating system. Some users may require a compiler and library linker, if they intend to develop ODBC compliant applications or re-link OpenLink's agents or Driver Manager.</p>
Compatibility
What Is The Compatibility with A Newer DB?
<p>Users who possess newer builds of popular databases. For example, OpenLink may provide software for Sybase 11 systems. However, users have Sybase 12. In most instances, consultants should encourage users to download the closest match to their database version. OpenLink's software is upwards compatible and should function with the newer product. Be advised - Progress databases and OpenLink's Progress software are compatible, as long as both products share the same major number. For instance, OpenLink's Progress 8 database agents will connect to most Progress 8 databases. However Progress 7 database agents will not connect to Progress 8 databases.</p>
Compatibility
What JDBC Connection Formats Do Multi-Tier Drivers Support?
<p>OpenLink's Multi-Tier drivers support Type 3 (DSN-Less) JDBC connections. Multi-Tier drivers also support a Type 3 ODBC-JDBC Bridge.</p>
Compatibility
What JDBC Connection Formats Do Single-Tier Drivers Support?
<p>Single-Tier drivers support Type 1 (JDBC-ODBC Bridge) JDBC connections. They also provide ODBC-JDBC Bridge connectivity.</p>
Compatibility
What Network Protocols Do You Support?
<p>OpenLink supports the TCP/IP and IPX/SPX protocols.</p>
Compatibility
What Suitable Software Should Be Used?
<p>Get a uname -a from all machines on which software would be installed. Get the name of the database to which the user wants to connect. See if OpenLink has a matching machine and database installation or database installation media. If OpenLink has the requisite materials, OpenLink can build an agent. If OpenLink does not have the operating system or database, the user may need to consider a custom build.</p><p> ALERT Users may use OpenLink's Generic ODBC drivers to connect to databases, for which no database agents exist. These users simply need an OpenLink-supported operating system, which contains 3rd-party drivers that connect to the database. Other users may benefit from Single-Tier or application server configuration Multi-Tier connections, when they have a common database on an uncommon operating system. This latter configuration requires the installation of the database native client on an OpenLink-supported O/S.</p>
Compatibility
What is the Compatibility With Newer OS?
<p>Users who possess newer builds of popular operating systems. For example, OpenLink may provide software for Solaris 2.8 systems. However, users have Solaris 2.9. In this instance, consultants should encourage users to download the closest match to their operating system version. OpenLink's software is upwards compatible and should function on the newer platform.</p>
Configuration
Do I need to configure my environment to support ODBC-ODBC Bridge connectivity?
<p>You need to insure that your 3rd party drivers connect to the target database. You need to insure that openlink.sh or openlink.csh is run on Unix machines that contain OpenLink Software. openlink.sh should be run in a Bourne or Bash shell. openlink.csh should be run in C shell.</p>
Configuration
Do I need to configure my environment to support my JDBC connections?
<p>Insure that the CLASSPATH environment variable is set on the machine that contains your JDBC client application.</p><p> CLASSPATH appears in the Windows System Utility (Control Panel). Windows users need to navigate to the portion of the utility that displays their User and System settings.</p><p> Unix users may use echo to display their CLASSPATH setting. For example: bash$ echo $CLASSPATH /home/openlink/v51/mt/jdk1.4</p><p> CLASSPATH must pass the full path to an OpenLink JDBC opljdbc.jar, opljdbc2.jar, opljdbc3.jar or megathin.jar, megathin2.jar file depending on your JDK.</p>
Configuration
Do users need to employ special configuration to operate in a firewalled environment?
<p>Single-Tier users should not need to open ports to accommodate the Single-Tier driver. However, ports may need to be opened to facilitate connections between the database native client and the database to which it connects.</p><p> Multi-Tier users need to take the following action, if a firewall surrounds the machine that contains the Multi-Tier server components</p>
Configuration
How Do I Assist A User Who Does Not Know What Values To Pass To His Or Her Variables?
<p>All database specific environment variables should appear in the database user's .profile (unix) or other, standard configuration file. Users may open these files to ascertain which values need to appear in their Single-Tier openlink.ini files and their Multi-Tier oplrqb.ini files. In fact, users should execute the database user's .profile before installing Single-Tier drivers or Multi-Tier server components. The installers will detect the variables and write them into the appropriate location. The standardized, ODBC and JDBC variables pass the following values:</p><p>— CLASSPATH A JAVA client variable that passes the full path to an OpenLink JDBC .jar file.</p><p>— LD_LIBRARY_PATH A generic library path variable that appends the full path to OpenLink's lib sub-directory.</p><p>— LIBPATH An AIX library path variable that appends the full path to OpenLink's lib sub-directory.</p><p>— ODBCINI Passes the full path to ~/openlink/bin/odbc.ini.</p><p>— ODBCINSTINI Passes the full path to ~/openlink/bin/odbcinst.ini.</p><p>— OPENLINKINI This Single-Tier variable passes the full path to ~/openlink/bin/openlink.ini.</p><p>— PATH Appends the full path to OpenLink's bin sub-directory.</p><p>— SHLIB_PATH An HP/UX library path variable that appends the full path to OpenLink's lib sub-directory.</p>
Configuration
How Do I Configure An JDBC-ODBC Bridge Connection?
<p>Create a Single-Tier JDBC connection URL that passes the following values:</p><p></p><p>jdbc:openlink://ODBC/DSN=Valid ODBC Data Source/UID=database username/PWD=database password</p><p>Here are some examples:</p><p>jdbc:openlink://ODBC/DSN=Informix Stores7/UID=informix/PWD=informix ;</p><p>jdbc:openlink://ODBC/DSN=My Oracle DB/UID=scott/PWD=tiger ;</p><p>jdbc:openlink//ODBC/DSN=SQLServer Northwind Database/UID=sa</p>
Configuration
How Do I Configure An ODBC-JDBC Bridge Connection?
<p>Unix Single-Tier users pass the following values in your ODBC-JDBC Bridge Data Source:</p><p></p><p> — Name - Any Descriptive Title ;</p><p> — Database Name - JDBC Driver Name String: openlink.jdbc3.Driver ;</p><p> — Options - Functional JDBC connection URL.: jdbc:openlink://localhost:5000/SVT=Oracle 8.1.x/DATABASE=ORCL/UID=scott/PWD=tiger ;</p><p> — Username - JDBC Data Source Userid ;</p><p> — Existing Environment - Pass the value that corresponds to your JRE version: JDBC 1.1, JDBC 1.2, JDBC 1.3, or JDBC 1.4.</p><p></p><p>Windows Single-Tier users pass the following values in your ODBC-JDBC Bridge Data Source:</p><p></p><p> — Data Source Name - Any Descriptive Title ;</p><p> — JDBC Driver - JDBC Driver Name String: openlink.jdbc3.Driver ;</p><p> — URL String - Functional JDBC connection URL.: jdbc:openlink://localhost:5000/SVT=Oracle 8.1.x/DATABASE=ORCL/UID=scott/PWD=tiger ;</p><p></p><p>Multi-Tier users pass the following values in your ODBC-JDBC Bridge Data Source Names:</p><p></p><p> — Name - Any Descriptive Title ;</p><p> — Domain (a.k.a 'ServerType') - Pass the value that corresponds to your JRE version: JDBC 1.1, JDBC 1.2, JDBC 1.3, or JDBC 1.4. ;</p><p> — Hostname - Hostname or IP of the machine that contains OpenLink's server components ;</p><p> — Database - JDBC Driver Name String: openlink.jdbc3.Driver ;</p><p> — Options - Functional JDBC connection URL.: jdbc:openlink://localhost:5000/SVT=Oracle 8.1.x/DATABASE=ORCL/UID=scott/PWD=tiger ;</p><p> — Login ID - Blank</p>
Configuration
How Do I Configure An ODBC-ODBCBridge Connection?
<p>Multi-Tier users pass the following values in your Data Source Names:</p><p></p><p> — Name - Any Descriptive Title</p><p> — Domain (aka 'ServerType') - Odbc</p><p> — Hostname - Hostname or IP of machine containing OpenLink server components</p><p> — Database - Exact name of 3rd Party Data Source</p><p> — Username - Database username, if required</p><p> — Server/Options - Blank</p><p></p><p>Single-Tier users pass a descriptive title in the Data-Source Name field of the Data Sources. Then, use the System, User, and File dialogs to choose the 3rd party Data Source to which you want to connect.</p>
Configuration
How Do I Create A Data Source Name?
<p>Users may employ a variety of means to create OpenLink Data Source Names. Consultants should encourage users to use OpenLink's HTTP-Based iODBC Data Sources Administrator or Multi-Tier Administrative Assistant, whenever possible.</p>
Configuration
How Do I Create A Zero Config DSN?
<p></p><p> 1. Open your server's Administrative Assistant in a Web Browser.</p><p> 2. Expand the Server Components Administration menu.</p><p> 3. Expand the Zero Config Administration menu.</p><p> 4. Click Zero Config Administration by Wizard or Zero Config Administration by Form.</p><p> 5. Edit an existing Zero Config template or add a new one.</p><p> 6. Hard-code the value that your users need to connect to the database.</p><p> 7. Reinitialize the Request Broker to register your Zero Config DSN.</p><p> 7. Supply the name of the Zero Config DSN to your end users.</p><p></p><p>You need to provide your end users with the name of your Zero Config DSN. End users take the following action to use the DSN:</p><p></p><p> 1. Create a new DSN using the Windows Data Source Administrator or the Administrative Assistant.</p><p> 2. Name the new DSN.</p><p> 3. Expand the server drop down menu that appears on the first screen of the DSN setup dialog.</p><p> 4. Locate the Zero Config DSN by name.</p><p> 5. Allow the Zero Config DSN to auto-fill the fields of the new DSN.</p><p> 6. Save the new DSN.</p><p> 7. Test.</p>
Configuration
How Do I Test My JDBC Connection URL?
<p>Multi-Tier users may use the Admin Assistant to test their JDBC URLs. The following instructions will assist you with this task:</p><p></p><p> — Open the Admin Assistant in a Web browser.</p><p> — Expand the Sample Applications menu.</p><p> — Click JDBC Applet Demos.</p><p> — Select your JDK version, as needed.</p><p> — Select the appropriate sample application.</p><p></p><p>Single-Tier drivers may use the iODBC Data Sources Administrator on Unix platforms. The following instructions will assist you with this task:</p><p></p><p> — Open the iODBC Data Sources Administrator in a Web browser.</p><p> — Expand the Sample Applications menu.</p><p> — Click JDBC Applet Demos.</p><p> — Select your JDK version, as needed.</p><p> — Select the appropriate sample application.</p><p></p><p>Single-Tier drivers may also use the JDBC sample applications on Windows platforms. The following instructions will assist you with this task:</p><p></p><p> — Expand your Start menu.</p><p> — Expand your Programs menu.</p><p> — Locate your OpenLink Single-Tier drivers folder.</p><p> — Expand Our OpenLink Single-Tier drivers folder.</p><p> — Expand the JDBC Samples sub-folder.</p><p> — Expand the JDK sub-folder that corresponds to your JDK version.</p><p> — Select the desired application.</p><p></p>
Configuration
How Do Users Configure The Odbc ini File?
<p>Single-Tier users should use their HTTP-Based iODBC Data Sources Administrator to configure the odbc.ini file. Multi-Tier users may use the Admin Assistant to configure the odbc.ini file. All users may configure odbc.ini with vi or a similar text editor, if no graphical assistant exists.</p>
Configuration
How Do Users Configure The Odbcinst ini File?
<p>Users should not need to configure the odbcinst.ini file. If configuration is necessary, users may edit it with vi or a similar text editor.</p>
Configuration
How Do Users Configure The Openlink ini File?
<p>Users do not want to make manual edits to Unix-based openlink.ini files. Instead, users should perform the following actions, before they install OpenLink drivers:</p><p></p><p> 1. Login to the Unix system.</p><p> 2. su to the database client user.</p><p> 3. Execute the database client user's .profile.</p><p> 4. Run OpenLink's installation procedure.</p><p></p><p>OpenLink's installation procedure should detect the database client user's environment variables and write them into openlink.ini. If this procedure fails, users's should take the following action:</p><p></p><p> 1. vi the database client user's .profile.</p><p> 2. Record the variables contained in the file.</p><p> 3. cd into the /bin sub-directory of the OpenLink installation.</p><p> 4. vi openlink.ini.</p><p> 5. Locate the [Environment] section that pertains to the OpenLink driver.</p><p> 6. Set the appropriate environment variables.</p><p></p>
Configuration
How Do Users Configure The Oplrqb ini File?
<p>Users may use the HTTP-based Administrative Assistant to configure their oplrqb.ini files. There are a wide variety of animated tutorials that explain the Administrative Assistant features. Instruct users to use the Administrative Assistant's refresh feature to initialize changes it makes to the file. Advanced users may edit oplrqb.ini with a text editor. Instruct users to restart the Broker or reinitialize the Broker ( oplshut +reinit ) to initialize changes made to the file.</p>
Configuration
How Do Users Configure The Udbc ini File?
<p>Users may install a Multi-Tier Request Broker archive on the machine that contains their Multi-Tier client components. This provides users with the HTTP-based Administrative Assistant. Users may use the Assistant to configure their udbc.ini files. There are animated tutorials, which explain this process. Text-based instructions appear below:</p><p></p><p> 1. Open the client-side Administrative Assistant in a Web browser.</p><p> 2. Expand the Client Components Administration menu.</p><p> 3. Expand the Data Source Name Configuration menu.</p><p> 4. Expand the Edit Data Sources by Wizard menu.</p><p> 5. Click Edit UDBC Data Sources.</p><p> 6. Click Add.</p><p> 7. Answer the questions posed by the Wizard.</p><p> 8. Save the DSN and test.</p><p></p><p>Advanced users may edit udbc.ini with a text editor.</p>
Configuration
How Do Users Create Data Source Names?
<p>Single-Tier users may create Data Source Names using the following methods:</p><p></p><p> 1. Use the HTTP-Based iODBC Data Sources Administrator.</p><p> 2. Use the Windows ODBC Data Sources Administrator.</p><p> 3. Use the Mac OS X OpenLink ODBC Administrator.</p><p> 4. Use the Mac Classic ODBC Setup PPC.</p><p> 5. Manually edit Unix-based odbc.ini files.</p><p></p><p>Multi-Tier users may create Data Source Names using the following methods:</p><p></p><p> 1. Use the HTTP-Based Multi-Tier Administrative Assistant.</p><p> 2. Use the HTTP-Based iODBC Data Sources Administrator.</p><p> 3. Use the Windows ODBC Data Sources Administrator.</p><p> 4. Use the Mac OS X OpenLink ODBC Administrator.</p><p> 5. Use the Mac Classic ODBC Setup PPC.</p><p> 6. Manually edit Unix-based odbc.ini files.</p><p></p>
Configuration
How do I configure Multi-Tier drivers, after I have installed them?
<p>Windows and Mac client users do not need to perform additional steps to configure their Multi-Tier clients. Unix client users must insure that their OpenLink environment variables are set. The following instructions will assist these users with this task:</p><p></p><p> 1. Users must login to their Unix clients.</p><p> 2. Users must cd into the root of their OpenLink installation.</p><p> 3. Users may run openlink.sh in a Bash or Bourne shell. Alternatively, users may run openlink.csh in a C shell.</p><p></p><p>All users must insure that their server components are properly configured. The following instructions will assist all users with this task:</p><p></p><p> 1. Unix users must login to their Unix servers and cd into the root of their OpenLink installations. These users may run openlink.sh in a Bourne or Bash shell. Alternatively if you are using a C shell, you require openlink.csh.</p><p> 2. All users must open their Session Rules Books. The Session Rules Book is the oplrqb.ini file, which reside in the /bin sub-directory of the OpenLink installation. Users may open oplrqb.ini with vi, Notepad, or another text editor. Locate the Environment section that corresponds to your OpenLink database agent and set the variables that are appropriate to to your Database setup. Typically, the main information required is the installation directory and location of the database libraries. If you are unsure what these values are, please request them from your Database or System administrator. Typically running the command `env' under the guise of the database owner will provide you with the necessary information</p><p> 3. Users must start their OpenLink Request Broker services. To do this on Unix, from the shell or terminal prompt run ./oplrqb either from the /bin sub-directory of your OpenLink installation or if openlink.sh/csh has been run, anywhere in the system. Windows users may start oplrqb with their Services Control Panel utility.</p>
Configuration
How do I configure Single-Tier drivers, after I have installed them?
<p>Windows and Mac users do not need to perform additional steps to configure their Single-Tier drivers.</p><p></p><p>Unix users need to insure that their OpenLink and database environment variables are set. The following instructions will assist Unix users with this task:</p><p></p><p> 1. Users must login to their Unix clients.</p><p> 2. Users must cd into the root of their OpenLink installation.</p><p> 3. Users may run openlink.sh in a Bash or Bourne shell. Alternatively, users may run openlink.csh in a C shell.</p><p> 4. Users must cd into the /bin sub-directory of their OpenLink Single-Tier installations.</p><p> 5. Users must edit openlink.ini or open the file with a text editor such as vi.</p><p> 6. Users must identify the Environment section that corresponds to their OpenLink Single-Tier driver.</p><p> 7. Users must ensure that the relevant variables are set within the Environment section.</p>
Configuration
I Do Not Know The Correct Values For My Multi-Tier DSN. What Do I Do?
<p>The following guidelines enable you to establish the values that you need to pass in a client/server Data Source Name. Name Provide any descriptive title for your Data Source Name. Limit the name to 32 characters and start with an alphanumeric character. Description You may provide an optional description for your Data Source Name. Server This field passes the hostname or IP address of the machine that contains your OpenLink server components installation. It also passes the TCP port on which the Request Broker listens. If you do not know the hostname or IP address of the machine, you may run hostname on the console. If you do not have access to the console, contact its System Administrator. The Broker's TCP port is recorded in the Session Rules Book. The Session Rules Book is the oplrqb.ini file that appears in the /bin sub-directory of the OpenLink server components installation. It may be opened with any text editor.</p>
Configuration
I do not know the correct values for my Single-Tier DSN. What do I do?
<p>OpenLink's Single-Tier drivers pass a name and a set of database-specific connection parameters. You may name your Data Source Name anything you want, so long as it observes length and special character considerations. However, you should consult your Database Administrator, if you need assistance with the database-specific connection parameters.</p><p> The database-specific parameters are parameters that the various database native clients use to connect to the database. OpenLink Product Support Staff is familiar with many database native clients. However, these products change frequently. Moreover, your Database Administrator and Database Vendor will have more intimate knowledge of these products as they instantiate in your environment.</p>
Configuration
What Are The Differences Among User System And File DSNs?
<p>User DSN - User DSNs are available for use only to the user who created it. User DSN connection parameters are stored in the HKEY_CURRENT_USER/Software/ODBC/ODBC.INI section of the registry.</p><p> System DSN - System DSNs are available for use to any user who logs onto the local system. System DSN connection parameters are stored in the HKEY_LOCAL_MACHINE/Software/ODBC/ODBC.INI section of the registry.</p><p> File DSN - File DSNs comprise a set of DSN connection parameters that are saved to a text file with a .DSN extension. File DSNs typically appear in C:/Program Files/Common Files/ODBC/Data Sources.</p><p> OpenLink recommends use of System DSNs whenever possible.</p>
Configuration
What Configuration Files Are Used By Multi-Tier Drivers?
<p>OpenLink's Multi-Tier drivers comprise a client component and a server component. The following files are used by OpenLink's client drivers: openlink.sh and openlink.csh - These files appear in the root of Unix-based, Multi-Tier installations. They contain ODBC-related environment variables. odbc.ini - This file appears in the /bin sub-directory of Unix-based, Multi-Tier installations. It contains Data Source Name connection attributes. Occasionally, it may contain client communication settings and ODBC tracing parameters. odbcinst.ini - This file appears in the /bin sub-directory of Unix-based, Multi-Tier installations. It contains path and setup information for the Single-Tier driver. The following files are used by OpenLink's server components: openlink.sh and openlink.csh - These files appear in the root of Unix-based, Multi-Tier installations. They contain ODBC-related environment variables. oplrqb.ini - This file appears in the /bin sub-directory of all, Multi-Tier server components installations. This file contains database-specific environment variables. It also contains parameters that affect security, port usage, agent behavior, and client/server communications. www_sv.ini - This file appears in the /bin/w3config sub-directory of all Multi-Tier server components installations. This file contains the Web-based Administrative Assistants username, encrypted password, and listening port.</p><p> Windows drivers do not contain the Multi-Tier client files. Client environment variables appear on the Environment or Advanced tab of the System utility. The odbc.ini and odbcinst.ini files are replaced by the HKEY_LOCAL_MACHINE/SOFTWARE/ODBC/ODBC.INI and HKEY_LOCAL_MACHINE/SOFTWARE/ODBC/ODBC.INI sections in the registry. Windows server installations retain the oplrqb.ini and www_sv.ini files.</p>
Configuration
What Configuration Files Are Used By Single-Tier Drivers?
<p>OpenLink's Single-Tier drivers rely on the following configuration files: openlink.sh and openlink.csh - These files appear in the root of Unix-based, Single-Tier installations. They contain ODBC-related environment variables. openlink.ini - This file appears in the /bin sub-directory of Unix-based, Single-Tier installations. It contains database-specific environment variables. odbc.ini - This file appears in the /bin sub-directory of Unix-based, Single-Tier installations. It contains Data Source Name connection attributes. Occasionally, it may contain ODBC tracing parameters. odbcinst.ini - This file appears in the /bin sub-directory of Unix-based, Single-Tier installations. It contains path and setup information for the Single-Tier driver. Windows drivers do not contain these files. Environment variables appear on the Environment or Advanced tab of the System utility. The odbc.ini and odbcinst.ini files are replaced by the HKEY_LOCAL_MACHINE/SOFTWARE/ODBC/ODBC.INI and HKEY_LOCAL_MACHINE/SOFTWARE/ODBC/ODBC.INI sections in the registry.</p>
Configuration
What Do I Do With The DSNs That I Create?
<p>Data Source Names enable applications to establish ODBC connections to database servers. Once you create your Data Source Name, you must ascertain how your application enables you to display, select, and connect to Data Source Names.</p>
Configuration
What Do I Need To Establish A Multi-Tier JDBC Connection?
<p>You need to install one of Sun's Java Runtime Environments (JRE) on the machine that contains your client application.</p><p> You need to install one of OpenLink's .jar files on the machine that contains your JAVA client application. (The JAVA version of the .jar should match the JAVA version of the JRE.)</p><p> You need to install OpenLink's server components on a machine that contains one of the following entities:</p><p> The actual database;</p><p> A database native client that connects to the database.</p>
Configuration
What Do I Need To Establish A Single-Tier JDBC Connection?
<p>You need to install one of Sun's Java Runtime Environments (JRE) on the machine that contains your client application.</p><p> You need to install one of OpenLink's .jar files on the machine that contains your JAVA client application. (The JAVA version of the .jar should match the JAVA version of the JRE.)</p><p> You need to insure that a functional database native client is installed on the machine that contains the application and the Single-Tier .jar.</p>
Configuration
What Do I Pass In A Multi-Tier JDBC Connection URL?
<p>Multi-Tier JDBC connection URLs take the following form:</p><p> jdbc:openlink://<Hostname>:[portnumber] [/UID] [/PWD] [/READONLY] [/SVT]</p><p> [/APPLICATION] [/FBS|FETCHBUFFERSIZE] [/ENCRYPTED] [/CHARSET] [/UNICODE]</p><p> [/DLF] [/DATABASE] [/OPTIONS] [/DRIVER] .</p><p></p><p>Here is a description of each of the parameters:</p><p></p><p> Hostname - Network Alias or IP address of machine that runs an OpenLink Request Broker instance;</p><p> Port Number - TCP port on which the Request Broker listens;</p><p> /UID - Database username;</p><p> /PWD - Database password;</p><p> /READONLY - Read-write or read-only session mode;</p><p> /SVT - A valid domain alias from the [Domain Aliases] section of the OpenLink server component's oplrqb.ini file. Default domain aliases represent the type of database agent to which the application intends to connect, e.g., DB2, Informix 2000, Oracle 8.1.x. Custom aliases may take any form;</p><p> /APPLICATION - The Application name. Enables connectivity when restrictive server side rules screen by application name;</p><p> /FBS - (also FETCHBUFFERSIZE) The Fetch Buffer Size. The Fetch Buffer Size is an integer that represents the number of rows to return during one fetch operation;</p><p> /ENCRYPTED - Sets the Encrypted flag for outgoing packets. /ENCRYPTED may pass '1', '0', 'Y', 'N', 'y', or 'n.' (This feature is disabled by default.);</p><p> /CHARSET - Specifies the charset of remote databases. The default value is read from System.getProperty("file.encoding");</p><p> /UNICODE - Instantiates unicode. The unicode connection isn't used by default. The value may be '1', '0', 'Y', 'N', 'y', 'n'(This feature is disabled by default.);</p><p> /DLF - Pushes large, binary objects to the end of the result-set. Smaller data types are retrieved first. This enhances performance. /DLF may be set to '1', '0', 'Y', 'N', 'y', or 'n.' (This feature is disabled by default.);</p><p> /DATABASE - Actual database name within a particular database environment;</p><p> /OPTIONS - Optional parameter that passes specialized database native client connection parameters. Used by users who connect to Progress databases in sockets mode. Also used by users who have 3-Tier or application server architectures;</p><p> /DRIVER - The Driver name contained in curly brackets ({}). Used for DSN-Less connections to remote ODBC Drivers.</p><p></p><p>Here are some sample JDBC connection URLs:</p><p>jdbc:openlink://localhost:5000/SVT=Ingres II/DATABASE=iidbdb/UID=ingres/PWD=ingres;</p><p>jdbc:openlink://192.128.13.119:5000/SVT=Oracle 8.1.x/DATABASE=ORCL/UID=scott/PWD=tiger;</p><p>jdbc:openlink://saturn:5000/SVT=Progress 91D/DATABASE=isports/OPTIONS=-S isports -N tcp -H saturn;</p><p>jdbc:openlink://localhost:5000/SVT=SQLServer 2000/DATABASE=Northwind/UID=sa/OPTIONS= -S SATURN;</p>
Configuration
What Do I Pass In A Single-Tier JDBC Connection URL?
<p>Single-Tier JDBC connection URLs take the following format: jdbc:openlink://ODBC[/DSN][/UID][/PWD][/READONLY] .</p><p> Here is a description of each of the URL parameters: /DSN - Local ODBC Data Source Name; /UID - Database Username;</p><p> /PWD - Database Password; /READONLY - Read-write or read-only session mode. Here is a sample Single-Tier JDBC connection URL:</p><p> jdbc:openlink://ODBC/DSN=Local Oracle ODBC Data Source/UID=scott/PWD=tiger</p>
Configuration
What Do Users Need To Do To Configure Their Multi-Tier Drivers?
<p>Unix users need to insure that openlink.sh (Bourne/Bash) or openlink.csh (C) is executed in the appropriate shell. These shell scripts set environment variables that pertain to ODBC. They appear in both client and server components installations.</p><p> Unix users need to run set or env to insure that the environment variables (ODBCINI, ODBCINSTINI, etc.) are actually set.</p><p> All users need to insure that the appropriate [Environment] section of the ~/openlink/bin/oplrqb.ini file contains the correct environment variables.</p><p> All users should uncomment and set the PortHigh parameter that appears in the [Protocol TCP] section of the ~/openlink/bin/oplrqb.ini file. PortHigh should equal PortLow + the number of concurrent connections alloted by the license + a few extra ports.</p><p> All users need to start the Request Broker. The Request Broker is the oplrqb executable that appears in the /bin sub-directory of Multi-Tier server components installation.</p>
Configuration
What Do Users Need To Do To Configure Their Single-Tier Drivers?
<p>Unix users need to insure that openlink.sh (Bourne/Bash) or openlink.csh (C) is executed in the appropriate shell. These shell scripts set environment variables that pertain to ODBC.</p><p> Unix users need to run set or env to insure that the environment variables (ODBCINI, ODBCINSTINI, etc.) are actually set.</p><p> Unix users need to insure that the appropriate [Environment] section of the ~/openlink/bin/openlink.ini file contains the correct environment variables.</p><p> Windows users need to insure that their System and User PATH variables contain the OpenLink driver .dlls and database native client .dlls. (Database native client .dll's are not required for MySQL, PostgreSQL, SQLServer, or Sybase.)</p><p> Windows users may need to set other System and User PATH variables depending on the database. For example, Progress users need to set PROGRESSINI and PROMSGS.</p>
Configuration
What Does Count Stored Procedure Parameters In SQL Procedures Do?
<p>This applies to the Oracle data-source.</p><p> "Count Stored Procedure Parameters" affects the output from SQLProcedures when "Custom Catalog Views" is enabled.</p><p> When "Custom Catalog Views" is off, the NUM_INPUT_PARAMETERS, NUM_OUTPUT_PARAMETERS and NUM_RESULT_SETS columns of the SQLProcedures result set all contain -1.</p><p> When "Custom Catalog Views" in on, "Count Stored Procedure Parameters" is enabled and an internal view, OPENLINK$SQL_PROCEDURES is used; when this is disabled, the internal view, OPENLINK$SQL_PROCS_NOCOUNT is used instead. The result set returned by SQL_PROCEDURES includes the number of input and output parameters for each procedure. The number of result sets is always -1 like the case when "Custom Catalog Views" is off, SQL_PROCS_NOCOUNT returns -1 for the NUM_INPUT_PARAMETERS, NUM_OUTPUT_PARAMETERS and NUM_RESULT_SETS columns.</p>
Configuration
What Does Custom Catalog Views Do?
<p>"Custom Catalog Views" controls whether custom OpenLink views are used to return meta-data for some ODBC catalog functions. These custom views provide more meta-data than is normally available. To create and use them, the script odbccat[8|9].sql must be run beforehand.</p><p> The ODBC catalog functions affected are: SQLForeignKeys, SQLPrimaryKeys, SQLProcedureColumns, SQLProcedures, SQLSpecialColumns</p>
Configuration
What Does Deadlock Timeout Do?
<p>If a deadlock occurs within Progress, due to a record been accessed simultaneously by the client, this is the default time in seconds, the database agent will wait for the Progesss server to release its lock before an error will be reported back to the client. The default value is 60 seconds.</p>
Configuration
What Does Default User ID Do?
<p>This option allows a default user to be specified when a connection is attempted to a remote database.</p>
Configuration
What Does Disable Auto Commit Do?
<p>This data-source option is used to control transactions via the OpenLink driver. This option changes the default commit behavior of the OpenLink Driver. By default, this mode is set to AutoCommit.</p>
Configuration
What Does Disable Interactive Login Do?
<p>By enabling this option, the application will not prompt for a username/password when connecting to the database. The assumption here is you do not require a password to connect. This will apply to the following scenarios:</p><p> The passwords are hard-coded in the server (applies to the Multi-Tier drivers);</p><p> The database server does not require a password to connect;</p><p> The application will pass the userid/password using its own method.</p><p> The only exception where enabling this option will still prompt an interactive login is when creating a new data-source.</p>
Configuration
What Does Disable RowsetSizeLimit Do?
<p>The OpenLink Scrollable Cursor Library (SCR) by default enforces a maximum cursor row-set size of 100 on any query. This is because the larger the row-set size the more memory the SCR will require to manage this, which could begin to unnecessarily impede performance as the system resources run low. Hence the need for this restriction as general no one should ever have the need to manipulate more data than can be viewed on their screen (ie a row-set). Thus if the an application makes SQLStmtOption(SQL_ROWSET_SIZE, value) where the value is greater than 100 our driver will return SQL_SUCCESS_WITH_INFO at which point a well written application which check SQLError and receive an "Option value changed" message at which point it should call SQLGetStmtOption(SQL_ROWSET_SIZE, &value) to see what it has actually been set to, which would be 100.</p><p> Some applications, for example Power Builder, ignored the SQL_SUCCESS_WITH_INFO response and assumed the value they requested resulting in errors when they attempted to scroll paste the end of the row-set (100 rows) our driver returned. To enable such applications to work with our driver we thus introduced the Disable Rowset Size Limit option which if set removes our imposed restriction and trusts the application to set the row-set size to a reasonable value.</p>
Configuration
What Does Dynamic Cursor Sensitivity Do?
<p>Enables or disables the row version cache used with dynamic cursors.</p><p> When dynamic cursor sensitivity is set to High, the Cursor Library calculates checksums for each row in the current row-set and compares these with the checksums (if any) already stored in the row version cache for the same rows when fetched previously. If the checksums differ for a row, the row has been updated since it was last fetched and the row status flag is set to SQL_ROW_UPDATED. The row version cache is then updated with the latest checksums for the row-set.</p><p> When dynamic cursor sensitivity is set to Low, (default) performance is improved. The calculation and comparison of checksums for each row fetched carries an overhead. as the application does not need to detect the row status, SQL_ROW_UPDATED.</p>
Configuration
What Does Enable Logging Do?
<p>This option turns on ODBC call tracing and enables OpenLink Driver ODBC logging to a file. If no directory is specified, the logfile will be created in the default OpenLink installation directory.</p>
Configuration
What Does Enable Microsoft Jet Engine Options Do?
<p>The Jet Engine is synonymous with Microsoft tools such as Access, Excel (http://www.microsoft.com/office) or when developing with DAO (Data Access Objects). If your application falls into any of those categories, it is recommended that +jetfix is selected.</p><p> This option will map Microsoft Jet data types to compatible SQL Types ready for ODBC and data access. For example, the MSAccess Data Type `Money` will be converted to Float or Decimal. This is because not all databases support this type.</p>
Configuration
What Does Expression Precision Do?
<p>This option is a Progress SQL-89/4GL configuration. It provides an accurate value for Precision and Scale when the result is a Numeric Expression. For instance, select 10 + 12 in Progress will return the result as a numeric expression.</p><p> In Progress SQL89/4GL, the Precision and Scale are returned as 0 as default. This means Applications, for example MSAccess, might interpret the results as a string and label it a char column. With these variables, the user has complete control over the Precision and Scale used for expressions. By default, the OpenLink drivers will return a default of 15,2 for Precision and scale respectively.</p>
Configuration
What Does Expression Scale Do?
<p>This option is a Progress SQL-89/4GL configuration. It provides an accurate value for Precision and Scale when the result is a Numeric Expression. For instance, select 10 + 12 in Progress will return the result as a numeric expression.</p><p> In Progress SQL89/4GL, the Precision and Scale are returned as 0 as default. This means Applications, for example MSAccess, might interpret the results as a string and label it a char column. With these variables, the user has complete control over the Precision and Scale used for expressions. By default, the OpenLink drivers will return a default of 15,2 for Precision and scale respectively.</p>
Configuration
What Does Field Size Maximum Do?
<p>This option is similar to the Expression Precision/Scale option. The Progress 4GL database engine allows the storage of character strings which are longer than the declared SQL width. For instance, creating a table with a char column will default to 8 but Progress will allow you to specify more than 8 characters. By specifying a Max value, with this option, the ODBC driver internally will override the value provided by the ODBC call SQLDescribecol and use the value provided.</p>
Configuration
What Does Field Size Minimum Do?
<p>This option is similar to the Expression Precision/Scale option and is related to Field Size Maximum. As the Progress 4GL database engine allows the storage of character strings which are longer than the declared SQL width. For instance, creating a table with a char column will default to 8 but Progress will allow you to specify more than 8 characters.</p><p> When the values are returned without this option, only the first 8 characters will be returned. By specifying a Min value, the ODBC driver will override the value provided by the ODBC call SQLDescribecol and will use the value provided instead.</p><p> This is the more important of the two Field Size options and should always be specified first. For example, if your column as defined as char(8) but you have at least 255 characters, please specify a Min Field size of 255.</p>
Configuration
What Does Force Online Database Do?
<p>This applies to the Informix 7 Database which has support for both Online and Standard Engine. By specifying this value, the Informix type you intend to connect to will be set. (0) SE or (1) ONLINE. If set, the database will always appear as online.</p>
Configuration
What Does Hide Login Dialog Do?
<p>By enabling this option, the application will not prompt for a username/password when connecting to the database. The assumption here is you do not require a password to connect. This will apply to the following scenarios:</p><p> The passwords are hard-coded in the server (applies to the Multi-Tier drivers);</p><p> The database server does not require a password to connect;</p><p> The application will pass the userid/password using its own method.</p><p> The only exception where enabling this option will still prompt an interactive login is when creating a new data-source.</p>
Configuration
What Does Initial SQL Do?
<p>On occasions, there is a requirement to execute certain instructions against the database when a connect is done against the database. For example, Transactional statements to set Isolation levels. By specifying this option and providing a SQL script with DB instructions, every database connection run will execute the contents of the sql script against the Database.</p><p> This option is set by specifying a Path & Filename. The default directory is the OpenLink Installation folder.</p>
Configuration
What Does Log File Do?
<p>There are two methods of tracing ODBC calls. Tracing can be set either by the Driver Manager or by the ODBC Driver. By specifying a Path & Filename in the Logfile option, the ODBC trace generated will be done by ODBC driver. This will inform the support team of what information the Driver is sending to the database.</p><p> Please note you might also be required to provide a Driver Manager trace where applicable.</p>
Configuration
What Does Max Long Data Length Do?
<p>"Max Long Data Length" controls the maximum length of SQL_LONGVARCHAR and SQL_LONGVARBINARY data returned when deferred fetching of long data is off. When off, this setting limits the amount of memory which must be allocated for a dataset cell to hold the retrieved value - the value is truncated to this length. The default limit is 60000 bytes.</p><p> When deferred fetching is enabled, the complete SQL_LONGVARCHAR or SQL_LONGVARBINARY value can be fetched. Note that any value set via SQLSetStmtAttr(SQL_ATTR_MAX_LENGTH) takes precedence over the 'Max Long Data Length' value.</p>
Configuration
What Does Max Rows Override Do?
<p>By specifying a value within this option, we specify the maximum number of rows to be returned by any given query as opposed to the actual value of rows contained within the table.</p>
Configuration
What Does Multiplex Sessions Do?
<p>This determines the connection parallelization mode within the Informix database. Multiplex sessions are now enabled by default.</p>
Configuration
What Does NoQuotedIdentifiers Do?
<p>The Option is use by the ODBC-JDBC bridge drivers to indicate a give JDBC driver does not support the quoted identifiers, which is required for Jet engine based products like MS Access. From Multi-Tier the environment variable is JET_NOSUPPORTOFQUOTEDIDENTIFIER=[YES|NO]</p>
Configuration
What Does OCIPrefetchMemory Do?
<p>OCIPrefetchMemory and OCIPrefetchRows control parameters relating to the Oracle OCI's prefetching facility. However, use of this facility has been disabled in the OpenLink agent and Lite driver because of problems experienced with Oracle 8.x and indicator variables.</p><p> To minimize server round trips and maximize performance, the OCI can prefetch result set rows when executing a query. This prefetching operates independently of OpenLink's prefetching facility. The OCI prefetching can be customized by setting two attributes, OCI_ATTR_PREFETCH_ROWS and OCI_ATTR_PREFETCH_MEMORY. The OCIPrefetchMemory and OCIPrefetchRows settings in the OpenLink setup dialogs map directly to these OCI attributes.</p><p> OCIPrefetchMemory sets the memory allocated for rows to be prefetched. The application then fetches as many rows as will fit into that much memory.</p><p> OCIPrefetchRows sets the number of rows to be prefetched.</p><p> When both of these attributes are set, the OCI prefetches rows up to the OCIPrefetchRows limit, or until the OCIPrefetchMemory limit is reached, if this is lower.</p>
Configuration
What Does OCIPrefetchRows Do?
<p>OCIPrefetchMemory and OCIPrefetchRows control parameters relating to the Oracle OCI's prefetching facility. However, use of this facility has been disabled in the OpenLink agent and Lite driver because of problems experienced with Oracle 8.x and indicator variables.</p><p> To minimize server round trips and maximize performance, the OCI can prefetch result set rows when executing a query. This prefetching operates independently of OpenLink's prefetching facility. The OCI prefetching can be customized by setting two attributes, OCI_ATTR_PREFETCH_ROWS and OCI_ATTR_PREFETCH_MEMORY. The OCIPrefetchMemory and OCIPrefetchRows settings in the OpenLink setup dialogs map directly to these OCI attributes.</p><p> OCIPrefetchMemory sets the memory allocated for rows to be prefetched. The application then fetches as many rows as will fit into that much memory.</p><p> OCIPrefetchRows sets the number of rows to be prefetched.</p><p> When both of these attributes are set, the OCI prefetches rows up to the OCIPrefetchRows limit, or until the OCIPrefetchMemory limit is reached, if this is lower.</p>
Configuration
What Does Packet Size Do?
<p>This is the size of TCP packets sent over the network on every network hop. Increasing this value should increase performance but is risky if a packet becomes lost in the network.</p>
Configuration
What Does Prepare Method Do?
<p>This option is specific to the TDS Driver for MS & Sybase SQLServers, and can take the values None, Partial and Full (connectoptions -O [0, 1, 2] respectively) which are used to determines whether stored procedures are created on the server for calls to SQLPrepare.</p><p> When set to Full (-O 2), stored procedures are created for every call to SQLPrepare. This setting can result in decreased performance when processing statements that do not contain parameters.</p><p> When set to Partial (-O 1) (the initial default), the driver creates stored procedures only if the statement contains parameters. Otherwise, the statement is cached and run directly at the time of SQLExecute.</p><p> When set to None (-O 0), stored procedures are never created. The driver caches the statement, executes it directly at the time of SQLExecute, and reports any syntax or similar errors at the time of SQLExecute.</p>
Configuration
What Does Remote Database Alias Refer To?
<p>An alias identifying the DB2 database to connect to. This alias should be configured using the DB2 Client Configuration Assistant.</p>
Configuration
What Does RowbufferSize Do?
<p>This attribute specifies the number of records to be transported over the network in a single network hop. Values can range from 1 to 99.</p>
Configuration
What Does SQL_DBMS_NAME Do?
<p>This option allows overriding of the SQLGetInfo (SQL_DBMS_NAME) response. Ordinarily this is "ORACLE ". This option was introduced to allow our drivers to work with MSProject.</p>
Configuration
What Does Show Remarks Do?
<p>Show Remarks affects the output from SQLColumns. When enabled, the REMARKS column of a SQLColumns result set includes the comments from the COMMENTS column of the Oracle ALL_COL_COMMENTS data dictionary view. When disabled, the REMARKS column is empty. Disabling Show Remarks improves performance.</p>
Configuration
What Does Space Pad Character Columns Do?
<p>Space pad character columns controls whether data from Informix CHAR columns are returned "blank padded". When enabled, character values less than the column width are padded to the maximum width with trailing spaces, before being returned. When disabled, any trailing spaces are stripped off.</p>
Configuration
What Does USEANSINulls Padding And Warnings Do?
<p>This affects the TDS agent & Lite Drivers but only the MS SQLServer database, not Sybase.</p><p> When enabled, the agent issues the Transact-SQL commands below on connecting: SET ANSI_NULL_DFLT_ON ON .</p><p> When disabled, the agent issues the commands: SET ANSI_NULLS OFF SET ANSI_PADDING OFF SET ANSI_WARNINGS OFF SET CONCAT_NULL_YIELDS_NULL OFF</p>
Configuration
What Does Use Extended Fetch Do?
<p>`Use Extended Fetch'' controls whether Our ODBC Bridge agent/Lite uses the SQLExtendedFetch() function of the underlying ODBC driver, if it's available, when fetching data. Using the bridged driver's SQLExtendedFetch() should improve performance. However it may be necessary to disable this setting- for instance, some drivers do not support extended fetching on a result-set produced by an ODBC catalog call.</p><p> When extended fetching is disabled, the bridged driver's SQLFetch() function is used instead.</p>
Configuration
What Does Use SPACE For SQL_IDENTIFIER_QUOTE_CHAR Do?
<p>This is a Progress SQL-89 specific option which if set the driver returns " " rather than "" to represent this database does not have a quoted identifier character. The ODBC specification says that " " is what should be returned but some applications (like Crystal Reports) interpret this response as meaning the quoted identifier character is a "space", which obviously does not make sense and fails, as they are expecting "" to be returned hence this need for this option.</p>
Configuration
What Does Users Own Tables First In SQL Tables Mean?
<p>This is an option specific to the UDA Oracle driver enabling the tables owned by the connected to user to be displayed first in the list present by SQLtables rather than purely in alphabetical order.</p>
Configuration
What Is The Openlink.ini File?
<p>The openlink.ini file is a Single-Tier configuration file. It appears in the /bin sub-directory of Unix-based, Single-Tier installations. openlink.ini contains database-specific environment variables.</p>
Configuration
What Is The Oplrqb.ini File?
<p>The oplrqb.ini file is the OpenLink Session Rules Book. The OpenLink Session Rules Book contains parameters that the Request Broker uses to resolve Multi-Tier connections. The Session Rules Book also contains:</p><p> Request Broker configuration parameters; Networking & protocol specific parameters; Expression-based rules that comprise Multi-Tier enhanced security;</p><p> Some Admin Assistant configuration parameters</p>
Configuration
What Is The Udbc.ini File?
<p>The udbc.ini file contains client configuration parameters and data source connection parameters that facilitate use of OpenLink's UDBC drivers. It is similar in structure to the standard odbc.ini file. Users do not need to configure udbc.ini, unless they choose to use OpenLink's proprietary UDBC data access protocol. Users choose UDBC to bypass dependence on an ODBC driver manager. However, due to prevalence of iODBC and other driver managers on Unix, UDBC is no longer needed. OpenLink has dropped support for UDBC in its 5.0 releases.</p>
Configuration
What Is The odbcinst.ini File?
<p>The odbcinst.ini file is a standard ODBC configuration file. It consists of a list of drivers installed on the operating system and individual configuration sections for each driver. The configuration sections usually contain a Driver parameter, which passes the full path to the driver. These sections also contain a Setup parameter, which passes the location of the setup dialogs that are use to configure data sources that reference the driver. Other parameters appear as needed.</p>
Configuration
What Is Zero Config?
<p>OpenLink's ZeroConfig functionality allows the OpenLink administrator to define sets of database connection parameters using the Administrative Assistant. For instance, the OpenLink Administrator may hard-code the Request Broker host and port, database name, database username, and database password in a ZeroConfig Data Source. Existing ZeroConfig Data Sources are broadcast over the corporate network. End users may create Data Source Names from scratch. Alternatively, users may select a convenient ZeroConfig Data Source Name. Use of ZeroConfig Data Sources allow novice or non-privileged users to connect to the database using an immediate and reliable set of connection parameters.</p>
Configuration
What Ports Do Users Need To Open On Their Firewalls To Use OpenLink Software?
<p>Single-Tier users should not need to open ports to accommodate the Single-Tier driver. However, ports may need to be opened to facilitate connections between the database native client and the database to which it connects. Multi-Tier users need to take the following action, if a firewall surrounds the machine that contains the Multi-Tier server components</p>
Configuration
What Services Do Users Start To Use OpenLink Drivers?
<p>OpenLink Single-Tier users do not need to start services to use their drivers. Single-Tier users need to start the HTTP-Based iODBC Data Sources Administrator, if they want to use the graphical configuration utility. Use the following command to proceed: iodbc-admin-httpd.sh start OpenLink Multi-Tier users need to start their Request Brokers to use their drivers. Use the following command to start the Broker and the associated Administrative Assistant: oplrqb</p>
Configuration
What Values Do Multi-Tier Users Need To Pass In Their Data-Sources?
<p>Multi-Tier users must pass the following values in their Multi-Tier DSNs: Server — Passes the hostname or IP address of the server on which the Multi-Tier Request Broker listens. Also passes the TCP port on which the Broker listens. The format is host:port.</p><p> Domain — This value corresponds to a Domain Alias that appears in the [Domain Aliases] section of the Session Rules Book. Default Domain Aliases are named after the databases to which the database agent connect. Custom Domain Aliases may take any form.</p><p> Database — This is the name of the database or Oracle SID.</p><p> Login ID — This is a valid database username.</p><p> Password — This is a valid database password.</p>
Configuration
What Values Do Single-Tier Users Need To Pass In Their DataSources?
<p>All Single-Tier users must pass a valid Data Source Name.</p>
Configuration
What Values Must I Pass In My Single-Tier DSN?
<p>UDA Support Primer Data Source Name (DNS) Creation What values must I pass in my Single-Tier DSN All Single-Tier users must pass a valid Data Source Name.</p>
Configuration
What is the odbc.ini file?
<p>The odbc.ini file is a standard, ODBC client configuration file. It is not specific to OpenLink drivers. In fact, many systems may have a pre-existing odbc.ini file in /etc or another directory. Nevertheless, OpenLink components ship with their own odbc.ini file. It appears in the /bin sub-directory of Unix installations. odbc.ini contains a list of all the Data Sources that appear within.</p>
Configuration
What values do I pass for my OpenLink environment variables?
<p>OpenLink's ODBC drivers recognize the following ODBC-specific environment variables.</p><p> Users should not set ODBC variables manually. OpenLink's drivers ship with openlink.sh and openlink.csh files. These files appear in the root of the OpenLink installation. openlink.sh should be sourced if using Bourne or Bash shells. openlink.csh should be sourced in C shell.</p>
Configuration
What values must I pass in my Multi-Tier DSN?
<p>You must pass the following values in your Multi-Tier DSN: Name A descriptive name that identifies the Data Source. Server Passes the hostname or IP address of the server on which the Multi-Tier Request Broker listens. Also passes the TCP port on which the Broker listens. The format is host:port. Domain This value corresponds to a Domain Alias that appears in the [Domain Aliases] section of the Session Rules Book. Default Domain Aliases are named after the databases to which the database agent connect. Custom Domain Aliases may take any form. Database This is the name of the database or Oracle SID. Login ID This is a valid database username. Password This is a valid database password.</p><p> Is your Multi-Tier Request Broker and DBMS installed on separate machines? If so, one of the following values must be added to your DSN:</p><p> DB2 Server/Adapter Passes a remote DB2 database alias. Informix Server Passes the name of the Informix server. Ingres Net (vnode) Passes vnode::database name. MySQL Connect Options Passes -H host -P port -T. Oracle SQL*Net Alias Passes an Oracle SQL*Net alias. PostgreSQL Connect Options Passes -H host -P port -T. Progress Connect Options Passes Progress -S socket -H host -N tcp parameters. SQLServer Connect Options Passes -S followed by a SQLServer instance name. Sybase Connect Options Passes the Sybase instance name.</p>
Configuration
Why Do Some Users Require Permanent Licenses Where as Some Users Do Not?
<p>OpenLink's 1.x and 3.x drivers shipped with built-in, non-expiring, 2 user/10 concurrent connection licenses. This feature mitigated the need for permanent key, so long as usage stayed within these parameters.</p>
Configuration
Why Do Some Users Require Temporary Licenses Where as Some Users Do Not?
<p>OpenLink's 1.x and 3.x drivers shipped with built-in, 2 user/10 concurrent connection licenses. This feature mitigated the need for a temporary license key.</p>
Configuration
Why Should I Upgrade?
<p>End-users are encouraged to upgrade to the latest software version. The latest software contains desirable new features and fixes for bugs. Additionally, support options are limited, when legacy software is involved. Development does not back-patch legacy bugs, and Support staff may have difficulties recreating legacy problems. The following table lists new features for recent software builds: 4.x ODBC 3.5 compliance. Multi-Threaded client & server components. Substantially-revised communications layer. 5.x Unicode support. Zero Config. Best communications layer.</p>
Documentation
How Do Your Drivers Work?
<p>OpenLink's Single-Tier drivers are client-side drivers. Users install most Single-Tier drivers on a machine, which contains the database native client. The drivers connect to this native client and send queries-through the client—to the database. In essence, the database native client speaks a proprietary network protocol that bridges the gap between a local driver and a remote database.</p><p> OpenLink's MS SQLServer, MySQL, PostgreSQL, and Sybase drivers are "wire protocol" drivers. These drivers contain libraries, which allow them to speak their database's native network protocol. Hence, users may install these drivers on any supported operating system. These drivers do not need the database native client to connect.</p><p> OpenLink's Multi-Tier drivers are client/server drivers. All users install the client on the machine, which contains their client application. Most users install OpenLink's Multi-Tier server components on a machine that contains the database or the database native client.</p><p> OpenLink's Multi-Tier server components consist of a Broker and a database-specific agent. The Broker responds to client requests and spawns the database agent that is designed to speak to the intended database. This agent is written in the database CLI and may speak directly to the database or proxy queries through the database native client. Moreover, the database agent is responsible for the return of data to the calling application.</p><p> Finally, persons with MS SQLServer, MySQL, PostgreSQL, and/or Sybase databases may install their Multi-Tier server components on any supported operating system. These agents speak the database native communications protocol. Consequently, they can establish connections to remote databases without the aid of the database native client.</p>
Evaluation
Does OpenLink produce custom software for evaluators?
<p>OpenLink can build custom software for users, provided OpenLink has access to the requisite databases, operating system, and development tools. (OpenLink can purchase these tools or use tools provided by the user.)</p><p> Note: Custom builds come at a cost so please contact your OpenLink Account Manager to discuss any arrangements you have.</p>
Evaluation
How Do I Get An Evaluation License File?
<p>OpenLink's downloads page emails licenses to the email account that appears in the user's profile. Take the following action, if a user does not receive a license file:</p><p></p><p> — Encourage the user to repeat the downloads process and stop, just before he or she downloads the software. The OpenLink web page should send a license key to the user's email.</p><p> — Verify the user's email address, if the problem persists.</p><p></p>
Evaluation
How can I assess my data access needs?
<p>Use the following series of questions to help you resolve your data access needs:</p><p>Do you need to:</p><p> — Category 1. Query a database with one or more client applications?</p><p> — Category 2. Query two or more heterogeneous databases simultaneously?</p><p> — Category 3. Migrate data from one DBMS to another?</p><p>If you fall into Category 1, you require our ODBC or JDBC Drivers. If you fall into Category 2, you require our Virtuoso suite.</p><p>For category 3, we recommend the Virtuoso suite. Alternatively, if you are using an existing Data Migration tool such as Oracle HS services, UDA is what you require as these drivers work in conjunction with other data migration utilities such as Ms SQLServer's DTS Wizard.</p><p>Does OpenLink provide Single-Tier or Multi-Tier drivers for the evaluator's DBMS?</p><p> — Category 1 - Yes.</p><p> — Category 2 - No.</p><p> Evaluators in Category 1 may use the appropriate UDA driver for your database.</p><p> If you fall into the second Category, you may use OpenLink's generic ODBC drivers. Both the generic Single-Tier and Multi-Tier ODBC drivers connect to 3rd-party Data Sources, which allow connectivity to your DBMS.</p><p> Does your evaluator have the database native client?</p><p> — Category 1 - Yes. It is installed on the same machine as the client application.</p><p> — Category 2 - Yes. It is installed on a different machine on the network.</p><p> — Category 3 - No.</p><p> For evaluators who fall into the Category 1, we recommend Our OpenLink Single-Tier drivers.</p><p> We recommend OpenLink's Multi-Tier drivers to evaluators in Category 2.</p><p> Evaluators in Category 3 must install the OpenLink server components on their database server.</p><p> NOTE:Evaluators in Category 2 may install the OpenLink server components on their database server or any machine, which contains the database native client. In this scenario, the OpenLink database agent can connect to the database through that database client. Please see the technical article on connecting via in a three-tier environment</p>
Features
Do OpenLink ODBC Drivers Load Share when used in Active-Active Clusters?
<p>Our Multi-Tier drivers may be deployed in a load balancing architecture.</p>
Features
Do OpenLink Drivers (ODBC or JDBC) function in Fail-over Cluster environments?
<p>Yes. OpenLink functions in Fail-over Cluster environments.</p><p> Multi-Tier users must install one set of OpenLink server components (Request Broker & Database Agent) on each node. The fail-over Broker may be instantiated by shell scripts, cron, or some other startup procedure, when the active node goes down.</p><p> Some environments may support multiple, running Request Brokers, so long as each Request Broker can bind to a unique IP address.</p>
Features
Do OpenLink ODBC & JDBC drivers also provide data migration facilities?
<p>OpenLink's ODBC & JDBC drivers can be used in conjunction with 3rd-party data migration facilities. However, OpenLink's Virtuoso Server provides Snapshot Replication and a Virtual Database Repository. Virtuoso Snapshot Replication is similar to MS SQLServer's Data Transformation Services (DTS) Wizard.</p><p> Virtuoso's Virtual Database Repository provides one with an interface and functionality similar to MS SQLServer's Linked Servers or Oracle's Heterogeneous Services.</p>
Features
What Do Your Drivers Do?
<p>OpenLink's Data Access drivers enable users to establish ODBC, ADO.Net, OLEDB and JDBC connections between applications and databases. Applications use these connections to execute SQL queries against the data contained within the databases. Typical SQL queries select, insert, update, or delete data. Other queries add, modify, or delete the structures that contain the data.</p>
Features
What Is The JDBC-ODBC Bridge?
<p>The JDBC-ODBC Bridge—or "Type 1" JDBC connection—allows users to establish connections to ODBC Data Source Names using a JDBC connection URL. The JDBC connection URL passes the name of a valid ODBC Data Source as a connection parameter</p>
Features
What Is The ODBC-JDBC Bridge?
<p>OpenLink's ODBC-JDBC Bridge drivers allow ODBC Data Source Names to connect to JDBC connection URLs. This allows ODBC compliant applications to connect to and query JDBC data stores.</p>
Features
What Is The ODBC-ODBC Bridge?
<p>OpenLink Software builds specific database agents for DB2, Informix, Ingres, MS SQLServer, MySQL, Oracle, PostgreSQL, Progress, and Sybase. However, many users have Access, Paradox, Btrieve, DBase, and other databases for which OpenLink does not build agents. The ODBC-ODBC Bridge enables users to connect OpenLink drivers to these databases. The Bridge proxies OpenLink driver connections through 3rd party drivers that already connect to the database.</p>
Installation
Can I Install New Software On Top Of Existing Software?
<p>Users can install new software on top of existing software. However, this is not the preferred course of action, in many circumstances. Users should install new software to new directories if they are attempting to compare software performance or troubleshoot problems.</p>
Installation
Can OpenLink provide ftp access to the downloads files?
<p>OpenLink has two ftp sites. They are: UK FTP: ftp://ftp.openlinksw.co.uk/ and US FTP: ftp://www.openlinksw.com/ . Please note that the products are labeled according to their internal code, therefore please check with your support consultant before downloading to ensure you have the right product.</p>
Installation
Can OpenLink provide installation files on CD?
<p>OpenLink does not have ready-made installation CDs. However, OpenLink has the facilities to create CDs on request for customers and partners. Please contact your account manager who will consider your request.</p>
Installation
Can users install on top of existing OpenLink software installations?
<p>Users may install new driver installations atop old driver installations. Users may install different UDA products -i.e., the Single-Tier and Multi-Tier suite on top of one another and maintain the functionality of both.</p>
Installation
Can users manually extract and install the software?
<p>Windows users must use WinZip or a similar utility to extract OpenLink components from .zip files. Unix users must use install.sh whenever possible. Manual extraction is not supported. However, users may use gunzip and tar to extract components, if all attempts to use install.sh fail.</p>
Installation
Can you explain OpenLink installation file naming conventions?
<p>OpenLink's installation archives follow an eight character naming convention. The first two characters represent the operating system, on which the product was compiled. The third and fourth characters represent the component type, i.e., client, database agent, request broker, Single-Tier driver. The remaining characters specify for which database a product is meant to connect.</p><p> Generic components will contain a series of `x's or `z's in this field.</p>
Installation
Components are missing after installation. What do I do?
<p>Occasionally, Unix database agent installation files do not contain database agents. Instead, they contain object code and re-link scripts, which allow users to compile their own agents. This is normal due to the actual database not been available on our internal servers. Nevertheless, users can confirm this with OpenLink Product Support staff.</p><p> If requesting a database agent or components from the OpenLink Support staff, please have the following information, where available, ready.</p>
Installation
How Do I Install Your Products?
<p>OpenLink's Data Access products are easy to install. Follow the instructions that correspond to the user's operating system:</p><p></p><p> 1. Linux/Unix - Download the appropriate component archives and install.sh. Place the archives and install.sh into the same directory. Run the following command and follow the instructions: sh install.sh</p><p> 2. Mac - Download the .dmg file and extract the .mpkg file that is contained inside it. Double-click the .mpkg file. Then, provide information and follow instructions, as prompted by the installation dialog screens.</p><p> 3. VMS</p><p> 4. Windows - Download the appropriate .zip installer. WinZip the installer and run setup.exe. (Setup.exe may appear in the root of the extracted files or in a Disk1 subdirectory.) Provide information and follow instructions, as prompted by the installation dialog screens.</p>
Installation
How To FTP?
<p>FTP all installation shell scripts (install.sh) in ASCII transfer mode. FTP all other files in binary.</p>
Installation
How To Uncompress Files?
<p>OpenLink's products ship in a compressed file format:</p><p> — .bin Binary Mac Classic</p><p> — .dmg Disk Image Mac OS X</p><p> — .hqx BinHex Mac Classic</p><p> — .tar Compressed Archive Unix Decompress with install.sh</p><p> — .taz GZIP Archive Unix Decompress with tar -xvfz or gunzip</p><p> — .zip Zip File WinZip Decompress with WinZip</p>
Installation
I cannot download software to the appropriate machine. What do I do?
<p>Network or security policies may restrict a user's ability to download software onto a machine.</p>
Installation
What Do I Do With The License File?
<p>Windows Single-Tier users must copy the file to their Lite32 directories. Mac and Unix Single-Tier users must copy the files to the /bin sub-directory of their OpenLink installations. No additional action is needed. All Multi-Tier users must copy their licenses to the /bin sub-directory of the OpenLink installation. Then, Multi-Tier users must restart their Request Broker services. ALERT OpenLink's 1.x and 3.x licensing mechanism differs substantially from the current procedure. Single-Tier legacy license holders must transfer their license file to the /bin sub-directory of their OpenLink installation. Then, they must run the register.exe program. Multi-Tier legacy license holders must perform the following actions:</p><p> Shutdown the OpenLink Request Broker;</p><p> Transfer the license file to the /bin sub-directory of their server installation;</p><p> Rename license name.ini to register.ini;</p><p> Run register.ini;</p><p> Restart the Request Broker Service.</p>
Installation
What Happened To The JdbcJodbc_sv And Judbc_sv Agents?
<p>OpenLink's 1.x and 3.x Multi-Tier connections spawned a JDBC-specific agent (jodbc_sv, judbc_sv), which spawned a database-specific agent. OpenLink's newer drivers have incorporated the functionality of jodbc_sv and judbc_sv into the database agents. Hence, separate jodbc_sv and judbc_sv agents are no longer needed.</p>
Installation
What Is The Proper Way To Perform An Upgrade?
<p>Single-Tier users should terminate active ODBC connections, which use OpenLink's drivers. All Single-Tier users should back up their licenses, and Unix Single-Tier users should back-up existing odbc.ini and openlink.ini files. Finally, Single-Tier users should proceed with their upgrades. Multi-Tier users should terminate active ODBC connections, which use OpenLink's drivers. Multi-Tier users should also stop their Request Broker services. All Multi-Tier users should back-up their license and oplrqb.ini files, and Unix Multi-Tier users should back-up their odbc.ini files. Finally, Multi-Tier users should proceed with their upgrades. What about upgrading driver name or installing new driver?</p>
Internal
Is OpenLink Support Staff responsible for all user problems?
<p>OpenLink Support staff should endeavor to solve most problems. However, some problems are the domain of the user. OpenLink Support staff is not responsible for extensive custom development. Users must code their own applications or seek assistance from OpenLink's Professional Services team. Likewise, OpenLink staff is not responsible for user database and network administration.</p><p></p><p> — Acceptable: Can you help me write a JDBC connection URL to connect my application to Informix?</p><p> — Questionable: Can you help me write a JAVA program?</p><p> — Acceptable: Can you help me establish an ODBC connection to Oracle?</p><p> — Questionable: Can you help me tune Oracle?</p><p></p>
Licensing
How Do Users Obtain Licenses?
<p>OpenLink's downloads page forwards temporary licenses to the user's email account. Users must approach an OpenLink Account Manager to obtain a permanent license or purchase using the online ordering system.</p>
Licensing
How can I tell if a license is or is not corrupt?
<p>Use ASNPRINT.exe to diagnose the functionality of 4.x and 5.x licenses. ASNPRINT.exe displays the terms of functional licenses. It cannot read corrupt licenses.</p><p> ASNPRINT.exe can not read OpenLink's 1.x and 3.x license file format. Transfer these licenses to the relevant platform. Attempt to register the appropriate product with these drivers. Then, take the action that corresponds to that product:</p><p> 1. Set the system clock ahead to test Single-Tier data sources.</p><p> 2. Start the Request Broker with oplrqb -dv to verify the proper license terms.</p>
Licensing
How do I get a commercial license?
<p>Users must contact an OpenLink Account Manager to obtain a commercial license. Consultants cannot generate non-expiring, commercial licenses for users.</p>
Licensing
How does clustering affect licensing?
<p>Single-Tier users must license each individual Single-Tier installation. Multi-Tier users must obtain a distinct license for each running Request Broker. Hence, all load balancing architectures require two or more Request Broker licenses. Fail-over architectures may share one license, so long as only one Request Broker runs at a time. However, some fail-over architectures may require or benefit from multiple licenses.</p><p> Note:Please contact your Account Manager for more information on your Clustering License needs</p>
Licensing
How much do licenses cost?
<p>Pricing Information can be obtained from the Sales section (http://www.openlinksw.com/sales ) of the OpenLink Web Site:</p>
Licensing
What Can I Do To Assist Users Who Have Lost Their Licenses?
<p>Users may repeat the downloads process—up to three times—to obtain new, temporary licenses. However, this option is inconvenient for many persons. Consequently, consultants may generate licenses with the license generators. Alternatively, consultants may ask the Account Manager to generate a temporary key. Users must contact their OpenLink Account Managers to obtain a new, permanent license.</p>
Licensing
What Do I Do If My Existing License Key Does Not Work?
<p>Some users cannot use existing licenses to register their software. Take the following action:</p><p></p><p> 1. Ensure that all ftp transfers are conducted in binary transfer mode. OpenLink's licenses are binary executables.</p><p> 2. Obtain Single-Tier client driver versions or Multi-Tier Broker versions. Use ASNPRINT.exe to ensure that the license and product share the same version. (Consultants must open 1.x and 3.x licenses with Notepad. ASNPRINT cannot read these files.)</p><p> 3. Remove extraneous, OpenLink licenses from the machine.</p><p> 4. Insure that the OpenLink's Windows and Unix licenses are passed by the PATH environment variable. Insure that Unix licenses are passed by the Unix OPL_LICENSE_DIR variable.</p><p> 5. Remove references to old, OpenLink licenses from the registry, if the problem persists. (Search using license product code.)</p><p> 6. Please reinstall and register the software, if the problem persists. Windows Single-Tier users should remove references to the Single-Tier driver-from their registries-before re-installation. Users may run regedit from a terminal prompt to access their registries.</p>
Licensing
What Do I Do If My Existing License Key Is Expired?
<p>Users may obtain additional, temporary license keys from the OpenLink web site. Users proceed through the downloads matrix and stop, when they are presented with the product download links. Licenses are mailed to users, before they click the actual links to obtain the software.</p>
Licensing
What Do I Tell Users Who Want New Temporary Licenses?
<p>Users may repeat the downloads process—up to three times—to obtain new, temporary licenses. However, this option is inconvenient for many persons. Consequently, consultants may generate licenses with the license generators. Alternatively, consultants may ask the Account Manager to generate a temporary key.</p>
Licensing
What Is A Concurrent Connection?
<p>A concurrent session is an open database session. Users often confuse database connections with perceived application connections. For example, Microsoft Access may appear to open one connection against the target database. However, Access really spawns 2 or more database sessions. This causes an unexpected number of licenses to be consumed. Users must understand that Access and other connections are coded to behave in this manner.</p>
Licensing
What Is A Concurrent User?
<p>A concurrent user is a distinct ip address.</p>
Licensing
What Is ASNPRINT.exe?
<p>ASNPRINT.exe is a diagnostic utility. It reads OpenLink 4.x and 5.x licenses, and displays the terms associated with those licenses. ASNPRINT.exe cannot read corrupt licenses. ASNPRINT.exe cannot read 1.x or 3.x licenses.</p>
Licensing
What Licenses are provided?
<p>OpenLink provided non-expiring, evaluation licenses with 1.x and 3.x Multi-Tier software. Inform 1.x and 3.x users that OpenLink's latest components use a new licensing model. Then, send these users to Account Management for additional information.</p>
Licensing
What are the UDA Licensing Model based on?
<p>Both Single-Tier and Multi-Tier license models are based on concurrent "users" and concurrent "connections."</p>
Open Database Connectivity (ODBC)
What is Generic ODBC?
<p>OpenLink's ODBC Lite and Generic ODBC drivers perform a special function. These drivers enable users to establish ODBC connections to databases, for which OpenLink does not provide an agent. To proceed, users must possess native or 3rd party ODBC drivers that connect to their databases. Then, users must install OpenLink's ODBC Lite drivers on the machine, which contains these drivers. Multi-Tier users must install the Request Broker and Generic ODBC Agent on the machine, which contains these drivers. Multi-Tier users may install the Multi-Tier client on any supported operating system. Finally, OpenLink's ODBC Lite and Generic ODBC drivers proxy SQL requests from the application-through the 3rd party Data Source Name-to the actual database.</p>
Performance
How can I bench-test OpenLink drivers?
<p>You can download OpenLink ODBC Bench to run TPC-A like and TPC-C like bench tests against OpenLink and non-OpenLink ODBC drivers.</p><p> OpenLink Software also provide a OpenLink JDBC Bench to run TPC-A like bench tests against OpenLink and non-OpenLink JDBC drivers.</p><p> Please feel free to contribute your results to the OpenLink Product Support team</p>
Performance
How can I detect bottlenecks caused by OpenLink drivers?
<p>Download ODBC Scan to detect bottlenecks caused by OpenLink drivers.</p>
Performance
How can I prevent performance problems?
<p>As the OpenLink MT and ST drivers are middleware software, it is important to note that its performance can be influenced by the Client and Server configurations in use. This means, lack of system memory, kernel configurations, disk space, sql queries, coding techniques, un-indexed tables, network can all play a major part in the performance of the driver. Notwithstanding, we have outlined below ways in which you can increase the performance of the drivers.</p><p></p><p> 1. Use OpenLink Single-Tier drivers where possible.</p><p> 2. It is always recommended that, OpenLink's latest drivers are used where possible as these contain patches that might alleviate any performance bottlenecks you are facing. Only use OpenLink 4.2 drivers where we do not have a driver available. If you request this driver, please contact a Product Support consultant who will liaise with your Account Manager.</p><p> 3. Establish 3-Tier Multi-Tier connections when Single-Tier connectivity is not possible.</p><p> 4. Establish shared memory connections to databases that provide sockets and shared memory alternatives.</p><p> 5. Check your DSN's "Defer fetching of long data" check box, when your result-sets contain binary data.</p><p> 6. Locate the Row Buffer Size box that appears on your DSN setup dialog. Set this value to 1. Test. Next, set Row Buffer Size to 99. Test. Do you see a difference? If the first test is faster, your performance problems may stem from the makeup of your result-sets. If the second test is faster, your performance problems may stem from network latency. This awareness will help you set your Row Buffer Size in a manner that is beneficial to your situation.</p><p> 7. Test a variety of client and server cursor modalities. Choose the modality that suits your application needs and provides the best performance.</p><p> 8. If you are using the Multi-Tier Drivers, you can also increase the Send & Receive sizes. These might have an adverse effect on the network if you increase it sharply. Please consult your Product Support consultant if you want more information on this. If you increase this value, please ensure the Client (Send size) matches the Server (Receive size) and vice versa. Typically, this value is only increase when sending data from the Server to the client</p><p> 9. If using the Multi-Tier drivers, please ensure your Reuse Rule is set in a manner that is appropriate for your system. If you anticipate long and complex queries, it is recommended that you do not reuse the agent. Alternatively, if you are in an environment that utilizes short, sharp bursts at the system, it might be conducive if you share agents, this means less system processes and resources will be instantiated on your system.</p><p> 10. In OpenLink 5.x Multi-Tier, we have introduced the Linger Timeout. This creates a Connection Pooling environment on the server when handling connections. This means dormant connections can be reused.</p>
Troubleshooting
Heavy load causes my ODBC connections to fail. What do I do?
<p>Use the following guidelines to troubleshoot heavy problems:</p><p></p><p> 1. Patch databases and operating systems regularly.</p><p> 2. Contact database and o/s vendors to see if patches are associated with problems.</p><p> 3. Insure Unix kernel tuning parameters match parameters specified by database and o/s documentation.</p><p> 4. Insure your machine has adequate memory and processor resources.</p><p> 5. Comparison test Multi-Tier drivers when Single-Tier drivers appear to expose limitations in a database native client.</p><p> 6. Re-link Multi-Tier database agents against databases, especially patched databases.</p><p> 7. Insure PortHigh is set in the [Protocol TCP] section of the Multi-Tier Session Rules Book. This is the oplrqb.ini file that resides in the /bin sub-directory of the server components installation.</p><p> 8. Multi-Tier users perform the following test:</p><p> — login to the machine that contains the OpenLink server components.</p><p> — Run oplshut -s on the command-line.</p><p> — Compare the output to the Windows Task Manager or Unix ps -ef.</p><p> — Upgrade server components if oplshut shows fewer processes when compared to the Task Manager or ps.</p><p></p><p>Multi-Tier users experiment with database agent reuse. Users should do comparison test with the following values:</p><p> — ifsame process, upto 5</p><p> — ifsame application, upto 5</p><p> — ifsame database, upto 5</p>
Troubleshooting
How Do I Assist Users Who Cannot Set Environment Variables?
<p>Instruct users to perform the following action:</p><p> — Insure that the openlink.sh and openlink.csh files are executable.;</p><p> — Run . ./openlink.sh in a Bourne and/or a Bash shell. ;</p><p> — Run source openlink.csh in a C shell, if the problem persists. ;</p><p> — Set the variables—contained within the shell scripts—manually, if the problem persists.</p><p>Users do not want to set variables on the command line. However, this may be a temporary solution to an environment variables problem. Remind users that some systems accept the following syntax: export ODBCINI=/usr/openlink/bin/odbc.ini .</p><p>However, some systems prefer this syntax: set ODBCINI=/usr/openlink/bin/odbc.ini;export ODBCINI .</p><p>When in doubt, consult the man pages or another Unix reference.</p>
Troubleshooting
How Do I Assist Users Who Cannot Start The Multi-Tier Request Broker?
<p>Take the following action:</p><p> 1. Insure that a valid license appears in the /bin sub-directory of the OpenLink server components installation. The broker will not start without a valid license. ;</p><p> 2. Check directory and file permissions.;</p><p> 3. Compare the name of the Unix .taz files with the output of uname -a. Determine whether or not the component is compatible with the operating system.;</p><p> 4. Use a text editor to open the oplrqb.ini file. Locate the [Protocol TCP] Listen parameter, and take note of the port.;</p><p> 5. Run netstat -a and open /etc/services or C:/WINNT/SYSTEM32/DRIVERS/ETC/services to determine if the Broker's Listen port is in use by another service. This is typical of Windows XP which uses port 5000 by default.;</p><p> 6. Run netstat -a open /etc/services or C:/WINNT/SYSTEM32/DRIVERS/ETC/services to determine if UDP port #60001 is in use. This will affect 1.x and 3.x installations.;</p><p> 7. Attempt to start Windows Brokers with the Services utility and the DOS command line.;</p><p> 8. Determine what service packs, patches, or upgrades have been applied to the operating system. Some upgrades cause the Broker service to fail.;</p>
Troubleshooting
How Do I Interpret Admin Assistant Logs?
<p>The Admin Assistant writes the following information to a file, when startup is successful:</p><p></p><p> Thu Mar 04 2004</p><p>15:07:11 started http://openlinux.openlinksw.com:8051</p><p></p><p>Here, we see the URL from which the Admin Assistant is accessed in a browser. The first part of the URL designates the machine (openlinux.openlinksw.com) on which it started. The number appended to the end of the machine is the TCP port on which it listens. This port is also the HTTPServer port that appears in the www_sv.ini file. The www_sv.ini file appears in the /bin/w3config sub-directory of OpenLink server components installations. The Admin Assistant will write simple error messages to the log when startup fails. Consultants must search the knowledge-base for the import of these errors. Finally, we have reviewed the default Admin Assistant log entries. However, users can cause the Admin Assistant to run at log level 7. This is achieved by setting the log level in the [www_sv] of the Session Rules Book. For example:</p><p></p><p>[www_sv]</p><p>Program = w3config/www_sv</p><p>Directory = w3config</p><p>CommandLine = +loglevel 6</p><p></p><p>Log level 7 causes the Admin Assistant to output an HTTP log that display individual scripts and images as it serves them. Be sure to look for errors interspersed between the entries. </p>
Troubleshooting
How Do I Interpret Classpaths?
<p>The CLASSPATH variable passes the full path to an OpenLink opljdbc.jar or megathin.jar file. Consultant's need to consider the following factors when examining CLASSPATH environment variables:</p><p></p><p> 1. Was CLASSPATH set at the time of reported failure? Review the output of set, the Windows autoexec.bat file, or Windows System utility screen-shots for corroboration.</p><p> 2. Does CLASSPATH point to a valid .jar file? Review the output of ls or dir in the directory structure for the purpose of corroboration.</p><p> 3. Do file or directory permissions issues restrict access to the .jar file?</p><p> 4. Does the .jar file JDK version correspond with the client JRE version?</p><p> 5. Does CLASSPATH need to be set within application code?</p>
Troubleshooting
How Do I Interpret DBMS Versions?
<p>DBMS server versions can provide a host of information:</p><p></p><p> 1. Compare the user's DBMS version with the Multi-Tier database agent version string or Single-Tier driver version. Is the DBMS compatible with the agent or lite driver?</p><p> 2. Compare the user's DBMS version with the DBMS version against which OpenLink's product was built. Are they the same? Differences in server version or patch level may contribute to a host of problems including outright compatibility or subtle stability issues.</p><p> 3. Compare the user's DBMS version with the operating system version and patch level. Does the operating system meet the system requirements of the DBMS?</p><p> 4. Obtain Unix server's kernel tuning parameters. Do the tuning parameters match the requirements specified in the DBMS documentation? Insufficient tuning parameters contribute to stability problems.</p><p> 5. Is the user's DBMS server version associated with limitations or bugs? Is the DBMS server's patch level current?</p><p></p><p>Recommend re-links to Multi-Tier users, when their DBMS version and their database agent version strings differ. Relinking resolves some compatibility issues.</p>
Troubleshooting
How Do I Interpret Database Agent Version Strings?
<p>Database Agent Version Strings produce the following information: Finally, version string errors provide useful, diagnostic information. Failure to produce version strings often stems from one of three problems:</p><p></p><p> 1. The agent does not exist on the system.</p><p> 2. Permissions prohibit the execution of the agent.</p><p> 3. The agent has library issues. Typically, the agent requires the addition of the database lib sub-directory to LD_LIBRARY_PATH, LIBPATH (AIX), or SHLIB_PATH (HP/UX).</p><p></p><p>Database Agent Version Strings should be compared to Request Broker Version Strings and Client Version Strings to insure compatibility. Compatibility and stability problems arise, when Multi-Tier component versions differ.</p>
Troubleshooting
How Do I Interpret Database Profiles?
<p>Database .profiles are Unix files that contain variables that databases need to function. They appear in the root directory of most database installations. Furthermore, these environment variables facilitate ODBC, JDBC, and other data access mechanisms. Multi-Tier users need to insure that pertinent database .profile variables appear in the [Environment] section of their Session Rules Books. The Session Rules Book is the oplrqb.ini file that resides in the /bin sub-directory of the OpenLink server components installation.</p>
Troubleshooting
How Do I Interpret Installation Shell Scripts?
<p></p><p> 1. Obtain copies of the user's installation shell script and installation files.</p><p> 2. Obtain the output of uname -a on the problem machine.</p><p> 3. Transfer the files to an appropriate test box.</p><p> 4. Run the installation procedure.</p>
Troubleshooting
How Do I Interpret Name Of Taz Files?
<p>.taz file names are useful for detecting product and operating system incompatibilities. (Failure to install, core dumps, segmentation faults, signals, and blatant incompatibility errors are all possible side effects of product and OS mismatch.) If you suspect an incompatibility, obtain the name of the .taz file and a uname -a from the affected machine. Decode the .taz file name to see if it was intended for the user's operating system.</p>
Troubleshooting
How Do I Interpret Openlink ini Files?
<p>The Single-Tier openlink.ini file associates database specific environment variables and port settings with Single-Tier domain aliases. For example:</p><p></p><p>[Server Types]</p><p>Oracle 8.1.x =</p><p></p><p>[Environment Oracle 8.1.x]</p><p>ORACLE_HOME = /dbs5/oracle9i/64bit/v9.2.0.1.0</p><p>ORACLE_SID = ora92</p><p>;ORACLE_SERVER = T</p><p>;TWO_TASK = P:</p><p>;ODBC_CATALOGS = Y</p><p>;MULTIPLEX_LDA = 5</p><p>;OPL_USR_TBLS_FIRST = Y</p><p>SHOW_REMARKS = N</p><p>CURSOR_SENSITIVITY = LOW</p><p>;OCI_PREFETCH_ROWS = 100 ;</p><p>;OCI_PREFETCH_MEMORY = 65535 ;</p><p>;NLS_LANG = AMERICAN_AMERICA.UTF8</p><p></p><p>Use the following guidelines to interpret openlink.ini files:</p><p></p><p> 1. Ascertain which server type (a.k.a. "domain alias") is passed in the Single-Tier Data Source.</p><p> 2. Open the openlink.ini file.</p><p> 3. Insure that the server type appears in the [Server Type] list.</p><p> 4. Locate the [Environment] section that is associated with the server type.</p><p> 5. Insure that the appropriate environment variables are set.</p><p> 6. Compare the variable settings with the database user .profile to insure accuracy.</p><p> 7. Use relevant database utilities or configuration files to verify any TCP port settings.</p><p></p>
Troubleshooting
How Do I Interpret Output Of Java Commands?
<p></p><p> 1. Insure that the java command returns driver version information. Failure to return version information may show an incompatibility or environment problem.</p><p> 2. Insure that successful driver version information matches the expected driver name and version.</p><p> 3. Check available resources to see if the driver version is associated with limitations, bugs, or other known issues. Bugzilla is the best point of reference for OpenLink JDBC drivers.</p><p> 4. Compare Multi-Tier JDBC client java output with Request Broker Version and Database Agent Version strings. Differing client and server versions create compatibility and stability problems.</p>
Troubleshooting
How Do I Interpret Output Of Oplshut?
<p>oplshut -s produces the following output:</p><p></p><p>[openlink@openlinux bin]$ ./oplshut -s</p><p>SVPID SVTYPE MACHINE OPSYS APPLIC DATABASE USERNAME CONNECT</p><p>——————————————————————————--</p><p>1480 mys3 dyn2.openlinksw msdos cppdmo32 test mysql Mar 30 12:01</p><p></p><p>Here is a brief overview of the output displayed by oplshut -s: SVPID - Associates a Process Identification Number with a database agent. Users can run oplshut +kill svpid to terminate database agents that will not disconnect. For example:</p><p></p><p>oplshut +kill 1480</p><p></p><p>oplshut +kill will terminate all connections associated with an agent. This is important since multi-threaded agents may handle multiple connections simultaneously. SVTYPE - Passes a label which identifies the Domain Alias, which was used to establish the connection. The Domain Aliases appear in the Session Rules Book (oplrqb.ini)</p>
Troubleshooting
How Do I Interpret Output Of Set?
<p>OpenLink's Unix components require the following ODBC environment variables to be set:</p><p>— CLASSPATH A JAVA client variable that passes the full path to an OpenLink JDBC .jar file. This variable should appear on all systems that contain OpenLink JDBC client components.</p><p>— LD_LIBRARY_PATH A generic library path variable that appends the full path to OpenLink's lib sub-directory. This variable should be set on any machine that contains Single-Tier or Multi-Tier client or server components.</p><p>— LIBPATH An AIX library path variable that appends the full path to OpenLink's lib sub-directory. This variable should be set on any AIX machine that contains Single-Tier or Multi-Tier client or server components.</p><p>— ODBCINI Passes the full path to ~/openlink/bin/odbc.ini. This variable should be set on any machine that contains Single-Tier or Multi-Tier client components.</p><p>— ODBCINSTINI Passes the full path to ~/openlink/bin/odbcinst.ini. This variable should be set on any machine that contains Single-Tier or Multi-Tier client components.</p><p>— OPENLINKINI This Single-Tier variable passes the full path to ~/openlink/bin/openlink.ini. This variable should be set on any machine that contains Single-Tier client components.</p><p>— PATH Appends the full path to OpenLink's bin sub-directory. This variable should be set on any machine that contains Single-Tier or Multi-Tier client or server components.</p><p>— SHLIB_PATH An HP/UX library path variable that appends the full path to OpenLink's lib sub-directory. This variable should be set on any HP/UX machine that contains Single-Tier or Multi-Tier client or server components.</p><p></p><p>set output should be checked against ls output for the relevant directories structures. This shows:</p><p></p><p> — Which environment variables are set.</p><p> — Which environment variables are missing.</p><p> — Whether or not variable paths are correct.</p><p> — Whether or not permissions prevent access to files or directories.</p><p></p><p>OpenLink's drivers also require database specific environment variables. set should be run before Single-Tier client installation or Multi-Tier server component installation. Users must insure that the relevant database native environment variables are set. This enables OpenLink's installers to detect the settings and write them into Single-Tier openlink.ini or Multi-Tier oplrqb.ini file.</p>
Troubleshooting
How Do I Interpret Relink Scripts?
<p>OpenLink's re-link scripts are associated with missing library errors and missing symbol errors. Use the following guidelines to troubleshoot these problems: Missing Libraries:</p><p></p><p> 1. Search the machine for the missing library.</p><p> 2. Insure that no file or directory permissions prohibit access to found libraries.</p><p> 3. Insure that LD_LIBRARY_PATH, LIBPATH, or SHLIB_PATH pass the location of found libraries.</p><p> 4. Pass the full path to found libraries within the re-link script itself. In most cases, pass the library on the cc -s -o line. However, pass the library on the make -f line in Oracle scripts. Pass the library under $PRO_EXTRA in Progress mkdlc scripts.</p><p></p><p>Missing Symbols</p><p></p><p> 1. Login to the machine.</p><p> 2. cd into the database's /lib sub-directory.</p><p> 3. Run the following command: nm -A *.so | grep . For example:</p><p></p><p> nm -A *.so | grep xsendto</p><p></p><p> 4. Record the names of files, which contain the symbols. The filename will be the first name in the nm output.</p><p> 5. cd to the /lib sub-directory of the OpenLink installation.</p><p> 6. vi the script that produced the error.</p><p> 7. Pass the full path to found libraries within the re-link script itself. In most cases, pass the library on the cc -s -o line. However, pass the library on the make -f line in Oracle scripts. Pass the library under $PRO_EXTRA in Progress mkdlc scripts.</p><p></p>
Troubleshooting
How Do I Interpret Request Broker Version Strings?
<p>Request Broker Version Strings produce the following information: Version Information - Is the Broker current? Is the Broker version associated with specific limitations, formal bugzillas, or other known problems? Platform of Compilation - Compare the platform of compilation information with the output of uname -a on the affected server. Is the Broker compatible with that operating system? Finally, version string errors provide useful, diagnostic information. Failure to produce version strings often stems from one of three problems:</p><p></p><p> 1. The Broker does not exist on the system.</p><p> 2. Permissions prohibit the execution of the Broker version string.</p><p> 3. The Broker has file dependency issues. Users may need to adjust PATH or other environment variables to pick up needed libraries.</p><p></p><p>Request Version Strings should be compared to Database Agent Version Strings and Client Version Strings to insure compatibility. Compatibility and stability problems arise, when Multi-Tier component versions differ.</p>
Troubleshooting
How Do I Interpret Udbc ini Files?
<p>Here are the operative portions of a udbc.ini file:</p><p></p><p>[UDBC]</p><p>;DebugFile= /tmp/udbc.out</p><p></p><p>[Communications]</p><p>ReceiveTimeout = 120</p><p>BrokerTimeout = 30;</p><p>RetryTimeout = 5</p><p>SendSize= 4096</p><p>ReceiveSize = 16000</p><p>ShowErrors= Y</p><p>DataEncryption = N</p><p></p><p>[dsn_oracle]</p><p>Description = Sample Oracle DSN</p><p>Host = 192.62.13.144</p><p>ServerType = Oracle 8.1.x</p><p>FetchBufferSize = 60</p><p>Database = ORCL</p><p>ServerOptions =</p><p>ConnectOptions =</p><p>Options =</p><p>UserName = scott</p><p>Password = tiger</p><p>ReadOnly = yes</p><p></p><p>Here is a description of important parameters: DebugFile</p><p></p><p>The DebugFile parameter controls UDBC tracing. Users must remove the semicolon from DebugFile, if they want to instantiate tracing. They must also pass the full path to a file to which DebugFile may write output. Users must place a semicolon in front of DebugFile to stop debug output. Communications The Communications section contains</p>
Troubleshooting
How Do I Troubleshoot A Failed JDBC-ODBC Bridge Connection?
<p></p><p> 1. Insure that the ODBC Data Source Name connects to the target database.</p><p> 2. Insure that Windows-based ODBC Data Sources are System Data Sources.</p><p> 3. Insure that OpenLink's Single-Tier driver is installed on the machine that contains the ODBC Data Source Name.</p><p> 4. Insure that you pass the exact name of the ODBC Data Source in the JDBC connection URL.</p><p> 5. Insure that your Single-Tier JDBC connection URL uses the following syntax:</p><p></p><p> jdbc:openlink://ODBC[/DSN][/UID][/PWD][/READONLY]</p><p></p><p> For example:</p><p></p><p> jdbc:openlink://ODBC/DSN=Local Oracle ODBC/UID=scott/PWD=tiger</p>
Troubleshooting
How Do I Troubleshoot A Failed ODBC-JDBC Bridge Connection?
<p></p><p> 1. Insure that the JDBC connection URL connects to the target database.</p><p> 2. Insure that OpenLink's Single-Tier client components or Multi-Tier server components are installed on the machine that contains the JDBC connection URL.</p><p> 3. Multi-Tier users insure that oplrqb and a JDBC Bridge Agent (jdbc13_mv, jdbc14_mv, etc.) appear in the /bin sub-directory of the OpenLink server components installation.</p><p> 4. Multi-Tier users insure that oplrqb and the JDBC Bridge Agent (jdbc13_mv, jdbc14_mv, etc.) return version and usage information. For example:</p><p></p><p> > jdbc14_mv -?</p><p> JDBC Database Agent (JDK 1.4)(multi threaded)</p><p> Version 1.2 as of Thu Sep 04 2003 (Release 5.1 cvsid 00068).</p><p> Compiled for Linux 2.2.25 (i686-pc-linux-glibc2.1)</p><p> Copyright (C) OpenLink Software</p><p></p><p> 5. Insure that you pass the exact JDBC driver name string and JDBC connection URL in your OpenLink Data Sources. You can test the driver name string with the java command. It should return version and release information. For example:</p><p></p><p> > java openlink.jdbc3.Driver</p><p> OpenLink Generic Driver for JDBC(TM) 3.0 Version 04.19 (Release 5.1)</p><p></p><p> 6. Multi-Tier users insure that JDBC 1.1, JDBC 1.2, JDBC 1.3, or JDBC 1.4 appears in the Domain or Server Type field of the Multi-Tier Data Source Name. (Case and spacing matter!)</p><p> 7. Unix Single-Tier users insure that JDBC 1.1, JDBC 1.2, JDBC 1.3, or JDBC 1.4 appears in the Existing Environment field of the Single-Tier Data Source Name. (Case and spacing matter!)</p><p></p><p>If the problem persists, complete a troubleshooting worksheet. Post the results into an online support case.</p>
Troubleshooting
How Do Users Start The Multi-Tier Request Broker?
<p>Windows users should take the following action:</p><p></p><p> 1. Login to the machine, which contains the OpenLink server components.</p><p> 2. Open the Services utility. (Control Panel)</p><p> 3. Locate the OpenLink Request Broker service.</p><p> 4. Highlight the service.</p><p> 5. Click the Start icon.</p><p></p><p>Unix users should take the following action:</p><p></p><p> 1. Login to the machine, which contains the OpenLink server components.</p><p> 2. cd into the root of the OpenLink installation.</p><p> 3. Execute openlink.sh (Bourne/Bash shell) or openlink.csh (C shell).</p><p> 4. cd into the /bin sub-directory of the installation.</p><p> 5. Execute the following command: oplrqb</p><p></p><p>New Unix users may want to start the Request Broker with oplrqb +loglevel 7 +logfile oplrqb.log. This instantiates logging and will elucidate problems that may occur.</p>
Troubleshooting
How can I determine which ports the Multi-Tier Request Broker uses?
<p>The Request Broker port appears in the Session Rules Book. This is the oplrqb.ini file that appears in the /bin sub-directory of the user's server components installation. Users need to open this file with a text editor and locate the following section:</p><p></p><p>[Protocol TCP]</p><p>PingWatchdog = No</p><p>PingInterval = 600</p><p>Listen = 5000</p><p>PortLow = 5000</p><p>PortHigh = 5099</p><p>IPAddress = 127.0.0.1</p><p></p><p>OpenLink's 4.x and 5.x Brokers listen on the port passed by the Listen parameter. OpenLink's 1.x and 3.x Brokers listen on the initial port as specified by the PortLow parameter.</p>
Troubleshooting
How can I prevent stability problems?
<p>Use the following guidelines to prevent stability problems:</p><p></p><p> 1. Patch databases and operating systems regularly.</p><p> 2. Contact database and o/s vendors to see if patches are associated with problems.</p><p> 3. Insure Unix kernel tuning parameters match parameters specified by database and o/s documentation.</p><p> 4. Insure your machine has adequate memory and processor resources.</p><p> 5. Comparison test Multi-Tier drivers when Single-Tier drivers appear to expose limitations in a database native client.</p><p> 6. Re-link Multi-Tier database agents against databases, especially patched databases.</p><p> 7. Insure PortHigh is set in the [Protocol TCP] section of the Multi-Tier Session Rules Book. This is the oplrqb.ini file that resides in the /bin sub-directory of the server components installation.</p><p></p><p>Multi-Tier users perform the following test:</p><p></p><p> 1. login to the machine that contains the OpenLink server components.</p><p> 2. Run oplshut -s on the command-line.</p><p> 3. Compare the output to the Windows (Task Manager) or Unix (ps -ef.)</p><p> 4. Upgrade server components if oplshut shows fewer processes when compared to the Task Manager or ps.</p><p></p><p>Multi-Tier users experiment with database agent reuse. Users should comparison test the following values:</p><p></p><p> — ifsame process, upto 5</p><p> — ifsame application, upto 5</p><p> — ifsame database, upto 5</p>
Troubleshooting
How can I tell what version I have?
<p>Users may employ a variety of methods to obtain their product version information. Windows and Mac Single-Tier users should open their ODBC Administrator. The Single-Tier driver version appears on the Drivers tab of this Administrator. Users simple scroll through the Driver list box, locate their driver, and record the version string, which appears to the right of the driver name.</p>
Troubleshooting
How do I interpret Database Native Error Logs?
<p>OpenLink Product Support does not have extensive information pertaining to the interpretation of 3rd-party database error logs. Examine these logs for errors. Then, search OPIE and the database vendor knowledge-bases for additional information.</p>
Troubleshooting
How do I interpret Operating System Patch Levels?
<p>Use the following guidelines:</p><p></p><p> 1. Insure that users have applied all, current operating system patches.</p><p> 2. Determine whether or not the DBMS requires a specific patch level.</p><p> 3. Ascertain whether patches are associated with issues presented by the user.</p><p> 4. Compare the user patch level to the OpenLink build server patch level. OpenLink's build servers may require patch updates, if they are behind user patch levels. Users may need patch updates, if they are behind OpenLink's patch level. Otherwise, discrepancies between the machines may contribute to compatibility and stability problems.</p>
Troubleshooting
How do I troubleshoot a failed ODBC-ODBC Bridge connection?
<p></p><p> 1. Insure that the non-OpenLink Data Source Name connects to the target database.</p><p> 2. Insure that OpenLink's Single-Tier client components or Multi-Tier server components are installed on the machine that contains the non-OpenLink Data Source Name.</p><p> 3. Multi-Tier users insure that oplrqb and odbc_mv appear in the /bin sub-directory of the OpenLink server components installation.</p><p> 4. Insure that all Windows-based Data Source Names are System Data Source Names.</p><p> 5. Insure that you pass the exact name of the non-OpenLink Data Source to the OpenLink Data Source. Multi-Tier users pass this name in the Database field of their OpenLink Data Sources.</p><p> 6. Multi-Tier users insure that "Odbc" appears in the Domain or Server Type field of the Multi-Tier Data Source Name. (Case matters!)</p><p></p><p>If the problem persists, complete a troubleshooting worksheet. Post the results into an online support case.</p>
Troubleshooting
I cant set my OpenLink variables. What do I do?
<p>If a Unix user cannot set their environment variables with openlink.sh or openlink.csh, please type sh or cshat the command line. This should allow you to run openlink.sh or openlink.csh respectively.</p><p> If the problem persists, a manual setting will need to be completed. Users should edit openlink.sh or openlink.csh with a text file editor. Please take care when editing this file as the variables contained within this file might affect the way the OpenLink installation works. Take note of the variables within the file, close it and set the variables on the command line.</p>
Troubleshooting
I cant shutdown my Admin Assistant. What do I do?
<p>The Multi-Tier Administrative Assistant is a service. It is powered by the www_sv agent that appears in the /bin/w3config sub-directory of Multi-Tier server components installations. Unlike the Request Broker, the Administrative Assistant does not require manual shutdown. Instead, the Request Broker kills the agent during its own shutdown routine.</p>
Troubleshooting
I cant shutdown my Request Broker. What do I do?
<p>Take the following actions, if you cannot shutdown your Request Broker: Login to the machine that contains your Multi-Tier server components installation. Use a text editor to open the oplrqb.ini file that appears in the /bin sub-directory of the OpenLink installation and so on ..</p>
Troubleshooting
I cant start my Admin Assistant. What do I do?
<p>The Multi-Tier Administrative Assistant is a service. It is powered by the www_sv agent that appears in the /bin/w3config sub-directory of Multi-Tier server components installations. Unlike the Request Broker, the Administrative Assistant does not require manual startup. Instead, the Request Broker spawns the agent during its own startup routine.</p>
Troubleshooting
I cant start my Request Broker. What do I do?
<p>OpenLink's Request Brokers are listening services. OpenLink's 4.x and newer Brokers listen on the TCP port that is passed to the Listen parameter. The Listen parameter appears in the Protocol TCP section of the Session Rules Book. OpenLink's 3.x and 1.x Brokers listen on PortLow. PortLow appears in the Protocol TCP section of the Session Rules Book. OpenLink's Request Brokers also use UDP port 60001 to broadcast license information.</p>
Troubleshooting
I think I have OpenLink Software. How can I tell?
<p>It is possible your machine might contain a copy of the OpenLink Software ODBC or JDBC drivers or you might require one or more additional components -e.g., clients or agents-to match pre-existing software.</p>
Troubleshooting
My JDBC Type 3 Connections Spawn Multiple Agents That Consume My Licenses. What Do I Do?
<p>This is expected behavior. OpenLink's 1.x and 3.x Multi-Tier connections spawn a JDBC-specific agent that spawns a database-specific agent. Hence, one JDBC connection results in two concurrent connections. OpenLink's latest drivers do not spawn both a JDBC agent and a database agent. OpenLink's new database agents are equipped to handle JDBC connections in their entirety.</p>
Troubleshooting
My Request Broker shuts itself down. What do I do?
<p>Users may experience intermittent Request Broker shutdowns. This problem stems from the use of one license on multiple machines, and it produces "Duplicate Serial Number" errors. Users who encounter this problem must request an additional temporary or permanent license keys from their account manager or shut down a request broker to resolve this problem.</p>
Troubleshooting
Troubleshooting registering a product with a temporary or commercial license?
<p>Use the following guidelines to troubleshoot licensing problems:</p><p> 1. Ensure that the Windows Single-Tier license is placed in your Lite32 sub-directories.</p><p> 2. If on Unix, ensure that the Single-Tier license is placed in the b/in sub-directory of the OpenLink installation. Alternatively, users may pass the full path to licenses to OPL_LICENSE_DIR. This variable may be set using the command line, openlink.sh, openlink.csh, or your .profile.</p><p> 3. Multi-Tier users ensure the licence is placed in the bin/ sub-directory of the server component installation.</p><p> 4. Ensure that ftp transfers are conducted in binary. OpenLink's .lic licenses are binary-format files.</p><p> 5. Windows Single-Tier users should uninstall their software, remove all references to Single-Tier software from the registry, and reinstall, if licensing problems persist. Occasionally, Windows Single-Tier users experience registry corruption, which necessitates the registry wipe and reinstall.</p><p>OpenLink consultants have other utilities that may help debugging if you suspect a license-file is corrupt.</p><p>The license version must match the Single-Tier driver version or the Multi-Tier request broker and agent version. Operating System Licenses must be generated for the appropriate operating system. CPU's The number of CPUs cited in the license must match the number of CPUs present in the machine. Access Mechanism Licenses may restrict ODBC or JDBC data access. Other licenses permit both ODBC and JDBC access. Database Licenses must list each of the databases to which the user intends to connect. Applications Certain licenses are limited for use with one application.</p><p>OpenLink's 1.x and 3.x ship with a license text file. Consultants may open this license with Notepad or a similar text editor. The file should contain the same parameters listed above.</p>
Troubleshooting
What Component Naming Conventions is Used?
<p>OpenLink's client drivers are library files. Consequently, Windows Multi-Tier drivers begin with olod (OpenLink ODBC Driver) and end with a .dll extension. Unix Multi-Tier drivers are named oplodbc (OpenLink ODBC) and end with a .la, .sl, or .so extension. OpenLink's Single-Tier drivers have a variety of names that are too numerous to list. Windows drivers continue to end with .dll, and Unix drivers continue to end with .la, .sl, and .so. However, the similarities end there. The actual Windows Single-Tier driver name begin with `ntl' (WinNT Lite) and end with a series of numbers and letters that denote the driver version and intended database. The actual Unix Single-Tier driver name begins with some combination of letters that represents the intended database, and it ends with _mt_lt (Multi-Threaded Lite) , _mt_lu (Multi-Threaded Lite Unicode), _st_lt (Single-Threaded Lite), _st_lu(Single-Threaded Lite Unicode). OpenLink's Unix-based iODBC Driver Manager is named libiodbc and ends with a .la, .sl, or .so extension. OpenLink's Multi-Tier Request Broker is named oplrqb. OpenLink's Multi-Tier Database Agents begin with a three or four character name that designate the intended database, and they end with a .sv (Single-Threaded version) or .mv (Multi-Threaded version) extension.</p>
Troubleshooting
What Do I Do If My Applications Fail To Connect After I Upgraded My Multi-Tier JDBC Drivers?
<p>OpenLink's 1.x and 3.x Multi-Tier drivers use different JDBC connection mechanisms. The older drivers route the request through a JDBC-specific agent that speaks to a database-specific agent. Here is the sequence of events needed to perform this task:</p><p> 1. User creates a JDBC connection URL. For example: jdbc:openlink://localhost:5000/SVT=Ingres II/DATABASE=iidbdb/UID=ingres/PWD=ingres/JDBCAGENT=jodbc</p><p> 2. The Broker associates all JDBC connection attempts with one of the JDBC Domains that appear in the [Domain] section of the Session Rules Book (oplrqb.ini). For example:</p><p></p><p> [Domain Aliases]</p><p> jodbc = jodbc</p><p> judbc = judbc</p><p> jdbc = jdbc</p><p></p><p> 3. The Broker uses the Domain Alias to resolve the connection using one of the JDBC Mapping Rules from the [Mapping Rules] section of oplrqb.ini. For example:</p><p></p><p> [Mapping Rules]</p><p> jodbc:*:*:java:*:*:* = accept jodbc_client</p><p> judbc:*:*:java:*:*:* = accept judbc_client</p><p> jdbc:*:*:java:*:*:* = accept jdbc_client</p><p> *:*:*:java:*:*:* = accept judbc_client</p><p></p><p> 4. The Mapping Rules associate the connection attempt with a JDBC agent configuration section. For example:</p><p></p><p> [jodbc_client]</p><p> Program = jodbc_sv.exe</p><p> CommandLine = ;+debug</p><p> ReUse = never</p><p></p><p> 5. The agent configuration section controls which JDBC agent is spawned to service the connection. In the above instance, jodbc_sv.exe is spawned.</p><p> The JDBC agent spawns the database agent that corresponds to the SVT parameter of the JDBC connection URL. The following sections of the Rules Book shows how SVT=Ingres II causes the JDBC agent to spawn the oig2_sv database agent:</p><p></p><p> Domain Aliases]</p><p> Ingres II = oig2</p><p></p><p> [Mapping Rules]</p><p> oig2:*:*:*:*:*:* = reject The Ingres II Database Agent is not configured</p><p></p><p> [generic_oig2]</p><p> Program = oig2_sv.exe</p><p> Environment = INGRES_II</p><p> OpsysLogin = Yes</p><p> ReUse = never</p><p></p><p>OpenLink's newest drivers omit the need for a distinct JDBC agent. JDBC-specific Domains, Mapping Rules, Agent Configuration Sections, and agents are omitted from the connection resolution. Instead, the Broker resolves the JDBC connection URL using only the SVT parameter. The database agent that is spawned is now able to handle both ODBC and JDBC connections Users may prevent most problems by removing JDBCAGENT= from their JDBC connection URLs. If problems persist, advanced users may resolve most problems by editing the Session Rules Book. New users are encouraged to contact OpenLink Product Support. Some 1.x and 3.x users create hybrid connections that pass an ODBC DSN in a Type 3 JDBC URL. For example:</p><p></p><p>jdbc:openlink://localhost:5000/DSN=My Ingres Data Source/UID=ingres/PWD=ingres</p><p></p><p>This connection format is no longer supported.</p>
Troubleshooting
What Do I Do If My Broker Shuts Down Intermittently?
<p>Most intermittent shutdowns share a common origin. Users have copied a single license to one or more machines on a network. Users can not do this. Instead, users must obtain individual licenses for each Multi-Tier server component installation. If the problem persists, apply standard stability troubleshooting guidelines.</p><p></p><p> 1. Patch databases and operating systems, as appropriate.</p><p> 2. Contact database and o/s vendors to see if patches are associated with problems.</p><p> 3. Insure Unix kernel tuning parameters match parameters specified by database and o/s documentation.</p><p> 4. Insure your machine has adequate memory and processor resources.</p><p> 5. Insure PortHigh is set in the [Protocol TCP] section of the Multi-Tier Session Rules Book. This is the oplrqb.ini file that resides in the /bin sub-directory of the server components installation.</p><p> 6. Multi-Tier users perform the following test:</p><p> — login to the machine that contains the OpenLink server components.</p><p> — Run oplshut -s on the command-line.</p><p> — Compare the output to the Windows Task Manager or Unix ps -ef.</p><p> — Upgrade server components if oplshut shows fewer processes when compared to the Task Manager or ps.</p><p> 7. Multi-Tier users experiment with database agent reuse. Users should comparison test the following values:</p><p> — ifsame process, upto 5</p><p> — ifsame application, upto 5</p><p> — ifsame database, upto 5</p>
Troubleshooting
What Do I Do If My Drivers Occasionally Fail To Disconnect?
<p>Both Multi-Tier and Single-Tier drivers users take the following action. Multi-Tier users see additional comments below.</p><p></p><p> 1. Use your database native transaction monitor to see if OpenLink drivers are locked in pending transactions. OpenLink drivers cannot disconnect from a database while they are still engaged in transactions.</p><p> 2. Insure that your application does not enforce manual commits. Use of manual commit may encourage the behavior described above.</p><p> 3. Check the database native error logs for failures that may contribute to this problem.</p><p> 4. Create a client-side ODBC trace. Examine the trace to insure that the application sends the proper sequence of SQLFree()s and SQLDisconnect()s to the driver.</p><p> 5. Ensure OpenLink's Progress drivers connect to Progress databases in sockets mode. A Progress shared memory library bug causes failure to disconnect.</p><p> 6. Contact OpenLink Product Support, if you use Progress 91C or 91D. OpenLink is working to resolve occurrences of lingering agents that are not associated with the shared memory bug.</p><p></p><p>Multi-Tier users perform the following, additional test:</p><p></p><p> 1. Recreate the problem.</p><p> 2. Run oplshut -s on a command line.</p><p> 3. Observe the number of OpenLink database agent processes.</p><p> 4. Compare the output of oplshut -s with a Unix ps -ef or Windows Task Manager.</p><p> 5. Upgrade if oplshut -s or the Windows Task Manager shows more agent processes.</p>
Troubleshooting
What Do I Do If My Drivers Produce Intermittent Core Dumps?
<p>No product should produce a core dump. Core dumps warrant the creation of a bug report. (Update existing bug reports, as appropriate.) Product Support Staff should attach the core file to the report. Moreover, staff must gather the following information from users:</p><p></p><p> 1. Does the database and operating system contain all current patches?</p><p> 2. Are the patches associated with stability problems?</p><p> 3. Do Unix kernel tuning parameters match parameters specified by database and o/s documentation?</p><p> 4. Does the machine have adequate memory and processor resources?</p><p> 5. Was the database agent re-linked against the database?</p><p> 6. Is PortHigh set in the [Protocol TCP] section of the Multi-Tier Session Rules Book? This is the oplrqb.ini file that resides in the /bin sub-directory of the server components installation.</p><p> 7. What happens when users comparison test the following ReUse values:</p><p> — ifsame process, upto 5</p><p> — ifsame application, upto 5</p><p> — ifsame database, upto 5</p><p> 8. Finally, Multi-Tier users should perform the following test:</p><p> — login to the machine that contains the OpenLink server components.</p><p> — Run oplshut -s on the command-line.</p><p> — Compare the output to the Windows Task Manager or Unix ps -ef.</p><p> — Upgrade server components if oplshut shows fewer processes when compared to the Task Manager or ps.</p>
Troubleshooting
What Do I Do If My Drivers Produce Intermittent Protrace Files?
<p>No product should produce a Progress protrace file. Protrace files warrant the creation of a bug report. (Update existing bug reports, as appropriate.) Product Support Staff should attach the protrace file to the report. Moreover, staff must gather the following information from users and post it in the report:</p><p></p><p> 1. Does the database and operating system contain all current patches?</p><p> 2. Are the patches associated with stability problems?</p><p> 3. Do Unix kernel tuning parameters match parameters specified by database and o/s documentation?</p><p> 4. Does the machine have adequate memory and processor resources?</p><p> 5. Was the database agent re-linked against the database?</p><p> 6. Is PortHigh set in the [Protocol TCP] section of the Multi-Tier Session Rules Book? This is the oplrqb.ini file that resides in the /bin sub-directory of the server components installation.</p><p> 7. What happens when users comparison test the following ReUse values:</p><p> — ifsame process, upto 5</p><p> — ifsame application, upto 5</p><p> — ifsame database, upto 5</p><p> 8. Finally, Multi-Tier users should perform the following test:</p><p> — login to the machine that contains the OpenLink server components.</p><p> — Run oplshut -s on the commandline.</p><p> — Compare the output to the Windows Task Manager or Unix ps -ef.</p><p> — Upgrade server components if oplshut shows fewer processes when compared to the Task Manager or ps.</p>
Troubleshooting
What Do I Do If My JDBC Connections Fail?
<p>Post the problem into an online support case — http://support.openlinksw.com/support/online-support.vsp</p>
Troubleshooting
What Do I Do If My Multi-Tier DSN Fails To Connect?
<p>Post the problem into an online support case — http://support.openlinksw.com/support/online-support.vsp</p>
Troubleshooting
What Do I Do If My Multi-Tier DSN Fails To Disconnect?
<p></p><p> 1. Use your database native transaction monitor to see if OpenLink drivers are locked in pending transactions. OpenLink drivers cannot disconnect from a database while they are still engaged in transactions.</p><p> 2. Insure that your application does not enforce manual commits. Use of manual commit may encourage the behavior described above.</p><p> 3. Check the database native error logs for failures that may contribute to this problem.</p><p> 4. Create a client-side ODBC trace. Examine the trace to insure that the application sends the proper sequence of SQLFree()s and SQLDisconnect()s to the driver.</p><p> 5. Perform the following test:</p><p> — Recreate the problem;</p><p> — Run oplshut -s on a command line.</p><p> — Observe the number of OpenLink database agent processes.</p><p> — Compare the output of oplshut -s with a Unix ps -ef or Windows Task Manager.</p><p> — Upgrade if oplshut -s or the Windows Task Manager shows more agent processes.</p><p> 6. Connect to Progress databases in sockets mode. A Progress shared memory library bug causes OpenLink's database agents to linger.</p><p> 7. Contact OpenLink Product Support, if you use Progress 91C or 91D. OpenLink is working to resolve occurrences of lingering agents that are not associated with the shared memory bug.</p>
Troubleshooting
What Do I Do If My ODBC Connectivity Suddenly Stopps Working Altogether?
<p>Sudden loss of functionality is attributed to two factors:</p><p></p><p> 1. License expiration.</p><p> 2. Installation of database patches, operating system upgrades, or anti-virus software.</p><p></p><p> Consequently, users take the following action:</p><p></p><p> 1. Search their entire machines for expired, temporary licenses.</p><p> 2. Delete temporary licenses.</p><p> 3. Send permanent keys to OpenLink Product Support for review.</p><p> 4. Ascertain whether or not patches, upgrades, or anti-virus software has been applied to the affected machine.</p><p> OpenLink Product Support may not have immediate answers for problems caused by patches, upgrades, or anti-virus software. Specialized testing may be needed.</p>
Troubleshooting
What Do I Do If My Single-Tier DSN Fails To Connect?
<p>Post the problem into an online support case — http://support.openlinksw.com/support/online-support.vsp</p>
Troubleshooting
What Do I Do If My Single-Tier DSN Fails To Disconnect?
<p></p><p> 1. Use your database native transaction monitor to see if OpenLink drivers are locked in pending transactions. OpenLink drivers cannot disconnect from a database while they are still engaged in transactions.</p><p> 2. Insure that your application does not enforce manual commits. Use of manual commit may encourage the behavior described above.</p><p> 3. Check the database native error logs for failures that may contribute to this problem.</p><p> 4. Create a client-side ODBC trace. Examine the trace to insure that the application sends the proper sequence of SQLFree()s and SQLDisconnect()s to the driver.</p><p> 5. Ensure OpenLink's Progress Single-Tier drivers establish sockets-based connections to Progress. A Progress shared memory library bug causes failures to disconnect.</p><p> 6. Contact OpenLink Product Support, if you use Progress 91C or 91D. OpenLink is working to resolve occurrences of lingering agents that are not associated with the shared memory bug.</p>
Troubleshooting
What Do I Do When The Installation Process Hangs Without An Error?
<p>Take the following action, if a hang occurs:</p><p></p><p> 1. Obtain the name of the installation file. Obtain the name and version of the operating system. (Use uname -a on Unix.) Compare the two resources to determine if the software and operating system are compatible.</p><p> 2. Ask about operating system patches. Patches can interfere with installs on otherwise supported operating systems.</p><p> 3. Check file and directory permissions.</p><p> 4. Use the Windows explorer or Unix df -k to check disk space.</p><p> 5. Insure unnecessary processes are shutdown.</p><p> 6. Determine how far the installation has progressed. Some Windows installers hang during registry update. However, the actual installation is complete and functional.</p><p> 7. Attempt to recreate the problem in-house.</p><p></p><p>Consultants should report persistent installation problems to the Tech Support Manager. These problems may indicate critical install bugs.</p>
Troubleshooting
What Do I Do When The Installation Process Produces Errors?
<p>Use the following guidelines to eradicate installation problems:</p><p></p><p> 1. Obtain the name of the installation file. Obtain the name and version of the operating system. (Use uname -a on Unix.) Compare the two resources to determine if the software and operating system are compatible.</p><p> 2. Ask about operating system patches. Patches can interfere with installs on otherwise supported operating systems.</p><p> 3. Check file and directory permissions.</p><p> 4. Use the Windows explorer or Unix df -k to check disk space.</p><p> 5. Insure unnecessary processes are shutdown.</p><p> 6. Determine how far the installation has progressed. Some Windows installers hang during registry update. However, the actual installation is complete and functional.</p><p> 7. Search OPIE for a description of the actual error.</p><p> 8. Attempt to recreate the problem in-house.</p><p></p><p>Consultants should report persistent installation problems to the Tech Support Manager. These problems may indicate critical install bugs.</p>
Troubleshooting
What Do I Need To Test The JDBC-ODBC Bridge?
<p>You need a functional ODBC Data Source Name (DSN). This DSN may use OpenLink or non-OpenLink drivers.</p><p> You need to install Sun's Java Runtime Environment (JRE) on the same machine as the ODBC Data Source.</p><p> You need to install OpenLink's Single-Tier JDBC driver on the machine that contains the ODBC Data Source and the JRE.</p><p> You need to run your JAVA application on the machine that contains OpenLink's Single-Tier JDBC driver.</p>
Troubleshooting
What Do I Need To Test The ODBC-JDBC Bridge?
<p>You need JDBC drivers that connect to your target data source.</p><p> You need to install your Single-Tier client driver or Multi-Tier server components (Request Broker & JDBC Bridge Agent) on the machine, which contains the JDBC connection URL.</p><p> Your JDBC client application must reside on the machine that contains the Single-Tier client driver or the Multi-Tier client components.</p>
Troubleshooting
What Do I Need To Test The ODBC-ODBC Bridge?
<p> You need 3rd party ODBC drivers that connect to your database;</p><p> You need to install your Single-Tier driver or Multi-Tier driver server components (Request Broker & Generic ODBC Agent) on the machine, which contains the 3rd party ODBC drivers;</p><p> Your client application must reside on the same machine as the Single-Tier driver or the Multi-Tier driver client components.</p>
Troubleshooting
What Environment Variables Need To Be Set On Unix Systems?
<p>Users need to run openlink.sh or openlink.csh in the appropriate shell to set the following variables on all unix systems: CLASSPATH A JAVA client variable that passes the full path to an OpenLink JDBC .jar file. LD_LIBRARY_PATH A generic library path variable that appends the full path to OpenLink's lib sub-directory. LIBPATH An AIX library path variable that appends the full path to OpenLink's lib sub-directory. ODBCINI Passes the full path to ~/openlink/bin/odbc.ini. ODBCINSTINI Passes the full path to ~/openlink/bin/odbcinst.ini. OPENLINKINI This Single-Tier variable passes the full path to ~/openlink/bin/openlink.ini. PATH Appends the full path to OpenLink's bin sub-directory. SHLIB_PATH An HP/UX library path variable that appends the full path to OpenLink's lib sub-directory.</p>
Troubleshooting
What Environment Variables Need To Be Set On Windows Systems?
<p>Most ODBC users do not need to set environment variables on Windows systems. JDBC users must insure that CLASSPATH is set as a System and/or User variable. CLASSPATH passes the full path to OpenLink's JDBC .jar files. This applies to both Multi-Tier and Single-Tier installations. OpenLink's Multi-Tier oplrqb.ini is a server side file that appears in the bin sub-directory of the server components installation. It contains a series of [Environment] sections. These sections pass variables that OpenLink components need to connect to specific databases.</p>
Troubleshooting
What Factors Contribute To Performance Problems?
<p>The following factors contribute to performance problems:</p><p> Use of OpenLink's older 1.x and 3.x drivers. The RPC communications layer—contained within newer, OpenLink drivers—was redesigned for enhanced performance.;</p><p> Use of OpenLink's Multi-Tier drivers when use of Single-Tier drivers is possible. Single-Tier drivers boost performance.;</p><p> Use of sockets connectivity where shared memory connectivity is possible.;</p><p> Retrieval of large, binary objects.;</p><p> Non-use or misuse of the Row Buffer Size DSN attribute.;</p><p> Use of less efficient cursor modalities.;</p><p> Poor use of indexes and table structuring.</p>
Troubleshooting
What Factors Contribute To Stability Problems?
<p>The following factors contribute to stability problems: Improper use of database agent reuse rules in the Multi-Tier oplrqb.ini file;</p><p> Inadequate memory; Inadequate processor count; Insufficient allocation of TCP ports in the Multi-Tier oplrqb.ini file;</p><p> Lack of critical database patches or application of flawed patches; Lack of critical o/s patches or application of flawed patches;</p><p> Sub-optimal kernel tuning parameters (Unix); Use of deprecated OpenLink components;</p><p> Use of OpenLink products with an incompatible databases or o/s; Use of Single-Tier drivers on top of unstable database native clients.</p>
Troubleshooting
What Resources Can I Use To Solve Support Cases?
<p>OpenLink consultants have a wide array of resources at their disposal. Resources include: OPIE Knowledge-base & Wiki;</p><p> OPIE Case Search Page; OpenLink Viewlet Library; UDA Product Documentation; OpenLink Internal Newsgroups; Google Web & Group Search; Database Vendor Sites & User Groups; Support staff should exhaust these resources before approaching senior support or management for assistance.</p>
Troubleshooting
What Steps Should I Take To Debug My Cases?
<p>No single procedure will enable consultants to resolve all problems. Instead, consultants will need to develop a flexible attitude and a wide-variety of diagnostic skills. In the interim, new consultants may use the following tips to debug their cases</p>
Troubleshooting
What Types Of Problems Do Consultants Debug?
<p>OpenLink Support consultants debug a wide array of problems. Problems range from simple downloads, installation, and licensing problems to complex stability, development, and migration problems.</p>
Troubleshooting
What can I do if I cant solve the problem?
<p>If you are experiencing any problem, it is recommended that you open an issue using the community forum at https://community.openlinksw.com or a support case via https://support.openlinksw.com</p>
Troubleshooting
What to Do if Can Not Download?
<p>Use the following guidelines to troubleshoot downloads problems:</p><p> 1. Re-attempt the download. OpenLink's servers occasionally fail due to temporary overload.</p><p> 2. Right-click product links and use "Save As" to download.</p><p> 3. Test with an alternative Web browser.</p><p> 4. Use an FTP client to download the software.</p><p> 5. Determine if evaluator firewalls prohibit downloads.</p><p> 6. Login as the user and test the download process in-house.</p><p>Finally, consultants must report persistent and/or reproducible downloads problems to the Tech Support Manager for immediate attention. Moreover, Consultants should email components to evaluators or provide alternative ftp access to components. Ask your Tech Support Manager for additional information.</p>
Troubleshooting
What to do if ASNPRINT does not read my license file?
<p>ASNPRINT.exe can read OpenLink's 4.x, 5.x and 6.x license formats but cannot read the older OpenLink 1.x and 3.x license format.</p>
Troubleshooting
What to do in case of Installation Failure?
<p>OpenLink's installers seldom fail. Furthermore, it is easy to troubleshoot installer issues, when they occur. Use the following guidelines to assist your users:</p><p></p><p> 1.Obtain the name of the user's installation files.</p><p> 2.Obtain the user's operating system and version. UNIX users should provide the output of uname -a. Linux users should provide the output of uname -a and rpm -qa | grep lib.</p><p> 3.Insure that the installation files are compatible with the user's operating system. Most installers are compatible with the intended o/s and updated versions of the o/s. For instance, Solaris 2.7 software should run on Solaris 2.7 and 2.8. It may not run on 2.5.</p><p> 4.Tell users to ftp installation shell scripts in ASCII. .taz, .dmg, and .zip files require BINARY transfer.</p><p></p><p>If the problem persists, invite UNIX users to use tar -xvf file name to decompress their .taz files. Use of tar should create a functional installation. However, environment variables may remain to be set in the product configuration files: i.e., openlink.sh, openlink.csh, openlink.ini, oplrqb.ini. Ask Windows users to check their OpenLink installation directories and registry. Occasionally, Windows installers report registry problems. However, these same installers create functional installations with properly configured variables. Consequently, users should attempt to start their brokers and test their DSNs. Finally, some Windows users may need to make substantial edits to their registries after an installer failure. Address this course of action with expert users. Do not encourage novice users to pursue this task.</p>
Uninstalling
How Do I Uninstall Existing OpenLink Software?
<p>Windows users may use OpenLink's uninstall utility to remove existing software. Windows users may also move the Add or Remove Programs utility, which appears in their Control Panel. OpenLink does not provide an uninstall utility for Unix platforms. Unix users may use rm or rmdir to remove existing builds.</p>
Uninstalling
How Do Users Uninstall OpenLink Software?
<p>OpenLink's Windows and Mac OS X drivers ship with uninstall utilities. OpenLink's Unix and Mac Classic drivers do not ship with uninstall utilities. Users must manually remove Unix and Mac Classic components. Unix users simply rm or rmdir the installation directory. Mac Classic users use their installation reports to identify and locate the components that need to be removed.</p>
