You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2010/05/04 20:01:12 UTC
[jira] Created: (DERBY-4641) aggregateOptimization.sql fails on
z/os with pmz3160sr5 with double quote and question mark output in runtime
statistics
aggregateOptimization.sql fails on z/os with pmz3160sr5 with double quote and question mark output in runtime statistics
-------------------------------------------------------------------------------------------------------------------------
Key: DERBY-4641
URL: https://issues.apache.org/jira/browse/DERBY-4641
Project: Derby
Issue Type: Bug
Components: Tools
Environment: $ java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build pmz3160sr5-20090604_01(SR5))
IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 z/OS s390-31 jvmmz3160sr5-20090519_3
5743 (JIT enabled, AOT enabled)
J9VM - 20090519_035743_bHdSMr
JIT - r9_20090518_2017
GC - 20090417_AA)
JCL - 20090529_01
$
Reporter: Kathey Marsden
Priority: Minor
With this one test and pmz3160sr5-20090604_01(SR5) the output of runtime statistics has double quote and question mark garbage, e.g
Source result set:
""""????"Scalar Aggregate ResultSet:
""""????"Number of opens = 1
""""????"Rows input = 1
" ""????"constructor time (milliseconds) = 0
" ""????"open time (milliseconds) = 0
" ""????"next time (milliseconds) = 0
" ""????"close time (milliseconds) = 0
" ""????"optimizer estimated row count: 15.00
" ""????"optimizer estimated cost: 21.13
""""????"Index Key Optimization = true
""""????"Source result set:
Looking manually at the plans, they look fine. I think this is likely a JVM issue, but don't know actually if it is impacting the test harness, ij, or derby itself. I did not see this with the 64 bit sr5 jvm, nor did I see it in 10.5 runs with earlier versions of the jvm.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-4641) aggregateOptimization.sql fails on
z/os with pmz3160sr5 with double quote and question mark output in runtime
statistics
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-4641:
----------------------------------
Attachment: aggregateOptimizationOutputAsOnZos.zip
aggregateOptimizationOutputAfterAsciiFtp.zip
Attaching output in orignal z/os format and after ascii ftp
> aggregateOptimization.sql fails on z/os with pmz3160sr5 with double quote and question mark output in runtime statistics
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4641
> URL: https://issues.apache.org/jira/browse/DERBY-4641
> Project: Derby
> Issue Type: Bug
> Components: Tools
> Environment: $ java -version
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pmz3160sr5-20090604_01(SR5))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 z/OS s390-31 jvmmz3160sr5-20090519_3
> 5743 (JIT enabled, AOT enabled)
> J9VM - 20090519_035743_bHdSMr
> JIT - r9_20090518_2017
> GC - 20090417_AA)
> JCL - 20090529_01
> $
> Reporter: Kathey Marsden
> Priority: Minor
> Attachments: aggregateOptimizationOutputAfterAsciiFtp.zip, aggregateOptimizationOutputAsOnZos.zip
>
>
> With this one test and pmz3160sr5-20090604_01(SR5) the output of runtime statistics has double quote and question mark garbage, e.g
> Source result set:
> """"????"Scalar Aggregate ResultSet:
> """"????"Number of opens = 1
> """"????"Rows input = 1
> " ""????"constructor time (milliseconds) = 0
> " ""????"open time (milliseconds) = 0
> " ""????"next time (milliseconds) = 0
> " ""????"close time (milliseconds) = 0
> " ""????"optimizer estimated row count: 15.00
> " ""????"optimizer estimated cost: 21.13
> """"????"Index Key Optimization = true
> """"????"Source result set:
> Looking manually at the plans, they look fine. I think this is likely a JVM issue, but don't know actually if it is impacting the test harness, ij, or derby itself. I did not see this with the 64 bit sr5 jvm, nor did I see it in 10.5 runs with earlier versions of the jvm.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.