
David Beavon (Software) asked a question.
It is many years since 10.2A was retired (2010).
But we were using that odbc client successfully in production until just this year. We were able to use it for connecting to all versions of server 11.X and all versions of server 12.X. For some reason there were never any errors, despite the fact that these odbc client-drivers are only officially supported to work on +/- one major version.
We never saw issues with the old client using v.10.2A. The connection string was like so:
- DRIVER=Progress OpenEdge 10.2A Driver;DB=lumbertrack;PORT=2001;HOST=whatever;DefaultIsolationLevel=READ UNCOMMITTED
We only used it for fairly simple read-only (reporting) purposes. The most interesting thing we ever did with it was to create specialized VIEWS in a different schema (not pub) and use those to reach the underlying tables.
More recently we decided to upgrade the odbc client in order to be "officially" supported. Over a period of two years we went from 10.2A to the 11.7 driver. We are using this new driver as-of about two months ago.
- DRIVER=Progress OpenEdge 11.7 Driver;DB=lumbertrack;PORT=2001;HOST=whatever;DefaultIsolationLevel=READ UNCOMMITTED
As the clients were slowly being upgraded to the 11.7 driver, the OE server was upgraded to 12.8.x. So this is still supported (+/- one version).
However today I'm astonished to see that our SQL queries (for non-critical, non-operational reporting) are trying to take locks on database records. We are seeing timeouts and other types of failures inlucing ones that explicitly talk about record locks. The failures look like so:
- System.Data.Odbc.OdbcException: ERROR [HY000] [DataDirect][ODBC Progress OpenEdge Wire Protocol driver][OPENEDGE]Failure getting record lock on a record from table PUB.fin_abc_xyz
In the code we do not appear to be changing the isolation level or opening any transactions. So the expectation is that the "DefaultIsolationLevel" (READ UNCOMMITTED) should remain in effect.
Can anybody with OE DBMS experience please try to help me understand where we took a wrong turn? How did we get to this place where we find ourselves locking records from our reports? Did that part of the connection string become invalid? Shouldn't it have given us a connection failure if so? Is there a way to get the connection string working as intended, so there are no database record locks being takend from these connections?
Any help would be appreciated. Sorry for the trip back in time to 10.2A. There is no excuse to refer to it in 2025, although I'm guessing we can't be the only company in the world that has baggage from 15 years ago.
I found out where things changed under us. There is a KB created back in 2015 about it:
https://community.progress.com/s/article/ODBC-DSN-less-connection-fails-on-newer-OE-versions
Instead of this:
DefaultIsolationLevel=READ UNCOMMITTED
We are now supposed to use this:
DIL=0
Else a sql connection will create a lot of conflicts with an ABL-based ERP.
Hope this is helpful.