| **
John, I'm trying to think of *why* I would have kept a 6.3 log file lying around and cannot think of a good reason here :-) But, since you have the thread ID, you could consider that the next statement on that thread ID is the worst case for the preceding statement having completed. If you don't see an OK, is there a COMMIT? if there's no OK, is it still running???? :-) TID = the id of the thread (inside the arserverd process) that sent the statement to the database Client RPC = the service number requested by the client (e.g 390620 is probably a fast server, 390635 a list server, 390603 the escalation server, etc). RPC ID = groups all of the transactions associated with a single API call together. Starts at zero and increments with each api call. Doug On May 26, 2010, at 2:06 PM, John Sundberg wrote: ** Doug -- Doug Blair +1 224-558-5462 200 North Arlington Heights Road Arlington Heights, Illinois 60004
|
- 6.3 arsql log - how to read? John Sundberg
- Re: 6.3 arsql log - how to read? Misi Mladoniczky
- Re: 6.3 arsql log - how to read? Doug Blair
- Mac ODBC Driver Russ Grant


