Ron_H_Java@xxxxxxxxxx wrote:

Hi Ron, thanks for the reply!

On the iSeries side, have you created a view and are using that view in 
your application?

Yes.

On the iSeries side, in the CREATE FUNCTION statement, what are you 
returning, a table?

Yes.

If you answered YES to both of the above, basically, the iSeries is 
pulling the entire table from Oracle 

[snip]

Once the entire table gets to the iSeries everything seems to run quickly. 

In order to speed things up I sometimes hard code the WHERE clause in the 
Java program.
On large tables I've found this speeds things up considerably but it's 
still slow, too slow for use in interactive or web based applications. 
That's been my experience.

This is true... but my stored procedure is specifying a "where" clause,
so the row count returned from the query to the i5 is 250 rows.  The
section of code that processes the result set is only taking about 5
milliseconds per row.

My tests indicate that the time delay is caused by the connection being
made, not the actual query running.  And that is what is driving me insane.


Let us know if support comes up with something.

I'm running a trace of the job as I type this!  I'm sure IBM will figure
this out -- I've always had good luck with their tech support gurus.

Best of luck

Thanks!

Barry


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.