[jira] [Created] (TRAFODION-2444) compile failed with 3 union alls

2017-01-12 Thread Joshua Liu (JIRA) 
Joshua Liu created TRAFODION-2444:
-

 Summary: compile failed with 3 union alls
 Key: TRAFODION-2444
 URL: https://issues.apache.org/jira/browse/TRAFODION-2444
 Project: Apache Trafodion
  Issue Type: Bug
Reporter: Joshua Liu
 Attachments: 三个union all编译出错，单独编译都能通过.msg

the sql is like:
--
query1
union all
query 2
union all
query3
--
it compiled failed
but query1&2&3 can compile successfully respectively.

see attachment for more details...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (TRAFODION-2443) update statistics gives a wrong error message

2017-01-12 Thread Joshua Liu (JIRA) 
Joshua Liu created TRAFODION-2443:
-

 Summary: update statistics gives a wrong error message
 Key: TRAFODION-2443
 URL: https://issues.apache.org/jira/browse/TRAFODION-2443
 Project: Apache Trafodion
  Issue Type: Bug
Reporter: Joshua Liu


// below query is of bad syntax
SQL>update statistics for table timestamp_test1 on every column, (aa;

*** ERROR[9209] Column AA does not exist in object 
TRAFODION.JOSH.TIMESTAMP_TEST1. [2017-01-12 08:26:01]

between, seems it tries to run the update statistics first, then try to check 
the syntax...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (TRAFODION-2442) timstamp can't compare with date type

2017-01-12 Thread Joshua Liu (JIRA) 
Joshua Liu created TRAFODION-2442:
-

 Summary: timstamp can't compare with date type
 Key: TRAFODION-2442
 URL: https://issues.apache.org/jira/browse/TRAFODION-2442
 Project: Apache Trafodion
  Issue Type: Bug
Reporter: Joshua Liu



SQL>select * from timestamp_test1 where a > date '2016-12-13';

A
--
2016-12-12 00:00:00.00
2017-01-10 00:00:00.00

--- 2 row(s) selected.

we can see that 2016-12-12 00:00:00.00 is large than '2016-12-13'

from the plan, we can see:

explain select * from timestamp_test1 where a > date '2016-12-13';
…
STATEMENT  select *
   from timestamp_test1
   where a > date '2016-12-13';
…
…
executor_predicates  (A > 65535-138-245 00:149:238.32757 ...0)
--- SQL operation complete.

here predicates is A > 65535-138-245 00:149:238.32757 which is abnormal



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (TRAFODION-2211) trafci should support up, down, left, right key in the keyboard

2016-09-09 Thread Joshua Liu (JIRA) 
Joshua Liu created TRAFODION-2211:
-

 Summary: trafci should support up, down, left, right key in the 
keyboard
 Key: TRAFODION-2211
 URL: https://issues.apache.org/jira/browse/TRAFODION-2211
 Project: Apache Trafodion
  Issue Type: New Feature
  Components: client-ci
Reporter: Joshua Liu
Priority: Minor


in trafci command interface,
if we click the 'up' key, then we should have a previous statement
and 'down' for the following
then use left or right key to modify



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (TRAFODION-2172) using informatica can't connect to trafodion

2016-08-19 Thread Joshua Liu (JIRA) 
Joshua Liu created TRAFODION-2172:
-

 Summary: using informatica can't connect to trafodion
 Key: TRAFODION-2172
 URL: https://issues.apache.org/jira/browse/TRAFODION-2172
 Project: Apache Trafodion
  Issue Type: Bug
  Components: client-odbc-windows
Reporter: Joshua Liu


configure informatca to connect to trafodion
it would give an orror like "No HOME variable"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (TRAFODION-2136) union all can't work efficiently

2016-07-29 Thread Joshua Liu (JIRA) 
Joshua Liu created TRAFODION-2136:
-

 Summary: union all can't work efficiently
 Key: TRAFODION-2136
 URL: https://issues.apache.org/jira/browse/TRAFODION-2136
 Project: Apache Trafodion
  Issue Type: Bug
  Components: sql-exe
Affects Versions: any
Reporter: Joshua Liu


there is one query called a
the first time we run
a;
and get the elapsed time time1
reconnect the database;
the second time we run 
a union all a;
and get another elapsed time.time2
here time2 ≈ time1*2
-
see below for detailed info
a is
select count(*)
from F_INCOME_DAY_RH a left join D_IN_SORTCODE_NEW b
on (A.INCOMESORTCODE_N = B.CODE1)
where (((a.BBQ >= date '2014-01-01') AND (a.BBQ <= date '2014-12-31')) AND
 ((a.BUDGETLEVEL = '3') AND
 ((a.TAXORGCODE in ('1', '2', '3', '4', '5'))) AND
 (a.DISTRICT_CO_CODE like 'A%' or
 a.DISTRICT_CO_CODE like 'B%')) AND
 ((a.INCOMESORTCODE_N LIKE 'A%') OR
 (a.INCOMESORTCODE_N LIKE 'B%') OR
 (a.INCOMESORTCODE_N LIKE 'C%') OR
 (a.INCOMESORTCODE_N LIKE 'F%') OR
 (a.INCOMESORTCODE_N LIKE 'G%')))
group by b.CODE5
-
SQL>explain options 'f' s1;

 
LC   RC   OP   OPERATOR  OPT   DESCRIPTION   CARD   
         -
 
7.8root  6.00E+000
6.7hash_partial_groupby  6.00E+000
5.6esp_exchange1:16(hash2)   6.00E+000
4.5hash_partial_groupby  6.00E+000
324left_hybrid_hash_joi  1.06E+006
..3trafodion_scan  F_INCOME_DAY_RH   1.06E+006
1.2esp_exchange16(rep-b):1 (m)   7.24E+002
..1trafodion_scan  D_IN_SORTCODE_NEW 7.24E+002

--- SQL operation complete.

SQL>set statistics on;

SQL>execute s1;

(EXPR)

  977626
   16080
   34817
   53722
5573

--- 5 row(s) selected.

 
Start Time 2016/07/30 09:47:50.913298
End Time   2016/07/30 09:48:05.018125
Elapsed Time  00:00:14.104827
Compile Time  00:00:05.641437
Execution Time00:00:14.104827

---
reconnect database and run a union all a;

SQL>explain options 'f' s1;

 
LC   RC   OP   OPERATOR  OPT   DESCRIPTION   CARD   
         -
 
15   .16   root  1.20E+001
714   15   merge_union   1.20E+001
13   .14   hash_partial_groupby  6.00E+000
12   .13   esp_exchange1:16(hash2)   6.00E+000
11   .12   hash_partial_groupby  6.00E+000
10   911   left_hybrid_hash_joi  1.06E+006
..10   trafodion_scan  F_INCOME_DAY_RH   1.06E+006
8.9esp_exchange16(rep-b):1 (m)   7.24E+002
..8trafodion_scan  D_IN_SORTCODE_NEW 7.24E+002
6.7hash_partial_groupby  6.00E+000
5.6esp_exchange1:16(hash2)   6.00E+000
4.5hash_partial_groupby  6.00E+000
324left_hybrid_hash_joi  1.06E+006
..3trafodion_scan  F_INCOME_DAY_RH   1.06E+006
1.2esp_exchange16(rep-b):1 (m)   7.24E+002
..1trafodion_scan  D_IN_SORTCODE_NEW 7.24E+002

--- SQL operation complete.

 
Start Time 2016/07/30 09:48:28.230061
End Time   2016/07/30 09:48:45.506429
Elapsed Time  00:00:17.276368
Compile Time  00:00:17.276368
Execution Time00:00:00.00
 


SQL>execute s1;

(EXPR)

  977626
   16080
   34817
   53722
5573
  977626
   16080
   34817
   53722
5573

--- 10 row(s) selected.

 
Start Time 2016/07/30 09:50:39.754195
End Time   2016/07/30 09:51:10.680951
Elapsed Time  00:00:30.926756
Compile Time  00:00:17.276368
Execution Time00:00:30.926756

---

her

[jira] [Created] (TRAFODION-2106) to_char() can't compare with one date

2016-07-12 Thread Joshua Liu (JIRA) 
Joshua  Liu created TRAFODION-2106:
--

 Summary: to_char() can't compare with one date
 Key: TRAFODION-2106
 URL: https://issues.apache.org/jira/browse/TRAFODION-2106
 Project: Apache Trafodion
  Issue Type: Bug
  Components: sql-cmp
Affects Versions: any
Reporter: Joshua  Liu


1.  Create one table josh_test
CREATE TABLE TRAFODION.SEABASE.JOSH_TEST
  ( 
APPDATE  VARCHAR(8) CHARACTER SET ISO88591 COLLATE
  DEFAULT DEFAULT NULL SERIALIZED
  , NAME VARCHAR(10) CHARACTER SET ISO88591 COLLATE
  DEFAULT DEFAULT NULL SERIALIZED
  )
;
Here appdate is of varchar(8) type

2.  Insert some values into the table
SQL>select * from josh_test;

APPDATE  NAME  
 --
20140101 josh  
20140102 jason 
20140821 James 
20140303 Tom   
20150209 Axia  
20150812 Jerry 
20161010 Hong  
20160802 Alex

3.  Try to test to_char:
SQL>select to_date(appdate, 'MMDD'), name from josh_test;

(EXPR) NAME  
-- --
2014-01-01 josh  
2014-01-02 jason 
2014-08-21 James 
2014-03-03 Tom   
2015-02-09 Axia  
2015-08-12 Jerry 
2016-10-10 Hong  
2016-08-02 Alex  

--- 8 row(s) selected.
Here we can see that to_char seems worked.

4.  Try to run another query
select * from josh_test where to_date(appdate, 'MMDD') > date '2015-01-01';
but failed:
*** ERROR[4041] Type CHAR(8) cannot be compared with type DATE. [2016-07-12 
10:20:12]




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (TRAFODION-1765) trafci would throw an error when set statistics on

2016-02-17 Thread Joshua Liu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/TRAFODION-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joshua  Liu updated TRAFODION-1765:
---
   Priority: Critical  (was: Minor)
Description: 
SQL>set statistics on;
SQL>get tables;
 
Tables in Schema TRAFODION.SEABASE
==
 
JOSH
JOSH_1
 
--- SQL operation complete.
 
*** ERROR[29003] Statement does not exist


  was:

SQL>set statistics on;
SQL>get tables;
 
Tables in Schema TRAFODION.SEABASE
==
 
JOSH
JOSH_1
 
--- SQL operation complete.
 
*** ERROR[29003] Statement does not exist



> trafci would throw an error when set statistics on
> --
>
> Key: TRAFODION-1765
> URL: https://issues.apache.org/jira/browse/TRAFODION-1765
> Project: Apache Trafodion
>  Issue Type: Bug
>  Components: Build Infrastructure
>Affects Versions: 1.3-incubating
>Reporter: Joshua  Liu
>Priority: Critical
>
> SQL>set statistics on;
> SQL>get tables;
>  
> Tables in Schema TRAFODION.SEABASE
> ==
>  
> JOSH
> JOSH_1
>  
> --- SQL operation complete.
>  
> *** ERROR[29003] Statement does not exist



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (TRAFODION-1805) monitor would give a wrong info for sqps when kill monitor and up node for some times

2016-02-02 Thread Joshua Liu (JIRA) 
Joshua  Liu created TRAFODION-1805:
--

 Summary: monitor would give a wrong info for sqps when kill 
monitor and up node for some times
 Key: TRAFODION-1805
 URL: https://issues.apache.org/jira/browse/TRAFODION-1805
 Project: Apache Trafodion
  Issue Type: Bug
  Components: foundation
 Environment: SUSE VM. daily build: 20160122_0900
Reporter: Joshua  Liu


Kill monitor in one node and use sqshell -a, up node to up it for some times
After up the node(here it’s suseha-4,nid 2), sqcheck would show
trafodion@suseha-2:/shares/Joshua> sqcheck
Checking if processes are up.
Checking attempt: 2; user specified max: 2. Execution time in seconds: 4.

The SQ environment is not up at all, or partially up and not operational. Check 
the logs.

Process Configured  Actual  Down
--- --  --  
DTM 5   5   
RMS 10  8   2
DcsMaster   1   1   
DcsServer   5   5   
mxosrvr 40  32  8
from ps -ef, we can see the mxsscp processes were up:
trafodion@suseha-2:~> pdsh $MY_NODES ps -ef | grep mxsscp
suseha-4: 501  41940 41664  0 08:01 ?00:00:08 mxsscp SQMON1.1 2 
2 041940 $ZSC002 192.168.0.46:33430 4 2 6 SPARE
suseha-2: 501  13919 13776  0 14:24 pts/100:00:00 grep mxsscp
suseha-2: 501  31436 31132  0 07:54 ?00:00:09 mxsscp SQMON1.1 0 
0 031436 $ZSC000 192.168.0.42:41942 4 0 6 SPARE
suseha-5: 501  52635 51607  0 07:49 ?00:00:08 mxsscp SQMON1.1 3 
3 052635 $ZSC003 192.168.0.45:33233 4 3 5 SPARE
suseha-6: 501  19601 18637  0 07:49 ?00:00:10 mxsscp SQMON1.1 4 
4 019601 $ZSC004 192.168.0.10:48671 4 4 5 SPARE
suseha-3: 501  49054 48798  0 07:58 ?00:00:11 mxsscp SQMON1.1 1 
1 049054 $ZSC001 192.168.0.44:51353 4 1 6 SPARE
but we could see different sqps info in node suseha-2 and suseha-4
trafodion@suseha-2:/shares/Joshua> sqps | grep mxsscp
[$Z001I4P] 000,00031436 001 GEN  ES--A-- $ZSC000 $PSD000 mxsscp 
[$Z001I4P] 001,00049054 001 GEN  ES--A-- $ZSC001 $PSD001 mxsscp 
[$Z001I4P] 003,00052635 001 GEN  ES--A-- $ZSC003 NONEmxsscp 
[$Z001I4P] 004,00019601 001 GEN  ES--A-- $ZSC004 NONEmxsscp 
trafodion@suseha-2:/shares/Joshua> ssh suseha-4
Last login: Tue Feb  2 17:03:47 2016 from suseha-2.novalocal
trafodion@suseha-4:~> sqps | grep mxsscp
[$Z0217Y6] 002,00041940 001 GEN  ES--A-- $ZSC002 $PSD002 mxsscp 
[$Z0217Y6] 003,00052635 001 GEN  ES--A-- $ZSC003 NONEmxsscp 
[$Z0217Y6] 004,00019601 001 GEN  ES--A-- $ZSC004 NONEmxsscp  




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (TRAFODION-1765) trafci would throw an error when set statistics on

2016-01-18 Thread Joshua Liu (JIRA) 
Joshua  Liu created TRAFODION-1765:
--

 Summary: trafci would throw an error when set statistics on
 Key: TRAFODION-1765
 URL: https://issues.apache.org/jira/browse/TRAFODION-1765
 Project: Apache Trafodion
  Issue Type: Bug
  Components: Build Infrastructure
Affects Versions: 1.3-incubating
Reporter: Joshua  Liu
Priority: Minor



SQL>set statistics on;
SQL>get tables;
 
Tables in Schema TRAFODION.SEABASE
==
 
JOSH
JOSH_1
 
--- SQL operation complete.
 
*** ERROR[29003] Statement does not exist




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (TRAFODION-1630) trafci would hang if shutdown the node at where mxosrvr used by trafci runs

2015-11-17 Thread Joshua Liu (JIRA) 
Joshua  Liu created TRAFODION-1630:
--

 Summary: trafci would hang if shutdown the node at where mxosrvr 
used by trafci runs
 Key: TRAFODION-1630
 URL: https://issues.apache.org/jira/browse/TRAFODION-1630
 Project: Apache Trafodion
  Issue Type: Bug
  Components: connectivity-mxosrvr
 Environment: daily build 1115. SUSE VM cluster
Reporter: Joshua  Liu
Priority: Minor


example:
1. use trafci to run some queries(make sure the queries won't finish within 5 
minutes)
2. check in dcs_master_node_ip:24400 to find which node is connected by trafci
3. shutdown this node
4. now 1 would hang

we should let trafci choose another MXOSRVR or just throw an error.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (TRAFODION-1629) when one node was shutdown, after turning on it, then use "sqshell -a" to up in trafodion can't make mxosrvr processes start

2015-11-16 Thread Joshua Liu (JIRA) 
Joshua  Liu created TRAFODION-1629:
--

 Summary: when one node was shutdown, after turning on it, then use 
"sqshell -a" to up in trafodion can't make mxosrvr processes start
 Key: TRAFODION-1629
 URL: https://issues.apache.org/jira/browse/TRAFODION-1629
 Project: Apache Trafodion
  Issue Type: Bug
 Environment: daily build 1115. SUSE VM cluster
Reporter: Joshua  Liu
Priority: Minor


for example
1. shutdown node suse-1
2. after a while then pow in it
3. now hadoop is OK
4. use "shell -c up up suse-1"
5. now DTM and RMS could be started except MXOSRVR processes in that node.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (TRAFODION-1593) use 'shell -c node info' to up a node may sometimes hang if kill monitor processes for some times

2015-11-06 Thread Joshua Liu (JIRA) 
Joshua  Liu created TRAFODION-1593:
--

 Summary: use 'shell -c node info' to up a node may sometimes hang 
if kill monitor processes for some times
 Key: TRAFODION-1593
 URL: https://issues.apache.org/jira/browse/TRAFODION-1593
 Project: Apache Trafodion
  Issue Type: Bug
  Components: foundation
Affects Versions: 2.0-incubating
Reporter: Joshua  Liu
Priority: Minor


 Today and yesterday we faced one issue on nap007~012 that:
 If we killed monitor on some node, then used ‘shell –c up node’ to up 
this node. Sometimes it failed to up and just hung there.

 The log file is like below:
 Cat mon.snmp.20151028.08.58.14.nap007.esgyn.local.1701.log
2015-10-28 08:58:15,037, INFO, MON, Node Number: 0,, PIN: 1701 , Process Name: 
$MONITOR,,, TID: 1701, Message ID: 101010401, [CCluster::CCluster] Validation 
of node down is enabled
2015-10-28 08:58:15,038, ERROR, MON, Node Number: 0,, PIN: 1701 , Process Name: 
$MONITOR,,, TID: 1701, Message ID: 101010402, [CCluster::CCluster], Error= No 
monitor.ini found, setting to defaults.

Cat node_up_nap007.esgyn.local.log
…
In perform_work: nap007.esgyn.local
remove shared memory ids on host nap007.esgyn.local
Unable to get the monitor port number
ssh -q nap007.esgyn.local ipcrm -m 65538
ssh -q nap007.esgyn.local ipcrm -m 327690
…

By the way, yesterday we faced the issue after killing monitor or tm for 20 
times. Today 40 times.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)