We are doing some testing with running some fenced java stored procedures
against an DB2 UDB version 7.2 fixpack 9 AIX database. Initially, we were
having a problem with the long amount of time (20 sec.) that it took to
call the stored procedure and return results so we changed some settings in
DBM as follows :
KEEPDARI = Yes
INITDARJVM = Yes
NUM_INITDARIS = 10
NUM_INITAGENTS = 10
NUM_POOLAGENTS = 10
After cycling the db2 we saw that the first invocation of the stored
procedure was still 20 seconds and invocations after that were cut in half,
but still not as fast as we would expect. When checking the processes on
the AIX machine, you can see 10 dari processes running at all times. When
the stored procedure is executed, the amount of resources used goes up
dramatically and can be traced to one of the dari processes running at all
times. When the SQL that the stored procedure executes is run outside of
the stored procedure, it returns very quickly so we are wondering why it is
taking so long for the stored procedure to run. Also, we have java stored
procedures that run on DB2 UDB version 7.2 fixpack 6 databases and they
seem to stay cached on the machine by simply changing the KEEPDARI = Yes.
Can someone out there give me a hint why we are having the problems that we
are having in the AIX environment or maybe give me an idea of what to look
at when the stored procedure is executing?
Thanks,
Tim Traxson
-
::: When replying to the list, please use 'Reply-All' and make sure
::: a copy goes to the list ([EMAIL PROTECTED]).
*** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
*** For more information, check http://www.db2eug.uni.cc
