Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ED544912E for ; Fri, 17 May 2013 22:15:15 +0000 (UTC) Received: (qmail 20221 invoked by uid 500); 17 May 2013 22:15:16 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 20202 invoked by uid 500); 17 May 2013 22:15:16 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 20114 invoked by uid 99); 17 May 2013 22:15:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 May 2013 22:15:16 +0000 Date: Fri, 17 May 2013 22:15:16 +0000 (UTC) From: "Mike Matrigali (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DERBY-6216) XPLAIN feature does not work and gives ERROR XCL16: ResultSet not open MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-6216?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1366= 1090#comment-13661090 ]=20 Mike Matrigali commented on DERBY-6216: --------------------------------------- it looks like this mode is never tested. See below todo comments in the Xp= lainStatisticsTest test: * FIXME -- some general to-do items that I don't want to forget: * - should resultSetNumber be its own column in sysxplain_resultsets? * - need tests of xplain-only mode * - need a test of external sorting/merging * - need to cross-check the result set types, and verify that they're * all tested at least once =20 > XPLAIN feature does not work and gives ERROR XCL16: ResultSet not open > ---------------------------------------------------------------------- > > Key: DERBY-6216 > URL: https://issues.apache.org/jira/browse/DERBY-6216 > Project: Derby > Issue Type: Bug > Components: Tools > Affects Versions: 10.6.2.3, 10.7.1.4, 10.8.3.1, 10.9.1.0 > Environment: Solaris 10, MacOS X 10.6, Windows XP > Reporter: Brett Bergquist > Labels: features > > I am running Derby 10.9.1.0 and am trying to figure out a performance pr= oblem with query taking too long. I don=E2=80=99t actually want to run th= e query so from the documentation, I try: > call syscs_util.syscs_set_runtimestatistics(1); > call syscs_util.syscs_set_xplain_schema('STATS'); > call syscs_util.syscs_set_xplain_mode(1); > --- my query here > call syscs_util.syscs_set_runtimestatistics(0); > call syscs_util.syscs_set_xplain_schema(''); > call syscs_util.syscs_set_xplain_mode(0); > When it runs my query, I get: > ERROR XCL16: ResultSet not open. Operation 'getMetaData' not permitted. V= erify that autocommit is OFF. > I try the following with IJ just to see: > call syscs_util.syscs_set_runtimestatistics(1); > call syscs_util.syscs_set_xplain_schema('STATS'); > call syscs_util.syscs_set_xplain_mode(1); > select sql_text from syscs_diag.transaction_table where status !=3D 'IDLE= '; > call syscs_util.syscs_set_runtimestatistics(0); > call syscs_util.syscs_set_xplain_schema(''); > call syscs_util.syscs_set_xplain_mode(0); > Note I have tried this with real tables as apposed to the syscs_diag.tran= saction_table with the same result. The only reason that I posted this wit= h this table is that it is a table that is accessible for any database. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira