trafodion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Liu, Yuan (Yuan)" <>
Subject RE: How to analyze the completed sql statement
Date Mon, 30 Jul 2018 06:13:12 GMT
We can also add below configuration into dcs-site.xml to save queries less than 60 seconds
into repository.

	<name> dcs.server.user.program.statistics.limit.time</name>

The value 0 means all sql will be saved into repository. We can set the value as we want.

Best regards


-----Original Message-----
From: Selva Govindarajan <> 
Sent: Monday, July 30, 2018 1:49 PM
Subject: RE: How to analyze the completed sql statement

Statistics of the running queries are stored in shared segment. To avoid  shared segment becoming
full, the statistics is removed as soon as the query is deallocated.  I believe If the query
takes longer than 60 seconds, the end statistics will be written to repository by default.
 This time duration of the query to be written  can be configured. 

In addition, the monitored queries are kept in the shared segment even after the query is
deallocated. You can start monitoring the query by issuing get statistics for qid <qid>
or any other equivalent command involving query id. However, if the query takes a very short
time, it is possible that query could complete before you start monitoring it.

Thanks, Selva

-----Original Message-----
From: Yang, Peng-Peng <> 
Sent: Sunday, July 29, 2018 9:55 PM
Subject: How to analyze the completed sql statement

Hi Trafodioneers,

Sometimes we need to analyze the sql running at the end, how can we get the statistics of
the completed sql?
Or configure sql statistics to stay longer in the offender?
Not "get statistics for qid current;",


View raw message