Migrating from Progress SQL-89 Connectivity to SQL-92 Connectivity

Migrating from Progress SQL-89 connectivity (Progress 7.x through 9.1x) to SQL-92 connectivity (Progress 9.1x through OpenEdge 10.x and beyond) presents many challenges. This is especially the case as more and more organizations move to Progress OpenEdge 10.x and newer. These challenges apply to all data access mechanisms -- ODBC, JDBC, OLE DB, ADO.NET, etc.

With proper planning, most known challenges are quickly and easily resolvable. (Some challenges do require more time and effort than others!)

This guide advises you of some of the hurdles ahead and shows you how to properly plan for them and troubleshoot them.


Data access challenges presented by Progress SQL-92 connectivity include --


To move forward with SQL-92 connectivity, you need to do the following on the Progress host:

If you are using our Single-Tier "Lite" Drivers, Progress® SQL-92 Client Access must be installed and functional on the same machine as our driver.

Choosing between SQL-89 and SQL-92 Connectivity

We support both SQL-89 and SQL-92 connections wherever possible.

If you are a veteran OpenLink user, you may be familiar with our SQL-89 drivers, which have letter-version-specific branding in their product names, e.g., "Multi-Threaded Database Agent for Progress 8.2A" and "Multi-Threaded ODBC Driver for Progress 9.1D."

Our SQL-92 drivers are only major-version-specific, e.g., "Multi-Threaded Database Agent for Progress 9 (SQL-92)" and "Multi-Threaded ODBC Driver for Progress 10 (SQL-92)."

Q.What is the difference between the 10.0A (SQL-89) and 10.0 (SQL-92) options in the Download Wizard?

A. OpenLink's Development Team endeavored to make SQL-89-based drivers for OpenEdge 10.x. This was possible on a limited number of operating systems, and only with very early versions of Progress OpenEdge 10.0A; later patches disable the required Progress features. These products appear in our download wizard with a "10.0A (SQL-89)" branding.

The "10.0 (SQL-92)"-branded links lead to SQL-92-based installers suitable for use with all Progress OpenEdge 10.x instances.

Installing Data Access Drivers for Progress (SQL-92)

Follow the installation instructions for your new drivers, as normal.

Verifying the Multi-Tier Database Agent for Progress 10 (SQL-92)

If you are using our Multi-Tier Drivers, you should verify your Progress 10 SQL-92 Database Agent's functionality. Our Database Agents should return version and usage information in any environment that is properly configured. Failure to return version and usage information usually reveals environment or compatibility issues that should be addressed before continuing on.

  1. Log into the machine that hosts your Multi-Tier server components installation.
  2. Open an MS-DOS command prompt or Unix terminal session.
  3. cd into the bin sub-directory of the OpenLink installation, e.g., cd /opt/openlink/bin.
  4. Execute this command:

    ./prs100_mv -?

  5. You should see output similar to the following:

    Progress 10 Database Agent Version 1.11 as of Wed Apr 29 2009 (Release 6.2 cvsid 00090). Compiled for Linux 2.6.9-78.0.13.EL (i686-generic-linux-glibc23-32) Copyright (C) OpenLink Software. Usage: pro100a_sv [-CmijrlLd] [+noautocommit] [+maxrows num] [+initsql arg] [+jetfix] [+norowsetlimit] [+loglevel num] [+logfile arg] [+debug] +noautocommit turn autocommit off by default +maxrows maximum allowed rows to fetch +initsql execute SQL from this file for every connection made +jetfix Jet Engine Compatibility Features +norowsetlimit turn off rowset size limit +loglevel log level +logfile log file +debug debug mode

    If the agent fails to return the desired output, use our Error Messages reference guide to troubleshoot your problem.

Error: error while loading shared libraries: libesql92.so: cannot open shared object file: No such file or directory.

This is the most common error produced by our agent during functionality verification. This error occurs when the Progress lib sub-directory is not found in the relevant shared library environment variable -- LD_LIBRARY_PATH, LIBPATH, or SHLIB_PATH on Unix, or PATH on Windows.

Resolution: Simply add the directory path(s) to the environment variable(s).

Troubleshooting Progress SQL-92 Connectivity

Initial SQL-92 connection attempts to Progress are often unsuccessful. However, the errors are almost always easily resolvable. Use these guidelines to troubleshoot any problems that arise in your environment:

Troubleshooting Progress SQL-92 Queries