db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6216) XPLAIN feature does not work and gives ERROR XCL16: ResultSet not open
Date Mon, 15 Jul 2013 08:38:48 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708312#comment-13708312
] 

Knut Anders Hatlen commented on DERBY-6216:
-------------------------------------------

It looks like there is an instability in one of the new test cases:

http://download.java.net/javadesktop/derby/javadb-5579342-report/javadb-task-3689858.html

    junit.framework.AssertionFailedError: Column value mismatch @ column '1', row 1:
    Expected: >1<
    Found:    >2<
	at org.apache.derbyTesting.junit.JDBC.assertRowInResultSet(JDBC.java:1278)
	at org.apache.derbyTesting.junit.JDBC.assertRowInResultSet(JDBC.java:1190)
	at org.apache.derbyTesting.junit.JDBC.assertFullResultSetMinion(JDBC.java:1077)
	at org.apache.derbyTesting.junit.JDBC.assertFullResultSet(JDBC.java:1000)
	at org.apache.derbyTesting.junit.JDBC.assertFullResultSet(JDBC.java:957)
	at org.apache.derbyTesting.junit.JDBC.assertFullResultSet(JDBC.java:915)
	at org.apache.derbyTesting.junit.JDBC.assertSingleValueResultSet(JDBC.java:900)
	at org.apache.derbyTesting.functionTests.tests.lang.XplainStatisticsTest.testSimpleXplainOnly(XplainStatisticsTest.java:1148)
	at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:117)
	at org.apache.derbyTesting.junit.BaseJDBCTestCase.runBareOverridable(BaseJDBCTestCase.java:439)
	at org.apache.derbyTesting.junit.BaseJDBCTestCase.runBare(BaseJDBCTestCase.java:456)
	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
	at junit.extensions.TestSetup.run(TestSetup.java:25)
	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
	at junit.extensions.TestSetup.run(TestSetup.java:25)
	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
                
> 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
>            Assignee: Bryan Pendleton
>              Labels: derby_triage10_11, features
>             Fix For: 10.11.0.0
>
>         Attachments: addTests.diff, emptyRS.diff, noMemberField.diff, preparedTests.diff,
xplain-only.diff
>
>
> I am running Derby 10.9.1.0 and am trying to figure out a  performance problem with query
taking too long.   I don’t actually want to run the 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. Verify 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 != '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.transaction_table
with the same result.  The only reason that I posted this with 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 administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message