I don't know the product but I assume it is using Java.
Sounds like perhaps a memory leak in the process or MYSQL driver perhaps causing it to balloon and crash randomly.
Or burp in networking and not being error handled. Without trace info hard to tell.
If using a 32-bit JVM, I suppose you could make sure you're using a 64-bit JVM possibly.
If you get to the point where you need to look for alternatives, our RPG2SQL components would probably work well.
https://www.helpsystems.com/products/data-integration-software-windows-and-ibm-i
No Java. Service program communicates to a Windows component that does all the ODBC work, thus no in-process memory issues.
Let us know what you find either way.
Regards,
Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com
------------------------------
message: 3
date: Wed, 6 Feb 2019 16:09:42 +0000
from: "Steinmetz, Paul via MIDRANGE-L" <midrange-l@xxxxxxxxxxxxxxxxxx>
subject: RDBIMPORT weirdness - Fails on every 3rd or 4th attempt
We're using RDBIMPORT (RDB40 from Prodata) to pull a 3 million record file daily.
Remote is MYSQL on a Linux server.
Normal good run is 10-12 minutes.
Fails on every 3rd or 4th attempt, around 2.6 million records, or less.
Failure occurs around 5-7 minutes.
Nothing done after failure.
Next attempt after failure is successful.
Recreated issue on R&D LPAR connecting to a different remote with a different MYSQL.
V7R3 latest cum and groups.
Latest version of RDB40.
RDBIMPORT uses RDBCONNECT which runs JVM 1.8.0.191 32 bit.
Engaged RDB support, nothing yet.
Turned on debug/trace, normal, nothing there.
Any thoughts from the group?
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx<mailto:psteinmetz@xxxxxxxxxx>
http://www.pencor.com/
midrange.com
