Christian Pflugradt wrote:Try if the following code changes anything. I've added con.setAutoCommit(false) and st.setFetchSize(100) which should lessen the impact on your memory.
setFetchSize(int rows) Gives the JDBC driver a hint as to the number of rows that should be fetched from the database when more rows are needed for ResultSet objects genrated by this Statement.
Balasubramaniam Muthusamy wrote:Thanks much for your replies. When i dig into this further resultSet.next returns true until the record count is 2147483646 and returns false when record count moves to 2147483647 which is the maximum of int value. is integer maximum value is limit of ResultSet?
Balasubramaniam Muthusamy wrote:I have a program which needs to process almost 30 billion records.
Balasubramaniam Muthusamy wrote:The issue has been resolved by upgrading the JDBC jar to next version and now I am able to process the expected records. thanks every one for their reply and suggestion.
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton