Title: Message
I'm starting a new thread... as I intend to try and flush out the stability problems I'm seeing with the ODBC client driver on Windows 2000 SP3.
 
I have MDAC 2.7 (latest), ODBC 7.3.0.28 driver.  We have found SAPDB to be great and stable for 18 months _until_ we changed from a unified app+database server to two different servers!  In other words, I believe the problem lies in the network portion of the ODBC driver.
 
Please, if anyone can help track down these bugs, please do.  I'm in no position to work on the SAPDB ODBC code myself, but I am doing my best to devise test programs that anyone can run and test.
 
In my case, I am using:  Windows 2000 SAPDB server <----> Windows 2000 Application server.  I'm curious if those with Linux SAPDB servers have the same problems I'm seeing with the ODBC driver.
 
I have put together a dotNet C# application that lets you execute a series of SQL commands in a loop.  I tried to make it simple to run.  Source code is also included.  You need to install the Microsoft dotNet Framework + ODBC.NET components and it is ready to run.
 
 http://www.RoundSparrow.com/SAPDB/Stress/
 
There is a ZIP file named v0-800.zip you can download.
 
 
What to do to try and see the problem
================================
The sample code will install a couple test tables on the SAPDB demo database, do select, then remove the tables.
 
What I've done is run three concurrent copies of the SELECT loop at a time (start up three command prompts and start the EXE up three times).  Make sure you are running it over the network to a remote SAPDB server... within 5 to 15 minutes I get a error from the ODBC driver on one of the instances (client applications on client machine).
 
 
How to REALLY stress things
================================
We have found that having three machines, two SAPDB servers and one client - run two instances of my client test program per remote SAPDB server (4 total), and the ODBC driver will sometimes hang the other instances of the application.  Sort of a system wide "lock" on the SAPDB ODBC driver.
 
 
We have urgent production problems related to this issue, I would really appreciate any assistance in reproducing this problem.
 
Thank you.
 
   Stephen Gutknecht
 

Reply via email to