| View previous topic :: View next topic |
| Author |
Message |
pardeike
Joined: 04 May 2006
Posts: 4
|
 Posted: Thu Nov 16, 2006 12:02 pm Post subject: HELP - iSeries ODBC memory leak |
 |
|
Hi,
when running SQL Grinder, our iSeries starts generating messages with an error id described in this IBM technote:
http://www-1.ibm.com/support/docview.wss?uid=nas12baf94c1a1ddbef48625660a0075db8a
As a result, the process that relates to my sqlgrinder session takes up more and more CPU time and memory effectively halting our mainframe and stops only when I quit SQLGrinder!
Help!
Andreas Pardeike |
|
| Back to top |
|
 |
michaeldupuis
Site Admin
Joined: 15 May 2003
Posts: 1427
Location: Lewiston, ME
|
| Posted: Sat Nov 18, 2006 2:55 pm Post subject: |
|
|
| I'm not sure why SQLGrinder is part of this problem, as it doesn't use ODBC, but JDBC which are two different unrelated database driver architectures. Do you have any more info? |
|
| Back to top |
|
|
pardeike
Joined: 04 May 2006
Posts: 4
|
| Posted: Sun Nov 19, 2006 7:55 am Post subject: |
|
|
| It's just the same memory related error message. I looked it up and maybe this can be found for JDBC too. Anyway, my sys admin is likely to kill me if I use SQLGrinder any more because it effectively brings our mainframe down! |
|
| Back to top |
|
|
michaeldupuis
Site Admin
Joined: 15 May 2003
Posts: 1427
Location: Lewiston, ME
|
| Posted: Sun Nov 19, 2006 9:55 am Post subject: |
|
|
Hm, I'm not sure what the problem could be in either case. SQLGrinder doesn't do anything on the server side, it's all client-side processing. Any memory used is on the client, not on the server.
The only problem I could see potentially is with the connection that is maintained, but normally there's not much memory or processing associated with that.
SQLGrinder does things in a generic way that works across many different servers, it's possible there is either a bug in the JDBC driver, or in the way SQLGrinder does things, but it does try and "clean up" after itself in the normal way, by closing statements and result sets when done, etc. Verify that you are using the latest version of the driver that is available.
Sorry I can't be of more help. |
|
| Back to top |
|
|
SeanM
Joined: 09 Feb 2007
Posts: 1
Location: Chicagoland
|
| Posted: Fri Feb 09, 2007 8:55 pm Post subject: |
|
|
Hi Andreas,
I am a 400 guy and have SQLGrinder and Aqua Data Studio working nicely with multiple 400's. I might suggest the following...
1.) Remove any 400 related entries from menu Prefs:JDBC Drivers. Quit SQLGrinder to write plist to disk.
2.) Ensure you download the latest version of JTOpen / JT400 from IBM. The jt400.jar file is all you need. Place it in the address below (or your prefered location).
3.) Start SQLGrinder and add a new JDBC entry as below..
Name: jt400
Base Class: com.ibm.as400.access.AS400JDBCDriver
URL Prefix: jdbc:as400
file: /Users/yournamehere/Library/Application%20Support/SQLGrinder/jt400.jar
Hope this helps.
Regards
Sean |
|
| Back to top |
|
|
|
