Hello,
We are running OpenEdge 10.1A-02 (I know, old version, came with our ERP), and I have an application which periodically (every 10 min) pulls data from the Progress DB (read only ODBC connection) to a MySQL DB.
The ODBC driver came with OpenEdge, 05.10.0039.
The DBs and the app runs on a Win2003 64bits, and this was working Ok until yesterday (18/Aug), 14:50 (last successful sync). After this the app hangs waiting for SELECT results from the ODBC connection. SELECTS returning just a few rows seem to work, but breaking the original SELECT into smaller ones still hangs on the third or second one.
Interestingly, if I run the app from my notebook on the network (Vista, same OpenEdge ODBC version, accessing the same DBs in the Win2003 server), it works without a hiccup (but it takes 5min instead of the 2min I used to get running on the server).
I tried opening/closing the ODBC connection on every SELECT (splitting the original big one in smaller ones), both enabling and disabling the "connection pool" option on the Windows ODBC manager, but then things get *extremely* slow running on the server (and small difference running from my notebook).
The only changes I believe happened between before yesterday and after were:
- Our data keeps increasing; maybe a limit was hit
- Patch Tuesday; Microsoft updates happened yesterday
The ERP supplier also has a similar "sync" app which uses the OpenEdge ODBC (but read/write), Their app has been hanging like that since many months ago. I have been saying that the problem was their app, since mine worked, but now I have my feet.
On some rare occasions, after a "hangup" (for which there is no error message, just no answer) the next access gets the "server crash likely" error, but this is very rare. Normally there is just no reply to the SELECT.
Would someone have some light to shed? I'm really lost, and the ERP supplier too.
Thanks!
Joao S Veiga
We are running OpenEdge 10.1A-02 (I know, old version, came with our ERP), and I have an application which periodically (every 10 min) pulls data from the Progress DB (read only ODBC connection) to a MySQL DB.
The ODBC driver came with OpenEdge, 05.10.0039.
The DBs and the app runs on a Win2003 64bits, and this was working Ok until yesterday (18/Aug), 14:50 (last successful sync). After this the app hangs waiting for SELECT results from the ODBC connection. SELECTS returning just a few rows seem to work, but breaking the original SELECT into smaller ones still hangs on the third or second one.
Interestingly, if I run the app from my notebook on the network (Vista, same OpenEdge ODBC version, accessing the same DBs in the Win2003 server), it works without a hiccup (but it takes 5min instead of the 2min I used to get running on the server).
I tried opening/closing the ODBC connection on every SELECT (splitting the original big one in smaller ones), both enabling and disabling the "connection pool" option on the Windows ODBC manager, but then things get *extremely* slow running on the server (and small difference running from my notebook).
The only changes I believe happened between before yesterday and after were:
- Our data keeps increasing; maybe a limit was hit
- Patch Tuesday; Microsoft updates happened yesterday
The ERP supplier also has a similar "sync" app which uses the OpenEdge ODBC (but read/write), Their app has been hanging like that since many months ago. I have been saying that the problem was their app, since mine worked, but now I have my feet.
On some rare occasions, after a "hangup" (for which there is no error message, just no answer) the next access gets the "server crash likely" error, but this is very rare. Normally there is just no reply to the SELECT.
Would someone have some light to shed? I'm really lost, and the ERP supplier too.
Thanks!
Joao S Veiga