Unanswered: From DB2 Client - More time to fetch result
I'm facing a performance issue on my project hence it would be great if you could give me some idea.
DB2 UDB V8.1 FP 10, Partitioned database with 8 logical partitions on AIX 5.3
DB2 Client v8.1 resides on Solaris box
A particular query takes around 90 seconds to execute against a table(non partitioned) which has nearly 6 million records when executed on the DB2 Server directly (local client) but when the same query was executed from the Solaris Client box (remote client) it executes for a very long time (765 Second s)
SELECT TREAD_INCDNT_KEY, SEQ_NBR, SR_NBR, SR_OPENED_DT, NHTSA_RPTD_FLAG, UPDT_TIMSTM, VIN FROM TREDIZ1.CARS_SIEBEL_SR Order By TREAD_INCDNT_KEY, SEQ_NBR Asc
I have a indexes on TREAD_INCDNT_KEY and SEQ_NBR. Table & Index statistics are looking fine. Explain plan is same whether the query is executed either from server or from client. I feel that this is due to network issue hence asked the help of network admins. But it would be helpful if you feel that there might be a issue from database perspective.
How can I check the blocking level of my package? from the DB2 Client we are using Ascential Datastage.
If I test it by having just the select statement how should I specify the blocking level? I read information centre to get details about it but thing are still vague to me.