This is a discussion on Snapshot command within the DB2 forums, part of the Database Server Software category; --> Hi all, I have a DB2 8.2 with a FixPak '7' on AIX 5.2. There is a procedure created ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi all, I have a DB2 8.2 with a FixPak '7' on AIX 5.2. There is a procedure created on the db2 which basically waits for the time given and then displays all the rows of a table.It's working fine if I run it but when a user is trying to run the same procedure from a different server using db2 command line it works sometimes and just hangs the other times.I did a list applications show detail while it was within the time limit submitted for the application and the status was 'UOW Executing' and once the time limit was reached it changed the status to 'UOW Waiting'.. I did a snapshot for bothe the applications that returned results and the one which failed, below is the main difference, The application with the result: UOW log space used (Bytes) = 0 Previous UOW completion timestamp = 01/17/2007 15:51:49.276448 Elapsed time of last completed uow (sec.ms)= 31.055513 UOW start timestamp = 01/17/2007 15:52:18.919463 UOW stop timestamp = 01/17/2007 15:52:49.974976 UOW completion status = Committed - Commit Statement The one failed : UOW log space used (Bytes) = 0 Previous UOW completion timestamp = 01/17/2007 16:00:58.152406 Elapsed time of last completed uow (sec.ms)= 0.000000 UOW start timestamp = 01/17/2007 16:01:36.353992 UOW stop timestamp = UOW completion status = I see that the UOW does not commited in the second request, but my question is if the same procedure is running from two different systems why one is failing..How do I verify if it returned the results? Is it a network issue as the user is connecting from a remote server? Thanks in advance. |