OpenLink Support: SupportWeb.TechnicalFAQs

Technical Frequently Asked Questions

Database Support

Do you connect to Access .mdb files hosted on Linux or other non-Windows systems?

No. OpenLink can only connect to a .mdb file if it is hosted on a Windows operating system with a full Access install.

Do you connect to DB2 on AS/400?

OpenLink does not build UDA components for AS/400.To establish connectivity to AS/400, install OpenLink components on any supported operating system that has a functional copy of DB2 client networking. OpenLink can ferry data access requests to DB2 on AS/400 via the local copy of DB2 client networking. At the time of writing, the DB2 native client product is called DB2 Connect. Marketing names may vary in the future.

Do you support Oracle 10 on Windows Opteron AMD (x64_86)?

At the time of writing, OpenLink has Multi-Tier, Single-Tier (Lite), and Single-Tier (Express) drivers that connect tp 32bit Oracle 10 DBMSs on Windows x86_64. We have Single-Tier (Express) drivers for 64bit Oracle DBMSs on Windows x86_64. Other driver formats are planned.

Do you support Progress 9.1E?

OpenLink can connect to Progress 91E04 DBMSs.

Do you support Progress 10.1C?

OpenLink is rolling out SQL92 database agents for Progress 10.1C DBMSs.

O/S Support

Do you support AIX 5.3?

OpenLink provides UDA drivers compiled for AIX 5.3. OpenLink's AIX 5.2 builds are binary compatible with AIX 5.3 operating systems, should an AIX 5.3 build not be immediately available.

Do you support Mac OS X 10.5 (Leopard)?

OpenLink provides UDA drivers compiled for Mac OS X 10.5. OpenLink's Mac OS X 10.4 builds maybe binary compatible with OS X 10.5 operating systems, should a Mac OS X 10.5 build not be immediately available.

Licenses

Do you license by chip or by core?

OpenLink licenses by physical core. Software hosted on a single quad core Xeon CPU would require a 4 CPU license.

Can I download licenses from your site?

Yes. You can purchase permanent license keys using OpenLink's online Shop Cart. The Shop Cart will email the keys to you. You will receive a 15 day temporary key when you first download our software. A second, 15 day key will be stored in your ODS dav repository.

How long do driver evaluation periods last?

OpenLink's evaluation period lasts 15 days.

Can I obtain a Single-User (1/1) license for Multi-Tier?

OpenLink's smallest Multi-Tier license comprises 5 users and 5 concurrent connections.

Can I deploy licenses from two different software releases on the same machine?

You can deploy two commercial or evaluation licenses from different releases on the same machine. On Unix be sure to set your OPL_LICENSE_DIR variable to point to the correct directory location before starting any service associated with OpenLink. And, if you are deploying OpenLink 6.x+ with a legacy release, be sure to start all services associated with OpenLink 6.x, before you start services associated with legacy installations.

How do I know which OpenLink license is being used?

Use OpenLink's Web-based GUIs to detect the license in use.

General Configuration

How do I obtain startup scripts for your Multi-Tier Server Components?

OpenLink Product Support does not write startup scripts for products in the Product Portfolio. Startup scripts must be carefully crafted and customized to guarantee proper functionality in the target environment. Professional Services can write such startup scripts for a fee. Product Support can provide a template which customers and evaluators may modify for their own environments.

HSODBC & DB4ODBC

Microsoft SQL Server Linked Servers & Import/Export

Progress Connectivity

Can I establish SQL89/4GL connections to Progress 10?

OpenLink does not facilitate SQL89/4GL connectivity to most Progress 10 DBMSs. This limitation stems from a lack of support in Progress 10 native Development libraries that OpenLink uses to build Progress agents and drivers.

Can I connect to Progress 9 & 10 databases running on the same machine?

Yes. This is simply a matter of configuring the environment and .ini files associated with the OpenLink product. Contact OpenLink Product Support for additional guidance.

Common Errors

Connection rejected by data source

"Connection rejected by Data source" messages are common and generic. They do not reveal the true error condition. In fact, these errors are often preceded by more informative statements.

Dependent module libesql92.so could not be loaded

This error occurs when Progress native library libesql92.so is not present on the local operating system. Ensure that Progress Client Networking or a full Progress DBMS is installed. Then, ensure that the relevant library path (LD_LIBRARY_PATH, LIBPATH, SHLIB_PATH) contains $DLC/lib, i.e., the library sub-directory of the local Progress installation. The relevant library variable should be set on the commandline before any services associated with OpenLink are started. It should also be set in the Single-Tier openlink.ini file or Multi-Tier oprlqb.ini file. Both of these files appear in the bin sub-directory of the relevant product installation.

License has expired

Do the following:

1. Login to the target operating system.

2. Stop the OpenLink License Manager Service (oplmgr) associated with 6.x installations.

3. Search the machine to ensure that all expired license files are removed.

4. Locate the correct icense file and put it in place.

5. Set OPL_LICENSE_DIR on non-Windows systems to point to the directory containing the license.

6. Ensure there are no permissions issues associated with the license.

7. Restart the OpenLink License Manager.

8. Restart the Multi-Tier Request Broker service, if applicable.

9. Restart the HTTP-based iODBC Data Sources Administrator, if applicable.

10. Test.

If the problem persists, have OpenLink Product Support check the integrity of the license. Likewise, ensure that ASCII ftp transfer was not used on the license.

License is already in use

This license occurs when the same license file is deployed on more than one system.

No valid license was found

Do the following:

1. Login to the target operating system.

2. Stop the OpenLink License Manager Service (oplmgr) associated with 6.x installations.

3. Locate the license file.

4. Set OPL_LICENSE_DIR on non-Windows systems to point to the directory containing the license.

5. Ensure there are no permissions issues associated with the license.

6. Restart the OpenLink License Manager.

7. Restart the Multi-Tier Request Broker service, if applicable.

8. Restart the HTTP-based iODBC Data Sources Administrator, if applicable.

9. Test.

If the problem persists, have OpenLink Product Support check the integrity of the license. Likewise, ensure that ASCII ftp transfer was not used on the license.

Number of CPUS too high for license

OpenLink's drivers are licensed by physical CPU core on the host machine. Use OpenLink's CPU Detection Help page to detect your physical cores. Contact Product Support, if you have problems attributed to Windows hyperthreading, Solaris Containers, AIX microprocessors, or other virtual processors.

RPC: Unable to receive

"Unable to receive" errors indicate bad client settings, incompatibilities, or portation issues.

Unable to contact the OpenLink License Manager

OpenLink's 6.x and newer drivers ship with a License Manager service. You need to use your Windows Task Manager or the command line to ensure that this process (oplmgr) is running. If it's not running, do this:

1. Ensure the proper license is in place.

2. Remove extraneous license files from the system.

3. Create an OPL_LICENSE_DIR variable and point it to the directory that contains your OpenLink license.

4. Attempt to start the License Manager using the Windows Services panel or run oplmgr +start on the commandline.

5. Use the Windows Task Manager or run ps -ef | grep oplmgr to ensure the License Manager is running.

6. Test a connection.

Unable to get a server handle

"Server handle" errors suggest environment or compatibility problems.

Unable to start the requested database agent

"Unable to start" messages are common and generic. They do not reveal the true error condition. In fact, these errors are often preceded by more informative statements.