** 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:

**

looking at a sql log from ars 6.3 -- how do you interpret ???


What is TID and RPC ID and Client-RPC.


I can guess at most - but thought I would get opinions.

Ultimately - the goal is to find the start and end times of a select or insert etc...

Is that even possible with a 6.3 log?

7.5 logs have OK statements - which relate back to the RPC ID -- and then you can do simple subtraction to figure out the diff time.




<SQL > <TID: 0000000007> <RPC ID: 0001002730> <Queue: Fast      > <Client-RPC: 390620   > 
<SQL > <TID: 0000000007> <RPC ID: 0001002730> <Queue: Fast      > <Client-RPC: 390620   > 
<SQL > <TID: 0000000007> <RPC ID: 0001002730> <Queue: Fast      > <Client-RPC: 390620   > 
<SQL > <TID: 0000000009> <RPC ID: 0001002731> <Queue: Fast      > <Client-RPC: 390620   > 




--
John Sundberg

Kinetic Data, Inc.

"Building a Better Service Experience"

Recipient of the WWRUG09 Innovator of the Year Award








_attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_



Doug

--
Doug Blair
+1 224-558-5462

200 North Arlington Heights Road
Arlington Heights, Illinois 60004



_attend WWRUG10 www.wwrug.com ARSlist: "Where the Answers Are"_

Reply via email to