[
https://issues.apache.org/jira/browse/TRAFODION-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700230#comment-14700230
]
ASF GitHub Bot commented on TRAFODION-1454:
-------------------------------------------
Github user selvaganesang commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/59#discussion_r37236841
--- Diff: core/sqf/export/limited-support-tools/LSO/README ---
@@ -152,40 +153,52 @@ URRENT_TIMESTAMP NODE PID
EXE_MEM_HIGH_WM_MB EXE_MEM
QUERIES BLOCKED IN SQL
+======================
This filtering mechanism lists the queries that are currently blocked in
the
SQL Engine (either while executing the query. or fetching the output row)
-longer than the given number of seconds. The SQL commands to list queries
-blocked in SQL are available at:
+longer than the given number of seconds.
+The SQL commands to list queries blocked in SQL are available at:
$MY_SQROOT/export/limited-support-tools/LSO/queries_in_sql.sql
Example output is shown below:
+CURRENT_TIMESTAMP TIME_IN_SECONDS QUERY_ID
SOURCE_TEXT
+------------------------- --------------------
-----------------------------------------------------------------------
--------------------------------------------
+013-02-22 16:29:03.842781 623
MXID11000031218212228308814844995000000000206U6553500_60_SQL_CUR_2 "select
[last 0] * from t113a A, t113a B
+
-CURRENT_TIMESTAMP TIME_IN_SECONDS QUERY_ID
SOURCE_TEXT
-------------------------- --------------------
-----------------------------------------------------------------------
--------------------------------------------
-013-02-22 16:29:03.842781 623
MXID11000031218212228308814844995000000000206U6553500_60_SQL_CUR_2 "select
[last 0] * from t113a A, t113a B
---- 1 row(s) selected.
-
QUERIES BLOCKED IN CLIENT
+=========================
This filtering mechanism lists the querie s which are not blocked in SQL
longer
-than the given number of seconds and haven't finished execution. The
-SQL commands to list queries blocked in the client are available at:
+than the given number of seconds and haven't finished execution.
+The SQL commands to list queries blocked in the client are available at:
$MY_SQROOT/export/limited-support-tools/LSO/queries_in_client.sql
Example output is below:
+CURRENT_TIMESTAMP TIME_IN_SECONDS QUERY_ID
EXECUTE_STATE
SOURCE_TEXT
+------------------------- --------------------
----------------------------------------------------------------------------
---------------
------------------------------------------------------------------------------------------------------------------------------
+013-02-22 16:29:30.430629 1772
MXID11000030466212228308797313024000000000106U6553500_5_SQL_DATASRC_Q1
FETCH "select translate(nid.obj_name using UCS2TOUTF8), nid.obj_id,
asd.default_type, asd.automation, dsn.max_srvr_cnt, dsn.avail_sr
+013-02-22 16:29:30.430629 1772
MXID11000030466212228308797313024000000000106U6553500_7_SQL_DATASRC_Q7
FETCH "select variable_sequence, variable_type,
translate(variable_value using UCS2TOUTF8) from
HP_SYSTEM_CATALOG.MXCS_SCHEMA.NAME2I
+013-02-22 16:29:30.430629 1772
MXID11000030466212228308797313024000000000106U6553500_6_SQL_ENV_Q6
FETCH "select cast(COUNT(*) as int) from
HP_SYSTEM_CATALOG.MXCS_SCHEMA.ENVIRONMENTVALUES where env_id = cast(? as
integer) FOR READ
+
+
+ACTIVE QUERIES
+================
+
+This statement lists queries which either have finished executing within
the
+given number of seconds or still being executed. The negative number in
+LAST_ACTIVITY_SECS means that the query has completed that many seconds
ago.
+
--- End diff --
If the query is still executing, LAST_ACTIVITY_SECS will be the number of
seconds(a positive number) the query has been running till then. The queries
are listed in the descending order of LAST_ACTIVITY_SECS to help the customer
to focus on these queries first
> Unable to detect the query id via RMS while running the tools like ODB
> ----------------------------------------------------------------------
>
> Key: TRAFODION-1454
> URL: https://issues.apache.org/jira/browse/TRAFODION-1454
> Project: Apache Trafodion
> Issue Type: Improvement
> Components: sql-exe
> Affects Versions: 0.6 (pre-incubation)
> Reporter: Selvaganesan Govindarajan
> Priority: Minor
> Fix For: 2.0-incubating
>
>
> Currently, the RMS offender is unable to find the query id while using tools
> like ODB. These query executions are short but executed many times and the
> offender is unable to detect them. Enhance offender to detect this kind of
> queries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
