Migrating from Progress SQL-89 connectivity (Progress 7.x through 9.1x) to SQL-92 connectivity (Progress 9.1x through
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.
We support both SQL-89 and SQL-92 connections wherever possible.
If you are a veteran
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?
The "10.0 (SQL-92)"-branded links lead to SQL-92-based installers suitable for use with all Progress
Follow the installation instructions for your new drivers, as normal.
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.
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
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).
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:
The shared memory is version <some number>; expected <some number> (1178)
Invalid Packet Length
Invalid user name[SQLSTATE:285890Invalid Auth Specs]
Disconnected from server because database name was incorrect. (437)
Remote Database Name not valid.
Server did not respond[SQLSTATE:k0k130Progress Open SQL network interface]
Server's received count 1 does not equal client(1)'s send count 16777216.