[jira] [Created] (TRAFODION-2705) user has "SHOW" privilege can't do 'showddl user'
Gao, Rui-Xian created TRAFODION-2705: Summary: user has "SHOW" privilege can't do 'showddl user' Key: TRAFODION-2705 URL: https://issues.apache.org/jira/browse/TRAFODION-2705 Project: Apache Trafodion Issue Type: Bug Components: sql-security Environment: Centos6.7 + HDP2.4.2 Centos6.7 + CDH5.7.6 Reporter: Gao, Rui-Xian Assignee: Roberta Marton Priority: Minor If a user wants to do “showddl user”, what privilege does the user need to have ? I granted “SHOW” to the user, but the user can only do showddl user on himself. Test result : === SQL>connect trafodion/traf123; Connected to EsgynDB Advanced SQL>grant component privilege "SHOW" on sql_operations to qauser_sqlqaa; --- SQL operation complete. SQL>connect qauser_sqlqaa/QAPassword; Connected to EsgynDB Advanced SQL>showddl user qauser1; *** ERROR[1017] You are not authorized to perform this operation. [2017-08-08 15:48:39] SQL>showddl user qauser_sqlqaa; REGISTER USER "QAUSER_SQLQAA"; --- SQL operation complete. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (TRAFODION-2294) need add privilege checking for explain statement
[ https://issues.apache.org/jira/browse/TRAFODION-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian closed TRAFODION-2294. Assignee: Gao, Rui-Xian (was: David Wayne Birdsall) > need add privilege checking for explain statement > - > > Key: TRAFODION-2294 > URL: https://issues.apache.org/jira/browse/TRAFODION-2294 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-security > Environment: CDH5.4.8 > Centos6.7 >Reporter: Gao, Rui-Xian >Assignee: Gao, Rui-Xian > Fix For: 2.2-incubating > > > we don't have privilege checking for 'explain' statements.If a user doesn't > have privilege to execute a statement, then after explain, the user will be > able to execute the statement. > Testuser1: > SQL>create schema testsch1; > > --- SQL operation complete. > > SQL>set schema testsch1; > > --- SQL operation complete. > > SQL>create table tab1(a int, b int); > > --- SQL operation complete. > > SQL>insert into tab1 values(1,1); > > --- 1 row(s) inserted. > > SQL>select * from tab1; > > A B > --- --- > 1 1 > > --- 1 row(s) selected. > > Tesuser2: > SQL>set schema testsch1; > > --- SQL operation complete. > > SQL>get tables; > > Tables in Schema TRAFODION.TESTSCH1 > === > > SB_HISTOGRAMS > SB_HISTOGRAM_INTERVALS > SB_PERSISTENT_SAMPLES > TAB1 > > --- SQL operation complete. > > SQL>select * from tab1; > > *** ERROR[4481] The user does not have SELECT privilege on table or view > TRAFODION.TESTSCH1.TAB1. [2016-10-18 09:07:32] > > SQL>explain options 'f' select * from tab1; > > > LC RC OP OPERATOR OPT DESCRIPTION CARD > - > > 1.2root 1.00E+002 > ..1trafodion_scan TAB1 1.00E+002 > > --- SQL operation complete. > > SQL>select * from tab1; > > A B > --- --- > 1 1 > > --- 1 row(s) selected. > > SQL>insert into tab1 values(20,20); > > *** ERROR[4481] The user does not have INSERT privilege on table or view > TRAFODION.TESTSCH1.TAB1. [2016-10-18 09:11:03] > > SQL>explain options 'f' insert into tab1 values(20,20); > > > LC RC OP OPERATOR OPT DESCRIPTION CARD > - > > 1.2root o 1.00E+000 > ..1trafodion_insertTAB1 1.00E+000 > > --- SQL operation complete. > > SQL>insert into tab1 values(20,20); > > --- 1 row(s) inserted. > > SQL>select * from tab1; > > A B > --- --- > 20 20 > 1 1 > > --- 2 row(s) selected. > > SQL>showddl tab1; > > > CREATE TABLE TRAFODION.TESTSCH1.TAB1 > ( > AINT DEFAULT NULL SERIALIZED > , BINT DEFAULT NULL SERIALIZED > ) > ; > > -- GRANT SELECT, INSERT, DELETE, UPDATE, REFERENCES ON > TRAFODION.TESTSCH1.TAB1 TO TESTUSER1 WITH GRANT OPTION; > > --- SQL operation complete. > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (TRAFODION-2294) need add privilege checking for explain statement
[
https://issues.apache.org/jira/browse/TRAFODION-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16009952#comment-16009952
]
Gao, Rui-Xian commented on TRAFODION-2294:
--
The fix has been verified on R2.3 0510 daily build.
SQL>connect testuser2/user2pass;
Connected to EsgynDB Advanced
SQL>set schema testsch1;
--- SQL operation complete.
SQL>select * from tab1;
*** ERROR[4481] The user does not have SELECT privilege on table or view
TRAFODION.TESTSCH1.TAB1. [2017-05-15 03:02:25]
SQL>explain options 'f' select * from tab1;
LC RC OP OPERATOR OPT DESCRIPTION CARD
-
1.2root 1.00E+002
..1trafodion_scan TAB1 1.00E+002
--- SQL operation complete.
SQL>select * from tab1;
*** ERROR[4481] The user does not have SELECT privilege on table or view
TRAFODION.TESTSCH1.TAB1. [2017-05-15 03:04:47]
SQL>insert into tab1 values(20,20);
*** ERROR[4481] The user does not have INSERT privilege on table or view
TRAFODION.TESTSCH1.TAB1. [2017-05-15 03:06:17]
SQL>explain options 'f' insert into tab1 values(20,20);
LC RC OP OPERATOR OPT DESCRIPTION CARD
-
1.2root o 1.00E+000
..1trafodion_insertTAB1 1.00E+000
--- SQL operation complete.
SQL>insert into tab1 values(20,20);
*** ERROR[4481] The user does not have INSERT privilege on table or view
TRAFODION.TESTSCH1.TAB1. [2017-05-15 03:06:31]
SQL>create view v1 as select * from tab1;
*** ERROR[4481] The user does not have SELECT privilege on table or view
TRAFODION.TESTSCH1.TAB1. [2017-05-15 03:06:50]
> need add privilege checking for explain statement
> -
>
> Key: TRAFODION-2294
> URL: https://issues.apache.org/jira/browse/TRAFODION-2294
> Project: Apache Trafodion
> Issue Type: Bug
> Components: sql-security
> Environment: CDH5.4.8
> Centos6.7
>Reporter: Gao, Rui-Xian
>Assignee: David Wayne Birdsall
> Fix For: 2.2-incubating
>
>
> we don't have privilege checking for 'explain' statements.If a user doesn't
> have privilege to execute a statement, then after explain, the user will be
> able to execute the statement.
> Testuser1:
> SQL>create schema testsch1;
>
> --- SQL operation complete.
>
> SQL>set schema testsch1;
>
> --- SQL operation complete.
>
> SQL>create table tab1(a int, b int);
>
> --- SQL operation complete.
>
> SQL>insert into tab1 values(1,1);
>
> --- 1 row(s) inserted.
>
> SQL>select * from tab1;
>
> A B
> --- ---
> 1 1
>
> --- 1 row(s) selected.
>
> Tesuser2:
> SQL>set schema testsch1;
>
> --- SQL operation complete.
>
> SQL>get tables;
>
> Tables in Schema TRAFODION.TESTSCH1
> ===
>
> SB_HISTOGRAMS
> SB_HISTOGRAM_INTERVALS
> SB_PERSISTENT_SAMPLES
> TAB1
>
> --- SQL operation complete.
>
> SQL>select * from tab1;
>
> *** ERROR[4481] The user does not have SELECT privilege on table or view
> TRAFODION.TESTSCH1.TAB1. [2016-10-18 09:07:32]
>
> SQL>explain options 'f' select * from tab1;
>
>
> LC RC OP OPERATOR OPT DESCRIPTION CARD
> -
>
> 1.2root 1.00E+002
> ..1trafodion_scan TAB1 1.00E+002
>
> --- SQL operation complete.
>
> SQL>select * from tab1;
>
> A B
> --- ---
> 1 1
>
> --- 1 row(s) selected.
>
> SQL>insert into tab1 values(20,20);
>
> *** ERROR[4481] The user does not have INSERT privilege on table or view
> TRAFODION.TESTSCH1.TAB1. [2016-10-18 09:11:03]
>
> SQL>explain options 'f' insert into tab1 values(20,20);
>
>
> LC RC OP OPERATOR OPT DESCRIPTION CARD
> -
>
> 1.2root o 1.00E+000
> ..1trafodion_insertTAB1 1.00E+000
>
> --- SQL operation complete.
>
> SQL>insert into tab1 values(20,20);
>
> --- 1 row(s) inserted.
>
> SQL>select * from tab1;
>
> A B
> --- ---
> 20 20
> 1 1
>
> --- 2 row(s) selected.
>
> SQL>showddl tab1;
>
>
> CREATE TABLE TRAFODION.TESTSCH1.TAB1
>
[jira] [Commented] (TRAFODION-2409) support privilege control(column privileges) for hive tables
[
https://issues.apache.org/jira/browse/TRAFODION-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15838931#comment-15838931
]
Gao, Rui-Xian commented on TRAFODION-2409:
--
double checked on R2.2.1 , we support column privileges for hive tables now.
column privilege for select works well, for insert we may need warning or error
at grant since insert data into specific column for hive table is not supported
in trafodion.
create hive table
==
create database qa_test4;
use qa_test4;
create external table ext_t1(c1 varchar(20), c2 int);
dbroot user -
===
SQL>update statistics for table hive.qa_test4.ext_t1 on every column;
--- SQL operation complete.
SQL>grant select(c2) on hive.qa_test4.ext_t1 to qauser99;
--- SQL operation complete.
SQL>grant insert(c2) on hive.qa_test4.ext_t1 to qauser99; // grant successfully
--- SQL operation complete.
user qauser99 -
SQL>cqd query_cache '0';
--- SQL operation complete.
SQL>cqd TRAF_RELOAD_NATABLE_CACHE 'on';
--- SQL operation complete.
SQL>select * from hive.qa_test4.ext_t1;
*** ERROR[4481] The user does not have SELECT privilege on table or view
HIVE.QA_TEST4.EXT_T1(columns: C1). [2017-01-26 08:39:58]
SQL>select c1 from hive.qa_test4.ext_t1;
*** ERROR[4481] The user does not have SELECT privilege on table or view
HIVE.QA_TEST4.EXT_T1(columns: C1). [2017-01-26 08:40:21]
SQL>select c2 from hive.qa_test4.ext_t1;
C2
---
3
1
2
--- 3 row(s) selected.
SQL>insert into hive.qa_test4.ext_t1 values('qauser99',3); // insert into table
successfully
--- 1 row(s) inserted.
SQL>insert into hive.qa_test4.ext_t1(c1) values('qauser99'); // insert specific
will get ERROR[4223]
*** ERROR[4223] Target column list specification for insert/upsert into a Hive
table is not supported in this software version. [2017-01-26 08:46:05]
As we don't support insert for single column, can we add warning/error for
grant that column privilege is not granted ? Or user would think the grant
worked but still can insert data into all columns.
> support privilege control(column privileges) for hive tables
>
>
> Key: TRAFODION-2409
> URL: https://issues.apache.org/jira/browse/TRAFODION-2409
> Project: Apache Trafodion
> Issue Type: Improvement
> Components: sql-security
>Reporter: Gao, Rui-Xian
>Assignee: Roberta Marton
>
> we need support column privileges for hive tables.
> 1. Currently, we have problem accessing hive native tables with users that is
> not trafodion --
> 1). create table from hive
> 2). connect with user1, select from hive table will get internal error
> SQL>select * from hive.hive.mytest;
> *** ERROR[1001] An internal error occurred in module
> ../sqlcomp/PrivMgrPrivileges.cpp on line 4149. DETAILS(objectUID is 0 for
> get privileges command). [2016-12-20 12:31:55]
> *** ERROR[1034] Unable to obtain privileges [2016-12-20 12:31:55]
> 2. after creating external table for hive table, we can grant/revoke on hive
> tables, but don't support column privileges, a user will have privilege on
> all columns though only granted privileges on one column.
> 1). create table from hive
> 2). do 'update statistics' for hive table from trafodion
> 3). grant column privilge on the hive table to a user
> 4). the user still have privileges on all columns
> User trafodion—
> **
> >>grant select(a) on hive.hive.inttab1 to qauser1;
> --- SQL operation complete.
> User qauser1 –
> **
> SQL>select * from hive.hive.inttab1; // qauser1 should not have select
> privilege on column b
> --- 0 row(s) selected.
> SQL>insert into hive.hive.inttab1 values(1,1);
> *** ERROR[4481] The user does not have INSERT privilege on table or view
> HIVE.HIVE.INTTAB1. [2016-12-20 15:12:40]
> User trafodion –
> **
> >>grant insert(a) on hive.hive.inttab1 to qauser1;
> --- SQL operation complete.
> User qauser1 –
> **
> SQL>insert into hive.hive.inttab1 values(2,2); // qauser1 only have privilege
> to insert data into column a, but can insert data into all columns.
> --- 1 row(s) inserted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (TRAFODION-2409) support privilege control(column privileges) for hive tables
[ https://issues.apache.org/jira/browse/TRAFODION-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian updated TRAFODION-2409: - Comment: was deleted (was: Another issue is, any user can do update statistics for a hive table -- 1. create table in hive : create external table ext_t1(a int); 2. logon trafci with user1, select from hive.hive.ext_t1 will get internal error as described above, but the user can do 'update statistics' for the hive table. connect user1/**; SQL>update statistics for table hive.qa_db_1.traf_ext_t1 on every column; --- SQL operation complete. Expect result is ERROR[4481], the user cannot do 'update statistics' since he/she doesn't have select privileges on the table.) > support privilege control(column privileges) for hive tables > > > Key: TRAFODION-2409 > URL: https://issues.apache.org/jira/browse/TRAFODION-2409 > Project: Apache Trafodion > Issue Type: Improvement > Components: sql-security >Reporter: Gao, Rui-Xian >Assignee: Roberta Marton > > we need support column privileges for hive tables. > 1. Currently, we have problem accessing hive native tables with users that is > not trafodion -- > 1). create table from hive > 2). connect with user1, select from hive table will get internal error > SQL>select * from hive.hive.mytest; > *** ERROR[1001] An internal error occurred in module > ../sqlcomp/PrivMgrPrivileges.cpp on line 4149. DETAILS(objectUID is 0 for > get privileges command). [2016-12-20 12:31:55] > *** ERROR[1034] Unable to obtain privileges [2016-12-20 12:31:55] > 2. after creating external table for hive table, we can grant/revoke on hive > tables, but don't support column privileges, a user will have privilege on > all columns though only granted privileges on one column. > 1). create table from hive > 2). do 'update statistics' for hive table from trafodion > 3). grant column privilge on the hive table to a user > 4). the user still have privileges on all columns > User trafodion— > ** > >>grant select(a) on hive.hive.inttab1 to qauser1; > --- SQL operation complete. > User qauser1 – > ** > SQL>select * from hive.hive.inttab1; // qauser1 should not have select > privilege on column b > --- 0 row(s) selected. > SQL>insert into hive.hive.inttab1 values(1,1); > *** ERROR[4481] The user does not have INSERT privilege on table or view > HIVE.HIVE.INTTAB1. [2016-12-20 15:12:40] > User trafodion – > ** > >>grant insert(a) on hive.hive.inttab1 to qauser1; > --- SQL operation complete. > User qauser1 – > ** > SQL>insert into hive.hive.inttab1 values(2,2); // qauser1 only have privilege > to insert data into column a, but can insert data into all columns. > --- 1 row(s) inserted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2463) Hive: Any user can do update statistics for hive tables
Gao, Rui-Xian created TRAFODION-2463: Summary: Hive: Any user can do update statistics for hive tables Key: TRAFODION-2463 URL: https://issues.apache.org/jira/browse/TRAFODION-2463 Project: Apache Trafodion Issue Type: Bug Components: sql-security Affects Versions: 2.2-incubating Environment: hadoop - HDP2.4 OS - CentOS6.7 Reporter: Gao, Rui-Xian Assignee: Roberta Marton Currently, any user can do 'update statistics' for hive tables, then the user will become owner for this table and has all privileges on it. 1. create table in hive : create external table ext_t1(a int); 2. logon trafci with user1, select from hive.hive.ext_t1 will get internal error as described above, but the user can do 'update statistics' for the hive table. connect user1/**; SQL>update statistics for table hive.qa_db_1.traf_ext_t1 on every column; — SQL operation complete. Expect result is ERROR[4481], the user cannot do 'update statistics' since he/she doesn't have select privileges on the table. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-2411) connection aborted when connecting with a re-registered user
[ https://issues.apache.org/jira/browse/TRAFODION-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian resolved TRAFODION-2411. -- Resolution: Fixed > connection aborted when connecting with a re-registered user > > > Key: TRAFODION-2411 > URL: https://issues.apache.org/jira/browse/TRAFODION-2411 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-security >Affects Versions: 2.2-incubating >Reporter: Gao, Rui-Xian >Assignee: Roberta Marton > > If we unregister a user and register again, then use the re-registered user > to connect to database, the connection will get 'server aborted' info, and > then it's actually connected as DB__ROOT. > [trafodion@gyvm-1 security]$ trafci > Welcome to EsgynDB Enterprise Command Interface > Copyright (c) 2015-2016 Esgyn Corporation > Host Name/IP Address: gyvm-1.novalocal:23400 > User Name: zz > *** ERROR[8837] Invalid username or password. User: ZZ [2016-12-21 11:44:15] > User Name: trafodion > Password: > Role Name [Primary Role]: > Connected to EsgynDB Advanced > SQL>unregister user qauser10; > --- SQL operation complete. > SQL>register user qauser10; > --- SQL operation complete. > SQL>connect qauser10/mypasswd; > Server aborted abnormally or Connection timed out > * > it didn't quit, asked for host name, if we don't provide any info and hit > Enter directly, then we will be back to the connection as DB__ROOT, so > connecting with the re-registered user failed. > * > Host Name/IP Address: > Unknown Host: > Host Name/IP Address: > Unknown Host: > SQL>select current_user from (values(1)) t; > (EXPR) > > DB__ROOT > > --- 1 row(s) selected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (TRAFODION-2411) connection aborted when connecting with a re-registered user
[ https://issues.apache.org/jira/browse/TRAFODION-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian closed TRAFODION-2411. closing the JIRA since fix has been verified on R2.2.1 RC1 build > connection aborted when connecting with a re-registered user > > > Key: TRAFODION-2411 > URL: https://issues.apache.org/jira/browse/TRAFODION-2411 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-security >Affects Versions: 2.2-incubating >Reporter: Gao, Rui-Xian >Assignee: Roberta Marton > > If we unregister a user and register again, then use the re-registered user > to connect to database, the connection will get 'server aborted' info, and > then it's actually connected as DB__ROOT. > [trafodion@gyvm-1 security]$ trafci > Welcome to EsgynDB Enterprise Command Interface > Copyright (c) 2015-2016 Esgyn Corporation > Host Name/IP Address: gyvm-1.novalocal:23400 > User Name: zz > *** ERROR[8837] Invalid username or password. User: ZZ [2016-12-21 11:44:15] > User Name: trafodion > Password: > Role Name [Primary Role]: > Connected to EsgynDB Advanced > SQL>unregister user qauser10; > --- SQL operation complete. > SQL>register user qauser10; > --- SQL operation complete. > SQL>connect qauser10/mypasswd; > Server aborted abnormally or Connection timed out > * > it didn't quit, asked for host name, if we don't provide any info and hit > Enter directly, then we will be back to the connection as DB__ROOT, so > connecting with the re-registered user failed. > * > Host Name/IP Address: > Unknown Host: > Host Name/IP Address: > Unknown Host: > SQL>select current_user from (values(1)) t; > (EXPR) > > DB__ROOT > > --- 1 row(s) selected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2411) connection aborted when connecting with a re-registered user
[ https://issues.apache.org/jira/browse/TRAFODION-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837839#comment-15837839 ] Gao, Rui-Xian commented on TRAFODION-2411: -- The fix has been verified on R2.2.1 rc1 - User Name: trafodion Password: Role Name [Primary Role]: Connected to EsgynDB Advanced SQL>register user qauser1; --- SQL operation complete. SQL>connect qauser1/mypass; Connected to EsgynDB Advanced SQL>values(current_user); (EXPR) QAUSER1 --- 1 row(s) selected. SQL>disconnect; Session Disconnected. Please connect to the database by using connect/reconnect command. SQL>connect trafodion/traf123; Connected to EsgynDB Advanced SQL>unregister user qauser1; --- SQL operation complete. SQL>register user qauser1; --- SQL operation complete. SQL>connect qauser1/mypass; Connected to EsgynDB Advanced SQL>values(current_user); (EXPR) QAUSER1 --- 1 row(s) selected. > connection aborted when connecting with a re-registered user > > > Key: TRAFODION-2411 > URL: https://issues.apache.org/jira/browse/TRAFODION-2411 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-security >Affects Versions: 2.2-incubating >Reporter: Gao, Rui-Xian >Assignee: Roberta Marton > > If we unregister a user and register again, then use the re-registered user > to connect to database, the connection will get 'server aborted' info, and > then it's actually connected as DB__ROOT. > [trafodion@gyvm-1 security]$ trafci > Welcome to EsgynDB Enterprise Command Interface > Copyright (c) 2015-2016 Esgyn Corporation > Host Name/IP Address: gyvm-1.novalocal:23400 > User Name: zz > *** ERROR[8837] Invalid username or password. User: ZZ [2016-12-21 11:44:15] > User Name: trafodion > Password: > Role Name [Primary Role]: > Connected to EsgynDB Advanced > SQL>unregister user qauser10; > --- SQL operation complete. > SQL>register user qauser10; > --- SQL operation complete. > SQL>connect qauser10/mypasswd; > Server aborted abnormally or Connection timed out > * > it didn't quit, asked for host name, if we don't provide any info and hit > Enter directly, then we will be back to the connection as DB__ROOT, so > connecting with the re-registered user failed. > * > Host Name/IP Address: > Unknown Host: > Host Name/IP Address: > Unknown Host: > SQL>select current_user from (values(1)) t; > (EXPR) > > DB__ROOT > > --- 1 row(s) selected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2458) connection will abort if trafodion is not initialized when security is enabled
Gao, Rui-Xian created TRAFODION-2458: Summary: connection will abort if trafodion is not initialized when security is enabled Key: TRAFODION-2458 URL: https://issues.apache.org/jira/browse/TRAFODION-2458 Project: Apache Trafodion Issue Type: Bug Components: sql-security Affects Versions: 2.2-incubating Reporter: Gao, Rui-Xian Assignee: Roberta Marton Priority: Minor connection will abort if trafodion is not initialized when security is enabled. [trafodion@centosqa-1 phase1]$ trafci Welcome to EsgynDB Enterprise Command Interface Copyright (c) 2015-2016 Esgyn Corporation Host Name/IP Address: centosqa-1.novalocal:23400 User Name: zz *** ERROR[29157] Server aborted abnormally or Connection timed out *** ERROR[8837] Internal error occurred. User: ZZ [2017-01-22 07:10:49] = use should be able to logon even if trafodion is not initialized. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2441) user has only select privilege on a table can do insert/update/delete on the view
Gao, Rui-Xian created TRAFODION-2441: Summary: user has only select privilege on a table can do insert/update/delete on the view Key: TRAFODION-2441 URL: https://issues.apache.org/jira/browse/TRAFODION-2441 Project: Apache Trafodion Issue Type: Bug Components: sql-security Affects Versions: 2.2-incubating Environment: hadoop - CDH 5.6 OS -- CentOS 6.7 Reporter: Gao, Rui-Xian Assignee: Roberta Marton a user has only select privilege on the table can do insert/update/delete on the view, then data in base table also get inserted/updated/deleted Reproduce Steps === 1. connect as trafodion -- create table testtab1(a int, b int); select * from testtab1; grant select on testtab1 to qauser_sqlqaa; showddl testtab1; 2. connect as qauser_sqlqaa -- select * from testtab1; create view v_tab1 as select * from testtab1; showddl v_tab1; insert into v_tab1 values(1,1); select * from v_tab1; select * from testtab1; delete from testtab1; delete from v_tab1; select * from testtab1; Test OutPut User Name: trafodion Password: Role Name [Primary Role]: Connected to EsgynDB Advanced SQL>create table testtab1(a int, b int); --- SQL operation complete. SQL>select * from testtab1; --- 0 row(s) selected. SQL>grant select on testtab1 to qauser_sqlqaa; --- SQL operation complete. SQL>showddl testtab1; CREATE TABLE TRAFODION.SEABASE.TESTTAB1 ( AINT DEFAULT NULL NOT SERIALIZED , BINT DEFAULT NULL NOT SERIALIZED ) ATTRIBUTES ALIGNED FORMAT ; -- GRANT SELECT, INSERT, DELETE, UPDATE, REFERENCES ON TRAFODION.SEABASE.TESTTAB1 TO DB__ROOT WITH GRANT OPTION; GRANT SELECT ON TRAFODION.SEABASE.TESTTAB1 TO QAUSER_SQLQAA; --- SQL operation complete. SQL>connect qauser_sqlqaa/QAPassword; Connected to EsgynDB Advanced SQL>select * from testtab1; --- 0 row(s) selected. SQL>create view v_tab1 as select * from testtab1; --- SQL operation complete. SQL>showddl v_tab1; // user only has SELECT privilege on the view CREATE VIEW TRAFODION.SEABASE.V_TAB1 AS SELECT TRAFODION.SEABASE.TESTTAB1.A, TRAFODION.SEABASE.TESTTAB1.B FROM TRAFODION.SEABASE.TESTTAB1 ; -- GRANT SELECT ON TRAFODION.SEABASE.V_TAB1 TO QAUSER_SQLQAA; --- SQL operation complete. SQL>insert into v_tab1 values(1,1); // user can insert data into view --- 1 row(s) inserted. SQL>select * from v_tab1; A B --- --- 1 1 --- 1 row(s) selected. SQL>select * from testtab1; // data in base table A B --- --- 1 1 --- 1 row(s) selected. SQL>delete from testtab1; // expected, user doesn’t have privilege to delete data from base table *** ERROR[4481] The user does not have DELETE privilege on table or view TRAFODION.SEABASE.TESTTAB1. [2017-01-12 10:39:11] SQL>delete from v_tab1; // user doesn’t have delete privilege but can delete data from the view --- 1 row(s) deleted. SQL>select * from testtab1; // data in base table got deleted --- 0 row(s) selected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-2424) we should remove meaningless 'role name' when launching trafci on server side
[ https://issues.apache.org/jira/browse/TRAFODION-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian updated TRAFODION-2424: - Environment: OS -- centos6.7 cloudera version -- CDH5.6 was: build -- EsgynDB R2.2 RC8 OS -- centos6.7 cloudera version -- CDH5.6 > we should remove meaningless 'role name' when launching trafci on server side > - > > Key: TRAFODION-2424 > URL: https://issues.apache.org/jira/browse/TRAFODION-2424 > Project: Apache Trafodion > Issue Type: Improvement > Components: client-jdbc-t4 > Environment: OS -- centos6.7 > cloudera version -- CDH5.6 >Reporter: Gao, Rui-Xian >Assignee: Kevin Xu >Priority: Minor > > When security is enabled, connecting from trafci, we need provide user name > and password, and for ‘Role Name’, seems it doesn’t take any effect, we can > leave it as blank or provide any string. > Since the 'Role Name' is meaningless, we should remove it when lauching > trafci. > User Name: qauser1 > Password: > Role Name [Primary Role]: 123 > Connected to EsgynDB Advanced > SQL> -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-2423) any user can perform 'initialize trafodion,drop'
[ https://issues.apache.org/jira/browse/TRAFODION-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian updated TRAFODION-2423: - Affects Version/s: 2.0-incubating > any user can perform 'initialize trafodion,drop' > > > Key: TRAFODION-2423 > URL: https://issues.apache.org/jira/browse/TRAFODION-2423 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-security >Affects Versions: 2.0-incubating > Environment: cloudera version -- CDH5.6 > hortonworks version -- HDP2.3.4 >Reporter: Gao, Rui-Xian >Assignee: Roberta Marton >Priority: Critical > > When security is enabled, any user can perform 'initialize trafodion,dorp' to > drop all objects, we should limit the user to DB__ROOT only. > [trafodion@gyvm-1 security]$ trafci > Welcome to EsgynDB Enterprise Command Interface > Copyright (c) 2015-2016 Esgyn Corporation > Host Name/IP Address: gyvm-1.novalocal:23400 > User Name: zz > *** ERROR[8837] Invalid username or password. User: ZZ [2017-01-01 22:40:23] > User Name: qauser2 > Password: > Role Name [Primary Role]: > Connected to EsgynDB Advanced > SQL>select * from user1sch.user1t; > *** ERROR[4481] The user does not have SELECT privilege on table or view > TRAFODION.USER1SCH.USER1T. [2017-01-01 22:41:03] > SQL>get component privileges on sql_operations for qauser2; > --- SQL operation complete. > SQL>initialize trafodion,drop; > --- SQL operation complete. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-2423) any user can perform 'initialize trafodion,drop'
[ https://issues.apache.org/jira/browse/TRAFODION-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian updated TRAFODION-2423: - Environment: cloudera version -- CDH5.6 hortonworks version -- HDP2.3.4 was: EsgynDB 2.2 rc8 CDH5.6 HDP2.3.4 > any user can perform 'initialize trafodion,drop' > > > Key: TRAFODION-2423 > URL: https://issues.apache.org/jira/browse/TRAFODION-2423 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-security > Environment: cloudera version -- CDH5.6 > hortonworks version -- HDP2.3.4 >Reporter: Gao, Rui-Xian >Assignee: Roberta Marton >Priority: Critical > > When security is enabled, any user can perform 'initialize trafodion,dorp' to > drop all objects, we should limit the user to DB__ROOT only. > [trafodion@gyvm-1 security]$ trafci > Welcome to EsgynDB Enterprise Command Interface > Copyright (c) 2015-2016 Esgyn Corporation > Host Name/IP Address: gyvm-1.novalocal:23400 > User Name: zz > *** ERROR[8837] Invalid username or password. User: ZZ [2017-01-01 22:40:23] > User Name: qauser2 > Password: > Role Name [Primary Role]: > Connected to EsgynDB Advanced > SQL>select * from user1sch.user1t; > *** ERROR[4481] The user does not have SELECT privilege on table or view > TRAFODION.USER1SCH.USER1T. [2017-01-01 22:41:03] > SQL>get component privileges on sql_operations for qauser2; > --- SQL operation complete. > SQL>initialize trafodion,drop; > --- SQL operation complete. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2424) we should remove meaningless 'role name' when launching trafci on server side
Gao, Rui-Xian created TRAFODION-2424: Summary: we should remove meaningless 'role name' when launching trafci on server side Key: TRAFODION-2424 URL: https://issues.apache.org/jira/browse/TRAFODION-2424 Project: Apache Trafodion Issue Type: Improvement Components: client-jdbc-t4 Environment: build -- EsgynDB R2.2 RC8 OS -- centos6.7 cloudera version -- CDH5.6 Reporter: Gao, Rui-Xian Assignee: Kevin Xu Priority: Minor When security is enabled, connecting from trafci, we need provide user name and password, and for ‘Role Name’, seems it doesn’t take any effect, we can leave it as blank or provide any string. Since the 'Role Name' is meaningless, we should remove it when lauching trafci. User Name: qauser1 Password: Role Name [Primary Role]: 123 Connected to EsgynDB Advanced SQL> -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2423) any user can perform 'initialize trafodion,drop'
Gao, Rui-Xian created TRAFODION-2423: Summary: any user can perform 'initialize trafodion,drop' Key: TRAFODION-2423 URL: https://issues.apache.org/jira/browse/TRAFODION-2423 Project: Apache Trafodion Issue Type: Bug Components: sql-security Environment: EsgynDB 2.2 rc8 CDH5.6 HDP2.3.4 Reporter: Gao, Rui-Xian Assignee: Roberta Marton Priority: Critical When security is enabled, any user can perform 'initialize trafodion,dorp' to drop all objects, we should limit the user to DB__ROOT only. [trafodion@gyvm-1 security]$ trafci Welcome to EsgynDB Enterprise Command Interface Copyright (c) 2015-2016 Esgyn Corporation Host Name/IP Address: gyvm-1.novalocal:23400 User Name: zz *** ERROR[8837] Invalid username or password. User: ZZ [2017-01-01 22:40:23] User Name: qauser2 Password: Role Name [Primary Role]: Connected to EsgynDB Advanced SQL>select * from user1sch.user1t; *** ERROR[4481] The user does not have SELECT privilege on table or view TRAFODION.USER1SCH.USER1T. [2017-01-01 22:41:03] SQL>get component privileges on sql_operations for qauser2; --- SQL operation complete. SQL>initialize trafodion,drop; --- SQL operation complete. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2409) support privilege control(column privileges) for hive tables
[ https://issues.apache.org/jira/browse/TRAFODION-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15782218#comment-15782218 ] Gao, Rui-Xian commented on TRAFODION-2409: -- Another issue is, any user can do update statistics for a hive table -- 1. create table in hive : create external table ext_t1(a int); 2. logon trafci with user1, select from hive.hive.ext_t1 will get internal error as described above, but the user can do 'update statistics' for the hive table. connect user1/**; SQL>update statistics for table hive.qa_db_1.traf_ext_t1 on every column; --- SQL operation complete. Expect result is ERROR[4481], the user cannot do 'update statistics' since he/she doesn't have select privileges on the table. > support privilege control(column privileges) for hive tables > > > Key: TRAFODION-2409 > URL: https://issues.apache.org/jira/browse/TRAFODION-2409 > Project: Apache Trafodion > Issue Type: Improvement > Components: sql-security >Reporter: Gao, Rui-Xian >Assignee: Roberta Marton > > we need support column privileges for hive tables. > 1. Currently, we have problem accessing hive native tables with users that is > not trafodion -- > 1). create table from hive > 2). connect with user1, select from hive table will get internal error > SQL>select * from hive.hive.mytest; > *** ERROR[1001] An internal error occurred in module > ../sqlcomp/PrivMgrPrivileges.cpp on line 4149. DETAILS(objectUID is 0 for > get privileges command). [2016-12-20 12:31:55] > *** ERROR[1034] Unable to obtain privileges [2016-12-20 12:31:55] > 2. after creating external table for hive table, we can grant/revoke on hive > tables, but don't support column privileges, a user will have privilege on > all columns though only granted privileges on one column. > 1). create table from hive > 2). do 'update statistics' for hive table from trafodion > 3). grant column privilge on the hive table to a user > 4). the user still have privileges on all columns > User trafodion— > ** > >>grant select(a) on hive.hive.inttab1 to qauser1; > --- SQL operation complete. > User qauser1 – > ** > SQL>select * from hive.hive.inttab1; // qauser1 should not have select > privilege on column b > --- 0 row(s) selected. > SQL>insert into hive.hive.inttab1 values(1,1); > *** ERROR[4481] The user does not have INSERT privilege on table or view > HIVE.HIVE.INTTAB1. [2016-12-20 15:12:40] > User trafodion – > ** > >>grant insert(a) on hive.hive.inttab1 to qauser1; > --- SQL operation complete. > User qauser1 – > ** > SQL>insert into hive.hive.inttab1 values(2,2); // qauser1 only have privilege > to insert data into column a, but can insert data into all columns. > --- 1 row(s) inserted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2411) connection aborted when connecting with a re-registered user
[ https://issues.apache.org/jira/browse/TRAFODION-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15766638#comment-15766638 ] Gao, Rui-Xian commented on TRAFODION-2411: -- If we provide hostname after the abort message, the connection will succeed. SQL>connect qauser10/mypasswd; Server aborted abnormally or Connection timed out Host Name/IP Address: 192.168.1.6:23400 Connected to EsgynDB Advanced SQL>select current_user from (values(1)) t; (EXPR) QAUSER10 --- 1 row(s) selected. > connection aborted when connecting with a re-registered user > > > Key: TRAFODION-2411 > URL: https://issues.apache.org/jira/browse/TRAFODION-2411 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-security >Affects Versions: 2.2-incubating >Reporter: Gao, Rui-Xian >Assignee: Roberta Marton > > If we unregister a user and register again, then use the re-registered user > to connect to database, the connection will get 'server aborted' info, and > then it's actually connected as DB__ROOT. > [trafodion@gyvm-1 security]$ trafci > Welcome to EsgynDB Enterprise Command Interface > Copyright (c) 2015-2016 Esgyn Corporation > Host Name/IP Address: gyvm-1.novalocal:23400 > User Name: zz > *** ERROR[8837] Invalid username or password. User: ZZ [2016-12-21 11:44:15] > User Name: trafodion > Password: > Role Name [Primary Role]: > Connected to EsgynDB Advanced > SQL>unregister user qauser10; > --- SQL operation complete. > SQL>register user qauser10; > --- SQL operation complete. > SQL>connect qauser10/mypasswd; > Server aborted abnormally or Connection timed out > * > it didn't quit, asked for host name, if we don't provide any info and hit > Enter directly, then we will be back to the connection as DB__ROOT, so > connecting with the re-registered user failed. > * > Host Name/IP Address: > Unknown Host: > Host Name/IP Address: > Unknown Host: > SQL>select current_user from (values(1)) t; > (EXPR) > > DB__ROOT > > --- 1 row(s) selected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-2411) connection aborted when connecting with a re-registered user
[ https://issues.apache.org/jira/browse/TRAFODION-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian updated TRAFODION-2411: - Description: If we unregister a user and register again, then use the re-registered user to connect to database, the connection will get 'server aborted' info, and then it's actually connected as DB__ROOT. [trafodion@gyvm-1 security]$ trafci Welcome to EsgynDB Enterprise Command Interface Copyright (c) 2015-2016 Esgyn Corporation Host Name/IP Address: gyvm-1.novalocal:23400 User Name: zz *** ERROR[8837] Invalid username or password. User: ZZ [2016-12-21 11:44:15] User Name: trafodion Password: Role Name [Primary Role]: Connected to EsgynDB Advanced SQL>unregister user qauser10; --- SQL operation complete. SQL>register user qauser10; --- SQL operation complete. SQL>connect qauser10/mypasswd; Server aborted abnormally or Connection timed out * it didn't quit, asked for host name, if we don't provide any info and hit Enter directly, then we will be back to the connection as DB__ROOT, so connecting with the re-registered user failed. * Host Name/IP Address: Unknown Host: Host Name/IP Address: Unknown Host: SQL>select current_user from (values(1)) t; (EXPR) DB__ROOT --- 1 row(s) selected. was: If we unregister a user and register again, then use the re-registered user to connect to database, the connection will get 'server aborted' info, and then it's actually connected as DB__ROOT. [trafodion@gyvm-1 security]$ trafci Welcome to EsgynDB Enterprise Command Interface Copyright (c) 2015-2016 Esgyn Corporation Host Name/IP Address: gyvm-1.novalocal:23400 User Name: zz *** ERROR[8837] Invalid username or password. User: ZZ [2016-12-21 11:44:15] User Name: trafodion Password: Role Name [Primary Role]: Connected to EsgynDB Advanced SQL>unregister user qauser10; --- SQL operation complete. SQL>register user qauser10; --- SQL operation complete. SQL>connect qauser10/mypasswd; Server aborted abnormally or Connection timed out * it didn't quit, ask for host name, if we don't provide any info and hit Enter directly, then we will be connected as DB__ROOT * Host Name/IP Address: Unknown Host: Host Name/IP Address: Unknown Host: SQL>select current_user from (values(1)) t; (EXPR) DB__ROOT --- 1 row(s) selected. > connection aborted when connecting with a re-registered user > > > Key: TRAFODION-2411 > URL: https://issues.apache.org/jira/browse/TRAFODION-2411 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-security >Affects Versions: 2.2-incubating >Reporter: Gao, Rui-Xian >Assignee: Roberta Marton > > If we unregister a user and register again, then use the re-registered user > to connect to database, the connection will get 'server aborted' info, and > then it's actually connected as DB__ROOT. > [trafodion@gyvm-1 security]$ trafci > Welcome to EsgynDB Enterprise Command Interface > Copyright (c) 2015-2016 Esgyn Corporation > Host Name/IP Address: gyvm-1.novalocal:23400 > User Name: zz > *** ERROR[8837] Invalid username or password. User: ZZ [2016-12-21 11:44:15] > User Name: trafodion > Password: > Role Name [Primary Role]: > Connected to EsgynDB Advanced > SQL>unregister user qauser10; > --- SQL operation complete. > SQL>register user qauser10; > --- SQL operation complete. > SQL>connect qauser10/mypasswd; > Server aborted abnormally or Connection timed out > * > it didn't quit, asked for host name, if we don't provide any info and hit > Enter directly, then we will be back to the connection as DB__ROOT, so > connecting with the re-registered user failed. > * > Host Name/IP Address: > Unknown Host: > Host Name/IP Address: > Unknown Host: > SQL>select current_user from (values(1)) t; > (EXPR) >
[jira] [Created] (TRAFODION-2411) connection aborted when connecting with a re-registered user
Gao, Rui-Xian created TRAFODION-2411: Summary: connection aborted when connecting with a re-registered user Key: TRAFODION-2411 URL: https://issues.apache.org/jira/browse/TRAFODION-2411 Project: Apache Trafodion Issue Type: Bug Components: sql-security Affects Versions: 2.2-incubating Reporter: Gao, Rui-Xian Assignee: Roberta Marton If we unregister a user and register again, then user the re-registered user to connect to database, the connection will get 'server aborted' info, and then it's actually connected as DB__ROOT. [trafodion@gyvm-1 security]$ trafci Welcome to EsgynDB Enterprise Command Interface Copyright (c) 2015-2016 Esgyn Corporation Host Name/IP Address: gyvm-1.novalocal:23400 User Name: zz *** ERROR[8837] Invalid username or password. User: ZZ [2016-12-21 11:44:15] User Name: trafodion Password: Role Name [Primary Role]: Connected to EsgynDB Advanced SQL>unregister user qauser10; --- SQL operation complete. SQL>register user qauser10; --- SQL operation complete. SQL>connect qauser10/mypasswd; Server aborted abnormally or Connection timed out * it didn't quit, ask for host name, if we don't provide any info and hit Enter directly, then we will be connected as DB__ROOT * Host Name/IP Address: Unknown Host: Host Name/IP Address: Unknown Host: SQL>select current_user from (values(1)) t; (EXPR) DB__ROOT --- 1 row(s) selected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-2411) connection aborted when connecting with a re-registered user
[ https://issues.apache.org/jira/browse/TRAFODION-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian updated TRAFODION-2411: - Description: If we unregister a user and register again, then use the re-registered user to connect to database, the connection will get 'server aborted' info, and then it's actually connected as DB__ROOT. [trafodion@gyvm-1 security]$ trafci Welcome to EsgynDB Enterprise Command Interface Copyright (c) 2015-2016 Esgyn Corporation Host Name/IP Address: gyvm-1.novalocal:23400 User Name: zz *** ERROR[8837] Invalid username or password. User: ZZ [2016-12-21 11:44:15] User Name: trafodion Password: Role Name [Primary Role]: Connected to EsgynDB Advanced SQL>unregister user qauser10; --- SQL operation complete. SQL>register user qauser10; --- SQL operation complete. SQL>connect qauser10/mypasswd; Server aborted abnormally or Connection timed out * it didn't quit, ask for host name, if we don't provide any info and hit Enter directly, then we will be connected as DB__ROOT * Host Name/IP Address: Unknown Host: Host Name/IP Address: Unknown Host: SQL>select current_user from (values(1)) t; (EXPR) DB__ROOT --- 1 row(s) selected. was: If we unregister a user and register again, then user the re-registered user to connect to database, the connection will get 'server aborted' info, and then it's actually connected as DB__ROOT. [trafodion@gyvm-1 security]$ trafci Welcome to EsgynDB Enterprise Command Interface Copyright (c) 2015-2016 Esgyn Corporation Host Name/IP Address: gyvm-1.novalocal:23400 User Name: zz *** ERROR[8837] Invalid username or password. User: ZZ [2016-12-21 11:44:15] User Name: trafodion Password: Role Name [Primary Role]: Connected to EsgynDB Advanced SQL>unregister user qauser10; --- SQL operation complete. SQL>register user qauser10; --- SQL operation complete. SQL>connect qauser10/mypasswd; Server aborted abnormally or Connection timed out * it didn't quit, ask for host name, if we don't provide any info and hit Enter directly, then we will be connected as DB__ROOT * Host Name/IP Address: Unknown Host: Host Name/IP Address: Unknown Host: SQL>select current_user from (values(1)) t; (EXPR) DB__ROOT --- 1 row(s) selected. > connection aborted when connecting with a re-registered user > > > Key: TRAFODION-2411 > URL: https://issues.apache.org/jira/browse/TRAFODION-2411 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-security >Affects Versions: 2.2-incubating >Reporter: Gao, Rui-Xian >Assignee: Roberta Marton > > If we unregister a user and register again, then use the re-registered user > to connect to database, the connection will get 'server aborted' info, and > then it's actually connected as DB__ROOT. > [trafodion@gyvm-1 security]$ trafci > Welcome to EsgynDB Enterprise Command Interface > Copyright (c) 2015-2016 Esgyn Corporation > Host Name/IP Address: gyvm-1.novalocal:23400 > User Name: zz > *** ERROR[8837] Invalid username or password. User: ZZ [2016-12-21 11:44:15] > User Name: trafodion > Password: > Role Name [Primary Role]: > Connected to EsgynDB Advanced > SQL>unregister user qauser10; > --- SQL operation complete. > SQL>register user qauser10; > --- SQL operation complete. > SQL>connect qauser10/mypasswd; > Server aborted abnormally or Connection timed out > * > it didn't quit, ask for host name, if we don't provide any info and hit Enter > directly, then we will be connected as DB__ROOT > * > Host Name/IP Address: > Unknown Host: > Host Name/IP Address: > Unknown Host: > SQL>select current_user from (values(1)) t; > (EXPR) > > DB__ROOT > > --- 1 row(s) selected.
[jira] [Created] (TRAFODION-2409) support privilege control(column privileges) for hive tables
Gao, Rui-Xian created TRAFODION-2409: Summary: support privilege control(column privileges) for hive tables Key: TRAFODION-2409 URL: https://issues.apache.org/jira/browse/TRAFODION-2409 Project: Apache Trafodion Issue Type: Improvement Components: sql-security Reporter: Gao, Rui-Xian Assignee: Roberta Marton we need support column privileges for hive tables. 1. Currently, we have problem accessing hive native tables with users that is not trafodion -- 1). create table from hive 2). connect with user1, select from hive table will get internal error SQL>select * from hive.hive.mytest; *** ERROR[1001] An internal error occurred in module ../sqlcomp/PrivMgrPrivileges.cpp on line 4149. DETAILS(objectUID is 0 for get privileges command). [2016-12-20 12:31:55] *** ERROR[1034] Unable to obtain privileges [2016-12-20 12:31:55] 2. after creating external table for hive table, we can grant/revoke on hive tables, but don't support column privileges, a user will have privilege on all columns though only granted privileges on one column. 1). create table from hive 2). do 'update statistics' for hive table from trafodion 3). grant column privilge on the hive table to a user 4). the user still have privileges on all columns User trafodion— ** >>grant select(a) on hive.hive.inttab1 to qauser1; --- SQL operation complete. User qauser1 – ** SQL>select * from hive.hive.inttab1; // qauser1 should not have select privilege on column b --- 0 row(s) selected. SQL>insert into hive.hive.inttab1 values(1,1); *** ERROR[4481] The user does not have INSERT privilege on table or view HIVE.HIVE.INTTAB1. [2016-12-20 15:12:40] User trafodion – ** >>grant insert(a) on hive.hive.inttab1 to qauser1; --- SQL operation complete. User qauser1 – ** SQL>insert into hive.hive.inttab1 values(2,2); // qauser1 only have privilege to insert data into column a, but can insert data into all columns. --- 1 row(s) inserted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2407) Need include privilege checking on 'PUBLIC' when getting privileges for a user
Gao, Rui-Xian created TRAFODION-2407: Summary: Need include privilege checking on 'PUBLIC' when getting privileges for a user Key: TRAFODION-2407 URL: https://issues.apache.org/jira/browse/TRAFODION-2407 Project: Apache Trafodion Issue Type: Improvement Components: sql-security Reporter: Gao, Rui-Xian Assignee: Roberta Marton Some privilege checking for specific commands will be affected by privileges on PUBLIC, so we'd better include privilege checking for PUBLIC when getting privileges for a user. For example, we have privilege checking for SHOWDDL commands. To perform a SHOWDDL one must: -- be DB__ROOT -- be object owner -- have the SHOW privilege (PUBLIC & DB__ROOTROLE has priv) -- have SELECT privileges on object So a user can do showddl on any objects if PUBLIC has SHOW component privilege. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-2396) When security is enabled, connection will get internal error if there is mxosrvr down
[ https://issues.apache.org/jira/browse/TRAFODION-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian updated TRAFODION-2396: - Description: Checking security status, is enabled – [trafodion@gy05 scripts]$ ./traf_authentication_setup --status INFO: Start of security (authentication and authorization) script Thu Nov 17 16:17:28 CST 2016. INFO: *** Trafodion security (authentication and authorization) status *** Authentication is ENABLED Authorization (grant/revoke) is ENABLED INFO: End of security (authorization and authentication) script Thu Nov 17 16:21:34 CST 2016. connection will get internal error if there is mxosrvr down on the cluster -- Process Configured Actual Down --- -- -- DTM 2 2 RMS 4 4 DcsMaster 1 1 DcsServer 2 2 mxosrvr 48 47 1 RestServer 1 1 User Name: trafodion Password: Role Name [Primary Role]: *** ERROR[8837] Internal error occurred. User: TRAFODION [2016-11-17 16:21:07] = This doesn't meet our HA expectations. We can connect when security is off even if there is mxosrvrs down. Process Configured Actual Down --- -- -- DTM 2 1 1 RMS 4 2 2 DcsMaster 1 1 DcsServer 2 2 mxosrvr 16 8 8 RestServer 1 1 [trafodion@gyvm-1 401]$ trafci Welcome to EsgynDB Enterprise Command Interface Copyright (c) 2015-2016 Esgyn Corporation Host Name/IP Address: gyvm-1.novalocal:23400 User Name: zz Connected to EsgynDB Advanced SQL> was: Checking security status, is enabled – [trafodion@gy05 scripts]$ ./traf_authentication_setup --status INFO: Start of security (authentication and authorization) script Thu Nov 17 16:17:28 CST 2016. INFO: *** Trafodion security (authentication and authorization) status *** Authentication is ENABLED Authorization (grant/revoke) is ENABLED INFO: End of security (authorization and authentication) script Thu Nov 17 16:21:34 CST 2016. connection will get internal error is there is mxosrvr down on the cluster -- Process Configured Actual Down --- -- -- DTM 2 2 RMS 4 4 DcsMaster 1 1 DcsServer 2 2 mxosrvr 48 47 1 RestServer 1 1 User Name: trafodion Password: Role Name [Primary Role]: *** ERROR[8837] Internal error occurred. User: TRAFODION [2016-11-17 16:21:07] = This doesn't meet our HA expectations. We can connect when security is off even if there is mxosrvrs down. Process Configured Actual Down --- -- -- DTM 2 1 1 RMS 4 2 2 DcsMaster 1 1 DcsServer 2 2 mxosrvr 16 8 8 RestServer 1 1 [trafodion@gyvm-1 401]$ trafci Welcome to EsgynDB Enterprise Command Interface Copyright (c) 2015-2016 Esgyn Corporation Host Name/IP Address: gyvm-1.novalocal:23400 User Name: zz Connected to EsgynDB Advanced SQL> > When security is enabled, connection will get internal error if there is > mxosrvr down > - > > Key: TRAFODION-2396 > URL: https://issues.apache.org/jira/browse/TRAFODION-2396 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-security >Reporter: Gao, Rui-Xian >Assignee: Roberta Marton > > Checking security status, is enabled – > [trafodion@gy05 scripts]$ ./traf_authentication_setup --status > INFO: Start of security (authentication and authorization) script Thu Nov 17 > 16:17:28 CST 2016. > INFO: *** Trafodion security (authentication and authorization) status *** >Authentication is ENABLED >Authorization (grant/revoke) is ENABLED > INFO: End of security (authorization and authentication) script Thu Nov 17 > 16:21:34 CST 2016. > connection will get internal error if there is mxosrvr down on the cluster -- > Process Configured Actual Down > --- -- -- > DTM 2 2 > RMS 4 4 > DcsMaster 1 1 > DcsServer 2 2 > mxosrvr 48
[jira] [Created] (TRAFODION-2396) When security is enabled, connection will get internal error if there is mxosrvr down
Gao, Rui-Xian created TRAFODION-2396: Summary: When security is enabled, connection will get internal error if there is mxosrvr down Key: TRAFODION-2396 URL: https://issues.apache.org/jira/browse/TRAFODION-2396 Project: Apache Trafodion Issue Type: Bug Components: sql-security Reporter: Gao, Rui-Xian Assignee: Roberta Marton Checking security status, is enabled – [trafodion@gy05 scripts]$ ./traf_authentication_setup --status INFO: Start of security (authentication and authorization) script Thu Nov 17 16:17:28 CST 2016. INFO: *** Trafodion security (authentication and authorization) status *** Authentication is ENABLED Authorization (grant/revoke) is ENABLED INFO: End of security (authorization and authentication) script Thu Nov 17 16:21:34 CST 2016. connection will get internal error is there is mxosrvr down on the cluster -- Process Configured Actual Down --- -- -- DTM 2 2 RMS 4 4 DcsMaster 1 1 DcsServer 2 2 mxosrvr 48 47 1 RestServer 1 1 User Name: trafodion Password: Role Name [Primary Role]: *** ERROR[8837] Internal error occurred. User: TRAFODION [2016-11-17 16:21:07] = This doesn't meet our HA expectations. We can connect when security is off even if there is mxosrvrs down. Process Configured Actual Down --- -- -- DTM 2 1 1 RMS 4 2 2 DcsMaster 1 1 DcsServer 2 2 mxosrvr 16 8 8 RestServer 1 1 [trafodion@gyvm-1 401]$ trafci Welcome to EsgynDB Enterprise Command Interface Copyright (c) 2015-2016 Esgyn Corporation Host Name/IP Address: gyvm-1.novalocal:23400 User Name: zz Connected to EsgynDB Advanced SQL> -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2395) Support conversion from secure to non-secure during installation
Gao, Rui-Xian created TRAFODION-2395: Summary: Support conversion from secure to non-secure during installation Key: TRAFODION-2395 URL: https://issues.apache.org/jira/browse/TRAFODION-2395 Project: Apache Trafodion Issue Type: Bug Components: sql-security Reporter: Gao, Rui-Xian Assignee: Roberta Marton If we enable ldap during the first install, security status is correct after the installation, and correct user/password can logon the database – This is correct. *Problem 1 -- If we install esgynDB again, and set the installation path same as the previous install, security will still be enabled though we gave ‘N’ to not to enable ldap during installation, and after installation, correct user/password can connect to the database. *Problem 2 – if we install esgynDB again, set the installation path to a different directory, security will still be enabled though we gave ‘N’ to not to enable ldap during installation, and there will be internal error connecting to database since there is no config file under $MY_SQROOT/sql/scripts output for problem#2, checking status after a second install -- [trafodion@suse-4 scripts]$ ./traf_authentication_setup --status INFO: Start of security (authentication and authorization) script Thu Nov 24 11:30:09 CST 2016. INFO: *** Trafodion security (authentication and authorization) status *** Authentication is ENABLED Authorization (grant/revoke) is ENABLED INFO: End of security (authorization and authentication) script Thu Nov 24 11:30:14 CST 2016. [trafodion@suse-4 scripts]$ trafci Welcome to EsgynDB Enterprise Command Interface Copyright (c) 2015-2016 Esgyn Corporation Host Name/IP Address: suse-4.novalocal:23400 User Name: zz *** ERROR[8837] Invalid username or password. User: ZZ [2016-11-24 11:31:06] User Name: trafodion Password: Role Name [Primary Role]: *** ERROR[29157] Server aborted abnormally or Connection timed out *** ERROR[8837] Internal error occurred. User: TRAFODION [2016-11-24 11:31:15] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (TRAFODION-2339) column privilege -- a user who doesn't have select privilege on all columns can insert data into the table
[ https://issues.apache.org/jira/browse/TRAFODION-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian reassigned TRAFODION-2339: Assignee: Roberta Marton > column privilege -- a user who doesn't have select privilege on all columns > can insert data into the table > -- > > Key: TRAFODION-2339 > URL: https://issues.apache.org/jira/browse/TRAFODION-2339 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-security > Environment: CDH5.4.8 HDP2.4.0 > esgynDB R2.2 1023 daily >Reporter: Gao, Rui-Xian >Assignee: Roberta Marton > > a user who doesn't have select privilege on all columns can insert data into > the table successfully. > >>create table tab2(a int, b int, c int); > --- SQL operation complete. > >>grant insert(a,c),select(a) on tab2 to testuser1; > --- SQL operation complete. > >>grant insert(b,c),select(b) on tab2 to testuser1; > --- SQL operation complete. > >>showddl tab2; > CREATE TABLE TRAFODION.MYTESTSCH.TAB2 > ( > AINT DEFAULT NULL NOT SERIALIZED > , BINT DEFAULT NULL NOT SERIALIZED > , CINT DEFAULT NULL NOT SERIALIZED > ) > ATTRIBUTES ALIGNED FORMAT > ; > -- GRANT SELECT, INSERT, DELETE, UPDATE, REFERENCES ON > TRAFODION.MYTESTSCH.TAB2 TO DB__ROOT WITH GRANT OPTION; > GRANT SELECT(A, B), INSERT(A, B, C) ON TRAFODION.MYTESTSCH.TAB2 TO > TESTUSER1; > --- SQL operation complete. > connect as testuser1 -- > SQL>select * from tab2; > *** ERROR[4481] The user does not have SELECT privilege on table or view > TRAFODION.MYTESTSCH.TAB2(columns: C). [2016-11-04 17:07:42] > SQL>insert into tab2 values(1,2,3); > --- 1 row(s) inserted. > testuser1 doesn't have select privilege on columnC, but insert data into > columnC successfully. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2339) column privilege -- a user who doesn't have select privilege on all columns can insert data into the table
Gao, Rui-Xian created TRAFODION-2339: Summary: column privilege -- a user who doesn't have select privilege on all columns can insert data into the table Key: TRAFODION-2339 URL: https://issues.apache.org/jira/browse/TRAFODION-2339 Project: Apache Trafodion Issue Type: Bug Components: sql-security Environment: CDH5.4.8 HDP2.4.0 esgynDB R2.2 1023 daily Reporter: Gao, Rui-Xian a user who doesn't have select privilege on all columns can insert data into the table successfully. >>create table tab2(a int, b int, c int); --- SQL operation complete. >>grant insert(a,c),select(a) on tab2 to testuser1; --- SQL operation complete. >>grant insert(b,c),select(b) on tab2 to testuser1; --- SQL operation complete. >>showddl tab2; CREATE TABLE TRAFODION.MYTESTSCH.TAB2 ( AINT DEFAULT NULL NOT SERIALIZED , BINT DEFAULT NULL NOT SERIALIZED , CINT DEFAULT NULL NOT SERIALIZED ) ATTRIBUTES ALIGNED FORMAT ; -- GRANT SELECT, INSERT, DELETE, UPDATE, REFERENCES ON TRAFODION.MYTESTSCH.TAB2 TO DB__ROOT WITH GRANT OPTION; GRANT SELECT(A, B), INSERT(A, B, C) ON TRAFODION.MYTESTSCH.TAB2 TO TESTUSER1; --- SQL operation complete. connect as testuser1 -- SQL>select * from tab2; *** ERROR[4481] The user does not have SELECT privilege on table or view TRAFODION.MYTESTSCH.TAB2(columns: C). [2016-11-04 17:07:42] SQL>insert into tab2 values(1,2,3); --- 1 row(s) inserted. testuser1 doesn't have select privilege on columnC, but insert data into columnC successfully. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2294) need add privilege checking for explain statement
Gao, Rui-Xian created TRAFODION-2294:
Summary: need add privilege checking for explain statement
Key: TRAFODION-2294
URL: https://issues.apache.org/jira/browse/TRAFODION-2294
Project: Apache Trafodion
Issue Type: Bug
Components: sql-security
Environment: CDH5.4.8
Centos6.7
Reporter: Gao, Rui-Xian
Assignee: Roberta Marton
we don't have privilege checking for 'explain' statements.If a user doesn't
have privilege to execute a statement, then after explain, the user will be
able to execute the statement.
Testuser1:
SQL>create schema testsch1;
--- SQL operation complete.
SQL>set schema testsch1;
--- SQL operation complete.
SQL>create table tab1(a int, b int);
--- SQL operation complete.
SQL>insert into tab1 values(1,1);
--- 1 row(s) inserted.
SQL>select * from tab1;
A B
--- ---
1 1
--- 1 row(s) selected.
Tesuser2:
SQL>set schema testsch1;
--- SQL operation complete.
SQL>get tables;
Tables in Schema TRAFODION.TESTSCH1
===
SB_HISTOGRAMS
SB_HISTOGRAM_INTERVALS
SB_PERSISTENT_SAMPLES
TAB1
--- SQL operation complete.
SQL>select * from tab1;
*** ERROR[4481] The user does not have SELECT privilege on table or view
TRAFODION.TESTSCH1.TAB1. [2016-10-18 09:07:32]
SQL>explain options 'f' select * from tab1;
LC RC OP OPERATOR OPT DESCRIPTION CARD
-
1.2root 1.00E+002
..1trafodion_scan TAB1 1.00E+002
--- SQL operation complete.
SQL>select * from tab1;
A B
--- ---
1 1
--- 1 row(s) selected.
SQL>insert into tab1 values(20,20);
*** ERROR[4481] The user does not have INSERT privilege on table or view
TRAFODION.TESTSCH1.TAB1. [2016-10-18 09:11:03]
SQL>explain options 'f' insert into tab1 values(20,20);
LC RC OP OPERATOR OPT DESCRIPTION CARD
-
1.2root o 1.00E+000
..1trafodion_insertTAB1 1.00E+000
--- SQL operation complete.
SQL>insert into tab1 values(20,20);
--- 1 row(s) inserted.
SQL>select * from tab1;
A B
--- ---
20 20
1 1
--- 2 row(s) selected.
SQL>showddl tab1;
CREATE TABLE TRAFODION.TESTSCH1.TAB1
(
AINT DEFAULT NULL SERIALIZED
, BINT DEFAULT NULL SERIALIZED
)
;
-- GRANT SELECT, INSERT, DELETE, UPDATE, REFERENCES ON TRAFODION.TESTSCH1.TAB1
TO TESTUSER1 WITH GRANT OPTION;
--- SQL operation complete.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (TRAFODION-2279) revoke all doesn't revoke column privileges
Gao, Rui-Xian created TRAFODION-2279: Summary: revoke all doesn't revoke column privileges Key: TRAFODION-2279 URL: https://issues.apache.org/jira/browse/TRAFODION-2279 Project: Apache Trafodion Issue Type: Bug Components: sql-security Environment: centos6.7 cdh5.4.8 Reporter: Gao, Rui-Xian Assignee: Roberta Marton 'revoke all' doesn't revoke column privileges. >>create table tabl1(a int, b int); --- SQL operation complete. >>grant select(a) on tabl1 to qauser1; --- SQL operation complete. >>grant delete on tabl1 to qauser1; --- SQL operation complete. >>showddl tabl1; CREATE TABLE TRAFODION.RACHEL_SCH.TABL1 ( AINT DEFAULT NULL NOT SERIALIZED , BINT DEFAULT NULL NOT SERIALIZED ) ATTRIBUTES ALIGNED FORMAT ; -- GRANT SELECT, INSERT, DELETE, UPDATE, REFERENCES ON TRAFODION.RACHEL_SCH.TABL1 TO DB__ROOT WITH GRANT OPTION; GRANT DELETE ON TRAFODION.RACHEL_SCH.TABL1 TO QAUSER1; GRANT SELECT(A) ON TRAFODION.RACHEL_SCH.TABL1 TO QAUSER1; --- SQL operation complete. >>revoke all on tabl1 from qauser1; --- SQL operation complete. >>showddl tabl1; CREATE TABLE TRAFODION.RACHEL_SCH.TABL1 ( AINT DEFAULT NULL NOT SERIALIZED , BINT DEFAULT NULL NOT SERIALIZED ) ATTRIBUTES ALIGNED FORMAT ; -- GRANT SELECT, INSERT, DELETE, UPDATE, REFERENCES ON TRAFODION.RACHEL_SCH.TABL1 TO DB__ROOT WITH GRANT OPTION; GRANT SELECT(A) ON TRAFODION.RACHEL_SCH.TABL1 TO QAUSER1; --- SQL operation complete. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2244) a user who has been granted drop_table privilege can cleanup any object
Gao, Rui-Xian created TRAFODION-2244: Summary: a user who has been granted drop_table privilege can cleanup any object Key: TRAFODION-2244 URL: https://issues.apache.org/jira/browse/TRAFODION-2244 Project: Apache Trafodion Issue Type: Bug Components: sql-security Environment: cdh5.4.8 centos6.7 Reporter: Gao, Rui-Xian Assignee: Roberta Marton a user who has been granted drop_table privilege can cleanup any object that he doesn't have privileges to drop. connect as testuser1: create schema testuser1_sch; set schema testuser1_sch; create table t5( a int, b int); create view v5 as select * from t5; create index idx5 on t5(a); connect as DB__ROOT - grant component privilege DROP_TABLE on sql_operations to testuser2; connect as testuser2 - SQL> cleanup table t5; --- SQL operation complete. SQL>cleanup object v5; --- SQL operation complete. SQL>cleanup index idx5; --- SQL operation complete. SQL>cleanup schema testuser1_sch; --- SQL operation complete. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2205) invalid character error at create schema when authorization is long user
Gao, Rui-Xian created TRAFODION-2205: Summary: invalid character error at create schema when authorization is long user Key: TRAFODION-2205 URL: https://issues.apache.org/jira/browse/TRAFODION-2205 Project: Apache Trafodion Issue Type: Bug Components: sql-cmu Environment: Centos6.7 EsgynDB R2.2 0825daily Reporter: Gao, Rui-Xian Assignee: Roberta Marton invalid character error at create schema when authorization is long user. The error can only be reproduced from trafci, there is no problem in sqlci. SQL>create schema myschema4 authorization qauser_1012345678201234567830123456784012345678501234567860123456787012345678801234567890123456781001234567110123456712012345128; *** ERROR[2109] Invalid Character error converting SQL statement from character set UTF8 to character set UCS2 (character position 137, byte offset 137). [2016-09-01 08:09:10] *** ERROR[1323] Unable to grant privileges while creating SB_HISTOGRAMS. [2016-09-01 08:09:10] *** ERROR[1029] Object TRAFODION.MYSCHEMA4.SB_HISTOGRAMS could not be created. [2016-09-01 08:09:10] *** ERROR[1058] Unable to create histogram table SB_HISTOGRAMS. [2016-09-01 08:09:10] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2203) a user can grant privileges that he doesn’t have to other users/roles successfully
Gao, Rui-Xian created TRAFODION-2203: Summary: a user can grant privileges that he doesn’t have to other users/roles successfully Key: TRAFODION-2203 URL: https://issues.apache.org/jira/browse/TRAFODION-2203 Project: Apache Trafodion Issue Type: Bug Components: sql-security Environment: Centos6.7 EsgynDB R2.2 0825daily Reporter: Gao, Rui-Xian Assignee: Roberta Marton a user can grant privileges that he doesn’t have to other users/roles successfully. To reproduce -- root user -- create role role1; create schema mysch; set schema mysch; create table tab1(a int, b int)no partition; grant insert on tab1 to testuser1 with grant option; connect as testuser1 -- set schema mysch; SQL>grant select on tab1 to role1; *** ERROR[1012] No privileges were granted. You lack grant option on the specified privileges. [2016-09-01 15:31:33] //Rachel: this is expected SQL>grant insert ,select on tab1 to role1; --- SQL operation complete. // should return error, testuser1 doesn’t have select privilege on tab1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2197) column privilege -- mxosrvr crashed when granting multiple column privileges to a user
Gao, Rui-Xian created TRAFODION-2197:
Summary: column privilege -- mxosrvr crashed when granting
multiple column privileges to a user
Key: TRAFODION-2197
URL: https://issues.apache.org/jira/browse/TRAFODION-2197
Project: Apache Trafodion
Issue Type: Bug
Components: sql-security
Environment: centos6.7
EsgynDB R2.2 0825 daily
Reporter: Gao, Rui-Xian
Assignee: Roberta Marton
mxosrvr crashed when granting multiple column privileges to a user.
SQL>grant select,insert(a),update,references(a) on atab1 to role1;
*** ERROR[29157] Server aborted abnormally or Connection timed out
*** ERROR[29160] The message header was not long enough
*** ERROR[29157] Server aborted abnormally or Connection timed out
*** ERROR[29160] The message header was not long enough
mxosrvr core stack trace -
#0 0x7f59ceb34625 in raise () from /lib64/libc.so.6
#1 0x7f59ceb35d8d in abort () from /lib64/libc.so.6
#2 0x7f59d03901c5 in os::abort(bool) ()
from /usr/java/jdk1.8.0_101/jre/lib/amd64/server/libjvm.so
#3 0x7f59d0531313 in VMError::report_and_die() ()
from /usr/java/jdk1.8.0_101/jre/lib/amd64/server/libjvm.so
#4 0x7f59d03959ef in JVM_handle_linux_signal ()
from /usr/java/jdk1.8.0_101/jre/lib/amd64/server/libjvm.so
#5 0x7f59d038c183 in signalHandler(int, siginfo*, void*) ()
from /usr/java/jdk1.8.0_101/jre/lib/amd64/server/libjvm.so
#6
#7 0x7f59c941c11d in PrivMgrPrivileges::hasColumnWGO (this=,
colPrivsArrayIn=std::vector of length 2, capacity 2 = {...},
roleIDs=std::vector of length 0, capacity 0, privStatus=@0x7f59bb80af44)
at ../sqlcomp/PrivMgrPrivileges.cpp:5766
#8 0x7f59c942a5f7 in PrivMgrPrivileges::grantColumnPrivileges
(this=0x7f59bb80b520,
objectType=COM_BASE_TABLE_OBJECT, granteeID=133, granteeName="ROLE1",
grantorName=
"TESTUSER1", colPrivsArrayIn=, isWGOSpecified=false)
at ../sqlcomp/PrivMgrPrivileges.cpp:1064
#9 0x7f59c942c099 in PrivMgrPrivileges::grantObjectPriv
(this=0x7f59bb80b520,
objectType=COM_BASE_TABLE_OBJECT, granteeID=133, granteeName="ROLE1",
grantorName=
"TESTUSER1", privsList=std::vector of length 2, capacity 2 = {...},
colPrivsArray=std::vector of length 2, capacity 2 = {...},
isAllSpecified=false,
isWGOSpecified=false) at ../sqlcomp/PrivMgrPrivileges.cpp:1385
#10 0x7f59c93f6593 in PrivMgrCommands::grantObjectPrivilege
(this=0x7f59bb80caa0,
objectUID=, objectName=,
objectType=COM_BASE_TABLE_OBJECT, granteeUID=133, granteeName="ROLE1",
grantorUID=33464,
grantorName="TESTUSER1", privsList=std::vector of length 2, capacity 2 =
{...},
colPrivsArray=std::vector of length 2, capacity 2 = {...},
isAllSpecified=false,
---Type to continue, or q to quit---
isWGOSpecified=false) at ../sqlcomp/PrivMgrCommands.cpp:695
#11 0x7f59c93a4ee1 in CmpSeabaseDDL::seabaseGrantRevoke
(this=0x7f59bb80e910,
stmtDDLNode=, isGrant=1, currCatName=...,
currSchName=...,
useHBase=-1149188864) at ../sqlcomp/CmpSeabaseDDLtable.cpp:9827
#12 0x7f59c9352815 in CmpSeabaseDDL::executeSeabaseDDL
(this=0x7f59bb80e910, ddlExpr=
0x7f595d8d56d0, ddlNode=0x7f595d8e54d0, currCatName=..., currSchName=...,
dws=0x0)
at ../sqlcomp/CmpSeabaseDDLcommon.cpp:9599
#13 0x7f59c6e5b6d0 in CmpStatement::process (this=,
statement=) at ../arkcmp/CmpStatement.cpp:922
#14 0x7f59c6e49287 in CmpContext::compileDirect (this=0x7f59b97a2090,
data=0x7f59ba3a0ee8 "\200",
data_len=208, outHeap=0x7f59badab128, charset=15,
op=CmpMessageObj::PROCESSDDL,
gen_code=@0x7f59bb80f320, gen_code_len=@0x7f59bb80f32c, parserFlags=4194304,
parentQid=0x7f59ba3a0d38
"MXID110010229892123393032426226600206U3346400_373_SQL_CUR_5",
parentQidLen=67, diagsArea=0x7f59ba3a0fc0) at ../arkcmp/CmpContext.cpp:877
#15 0x7f59ccad4374 in ExDDLTcb::work (this=0x7f59ba33b918) at
../executor/ex_ddl.cpp:281
#16 0x7f59ccc49663 in ExScheduler::work (this=0x7f59ba33b480,
prevWaitTime=)
at ../executor/ExScheduler.cpp:331
#17 0x7f59ccb402d2 in ex_root_tcb::execute (this=0x7f59ba33c890,
cliGlobals=0x17fce80, glob=
0x7f59ba3a08b0, input_desc=0x7f59ba329948, diagsArea=@0x7f59bb810a50,
reExecute=0)
at ../executor/ex_root.cpp:1057
#18 0x7f59ce258b64 in CliStatement::execute (this=0x7f59ba347040,
cliGlobals=0x17fce80,
input_desc=0x7f59ba329948, diagsArea=,
execute_state=,
fixupOnly=0, cliflags=0) at ../cli/Statement.cpp:4534
#19 0x7f59ce1f1e7c in SQLCLI_PerformTasks(CliGlobals *, ULng32, SQLSTMT_ID
*, SQLDESC_ID *, SQLDESC_ID *, Lng32, Lng32, typedef __va_list_tag
__va_list_tag *, SQLCLI_PTR_PAIRS *, SQLCLI_PTR_PAIRS *) (
cliGlobals=0x17fce80, tasks=8063, statement_id=0x39f4eb8,
input_descriptor=0x39f4ee8,
output_descriptor=0x0, num_input_ptr_pairs=0, num_output_ptr_pairs=0,
ap=0x7f59bb810bf0,
in
[jira] [Updated] (TRAFODION-2196) column privilege -- a user who has been granted privileges on a table with grant option will get error when he grants column privilges to other users/roles
[ https://issues.apache.org/jira/browse/TRAFODION-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian updated TRAFODION-2196: - Assignee: Roberta Marton > column privilege -- a user who has been granted privileges on a table with > grant option will get error when he grants column privilges to other > users/roles > --- > > Key: TRAFODION-2196 > URL: https://issues.apache.org/jira/browse/TRAFODION-2196 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-security > Environment: centos6.7 > EsgynDB R2.2 0825daily >Reporter: Gao, Rui-Xian >Assignee: Roberta Marton > > A user has been granted privileges on a table with grant option will get > error when he grants column privilges to other users/roles > Reproduce Steps -- > create role role1; > create schema mysch; > set schema mysch; > create table atab1(a int not null primary key, b int, c varchar(10)); > grant select,insert ,delete, update ,references(a) on atab1 to testuser1 with > grant option; > Connect as testuser1 - > Set schema mysch; > grant select(a,b),insert(a),update(b,c),references(a) on atab1 to role1; > *** ERROR[1012] No privileges were granted. You lack grant option on the > specified privileges. [2016-08-27 17:38:32] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2196) column privilege -- a user who has been granted privileges on a table with grant option will get error when he grants column privilges to other users/roles
Gao, Rui-Xian created TRAFODION-2196: Summary: column privilege -- a user who has been granted privileges on a table with grant option will get error when he grants column privilges to other users/roles Key: TRAFODION-2196 URL: https://issues.apache.org/jira/browse/TRAFODION-2196 Project: Apache Trafodion Issue Type: Bug Components: sql-security Environment: centos6.7 EsgynDB R2.2 0825daily Reporter: Gao, Rui-Xian A user has been granted privileges on a table with grant option will get error when he grants column privilges to other users/roles Reproduce Steps -- create role role1; create schema mysch; set schema mysch; create table atab1(a int not null primary key, b int, c varchar(10)); grant select,insert ,delete, update ,references(a) on atab1 to testuser1 with grant option; Connect as testuser1 - Set schema mysch; grant select(a,b),insert(a),update(b,c),references(a) on atab1 to role1; *** ERROR[1012] No privileges were granted. You lack grant option on the specified privileges. [2016-08-27 17:38:32] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2189) user has incorrect privilege on columns if multiple roles with different column privileges are granted to the user
Gao, Rui-Xian created TRAFODION-2189: Summary: user has incorrect privilege on columns if multiple roles with different column privileges are granted to the user Key: TRAFODION-2189 URL: https://issues.apache.org/jira/browse/TRAFODION-2189 Project: Apache Trafodion Issue Type: Bug Components: sql-security Reporter: Gao, Rui-Xian Assignee: Roberta Marton create role role1; create role role2; create schema mysch; set schema mysch; create table tab1(col1 int not null primary key,col2 int ,col3 varchar(10)); grant insert(col1,col2), select(col1,col2) on tab1 to role1 with grant option; grant update(col2) on tab1 to role1 with grant option; grant update(col2) on tab1 to role2 with grant option; grant role role1, role2 to qauser2; connect as qauser2: set schema mysch; insert into tab1(col1,col2) values(2,2); // insert should succeed because role1 has select privilege on col2. *** ERROR[4481] The user does not have SELECT privilege on table or view TRAFODION.MYSCH.TAB1(columns: COL2). [2016-08-24 10:04:08] *** ERROR[4481] The user does not have INSERT privilege on table or view TRAFODION.MYSCH.TAB1(columns: COL2). [2016-08-24 10:04:08] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2177) Revoke combined column privileges from role failed
Gao, Rui-Xian created TRAFODION-2177: Summary: Revoke combined column privileges from role failed Key: TRAFODION-2177 URL: https://issues.apache.org/jira/browse/TRAFODION-2177 Project: Apache Trafodion Issue Type: Bug Components: sql-security Reporter: Gao, Rui-Xian Assignee: Roberta Marton Revoke combined column privileges from role failed, but revoke the privileges seperately would succeed. Reproduce Steps -- create role role1; create schema grantsch; set schema grantsch; create table a03tab1(col1 int, col2 int, col3 varchar(10))no partition; grant insert(col1,col2), select on a03tab1 to role1; SQL>revoke insert(col1,col2), select on a03tab1 from role1; *** ERROR[1037] Revoke failed because of a dependent grant between authorization ID _SYSTEM and authorization ID DB__ROOT [2016-08-17 10:00:20] >>revoke select on a03tab1 from role1; --- SQL operation complete. >>revoke insert(col1,col2) on a03tab1 from role1; --- SQL operation complete. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2176) a user grant component privilege to another user with by clause got error if the user in by clause is the grantor itself
Gao, Rui-Xian created TRAFODION-2176: Summary: a user grant component privilege to another user with by clause got error if the user in by clause is the grantor itself Key: TRAFODION-2176 URL: https://issues.apache.org/jira/browse/TRAFODION-2176 Project: Apache Trafodion Issue Type: Bug Components: sql-security Reporter: Gao, Rui-Xian Assignee: Roberta Marton Priority: Minor a user grant component privilege to another user with by clause got error if the user in by clause is the grantor itself. But the grant will succeed without the by clause. Reproduce Steps -- create role role1; create role role2; register component comp1; create component privilege created as 'cr' on comp1 ; create component privilege updated as 'up' on comp1 ; create component privilege deleted as 'de' on comp1 ; grant component privilege created ,updated on comp1 to qauser1 with grant option by db__root; connect as qauser1: SQL>grant component privilege updated on comp1 to qauser2 by qauser1; *** ERROR[1017] You are not authorized to perform this operation. [2016-08-16 08:31:00] SQL>grant component privilege updated on comp1 to qauser2; --- SQL operation complete. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2175) a user should only see specific schemas/tables that he has privileges to
Gao, Rui-Xian created TRAFODION-2175: Summary: a user should only see specific schemas/tables that he has privileges to Key: TRAFODION-2175 URL: https://issues.apache.org/jira/browse/TRAFODION-2175 Project: Apache Trafodion Issue Type: Improvement Components: sql-security Environment: OS -- centos6.7 , centos7.1 , centos7.2 esgynDB -- R2.2 daily build Reporter: Gao, Rui-Xian Assignee: Roberta Marton we have a requirement that a user should only see the objects that he has privileges to do operations on. Current feature is, ‘get schemas’ will return all schemas in the database, and in a private schema created by a user, another user can still see all tables with ‘get tables’, and also can check table’s structure with ‘showddl’. If we have many customer data on cloud cluster, we don’t want a customer to view any other customers’ data, we want the customers to be isolated from each other. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2171) 'get users' returned invalid character error when trying to turn on security on centos7.x
Gao, Rui-Xian created TRAFODION-2171: Summary: 'get users' returned invalid character error when trying to turn on security on centos7.x Key: TRAFODION-2171 URL: https://issues.apache.org/jira/browse/TRAFODION-2171 Project: Apache Trafodion Issue Type: Bug Components: sql-security Environment: OS -- Centos7.2 esgynDB -- poc build 20160808_1715 based on R2.1 Reporter: Gao, Rui-Xian Assignee: Roberta Marton 'get users' returned invalid character error on centos7.1 and centos7.2, so failed to turn security on. >>get users; *** ERROR[2109] Invalid Character error converting SQL statement from character set UTF8 to character set UCS2 (character position 76, byte offset 76). *** ERROR[8822] The statement was not prepared. --- SQL operation failed with errors 'select from TRAFODION."_MD_".AUTHS' can return data normally. 'get roles' works fine. 'get users for roles' works fine. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1758) A user has dbroot role can't grant component privilege to other users/roles
[ https://issues.apache.org/jira/browse/TRAFODION-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian updated TRAFODION-1758: - Assignee: Roberta Marton > A user has dbroot role can't grant component privilege to other users/roles > --- > > Key: TRAFODION-1758 > URL: https://issues.apache.org/jira/browse/TRAFODION-1758 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-security >Reporter: Gao, Rui-Xian >Assignee: Roberta Marton > > A user has dbroot role can't grant component privilege to other users/roles > Reproduce steps -- > User DBROOT -- > create role myrole1; > register component myusers1; > create component privilege created as 'cr' on myusers1 detail 'create users'; > create table t2(a int, b int); > grant role DB__rootrole to testuser1 ; > > User testuser1 -- > qi_mxci2>grant component privilege created on myusers1 to myrole1 with grant > option; > *** ERROR[1017] You are not authorized to perform this operation. [2015-12-31 > 15:07:32] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2161) Metadata upgrade failed when there is user view on repository tables
Gao, Rui-Xian created TRAFODION-2161: Summary: Metadata upgrade failed when there is user view on repository tables Key: TRAFODION-2161 URL: https://issues.apache.org/jira/browse/TRAFODION-2161 Project: Apache Trafodion Issue Type: Bug Components: sql-cmu Environment: centos6.7 CDH5.4.8 esgynDB R2.2 0811 daily build Reporter: Gao, Rui-Xian Assignee: Roberta Marton [trafodion@centosqa-1 ~]$ sqlci EsgynDB Advanced Conversational Interface 2.2.0 Copyright (c) 2015-2016 Esgyn Corporation >>get schemas; *** ERROR[1395] Trafodion needs to be upgraded on this system due to metadata version mismatch. Do 'initialize trafodion, upgrade' to upgrade metadata. Or do 'initialize trafodion, drop' followed by 'initialize trafodion'. Be aware that the second option will delete all metadata and user objects from Trafodion database . *** ERROR[8822] The statement was not prepared. >>initialize trafodion, upgrade; Metadata Upgrade: started Version Check: started Metadata needs to be upgraded from Version 1.0.1 to 2.1.0. Upgrade needed for Catalogs, Privileges, Repository. Version Check: done Drop Old Metadata: started Drop Old Metadata: done Backup Current Metadata: started Backup Current Metadata: done Drop Current Metadata: started Drop Current Metadata: done Initialize New Metadata: started Initialize New Metadata: done Copy Old Metadata: started Copy Old Metadata: done Validate Metadata Copy: started Validate Metadata Copy: done Delete Old Metadata Info: started Delete Old Metadata Info: done Upgrade Repository: Started Start: Drop Old Repository End: Drop Old Repository Start: Rename Current Repository Upgrade Repository: Restoring Old Repository Start: Rename Old Repository back to New End: Rename Old Repository back to New Upgrade Repository: Restore done Drop Old Metadata: started Drop Old Metadata: done Metadata Upgrade: failed *** ERROR[1427] Table cannot be renamed. Reason: Operation not allowed if dependent views exist. Drop the views and recreate them after rename. *** ERROR[8839] Transaction was aborted. --- SQL operation failed with errors. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-1966) [offline backup&restore] TrafexportSnapshot ran into NoClassDefFoundError on HDP2.4
[ https://issues.apache.org/jira/browse/TRAFODION-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383618#comment-15383618 ] Gao, Rui-Xian commented on TRAFODION-1966: -- Yes, we still can not do offline backup with default options on HDP, TrafexportSnapshot is a custom utility in $MY_SQROOT/export/lib/trafodion-utility-2.1.0.jar , maybe it's unavailable on HDP. Current workaround is to use option '-l 0' to force using hbase ExportSnapshot class instead. > [offline backup&restore] TrafexportSnapshot ran into NoClassDefFoundError on > HDP2.4 > > > Key: TRAFODION-1966 > URL: https://issues.apache.org/jira/browse/TRAFODION-1966 > Project: Apache Trafodion > Issue Type: Bug > Components: db-utility-backup-restore > Environment: centos6.7, hbase1.1 HDP2.4.0 >Reporter: Gao, Rui-Xian >Assignee: liu ming > > offline backup on HDP2.4.0 will run into error -- > ./run_full_trafodion_backup.sh > Exporting TRAFODION.RACHEL_QA.IDX1_SNAP_20160503-2207 ... > hbase org.trafodion.utility.backuprestore.TrafExportSnapshot -snapshot > TRAFODION.RACHEL_QA.IDX1_SNAP_20160503-2207 -copy-to > hdfs://suse-0.novalocal:8020/trafodion_backups/backup_20160503-2207/TRAFODION.RACHEL_QA.IDX1_SNAP_20160503-2207 > -mappers 0 -mr-lowlimit-mb 100 > 2016-05-03 22:09:49,141 INFO [main] backuprestore.TrafExportSnapshot: > Trafodion Export Snapshot Utility > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in > [jar:file:/usr/hdp/2.3.4.7-4/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in > [jar:file:/usr/hdp/2.3.4.7-4/zookeeper/lib/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an > explanation. > SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory] > 2016-05-03 22:09:50,797 INFO [main] backuprestore.TrafExportSnapshot: Copy > Snapshot Manifest > 2016-05-03 22:09:51,246 INFO [main] backuprestore.TrafExportSnapshot: > Loading Snapshot 'TRAFODION.RACHEL_QA.IDX1_SNAP_20160503-2207' hfile list > 2016-05-03 22:09:51,487 INFO [main] backuprestore.TrafExportSnapshot: Copy > Snapshot Data Files > Exception in thread "main" java.lang.NoClassDefFoundError: > org/apache/hadoop/hbase/mob/MobUtils > at > org.trafodion.utility.backuprestore.TrafExportSnapshot.getCopyInputPath(TrafExportSnapshot.java:1052) > at > org.trafodion.utility.backuprestore.TrafExportSnapshot.run(TrafExportSnapshot.java:983) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76) > at > org.trafodion.utility.backuprestore.TrafExportSnapshot.innerMain(TrafExportSnapshot.java:1109) > at > org.trafodion.utility.backuprestore.TrafExportSnapshot.main(TrafExportSnapshot.java:1114) > Caused by: java.lang.ClassNotFoundException: > org.apache.hadoop.hbase.mob.MobUtils > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 5 more > ***[ERROR]: Error while exporting snapshot: > TRAFODION.RACHEL_QA.IDX1_SNAP_20160503-2207. > For more information please check the logs at > /home/trafodion/esgynDBadv-20160501_0830-bin/hbase_utilities/backup_and_restore/logs/run_traf_backup_20160503-2207.log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2079) [3rd party tool-Squirrel] indexes won't show up on objects panel, sql command line works fine
Gao, Rui-Xian created TRAFODION-2079: Summary: [3rd party tool-Squirrel] indexes won't show up on objects panel, sql command line works fine Key: TRAFODION-2079 URL: https://issues.apache.org/jira/browse/TRAFODION-2079 Project: Apache Trafodion Issue Type: Bug Components: client-jdbc-t4 Affects Versions: 2.1-incubating Environment: Squirrel 3.7 server info -- esgynDBadv R2.1, centos 6.7, hbase1.0 cdh5.4.8 Reporter: Gao, Rui-Xian Assignee: Kevin Xu Priority: Minor click table name from objects panel, indexes won't show up. But checking from sql command line, indexes will be returned. >>get indexes on table BTSEL04; Indexes on Table RACHEL_SCH.BTSEL04 === BTSEL04A BTSEL04B -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2078) [3rd party tool-Squirrel] query cancel is not supported
Gao, Rui-Xian created TRAFODION-2078: Summary: [3rd party tool-Squirrel] query cancel is not supported Key: TRAFODION-2078 URL: https://issues.apache.org/jira/browse/TRAFODION-2078 Project: Apache Trafodion Issue Type: Bug Components: client-jdbc-t4 Affects Versions: 2.1-incubating Environment: Squirrel 3.7 server info -- esgynDBadv R2.1, centos6.7, hbase1.0, cdh5.4.8 Reporter: Gao, Rui-Xian Assignee: Kevin Xu can't cancel query from squirrel, syntax error returned -- control query cancel qid 'MXID11073282123331732153682000206U300_483_XX'; Error: *** ERROR[15001] A syntax error occurred at or before: control query cancel qid 'MXID11073282123331732153682000206U300 _483_XX'; ^ (87 characters from start of SQL statement) [2016-06-20 17:21:38] SQLState: 42000 ErrorCode: -15001 Error: *** ERROR[8822] The statement was not prepared. [2016-06-20 17:21:38] SQLState: X08MU ErrorCode: -8822 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-2076) [3rd party tool-Squirrel] call spj will return error though the procedure is actually executed successfully
[ https://issues.apache.org/jira/browse/TRAFODION-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian updated TRAFODION-2076: - Summary: [3rd party tool-Squirrel] call spj will return error though the procedure is actually executed successfully (was: [Squirrel] call spj will return error though the procedure is actually executed successfully ) > [3rd party tool-Squirrel] call spj will return error though the procedure is > actually executed successfully > > > Key: TRAFODION-2076 > URL: https://issues.apache.org/jira/browse/TRAFODION-2076 > Project: Apache Trafodion > Issue Type: Bug > Components: client-jdbc-t4 >Affects Versions: 2.1-incubating > Environment: Squirrel 3.7 > server info -- esgynDBadv R2.1, centos6.7, hbase1.0, cdh5.4.8 >Reporter: Gao, Rui-Xian >Assignee: Kevin Xu >Priority: Minor > > create library qa_dfr file '/home/trafodion/QALibs/SPJ/dfr.jar' > Create procedure createTable() > external name 'TestDDL.createTable' > LIBRARY qa_dfr > language java >NO TRANSACTION REQUIRED > parameter style java; > call createTable(); > Following error will be returned -- > java.lang.ClassCastException: org.trafodion.jdbc.t4.TrafT4Statement cannot be > cast to org.trafodion.jdbc.t4.TrafT4CallableStatement > But actually the table is created successfully. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-2077) [3rd party tool Squirrel] parameter is not support
[ https://issues.apache.org/jira/browse/TRAFODION-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian updated TRAFODION-2077: - Summary: [3rd party tool Squirrel] parameter is not support (was: [Squirrel] parameter is not support ) > [3rd party tool Squirrel] parameter is not support > --- > > Key: TRAFODION-2077 > URL: https://issues.apache.org/jira/browse/TRAFODION-2077 > Project: Apache Trafodion > Issue Type: Bug > Components: client-jdbc-t4 >Affects Versions: 2.1-incubating > Environment: Squirrel 3.7 > server info -- esgynDBadv R2.1, centos 6.7, hbase 1.0, cdh5.4.8 >Reporter: Gao, Rui-Xian >Assignee: Kevin Xu > > set parameter will get syntax error with Squirrel -- > set param ?p1 B; > Error: *** ERROR[15001] A syntax error occurred at or before: > set param ?p1 B; > ^ (9 characters from start of SQL statement) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2077) [Squirrel] parameter is not support
Gao, Rui-Xian created TRAFODION-2077: Summary: [Squirrel] parameter is not support Key: TRAFODION-2077 URL: https://issues.apache.org/jira/browse/TRAFODION-2077 Project: Apache Trafodion Issue Type: Bug Components: client-jdbc-t4 Affects Versions: 2.1-incubating Environment: Squirrel 3.7 server info -- esgynDBadv R2.1, centos 6.7, hbase 1.0, cdh5.4.8 Reporter: Gao, Rui-Xian Assignee: Kevin Xu set parameter will get syntax error with Squirrel -- set param ?p1 B; Error: *** ERROR[15001] A syntax error occurred at or before: set param ?p1 B; ^ (9 characters from start of SQL statement) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2076) [Squirrel] call spj will return error though the procedure is actually executed successfully
Gao, Rui-Xian created TRAFODION-2076: Summary: [Squirrel] call spj will return error though the procedure is actually executed successfully Key: TRAFODION-2076 URL: https://issues.apache.org/jira/browse/TRAFODION-2076 Project: Apache Trafodion Issue Type: Bug Components: client-jdbc-t4 Affects Versions: 2.1-incubating Environment: Squirrel 3.7 server info -- esgynDBadv R2.1, centos6.7, hbase1.0, cdh5.4.8 Reporter: Gao, Rui-Xian Assignee: Kevin Xu Priority: Minor create library qa_dfr file '/home/trafodion/QALibs/SPJ/dfr.jar' Create procedure createTable() external name 'TestDDL.createTable' LIBRARY qa_dfr language java NO TRANSACTION REQUIRED parameter style java; call createTable(); Following error will be returned -- java.lang.ClassCastException: org.trafodion.jdbc.t4.TrafT4Statement cannot be cast to org.trafodion.jdbc.t4.TrafT4CallableStatement But actually the table is created successfully. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2075) [3rd party tool] Squirrel doesn't support prepare/explain/excute, will return syntax error
Gao, Rui-Xian created TRAFODION-2075: Summary: [3rd party tool] Squirrel doesn't support prepare/explain/excute, will return syntax error Key: TRAFODION-2075 URL: https://issues.apache.org/jira/browse/TRAFODION-2075 Project: Apache Trafodion Issue Type: Bug Components: client-jdbc-t4 Affects Versions: 2.1-incubating Environment: squirrel 3.7 server with esgynDBadv R2.1, centos 6.7, hbase1.0 cdh 5.4.8 Reporter: Gao, Rui-Xian Assignee: Kevin Xu Prepare/explain/execute statement is not supported -- prepare xx from select * from btsel02; Error: *** ERROR[15001] A syntax error occurred at or before: prepare xx from select * from btsel02; ^ (22 characters from start of SQL statement) [2016-06-20 17:07:00] SQLState: 42000 ErrorCode: -15001 Error: *** ERROR[8822] The statement was not prepared. [2016-06-20 17:07:00] SQLState: X08MU ErrorCode: -8822 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2071) [3rd party tool] Squirrel return wrong value for interval data
Gao, Rui-Xian created TRAFODION-2071: Summary: [3rd party tool] Squirrel return wrong value for interval data Key: TRAFODION-2071 URL: https://issues.apache.org/jira/browse/TRAFODION-2071 Project: Apache Trafodion Issue Type: Bug Components: client-jdbc-t4 Affects Versions: any Environment: Centos6.7 hbase1.0 CDH5.4.8 Reporter: Gao, Rui-Xian Assignee: Kevin Xu create table ht(h10s4 interval hour(10) to second(4)) no partition; insert into ht values(-interval '11:12:00.1234'hour(10) to second(4)); >From trafci -- >>select * from ht; H10S4 -- -11:12:00.1234 --- 1 row(s) selected. >From Squirrel -- select will return checking with content button, it shows -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2000) trafodion is not picked up as DB__ROOT if security is enabled after install
Gao, Rui-Xian created TRAFODION-2000: Summary: trafodion is not picked up as DB__ROOT if security is enabled after install Key: TRAFODION-2000 URL: https://issues.apache.org/jira/browse/TRAFODION-2000 Project: Apache Trafodion Issue Type: Bug Components: sql-security Affects Versions: 2.1-incubating Environment: centos6.7 hbase1.0 CDH5.4.8 Reporter: Gao, Rui-Xian users for DB__ROOT and DB__ADMIN are same, both are 'trafodion', and DB__ADMIN is picked up for trafodion. SQL>showddl user db__root; REGISTER USER "TRAFODION" AS "DB__ROOT"; --- SQL operation complete. SQL>showddl user db__admin; REGISTER USER "TRAFODION" AS "DB__ADMIN"; --- SQL operation complete. SQL>values(user); (EXPR) DB__ADMIN --- 1 row(s) selected. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1967) [offline backup&restore] trafodion is not started automatically without -o option
Gao, Rui-Xian created TRAFODION-1967:
Summary: [offline backup&restore] trafodion is not started
automatically without -o option
Key: TRAFODION-1967
URL: https://issues.apache.org/jira/browse/TRAFODION-1967
Project: Apache Trafodion
Issue Type: Bug
Components: db-utility-backup-restore
Environment: Centos6.7 hbase1.0 CDH5.4.4
esgynDBadv-0430 build
Reporter: Gao, Rui-Xian
Priority: Minor
During backup, the output is like this --
Starting Trafodion...
sudo: unknown user: Trafodion
sudo: unable to initialize policy plugin
Trafodion not started. Please start Trafodion at your convinience.
trafodion user is hardcoded to 'Trafodion' in backup_restore_functions.sh, we
should use either 'trafodion' or a variable instead.
trafodion_user="Trafodion"
echo "Trafodion user name: $trafodion_user" | tee -a ${log_file}
else
echo "***[ERROR]: Did not find supported Hadoop distribution or $MY_SQROOT
is not set."
return 1
fi
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (TRAFODION-1966) [offline backup&restore] TrafexportSnapshot ran into NoClassDefFoundError on HDP2.4
Gao, Rui-Xian created TRAFODION-1966: Summary: [offline backup&restore] TrafexportSnapshot ran into NoClassDefFoundError on HDP2.4 Key: TRAFODION-1966 URL: https://issues.apache.org/jira/browse/TRAFODION-1966 Project: Apache Trafodion Issue Type: Bug Components: db-utility-backup-restore Environment: centos6.7, hbase1.1 HDP2.4.0 Reporter: Gao, Rui-Xian offline backup on HDP2.4.0 will run into error -- ./run_full_trafodion_backup.sh Exporting TRAFODION.RACHEL_QA.IDX1_SNAP_20160503-2207 ... hbase org.trafodion.utility.backuprestore.TrafExportSnapshot -snapshot TRAFODION.RACHEL_QA.IDX1_SNAP_20160503-2207 -copy-to hdfs://suse-0.novalocal:8020/trafodion_backups/backup_20160503-2207/TRAFODION.RACHEL_QA.IDX1_SNAP_20160503-2207 -mappers 0 -mr-lowlimit-mb 100 2016-05-03 22:09:49,141 INFO [main] backuprestore.TrafExportSnapshot: Trafodion Export Snapshot Utility SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/usr/hdp/2.3.4.7-4/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/usr/hdp/2.3.4.7-4/zookeeper/lib/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory] 2016-05-03 22:09:50,797 INFO [main] backuprestore.TrafExportSnapshot: Copy Snapshot Manifest 2016-05-03 22:09:51,246 INFO [main] backuprestore.TrafExportSnapshot: Loading Snapshot 'TRAFODION.RACHEL_QA.IDX1_SNAP_20160503-2207' hfile list 2016-05-03 22:09:51,487 INFO [main] backuprestore.TrafExportSnapshot: Copy Snapshot Data Files Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/hadoop/hbase/mob/MobUtils at org.trafodion.utility.backuprestore.TrafExportSnapshot.getCopyInputPath(TrafExportSnapshot.java:1052) at org.trafodion.utility.backuprestore.TrafExportSnapshot.run(TrafExportSnapshot.java:983) at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76) at org.trafodion.utility.backuprestore.TrafExportSnapshot.innerMain(TrafExportSnapshot.java:1109) at org.trafodion.utility.backuprestore.TrafExportSnapshot.main(TrafExportSnapshot.java:1114) Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.hbase.mob.MobUtils at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 5 more ***[ERROR]: Error while exporting snapshot: TRAFODION.RACHEL_QA.IDX1_SNAP_20160503-2207. For more information please check the logs at /home/trafodion/esgynDBadv-20160501_0830-bin/hbase_utilities/backup_and_restore/logs/run_traf_backup_20160503-2207.log. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1882) Column Privilege: a user can grant column privilege to others when the user doesn't have privilege on the column
Gao, Rui-Xian created TRAFODION-1882: Summary: Column Privilege: a user can grant column privilege to others when the user doesn't have privilege on the column Key: TRAFODION-1882 URL: https://issues.apache.org/jira/browse/TRAFODION-1882 Project: Apache Trafodion Issue Type: Bug Components: sql-security Reporter: Gao, Rui-Xian dbroot: SQL> grant select(a), delete,insert(a), update(a) on t1 to user2 with grant option; --- SQL operation complete. User2: qi_mxci2> set schema my_sec_test; --- SQL operation complete. qi_mxci2> grant select(a), delete on t1 to user5; --- SQL operation complete. qi_mxci2> grant select(b) on t1 to user5; --- SQL operation complete. user2 doesn’t have select privilege on column b but can grant the privilege to other user. It should get ERROR[4481] here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1806) create view with sequence failed with ERROR[4481] though the user has been granted usage privilege
Gao, Rui-Xian created TRAFODION-1806: Summary: create view with sequence failed with ERROR[4481] though the user has been granted usage privilege Key: TRAFODION-1806 URL: https://issues.apache.org/jira/browse/TRAFODION-1806 Project: Apache Trafodion Issue Type: Bug Components: sql-security Affects Versions: 2.0-incubating Environment: esgynDB: esgynDB-20160107_0900-bin platform: suse11 Reporter: Gao, Rui-Xian create view with sequence failed though the user has been granted usage privileges on the sequence, here is the steps to reproduce -- User dbroot-- create schema myschema; GRANT COMPONENT privilege create_view on sql_operations to testuser1; set schema myschema; create table mytable (a int, b int); insert into mytable values (1,1); create sequence myseq; grant select on mytable to testuser1; grant usage on sequence myseq to testuser1; >>showddl sequence myseq; CREATE SEQUENCE TRAFODION.MYSCHEMA.MYSEQ START WITH 1 /* NEXT AVAILABLE VALUE 1 */ INCREMENT BY 1 MAXVALUE 9223372036854775806 MINVALUE 1 CACHE 25 NO CYCLE LARGEINT ; -- GRANT USAGE ON SEQUENCE TRAFODION.MYSCHEMA.MYSEQ TO DB__ROOT WITH GRANT OPTION; GRANT USAGE ON SEQUENCE TRAFODION.MYSCHEMA.MYSEQ TO TESTUSER1; user testuser1-- set schema myschema; create view myview as select seqnum(myseq) as a from mytable; *** ERROR[4481] The user does not have SELECT privilege on table or view . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1773) internal error to revoke role with restrict option when there is dependent views
Gao, Rui-Xian created TRAFODION-1773: Summary: internal error to revoke role with restrict option when there is dependent views Key: TRAFODION-1773 URL: https://issues.apache.org/jira/browse/TRAFODION-1773 Project: Apache Trafodion Issue Type: Bug Components: sql-security Affects Versions: 2.0-incubating Reporter: Gao, Rui-Xian When processing through the list of dependencies, the code does not assum dependent views. Reproduce steps -- user dbroot-- create role rp_a22role1; create role rp_a22role2; grant role rp_a22role1,rp_a22role2 to testuser3; create shared schema mysch_share; set schema mysch_share; create table a22tab1(a1 int not null primary key, b1 varchar(10)); create table a22tab2(a2 int ,b2 varchar(10))no partition; create view a22v1 as select * from a22tab1; grant select on a22tab2 to rp_a22role1; grant select on a22v1 to rp_a22role2 ; user testuser3-- set schema mysch_share; create view a22v3(col1,col2) as select b1,b2 from a22v1,a22tab2 where a1=a2; user dbroot-- set schema mysch_share; revoke role rp_a22role1 from testuser3 ; *** ERROR[1364] Cannot revoke role RP_A22ROLE1. Object TRAFODION.MY_SCHEMA22.A22V3 depends on privileges on object TRAFODION.MY_SCHEMA22.A22TAB2. [2016-01-14 06:13:11] revoke role rp_a22role2 from testuser3 restrict; // Rachel: should get ERROR[1364] too *** ERROR[1001] An internal error occurred in module ../sqlcomp/PrivMgrRoles.cpp on line 421. DETAILS(Unrecognized PrivType). [2016-01-14 06:13:11] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1759) ODBC: unable to establish connction when running coast unicode tests on linux
Gao, Rui-Xian created TRAFODION-1759: Summary: ODBC: unable to establish connction when running coast unicode tests on linux Key: TRAFODION-1759 URL: https://issues.apache.org/jira/browse/TRAFODION-1759 Project: Apache Trafodion Issue Type: Bug Components: client-odbc-linux Environment: centos6.7, suse11 Reporter: Gao, Rui-Xian when running coast unicode tests on linux platform, output for SQLDriverConnect is incorrect-- SQLDriverConnect(hdbc,NULL,(SQLTCHAR*)ConnectStringIn, InStringLen, (SQLTCHAR*)ConnectStringOut,sizeof(ConnectStringOut),&Conn_tcslengthOut,SQL_DRIVER_NOPROMPT); test log -- Log file 'coast_2016-01-15_05.53.06.UNICODE.GBK.SQLAllocEnv.linux64.TRAF_UTF8.log' initialized. === State: ‚0Û69¥01 Native Error: 0 Error: Ǻ‘`ÁʘBœ«´«‚2à56¨7 ›°] °6«3[‚2à2‚3¯6·Í6©9µèºõ‚2ú16ª4ׂ3‘7…Í6¨5Ìå„|‚3®76§1‚3ü66¨9Ê®> Ìå‚4–5…ÍÒ6©8‚3°3‡t‚2ú56¨9¾ÃÌÞ6ª9»ÜH…Ö‚3Ä8†–‚3–3´«6ª2‚4ú7ÄÅ8ù99Ž4¬9•1“´»»Æô‚2È4‚3•5ÅÒ The InConnectionString is: ="DSN=TRAF_UTF8;UID=trafodion;PWD=traf123;" === Returned ConnectString="^A" === === ***ERROR: Unable to establish an initial connection. No tests can be executed. === -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1758) A user has dbroot role can't grant component privilege to other users/roles
Gao, Rui-Xian created TRAFODION-1758: Summary: A user has dbroot role can't grant component privilege to other users/roles Key: TRAFODION-1758 URL: https://issues.apache.org/jira/browse/TRAFODION-1758 Project: Apache Trafodion Issue Type: Bug Components: sql-security Reporter: Gao, Rui-Xian A user has dbroot role can't grant component privilege to other users/roles Reproduce steps -- User DBROOT -- create role myrole1; register component myusers1; create component privilege created as 'cr' on myusers1 detail 'create users'; create table t2(a int, b int); grant role DB__rootrole to testuser1 ; User testuser1 -- qi_mxci2>grant component privilege created on myusers1 to myrole1 with grant option; *** ERROR[1017] You are not authorized to perform this operation. [2015-12-31 15:07:32] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1728) [MTDCS] ODBC: SQLExecute ran into communication link failure when mtdcs is on
Gao, Rui-Xian created TRAFODION-1728:
Summary: [MTDCS] ODBC: SQLExecute ran into communication link
failure when mtdcs is on
Key: TRAFODION-1728
URL: https://issues.apache.org/jira/browse/TRAFODION-1728
Project: Apache Trafodion
Issue Type: Bug
Components: connectivity-dcs
Affects Versions: 2.0-incubating
Environment: platform: suse11
connect info : 10.10.10.176:23400
esgynDB version :esgynDB-20151223_0900-bin
driver version: 1223
Reporter: Gao, Rui-Xian
With MTDCS on, sqlexecute will run into communication link failure.
reproduce steps --
1. create the table with sqlexecdirect --
create table XE2MNWFUZ1 (IERZCDTBNK char(10),H_ELKF5RLQ varchar(10),JDIV8HVNP3
decimal(10,5),SRCYICXAZ0 numeric(10,5),DOG4S9TXE2 smallint,MNWFUZ1BMP
integer,TUH_ELKF5R real,LQQY7KOGAJ float,BWJDIV8HVN double precision,VPMHA9UJ0Y
date,G6SPJCWBEV time,G3TQAXXDQU timestamp,IWOY8F4SFL bigint,M1KROLHZN7
NUMERIC(19,0),KOGAJBWJDI NUMERIC(19,6),V8HVNP3SRC NUMERIC(128,0),YICXAZ06DO
NUMERIC(128,128),G4S9TXE2MN NUMERIC(10,5) UNSIGNED,WFUZ1BMPTU NUMERIC(18,5)
UNSIGNED,QY7KOGAJBW NUMERIC(30,10) UNSIGNED) NO PARTITION;
2. prepare the sql statement --
insert into XE2MNWFUZ1 values
('uh_["^El}k','F5R:\Lq$*Q',1234.56789,1234.56789,1200,12000,123.45E2,123.45E3,123.45E4,{d
'1993-07-01'},{t '09:45:30'},{ts '1993-08-02
08:44:31.001'},12,1234567890.56789,1234567890.456789,1234567890.456789,0.01234567890123456789,1234.56789,1234567890.56789,12345678901234567890.0123456789);
3. sqlexecute -- error will show up
***ERROR: SQLExecute: Expected: SQL_SUCCESS Actual: SQL_ERROR
File: ../../../../src/coast/coast_unified/src/execute.c Line: 375
State: 08S01
Native Error: 98
Error: [Trafodion ODBC Driver] COMMUNICATION LINK FAILURE. THE SERVER TIMED
OUT OR DISAPPEARED. Platform: UNIX, Transport: TCPIP, Api: SQLEXECUTE2, Error
type: DRIVER, Process: TCP:10.10.10.176/23401:ODBC, Operation: DO_WRITE_READ,
function: RECV, error: 104, error_detail: 0, error text:recv() returned zero
bytes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (TRAFODION-1656) [MTDCS] When MultiThread DCS is on, server-side do nothing while receiving disconnecting request until connection timeout
[ https://issues.apache.org/jira/browse/TRAFODION-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian closed TRAFODION-1656. The fix has been verified on esgynDB-20151223_0900-bin > [MTDCS] When MultiThread DCS is on, server-side do nothing while receiving > disconnecting request until connection timeout > - > > Key: TRAFODION-1656 > URL: https://issues.apache.org/jira/browse/TRAFODION-1656 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-dcs >Affects Versions: 2.0-incubating > Environment: platform: suse11 > connect info : 10.10.10.176:23400 > esgynDB version :esgynDB-20151121_0900-bin > driver version: 1119 >Reporter: Gao, Rui-Xian >Assignee: Kevin Xu >Priority: Critical > Fix For: 2.0-incubating > > > server takes almost 30secs to become available after disconnection. It's > because server actually did nothing after receiving disconnecting request > until connection time out. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (TRAFODION-1665) [MTDCS] connection failed with mtdcs on
[ https://issues.apache.org/jira/browse/TRAFODION-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian closed TRAFODION-1665. The fix has been verified on esgynDB-20151223_0900-bin > [MTDCS] connection failed with mtdcs on > --- > > Key: TRAFODION-1665 > URL: https://issues.apache.org/jira/browse/TRAFODION-1665 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-dcs >Affects Versions: 2.0-incubating > Environment: platform: suse11 > connect info : 10.10.10.176:23400 > esgynDB version :esgynDB-20151121_0900-bin > driver version: 1119 >Reporter: Gao, Rui-Xian >Assignee: Kevin Xu >Priority: Blocker > Fix For: 2.0-incubating > > > connection failed with mtdcs on, and it returns > hostname(TCP:suse-9.novalocal/23404) instead of ip address. >State: S1T00 >Native Error: 0 >Error: [Trafodion ODBC Driver] TIMEOUT EXPIRED. Platform: UNIX, Transport: > TCPIP, Api: SQLCONNECT, Error type: DRIVER, Process: > TCP:suse-9.novalocal/23404:ODBC, Operation: OPEN_SESSION, function: CONNECT, > error: 110, error_detail: 0, error text:Connection timed out. >The InConnectionString is: > ="DSN=TRAF_DSN176_ANSI;UID=trafodion;PWD=traf123;" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1665) [MTDCS] connection failed with mtdcs on
[ https://issues.apache.org/jira/browse/TRAFODION-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian resolved TRAFODION-1665. -- Resolution: Fixed Fix Version/s: 2.0-incubating > [MTDCS] connection failed with mtdcs on > --- > > Key: TRAFODION-1665 > URL: https://issues.apache.org/jira/browse/TRAFODION-1665 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-dcs >Affects Versions: 2.0-incubating > Environment: platform: suse11 > connect info : 10.10.10.176:23400 > esgynDB version :esgynDB-20151121_0900-bin > driver version: 1119 >Reporter: Gao, Rui-Xian >Assignee: Kevin Xu >Priority: Blocker > Fix For: 2.0-incubating > > > connection failed with mtdcs on, and it returns > hostname(TCP:suse-9.novalocal/23404) instead of ip address. >State: S1T00 >Native Error: 0 >Error: [Trafodion ODBC Driver] TIMEOUT EXPIRED. Platform: UNIX, Transport: > TCPIP, Api: SQLCONNECT, Error type: DRIVER, Process: > TCP:suse-9.novalocal/23404:ODBC, Operation: OPEN_SESSION, function: CONNECT, > error: 110, error_detail: 0, error text:Connection timed out. >The InConnectionString is: > ="DSN=TRAF_DSN176_ANSI;UID=trafodion;PWD=traf123;" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (TRAFODION-1656) [MTDCS] When MultiThread DCS is on, server-side do nothing while receiving disconnecting request until connection timeout
[ https://issues.apache.org/jira/browse/TRAFODION-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian resolved TRAFODION-1656. -- Resolution: Fixed Fix Version/s: 2.0-incubating > [MTDCS] When MultiThread DCS is on, server-side do nothing while receiving > disconnecting request until connection timeout > - > > Key: TRAFODION-1656 > URL: https://issues.apache.org/jira/browse/TRAFODION-1656 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-dcs >Affects Versions: 2.0-incubating > Environment: platform: suse11 > connect info : 10.10.10.176:23400 > esgynDB version :esgynDB-20151121_0900-bin > driver version: 1119 >Reporter: Gao, Rui-Xian >Assignee: Kevin Xu >Priority: Critical > Fix For: 2.0-incubating > > > server takes almost 30secs to become available after disconnection. It's > because server actually did nothing after receiving disconnecting request > until connection time out. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (TRAFODION-994) LP Bug: 1420523 - ODBC: Several values returned by SQLColumns are incorrect
[ https://issues.apache.org/jira/browse/TRAFODION-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050895#comment-15050895 ] Gao, Rui-Xian edited comment on TRAFODION-994 at 12/10/15 12:24 PM: API SQLColumns still run into the failure as described in the LP Bug. Test create table =>create table GTN2BSG5FQ (KXE2QSC7HC char(10) CHARACTER SET ISO88591) no partition === SQLColumns: compare results of columns fetched for following column The Column Name is KXE2QSC7HC and column type is char ***ERROR: ColNullable expect: 1 and actual: 2 are not matched ***ERROR: Remark expect: CHARACTER CHARACTER SET ISO88591 and actual: are not matched Number of rows fetched: 1 09:29:32 Test create table =>create table GTN2BSG5FQ (KXE2QSC7HC char(10) CHARACTER SET ISO88591,RMSYLIFAR4 varchar(10) CHARACTER SET ISO88591,E5IPGXAHNB long varchar CHARACTER SET ISO88591,ZQW9LNYDG3 decimal(10,5)) no partition === 09:29:33 SQLColumns: Test #3 SQLColumns: SQLColumns function call executed correctly. SQLColumns: compare results of columns fetched for following column The Column Name is KXE2QSC7HC and column type is char ***ERROR: ColNullable expect: 1 and actual: 2 are not matched ***ERROR: Remark expect: CHARACTER CHARACTER SET ISO88591 and actual: are not matched SQLColumns: compare results of columns fetched for following column The Column Name is RMSYLIFAR4 and column type is varchar ***ERROR: ColNullable expect: 1 and actual: 2 are not matched ***ERROR: Remark expect: VARCHAR CHARACTER SET ISO88591 and actual: are not matched SQLColumns: compare results of columns fetched for following column The Column Name is E5IPGXAHNB and column type is long varchar ***ERROR: ColName expect: E5IPGXAHNB and actual: ZQW9LNYDG3 are not matched ***ERROR: ColDataType expect: 12 and actual: 3 are not matched ***ERROR: ColTypeName expect: VARCHAR and actual: DECIMAL are not matched ***ERROR: ColPrec expect: 2000 and actual: 10 are not matched ***ERROR: ColLen expect: 2000 and actual: 12 are not matched ***ERROR: ColScale expect: 0 and actual: 5 are not matched ***ERROR: ColRadix expect: 0 and actual: 10 are not matched ***ERROR: ColNullable expect: 1 and actual: 2 are not matched ***ERROR: Remark expect: VARCHAR CHARACTER SET ISO88591 and actual: are not matched Number of rows fetched: 3 was (Author: rachelgao): API SQLColumns still run into the failure as described in the LP Bug. Test create table =>create table GTN2BSG5FQ (KXE2QSC7HC char(10) CHARACTER SET ISO88591) no partition === SQLColumns: compare results of columns fetched for following column The Column Name is KXE2QSC7HC and column type is char ***ERROR: ColNullable expect: 1 and actual: 2 are not matched ***ERROR: Remark expect: CHARACTER CHARACTER SET ISO88591 and actual: are not matched Number of rows fetched: 1 Test create table =>create table GTN2BSG5FQ (KXE2QSC7HC char(10) CHARACTER SET ISO88591,RMSYLIFAR4 varchar(10) CHARACTER SET ISO88591,E5IPGXAHNB long varchar CHARACTER SET ISO88591,ZQW9LNYDG3 decimal(10,5)) no partition === 19:18:40 SQLColumns: Test #3 SQLColumns: SQLColumns function call executed correctly. SQLColumns: compare results of columns fetched for following column The Column Name is KXE2QSC7HC and column type is char ***ERROR: ColNullable expect: 1 and actual: 2 are not matched ***ERROR: Remark expect: CHARACTER CHARACTER SET ISO88591 and actual: are not matched SQLColumns: compare results of columns fetched for following column The Column Name is RMSYLIFAR4 and column type is varchar ***ERROR: ColNullable expect: 1 and actual: 2 are not matched ***ERROR: Remark expect: VARCHAR CHARACTER SET ISO88591 and actual: are not matched SQLColumns: compare results of columns fetched for following column The Column Name is E5IPGXAHNB and column type is long varchar ***ERROR: ColName expect: E5IPGXAHNB and actual: ZQW9LNYDG3 are not matched ***ERROR: ColDataType expect: 12 and actual: 3 are not matched ***ERROR: ColTypeName expect: VARCHAR and actual: DECIMAL are not matched ***ERROR: ColPrec expect: 2000 and actual: 10 are not matched ***ERROR: ColLen expect: 2000 and actual: 12 are not matched ***ERROR: ColScale expect: 0 and actual: 5 are not matched ***ERROR: ColRadix expect: 0 and actual: 10 are not matched ***ERROR: ColNullable expect: 1 and actual: 2 are not matched ***ERROR: Remark expect: VARCHAR CHARACTER SET ISO88591 and actual: are not matched Number of rows fetched: 3 > LP Bug: 1420523 - ODBC: Several values returned by SQLColumns are incorrect > --- > >
[jira] [Updated] (TRAFODION-994) LP Bug: 1420523 - ODBC: Several values returned by SQLColumns are incorrect
[ https://issues.apache.org/jira/browse/TRAFODION-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian updated TRAFODION-994: Description: Below are the failures in SQLColumn API testing: 1. In the resultset returned by SQLColumn API, value of column ColNullable is 2 rather than 1, column REMARK is empty. Test create table =>create table GTN2BSG5FQ (KXE2QSC7HC char(10) CHARACTER SET ISO88591) no partition === SQLColumns: compare results of columns fetched for following column The Column Name is KXE2QSC7HC and column type is char ***ERROR: ColNullable expect: 1 and actual: 2 are not matched ***ERROR: Remark expect: CHARACTER CHARACTER SET ISO88591 and actual: are not matched Number of rows fetched: 1 2. Somehow if the table has more than 3 columns, the 3rd column seems got lost as nothing regarding the 3rd column is returned in the resultset. For test case below, 3rd column E5IPGXAHNB has no info in the resultset. 19:18:38 Test create table =>create table GTN2BSG5FQ (KXE2QSC7HC char(10) CHARACTER SET ISO88591,RMSYLIFAR4 varchar(10) CHARACTER SET ISO88591,E5IPGXAHNB long varchar CHARACTER SET ISO88591,ZQW9LNYDG3 decimal(10,5)) no partition === 19:18:40 SQLColumns: Test #3 SQLColumns: SQLColumns function call executed correctly. SQLColumns: compare results of columns fetched for following column The Column Name is KXE2QSC7HC and column type is char ***ERROR: ColNullable expect: 1 and actual: 2 are not matched ***ERROR: Remark expect: CHARACTER CHARACTER SET ISO88591 and actual: are not matched SQLColumns: compare results of columns fetched for following column The Column Name is RMSYLIFAR4 and column type is varchar ***ERROR: ColNullable expect: 1 and actual: 2 are not matched ***ERROR: Remark expect: VARCHAR CHARACTER SET ISO88591 and actual: are not matched SQLColumns: compare results of columns fetched for following column The Column Name is E5IPGXAHNB and column type is long varchar ***ERROR: ColName expect: E5IPGXAHNB and actual: ZQW9LNYDG3 are not matched ***ERROR: ColDataType expect: 12 and actual: 3 are not matched ***ERROR: ColTypeName expect: VARCHAR and actual: DECIMAL are not matched ***ERROR: ColPrec expect: 2000 and actual: 10 are not matched ***ERROR: ColLen expect: 2000 and actual: 12 are not matched ***ERROR: ColScale expect: 0 and actual: 5 are not matched ***ERROR: ColRadix expect: 0 and actual: 10 are not matched ***ERROR: ColNullable expect: 1 and actual: 2 are not matched ***ERROR: Remark expect: VARCHAR CHARACTER SET ISO88591 and actual: are not matched Number of rows fetched: 3 was: Below are the failures in SQLColumn API testing: 1. In the resultset returned by SQLColumn API, value of column ColNullable is 2 rather than 1, column REMARK is empty. Test create table =>create table GTN2BSG5FQ (KXE2QSC7HC char(10) CHARACTER SET ISO88591) no partition === SQLColumns: compare results of columns fetched for following column The Column Name is KXE2QSC7HC and column type is char ***ERROR: ColNullable expect: 1 and actual: 2 are not matched ***ERROR: Remark expect: CHARACTER CHARACTER SET ISO88591 and actual: are not matched Number of rows fetched: 1 2. Somehow if the table has more than 3 columns, the 3rd column seems got lost as nothing regarding the 3rd column is returned in the resultset. For test case below, 3rd column E5IPGXAHNB has no info in the resultset. 19:18:38 > LP Bug: 1420523 - ODBC: Several values returned by SQLColumns are incorrect > --- > > Key: TRAFODION-994 > URL: https://issues.apache.org/jira/browse/TRAFODION-994 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-general, sql-cmu >Reporter: JiepingZhang >Assignee: Sandhya Sundaresan >Priority: Critical > Fix For: 2.0-incubating > > > Below are the failures in SQLColumn API testing: > 1. In the resultset returned by SQLColumn API, value of column ColNullable is > 2 rather than 1, column REMARK is empty. > Test create table =>create table GTN2BSG5FQ (KXE2QSC7HC char(10) CHARACTER > SET ISO88591) no partition > === > SQLColumns: compare results of columns fetched for following column > The Column Name is KXE2QSC7HC and column type is char > ***ERROR: ColNullable expect: 1 and actual: 2 are not matched > ***ERROR: Remark expect: CHARACTER CHARACTER SET ISO88591 and actual: are > not matched > Number of rows fetched: 1 > 2. Somehow if the table has more than 3 columns, the 3rd column seems got > lost as nothing regarding the 3rd col
[jira] [Updated] (TRAFODION-994) LP Bug: 1420523 - ODBC: Several values returned by SQLColumns are incorrect
[ https://issues.apache.org/jira/browse/TRAFODION-994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian updated TRAFODION-994: Description: Below are the failures in SQLColumn API testing: 1. In the resultset returned by SQLColumn API, value of column ColNullable is 2 rather than 1, column REMARK is empty. Test create table =>create table GTN2BSG5FQ (KXE2QSC7HC char(10) CHARACTER SET ISO88591) no partition === SQLColumns: compare results of columns fetched for following column The Column Name is KXE2QSC7HC and column type is char ***ERROR: ColNullable expect: 1 and actual: 2 are not matched ***ERROR: Remark expect: CHARACTER CHARACTER SET ISO88591 and actual: are not matched Number of rows fetched: 1 2. Somehow if the table has more than 3 columns, the 3rd column seems got lost as nothing regarding the 3rd column is returned in the resultset. For test case below, 3rd column E5IPGXAHNB has no info in the resultset. 19:18:38 was: Below are the failures in SQLColumn API testing: 1. In the resultset returned by SQLColumn API, value of column ColNullable is 2 rather than 1, column REMARK is empty. Test create table =>create table GTN2BSG5FQ (KXE2QSC7HC char(10) CHARACTER SET ISO88591) no partition === SQLColumns: compare results of columns fetched for following column The Column Name is KXE2QSC7HC and column type is char ***ERROR: ColNullable expect: 1 and actual: 2 are not matched ***ERROR: Remark expect: CHARACTER CHARACTER SET ISO88591 and actual: are not matched Number of rows fetched: 1 2. Somehow if the table has more than 3 columns, the 3rd column seems got lost as nothing regarding the 3rd column is returned in the resultset. For test case below, 3rd column E5IPGXAHNB has no info in the resultset. 19:18:38 Test create table =>create table GTN2BSG5FQ (KXE2QSC7HC char(10) CHARACTER SET ISO88591,RMSYLIFAR4 varchar(10) CHARACTER SET ISO88591,E5IPGXAHNB long varchar CHARACTER SET ISO88591,ZQW9LNYDG3 decimal(10,5)) no partition === 19:18:40 SQLColumns: Test #3 SQLColumns: SQLColumns function call executed correctly. SQLColumns: compare results of columns fetched for following column The Column Name is KXE2QSC7HC and column type is char ***ERROR: ColNullable expect: 1 and actual: 2 are not matched ***ERROR: Remark expect: CHARACTER CHARACTER SET ISO88591 and actual: are not matched SQLColumns: compare results of columns fetched for following column The Column Name is RMSYLIFAR4 and column type is varchar ***ERROR: ColNullable expect: 1 and actual: 2 are not matched ***ERROR: Remark expect: VARCHAR CHARACTER SET ISO88591 and actual: are not matched SQLColumns: compare results of columns fetched for following column The Column Name is E5IPGXAHNB and column type is long varchar ***ERROR: ColName expect: E5IPGXAHNB and actual: ZQW9LNYDG3 are not matched ***ERROR: ColDataType expect: 12 and actual: 3 are not matched ***ERROR: ColTypeName expect: VARCHAR and actual: DECIMAL are not matched ***ERROR: ColPrec expect: 2000 and actual: 10 are not matched ***ERROR: ColLen expect: 2000 and actual: 12 are not matched ***ERROR: ColScale expect: 0 and actual: 5 are not matched ***ERROR: ColRadix expect: 0 and actual: 10 are not matched ***ERROR: ColNullable expect: 1 and actual: 2 are not matched ***ERROR: Remark expect: VARCHAR CHARACTER SET ISO88591 and actual: are not matched Number of rows fetched: 3 > LP Bug: 1420523 - ODBC: Several values returned by SQLColumns are incorrect > --- > > Key: TRAFODION-994 > URL: https://issues.apache.org/jira/browse/TRAFODION-994 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-general, sql-cmu >Reporter: JiepingZhang >Assignee: Sandhya Sundaresan >Priority: Critical > Fix For: 2.0-incubating > > > Below are the failures in SQLColumn API testing: > 1. In the resultset returned by SQLColumn API, value of column ColNullable is > 2 rather than 1, column REMARK is empty. > Test create table =>create table GTN2BSG5FQ (KXE2QSC7HC char(10) CHARACTER > SET ISO88591) no partition > === > SQLColumns: compare results of columns fetched for following column > The Column Name is KXE2QSC7HC and column type is char > ***ERROR: ColNullable expect: 1 and actual: 2 are not matched > ***ERROR: Remark expect: CHARACTER CHARACTER SET ISO88591 and actual: are > not matched > Number of rows fetched: 1 > 2. Somehow if the table has more than 3 columns, the 3rd column seems got > lost as nothing regarding the 3
[jira] [Commented] (TRAFODION-994) LP Bug: 1420523 - ODBC: Several values returned by SQLColumns are incorrect
[ https://issues.apache.org/jira/browse/TRAFODION-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050895#comment-15050895 ] Gao, Rui-Xian commented on TRAFODION-994: - API SQLColumns still run into the failure as described in the LP Bug. Test create table =>create table GTN2BSG5FQ (KXE2QSC7HC char(10) CHARACTER SET ISO88591) no partition === SQLColumns: compare results of columns fetched for following column The Column Name is KXE2QSC7HC and column type is char ***ERROR: ColNullable expect: 1 and actual: 2 are not matched ***ERROR: Remark expect: CHARACTER CHARACTER SET ISO88591 and actual: are not matched Number of rows fetched: 1 Test create table =>create table GTN2BSG5FQ (KXE2QSC7HC char(10) CHARACTER SET ISO88591,RMSYLIFAR4 varchar(10) CHARACTER SET ISO88591,E5IPGXAHNB long varchar CHARACTER SET ISO88591,ZQW9LNYDG3 decimal(10,5)) no partition === 19:18:40 SQLColumns: Test #3 SQLColumns: SQLColumns function call executed correctly. SQLColumns: compare results of columns fetched for following column The Column Name is KXE2QSC7HC and column type is char ***ERROR: ColNullable expect: 1 and actual: 2 are not matched ***ERROR: Remark expect: CHARACTER CHARACTER SET ISO88591 and actual: are not matched SQLColumns: compare results of columns fetched for following column The Column Name is RMSYLIFAR4 and column type is varchar ***ERROR: ColNullable expect: 1 and actual: 2 are not matched ***ERROR: Remark expect: VARCHAR CHARACTER SET ISO88591 and actual: are not matched SQLColumns: compare results of columns fetched for following column The Column Name is E5IPGXAHNB and column type is long varchar ***ERROR: ColName expect: E5IPGXAHNB and actual: ZQW9LNYDG3 are not matched ***ERROR: ColDataType expect: 12 and actual: 3 are not matched ***ERROR: ColTypeName expect: VARCHAR and actual: DECIMAL are not matched ***ERROR: ColPrec expect: 2000 and actual: 10 are not matched ***ERROR: ColLen expect: 2000 and actual: 12 are not matched ***ERROR: ColScale expect: 0 and actual: 5 are not matched ***ERROR: ColRadix expect: 0 and actual: 10 are not matched ***ERROR: ColNullable expect: 1 and actual: 2 are not matched ***ERROR: Remark expect: VARCHAR CHARACTER SET ISO88591 and actual: are not matched Number of rows fetched: 3 > LP Bug: 1420523 - ODBC: Several values returned by SQLColumns are incorrect > --- > > Key: TRAFODION-994 > URL: https://issues.apache.org/jira/browse/TRAFODION-994 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-general, sql-cmu >Reporter: JiepingZhang >Assignee: Sandhya Sundaresan >Priority: Critical > Fix For: 2.0-incubating > > > Below are the failures in SQLColumn API testing: > 1. In the resultset returned by SQLColumn API, value of column ColNullable is > 2 rather than 1, column REMARK is empty. > Test create table =>create table GTN2BSG5FQ (KXE2QSC7HC char(10) CHARACTER > SET ISO88591) no partition > === > SQLColumns: compare results of columns fetched for following column > The Column Name is KXE2QSC7HC and column type is char > ***ERROR: ColNullable expect: 1 and actual: 2 are not matched > ***ERROR: Remark expect: CHARACTER CHARACTER SET ISO88591 and actual: are > not matched > Number of rows fetched: 1 > 2. Somehow if the table has more than 3 columns, the 3rd column seems got > lost as nothing regarding the 3rd column is returned in the resultset. For > test case below, 3rd column E5IPGXAHNB has no info in the resultset. > 19:18:38 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1698) ODBC: trafodion doesn't support API SQLForeignKeys
Gao, Rui-Xian created TRAFODION-1698: Summary: ODBC: trafodion doesn't support API SQLForeignKeys Key: TRAFODION-1698 URL: https://issues.apache.org/jira/browse/TRAFODION-1698 Project: Apache Trafodion Issue Type: Improvement Components: connectivity-dcs Affects Versions: 1.0 (pre-incubation), 2.0-incubating Environment: client platform: windows7, windows8, centos6.7, suse11 Reporter: Gao, Rui-Xian API SQLForeignKeys returned error that the API type is not supported. To reproduce -- create table TDV5WYPAQVA (V5WYPAQVJJ char(10) CHARACTER SET ucs2 not null not droppable, PDO_6ERNAZ char(10) CHARACTER SET ucs2, primary key(V5WYPAQVJJ)) NO PARTITION create table TDV5WYPAQVB (LRO90EZUSH char(10) CHARACTER SET ucs2 not null not droppable, IKLI4HXBSC char(10) CHARACTER SET ucs2, primary key(LRO90EZUSH), foreign key (IKLI4HXBSC) references TDV5WYPAQVA(V5WYPAQVJJ)) NO PARTITION create table TDV5WYPAQVC (BG1TCQFK2X char(10) CHARACTER SET ucs2 not null not droppable, W8UMGMNY7F char(10) CHARACTER SET ucs2, primary key(BG1TCQFK2X), foreign key (W8UMGMNY7F) references TDV5WYPAQVB(LRO90EZUSH)) NO PARTITION == SQLForeignKeys(hstmt, TRAFODION, 9, RACHEL_ODBCTEST_L, 17, TDV5WYPAQVA, 11, TRAFODION, 9, RACHEL_ODBCTEST_L, 17, , 0) 10:46:03 ***ERROR: SQLForeignKeys: Expected: SQL_SUCCESS Actual: SQL_ERROR File: ../../../../src/coast/coast_unified/src/forkeys.c Line: 302 State: HYC00 Native Error: 1 Error: [Trafodion ODBC Driver][DCS Server] OPTIONAL FEATURE NOT IMPLEMENTED.UNSUPPORTED INPUT SMD API TYPE -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1696) drop authorization doesn't drop all roles, and create role will run into internal error
[ https://issues.apache.org/jira/browse/TRAFODION-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian updated TRAFODION-1696: - Description: >>initialize authorization,drop; --- SQL operation complete. >>get roles; Roles = A19ROLE1 DB__HBASEROLE DB__HIVEROLE DB__ROOTROLE GROBJ_A37ROLE1 GROBJ_A37ROLE2 GROBJ_A42ROLE1 GROBJ_A47ROLE1 GROBJ_A47ROLE2 QAUSER_1012345678201234567830123456784012345678501234567860123456787012345678801234567890123456710012345671101234567120123456129 RER_A18ROLE2 RER_A19ROLE1 RER_A20ROLE1 RER_A20ROLE2 RER_A24ROLE2 >>create role auth_role1; *** ERROR[8448] Unable to access Hbase interface. Call to ExpHbaseInterface::checkAndInsertRow returned error HBASE_ACCESS_ERROR(-706). Cause: org.apache.hadoop.hbase.TableNotFoundException: TRAFODION._PRIVMGR_MD_.ROLE_USAGE org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegionInMeta(ConnectionManager.java:1298) org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(ConnectionManager.java:1126) org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(ConnectionManager.java:1110) org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(ConnectionManager.java:1067) org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.getRegionLocation(ConnectionManager.java:902) org.apache.hadoop.hbase.client.HTable.getRegionLocation(HTable.java:558) org.apache.hadoop.hbase.client.transactional.TransactionalTable.getRegionLocation(TransactionalTable.java:907) org.apache.hadoop.hbase.client.transactional.RMInterface.registerTransaction(RMInterface.java:368) org.apache.hadoop.hbase.client.transactional.RMInterface.registerTransaction(RMInterface.java:410) org.apache.hadoop.hbase.client.transactional.RMInterface.checkAndPut(RMInterface.java:727) org.trafodion.sql.HTableClient.putRow(HTableClient.java:1204) org.trafodion.sql.HBaseClient.insertRow(HBaseClient.java:1505) . *** ERROR[1001] An internal error occurred in module ../sqlcomp/CmpSeabaseDDLauth.cpp on line 1385. DETAILS(Unable to grant role to role administrator). was: >>initialize authorization,drop; --- SQL operation complete. Roles = A19ROLE1 DB__HBASEROLE DB__HIVEROLE DB__ROOTROLE GROBJ_A37ROLE1 GROBJ_A37ROLE2 GROBJ_A42ROLE1 GROBJ_A47ROLE1 GROBJ_A47ROLE2 QAUSER_1012345678201234567830123456784012345678501234567860123456787012345678801234567890123456710012345671101234567120123456129 RER_A18ROLE2 RER_A19ROLE1 RER_A20ROLE1 RER_A20ROLE2 RER_A24ROLE2 >>create role auth_role1; *** ERROR[8448] Unable to access Hbase interface. Call to ExpHbaseInterface::checkAndInsertRow returned error HBASE_ACCESS_ERROR(-706). Cause: org.apache.hadoop.hbase.TableNotFoundException: TRAFODION._PRIVMGR_MD_.ROLE_USAGE org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegionInMeta(ConnectionManager.java:1298) org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(ConnectionManager.java:1126) org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(ConnectionManager.java:1110) org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(ConnectionManager.java:1067) org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.getRegionLocation(ConnectionManager.java:902) org.apache.hadoop.hbase.client.HTable.getRegionLocation(HTable.java:558) org.apache.hadoop.hbase.client.transactional.TransactionalTable.getRegionLocation(TransactionalTable.java:907) org.apache.hadoop.hbase.client.transactional.RMInterface.registerTransaction(RMInterface.java:368) org.apache.hadoop.hbase.client.transactional.RMInterface.registerTransaction(RMInterface.java:410) org.apache.hadoop.hbase.client.transactional.RMInterface.checkAndPut(RMInterface.java:727) org.trafodion.sql.HTableClient.putRow(HTableClient.java:1204) org.trafodion.sql.HBaseClient.insertRow(HBaseClient.java:1505) . *** ERROR[1001] An internal error occurred in module ../sqlcomp/CmpSeabaseDDLauth.cpp on line 1385. DETAILS(Unable to grant role to role administrator). > drop authorization doesn't drop all roles, and create role will run into > internal error > --- > > Key: TRAFODION-1696 > URL: https://issues.apache.org/jira/browse/TRAFODION-1696 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-security >Affects Versions: 2.0-incubating > Environment: os: suse11 > esgynDB version: esgynDB-20151119_0900-bin >Reporter: Gao, Rui-Xian > > >>initialize authorization,drop; > > --- SQL operation complete. > >>get roles; > Roles > = > A19ROLE1 > DB__HBASEROLE > DB__HIVEROLE > DB__ROOTROLE > GROBJ_A37ROLE1
[jira] [Created] (TRAFODION-1696) drop authorization doesn't drop all roles, and create role will run into internal error
Gao, Rui-Xian created TRAFODION-1696: Summary: drop authorization doesn't drop all roles, and create role will run into internal error Key: TRAFODION-1696 URL: https://issues.apache.org/jira/browse/TRAFODION-1696 Project: Apache Trafodion Issue Type: Bug Components: sql-security Affects Versions: 2.0-incubating Environment: os: suse11 esgynDB version: esgynDB-20151119_0900-bin Reporter: Gao, Rui-Xian >>initialize authorization,drop; --- SQL operation complete. Roles = A19ROLE1 DB__HBASEROLE DB__HIVEROLE DB__ROOTROLE GROBJ_A37ROLE1 GROBJ_A37ROLE2 GROBJ_A42ROLE1 GROBJ_A47ROLE1 GROBJ_A47ROLE2 QAUSER_1012345678201234567830123456784012345678501234567860123456787012345678801234567890123456710012345671101234567120123456129 RER_A18ROLE2 RER_A19ROLE1 RER_A20ROLE1 RER_A20ROLE2 RER_A24ROLE2 >>create role auth_role1; *** ERROR[8448] Unable to access Hbase interface. Call to ExpHbaseInterface::checkAndInsertRow returned error HBASE_ACCESS_ERROR(-706). Cause: org.apache.hadoop.hbase.TableNotFoundException: TRAFODION._PRIVMGR_MD_.ROLE_USAGE org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegionInMeta(ConnectionManager.java:1298) org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(ConnectionManager.java:1126) org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(ConnectionManager.java:1110) org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.locateRegion(ConnectionManager.java:1067) org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.getRegionLocation(ConnectionManager.java:902) org.apache.hadoop.hbase.client.HTable.getRegionLocation(HTable.java:558) org.apache.hadoop.hbase.client.transactional.TransactionalTable.getRegionLocation(TransactionalTable.java:907) org.apache.hadoop.hbase.client.transactional.RMInterface.registerTransaction(RMInterface.java:368) org.apache.hadoop.hbase.client.transactional.RMInterface.registerTransaction(RMInterface.java:410) org.apache.hadoop.hbase.client.transactional.RMInterface.checkAndPut(RMInterface.java:727) org.trafodion.sql.HTableClient.putRow(HTableClient.java:1204) org.trafodion.sql.HBaseClient.insertRow(HBaseClient.java:1505) . *** ERROR[1001] An internal error occurred in module ../sqlcomp/CmpSeabaseDDLauth.cpp on line 1385. DETAILS(Unable to grant role to role administrator). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (TRAFODION-1644) 'initialize trafodion,drop' doesn't drop _DTM_ objects
[ https://issues.apache.org/jira/browse/TRAFODION-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian closed TRAFODION-1644. Resolution: Won't Fix > 'initialize trafodion,drop' doesn't drop _DTM_ objects > -- > > Key: TRAFODION-1644 > URL: https://issues.apache.org/jira/browse/TRAFODION-1644 > Project: Apache Trafodion > Issue Type: Bug > Components: db-utility-backup-restore, sql-general >Affects Versions: 2.0-incubating >Reporter: Gao, Rui-Xian >Assignee: Suresh Subbiah >Priority: Minor > > currently, 'initialize trafodion, drop' doesn't drop all TRAFODION objects, > we need cleanup _DTM_ objects from hbase shell. > >>initialize trafodion, drop; > --- SQL operation complete. > hbase(main):002:0> list 'TRAFODION.*' > TABLE > TRAFODION._DTM_.TLOG0_CONTROL_POINT > TRAFODION._DTM_.TLOG0_LOG_0 > TRAFODION._DTM_.TLOG0_LOG_1 > TRAFODION._DTM_.TLOG0_LOG_2 > TRAFODION._DTM_.TLOG0_LOG_3 > TRAFODION._DTM_.TLOG0_LOG_4 > TRAFODION._DTM_.TLOG0_LOG_5 > TRAFODION._DTM_.TLOG0_LOG_6 > TRAFODION._DTM_.TLOG0_LOG_7 > TRAFODION._DTM_.TLOG0_LOG_8 > TRAFODION._DTM_.TLOG0_LOG_9 > TRAFODION._DTM_.TLOG0_LOG_a > TRAFODION._DTM_.TLOG0_LOG_b > TRAFODION._DTM_.TLOG0_LOG_c > TRAFODION._DTM_.TLOG0_LOG_d > TRAFODION._DTM_.TLOG0_LOG_e > TRAFODION._DTM_.TLOG0_LOG_f > TRAFODION._DTM_.TLOG1_CONTROL_POINT > TRAFODION._DTM_.TLOG1_LOG_0 > TRAFODION._DTM_.TLOG1_LOG_1 > TRAFODION._DTM_.TLOG1_LOG_2 > TRAFODION._DTM_.TLOG1_LOG_3 > TRAFODION._DTM_.TLOG1_LOG_4 > TRAFODION._DTM_.TLOG1_LOG_5 > TRAFODION._DTM_.TLOG1_LOG_6 > TRAFODION._DTM_.TLOG1_LOG_7 > TRAFODION._DTM_.TLOG1_LOG_8 > TRAFODION._DTM_.TLOG1_LOG_9 > TRAFODION._DTM_.TLOG1_LOG_a > TRAFODION._DTM_.TLOG1_LOG_b > TRAFODION._DTM_.TLOG1_LOG_c > TRAFODION._DTM_.TLOG1_LOG_d > TRAFODION._DTM_.TLOG1_LOG_e > TRAFODION._DTM_.TLOG1_LOG_f > TRAFODION._DTM_.TLOG2_CONTROL_POINT > TRAFODION._DTM_.TLOG2_LOG_0 > TRAFODION._DTM_.TLOG2_LOG_1 > TRAFODION._DTM_.TLOG2_LOG_2 > TRAFODION._DTM_.TLOG2_LOG_3 > TRAFODION._DTM_.TLOG2_LOG_4 > TRAFODION._DTM_.TLOG2_LOG_5 > TRAFODION._DTM_.TLOG2_LOG_6 > TRAFODION._DTM_.TLOG2_LOG_7 > TRAFODION._DTM_.TLOG2_LOG_8 > TRAFODION._DTM_.TLOG2_LOG_9 > TRAFODION._DTM_.TLOG2_LOG_a > TRAFODION._DTM_.TLOG2_LOG_b > TRAFODION._DTM_.TLOG2_LOG_c > TRAFODION._DTM_.TLOG2_LOG_d > TRAFODION._DTM_.TLOG2_LOG_e > TRAFODION._DTM_.TLOG2_LOG_f > 51 row(s) in 0.0320 seconds > => ["TRAFODION._DTM_.TLOG0_CONTROL_POINT", "TRAFODION._DTM_.TLOG0_LOG_0", > "TRAFODION._DTM_.TLOG0_LOG_1", "TRAFODION._DTM_.TLOG0_LOG_2", > "TRAFODION._DTM_.TLOG0_LOG_3", "TRAFODION._DTM_.TLOG0_LOG_4", > "TRAFODION._DTM_.TLOG0_LOG_5", "TRAFODION._DTM_.TLOG0_LOG_6", > "TRAFODION._DTM_.TLOG0_LOG_7", "TRAFODION._DTM_.TLOG0_LOG_8", > "TRAFODION._DTM_.TLOG0_LOG_9", "TRAFODION._DTM_.TLOG0_LOG_a", > "TRAFODION._DTM_.TLOG0_LOG_b", "TRAFODION._DTM_.TLOG0_LOG_c", > "TRAFODION._DTM_.TLOG0_LOG_d", "TRAFODION._DTM_.TLOG0_LOG_e", > "TRAFODION._DTM_.TLOG0_LOG_f", "TRAFODION._DTM_.TLOG1_CONTROL_POINT", > "TRAFODION._DTM_.TLOG1_LOG_0", "TRAFODION._DTM_.TLOG1_LOG_1", > "TRAFODION._DTM_.TLOG1_LOG_2", "TRAFODION._DTM_.TLOG1_LOG_3", > "TRAFODION._DTM_.TLOG1_LOG_4", "TRAFODION._DTM_.TLOG1_LOG_5", > "TRAFODION._DTM_.TLOG1_LOG_6", "TRAFODION._DTM_.TLOG1_LOG_7", > "TRAFODION._DTM_.TLOG1_LOG_8", "TRAFODION._DTM_.TLOG1_LOG_9", > "TRAFODION._DTM_.TLOG1_LOG_a", "TRAFODION._DTM_.TLOG1_LOG_b", > "TRAFODION._DTM_.TLOG1_LOG_c", "TRAFODION._DTM_.TLOG1_LOG_d", > "TRAFODION._DTM_.TLOG1_LOG_e", "TRAFODION._DTM_.TLOG1_LOG_f", > "TRAFODION._DTM_.TLOG2_CONTROL_POINT", "TRAFODION._DTM_.TLOG2_LOG_0", > "TRAFODION._DTM_.TLOG2_LOG_1", "TRAFODION._DTM_.TLOG2_LOG_2", > "TRAFODION._DTM_.TLOG2_LOG_3", "TRAFODION._DTM_.TLOG2_LOG_4", > "TRAFODION._DTM_.TLOG2_LOG_5", "TRAFODION._DTM_.TLOG2_LOG_6", > "TRAFODION._DTM_.TLOG2_LOG_7", "TRAFODION._DTM_.TLOG2_LOG_8", > "TRAFODION._DTM_.TLOG2_LOG_9", "TRAFODION._DTM_.TLOG2_LOG_a", > "TRAFODION._DTM_.TLOG2_LOG_b", "TRAFODION._DTM_.TLOG2_LOG_c", > "TRAFODION._DTM_.TLOG2_LOG_d", "TRAFODION._DTM_.TLOG2_LOG_e", > "TRAFODION._DTM_.TLOG2_LOG_f"] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1686) [MTDCS] ODBC: SQLParamdata ran into error for date type columns
Gao, Rui-Xian created TRAFODION-1686: Summary: [MTDCS] ODBC: SQLParamdata ran into error for date type columns Key: TRAFODION-1686 URL: https://issues.apache.org/jira/browse/TRAFODION-1686 Project: Apache Trafodion Issue Type: Bug Components: connectivity-dcs Affects Versions: 2.0-incubating Environment: platform: suse11 connect info : 10.10.10.176:23400 esgynDB version :esgynDB-20151121_0900-bin driver version: 1119 Reporter: Gao, Rui-Xian When MTDCS is on, sqlparamdata will get error for date type columns. Reproducible code -- SQLAllocStmt(hdbc, &hstmt); SQLExecDirect(hstmt,(SQLTCHAR*)InsStr,SQL_NTS); SQLPrepare(hstmt,(SQLTCHAR*)InsTab1,SQL_NTS); SQLBindParameter(hstmt,(SWORD)(j+1),ParamType,CDataValueTOSQL1[i].CType, CDataArgToSQL1.SQLType[j],CDataValueTOSQL1[i].ColPrec[j], CDataValueTOSQL1[i].ColScale[j],NULL,NAME_LEN, &InValue); SQLExecute(hstmt); SQLParamData(hstmt,&pToken); ***ERROR: SQLParamData failed State: 22003 Native Error: 0 Error: [Trafodion ODBC Driver] NUMERIC VALUE OUT OF RANGE. Row: 1 Column: 10 The actual statement the above apis are running -- 1. create table CREATE TABLE OSD28DL_Z1(SK_PE9ETUK CHAR(10) CHARACTER SET ISO88591,JQJAAFUO4B VARCHAR(10) CHARACTER SET ISO88591,O4BQVTFXOS DECIMAL(10,5),D28DL_Z1HP NUMERIC(10,5),EK7XIK0RPU SMALLINT,LR5GT3YMEY INTEGER,CWBGHNZMVN REAL,SWI9CJQJAA FLOAT,FUO4BQVTFX DOUBLE PRECISION,QJZVF2ABMN DATE,QIGXW1HCDO TIME,VOWHPAC75R TIMESTAMP,L6DYIXRZJ3 LONG VARCHAR CHARACTER SET ISO88591,L0MSNYUGTF BIGINT,B8SK_PE9ET CHAR(10) CHARACTER SET UCS2,UKQJZVF2AB VARCHAR(10) CHARACTER SET UCS2,MN4QIGXW1H LONG VARCHAR CHARACTER SET UCS2,CDOVOWHPAC NUMERIC(19,0),RL6DYIXRZJ NUMERIC(19,6),QVTFXOSD28 NUMERIC(128,0),DL_Z1HPEK7 NUMERIC(128,128),XIK0RPULR5 NUMERIC(128,64),GT3YMEYCWB NUMERIC(10,5) UNSIGNED,GHNZMVN6SW NUMERIC(18,5) UNSIGNED,I9CJQJAAFU NUMERIC(30,10) UNSIGNED) NO PARTITION 2. prepare INSERT INTO OSD28DL_Z1 (SK_PE9ETUK,JQJAAFUO4B,O4BQVTFXOS,D28DL_Z1HP,EK7XIK0RPU,LR5GT3YMEY,CWBGHNZMVN,SWI9CJQJAA,FUO4BQVTFX,QJZVF2ABMN,QIGXW1HCDO,VOWHPAC75R,L6DYIXRZJ3,L0MSNYUGTF,B8SK_PE9ET,UKQJZVF2AB,MN4QIGXW1H,CDOVOWHPAC,RL6DYIXRZJ,QVTFXOSD28,DL_Z1HPEK7,XIK0RPULR5,GT3YMEYCWB,GHNZMVN6SW,I9CJQJAAFU) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) 3. bindparameter SQLBindParameter, Column #1, SQL_C_TCHAR to SQL_CHAR. SQLBindParameter, Column #2, SQL_C_TCHAR to SQL_VARCHAR. SQLBindParameter, Column #3, SQL_C_TCHAR to SQL_DECIMAL. SQLBindParameter, Column #4, SQL_C_TCHAR to SQL_NUMERIC. SQLBindParameter, Column #5, SQL_C_TCHAR to SQL_SMALLINT. SQLBindParameter, Column #6, SQL_C_TCHAR to SQL_INTEGER. SQLBindParameter, Column #7, SQL_C_TCHAR to SQL_REAL. SQLBindParameter, Column #8, SQL_C_TCHAR to SQL_FLOAT. SQLBindParameter, Column #9, SQL_C_TCHAR to SQL_DOUBLE. SQLBindParameter, Column #10, SQL_C_TCHAR to SQL_DATE. SQLBindParameter, Column #11, SQL_C_TCHAR to SQL_TIME. SQLBindParameter, Column #12, SQL_C_TCHAR to SQL_TIMESTAMP. SQLBindParameter, Column #13, SQL_C_TCHAR to SQL_LONGVARCHAR. SQLBindParameter, Column #14, SQL_C_TCHAR to SQL_BIGINT. SQLBindParameter, Column #15, SQL_C_TCHAR to SQL_WCHAR. SQLBindParameter, Column #16, SQL_C_TCHAR to SQL_WVARCHAR. SQLBindParameter, Column #17, SQL_C_TCHAR to SQL_WLONGVARCHAR. SQLBindParameter, Column #18, SQL_C_TCHAR to SQL_NUMERIC. SQLBindParameter, Column #19, SQL_C_TCHAR to SQL_NUMERIC. SQLBindParameter, Column #20, SQL_C_TCHAR to SQL_NUMERIC. SQLBindParameter, Column #21, SQL_C_TCHAR to SQL_NUMERIC. SQLBindParameter, Column #22, SQL_C_TCHAR to SQL_NUMERIC. SQLBindParameter, Column #23, SQL_C_TCHAR to SQL_NUMERIC. SQLBindParameter, Column #24, SQL_C_TCHAR to SQL_NUMERIC. SQLBindParameter, Column #25, SQL_C_TCHAR to SQL_NUMERIC. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1682) [MTDCS] ODBC: SQLFetch returned invalid cursor state
Gao, Rui-Xian created TRAFODION-1682: Summary: [MTDCS] ODBC: SQLFetch returned invalid cursor state Key: TRAFODION-1682 URL: https://issues.apache.org/jira/browse/TRAFODION-1682 Project: Apache Trafodion Issue Type: Bug Components: connectivity-dcs Affects Versions: 2.0-incubating Environment: platform: suse11 connect info : 10.10.10.176:23400 esgynDB version :esgynDB-20151121_0900-bin driver version: 1119 Reporter: Gao, Rui-Xian SQLFetch returned invalid cursor state An unexpected error occurred when calling SQLFetch() in common.c. Log SHOWCONTROL ALL error. Expected SQL_SUCCESS, returned -1 State: 24000 Native Error: 0 Error: [Trafodion ODBC Driver] INVALID CURSOR STATE. test code - SQLAllocStmt((SQLHANDLE)hdbc, &hstmt); SQLExecDirect(hstmt,(SQLTCHAR *) ShowCntl, SQL_NTS); //this statement is 'showcontrol all' SQLFetch(hstmt); // it will return error -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1684) ODBC: trafodion doesn't support API SQLStatistics
Gao, Rui-Xian created TRAFODION-1684: Summary: ODBC: trafodion doesn't support API SQLStatistics Key: TRAFODION-1684 URL: https://issues.apache.org/jira/browse/TRAFODION-1684 Project: Apache Trafodion Issue Type: Improvement Components: connectivity-dcs Affects Versions: 1.0 (pre-incubation), 2.0-incubating Environment: client os: window7,windows8,linux(centos6.7, suse11) Reporter: Gao, Rui-Xian Test code-- FullConnect SQLAllocStmt((SQLHANDLE)hdbc, &hstmt); SQLExecDirect(hstmt,(SQLTCHAR*)CreateTbl[t],SQL_NTS); SQLExecDirect(hstmt,(SQLTCHAR*)CreateIdx,SQL_NTS); SQLStatistics(hstmt,(SQLTCHAR*)TQualifier,(SWORD)_tcslen(TQualifier),(SQLTCHAR*)TOwner,(SWORD)_tcslen(TOwner),(SQLTCHAR*)TName,(SWORD)_tcslen(TName),Unique[idx],Accuracy[a]); The sql statement sqlexecdirect is running -- create table WZDPCMJFIV (V6COTKFLZS char(10) CHARACTER SET ISO88591 NOT NULL,primary key(V6COTKFLZS)); create unique index KBROLZG1HL on WZDPCMJFIV (V6COTKFLZS ASC); Then sqlstatistics will return error that the api type is unsupported -- 09:43:34 ***ERROR: SQLStatistics: Expected: SQL_SUCCESS Actual: SQL_ERROR File: ../../../../src/coast/coast_unified/src/stat.c Line: 351 State: HYC00 Native Error: 1 Error: [Trafodion ODBC Driver][DCS Server] OPTIONAL FEATURE NOT IMPLEMENTED.UNSUPPORTED INPUT SMD API TYPE -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1683) ODBC: trafodion doesn't support API SQLSpecialcolumns
Gao, Rui-Xian created TRAFODION-1683: Summary: ODBC: trafodion doesn't support API SQLSpecialcolumns Key: TRAFODION-1683 URL: https://issues.apache.org/jira/browse/TRAFODION-1683 Project: Apache Trafodion Issue Type: Improvement Components: connectivity-dcs Affects Versions: 1.0 (pre-incubation), 2.0-incubating Environment: client os: windows7, windows8,linux(centos6.7, suse11) Reporter: Gao, Rui-Xian SQLExecDirect(hstmt,(SQLTCHAR*)CreateTbl,SQL_NTS);//this statement is -- create table JTJZL513OG (JJPDO_6ERN char(10) CHARACTER SET ISO88591 not null, primary key(JJPDO_6ERN)) SQLSpecialColumns(hstmt,fColType[ct],(SQLTCHAR*)TQualifier,(SWORD)_tcslen(TQualifier),(SQLTCHAR*)TOwner,(SWORD)_tcslen(TOwner),(SQLTCHAR*)TName,(SWORD)_tcslen(TName),Scope[s],Nullable[n]); output -- 09:41:37 ***ERROR: SQLSpecialColumns: Expected: SQL_SUCCESS Actual: SQL_ERROR File: ../../../../src/coast/coast_unified/src/specol.c Line: 263 State: HYC00 Native Error: 1 Error: [Trafodion ODBC Driver][DCS Server] OPTIONAL FEATURE NOT IMPLEMENTED.UNSUPPORTED INPUT SMD API TYPE -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1675) [MTDCS] ODBC: SQLGetData run into error, invalid character value for cast specification
Gao, Rui-Xian created TRAFODION-1675:
Summary: [MTDCS] ODBC: SQLGetData run into error, invalid
character value for cast specification
Key: TRAFODION-1675
URL: https://issues.apache.org/jira/browse/TRAFODION-1675
Project: Apache Trafodion
Issue Type: Bug
Components: connectivity-dcs
Affects Versions: 2.0-incubating
Environment: platform: suse11
connect info: 10.10.10.176:23400
esgynDB version: esgynDB-20151121_0900-bin
driver version: 1119
Reporter: Gao, Rui-Xian
with MTDCS on, SQLGetData API will run into error for data type SQL_C_DATE --
comparing values SQL_WCHAR to SQL_C_DATE(9) after fetched
06:55:49 ***ERROR: SQLGetData: Expected: SQL_SUCCESS Actual: SQL_ERROR
File: ../../../../src/coast/coast_unified/src/getdata.c Line: 1859
State: 22018
Native Error: 0
Error: [Trafodion ODBC Driver] INVALID CHARACTER VALUE FOR CAST
SPECIFICATION. Row: 1 Column: 6
Here is the test code it's running --
CREATE TABLE SQLTODATE(C1 CHAR(10),C2 VARCHAR(10),C3 DATE,C4 TIMESTAMP,C5 LONG
VARCHAR,C6 NCHAR(10),C7 NCHAR VARYING(10),C8 LONG VARCHAR CHARACTER SET UCS2)
NO PARTITION;
INSERT INTO SQLTODATE (C1,C2,C3,C4,C5,C6,C7,C8) VALUES
('1997-10-11','1999-01-01',{d '1993-12-30'},{ts '1992-12-31
00:00:00'},'1998-04-23',_UCS2'1997-10-11',_UCS2'1999-01-01',_UCS2'1998-04-23');
SELECT * FROM SQLTODATE;
SQLFetch(hstmt);
SQLGetData(hstmt,
(SWORD)(i+1),SQLDataValueTOC5[k].CType,&CDateOutput[i],0,&OutputLen2[i]);
in above statement, column number is 6, and target type is SQL_C_DATE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TRAFODION-1674) [MTDCS] ODBC: SQLGetinfo can't get database name
[ https://issues.apache.org/jira/browse/TRAFODION-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian updated TRAFODION-1674: - Component/s: client-odbc-linux > [MTDCS] ODBC: SQLGetinfo can't get database name > > > Key: TRAFODION-1674 > URL: https://issues.apache.org/jira/browse/TRAFODION-1674 > Project: Apache Trafodion > Issue Type: Bug > Components: client-odbc-linux >Affects Versions: 2.0-incubating > Environment: platform: suse11 > connect info: 10.10.10.176:23400 > esgynDB version: esgynDB-20151121_0900-bin > driver version: 1119 >Reporter: Gao, Rui-Xian > > with MTDCS on, sqlgetinfo can't get correct database name > 05:47:01 Test SQLGetInfo(SQL_DATABASE_NAME(16)) > ***ERROR: Count of bytes returned is wrong >Expected:9 Actual:1 > ***ERROR: Returned value is wrong > > Expected:TRAFODION > Actual:^? > > Actual(hex):7F00 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1674) [MTDCS] ODBC: SQLGetinfo can't get database name
Gao, Rui-Xian created TRAFODION-1674: Summary: [MTDCS] ODBC: SQLGetinfo can't get database name Key: TRAFODION-1674 URL: https://issues.apache.org/jira/browse/TRAFODION-1674 Project: Apache Trafodion Issue Type: Bug Affects Versions: 2.0-incubating Environment: platform: suse11 connect info: 10.10.10.176:23400 esgynDB version: esgynDB-20151121_0900-bin driver version: 1119 Reporter: Gao, Rui-Xian with MTDCS on, sqlgetinfo can't get correct database name 05:47:01 Test SQLGetInfo(SQL_DATABASE_NAME(16)) ***ERROR: Count of bytes returned is wrong Expected:9 Actual:1 ***ERROR: Returned value is wrong Expected:TRAFODION Actual:^? Actual(hex):7F00 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-1644) 'initialize trafodion,drop' doesn't drop _DTM_ objects
[ https://issues.apache.org/jira/browse/TRAFODION-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15035419#comment-15035419 ] Gao, Rui-Xian commented on TRAFODION-1644: -- Thanks Sean. I will follow your suggestion to cleanup all objects from trafodion. Since this is not a bug, I will close it. > 'initialize trafodion,drop' doesn't drop _DTM_ objects > -- > > Key: TRAFODION-1644 > URL: https://issues.apache.org/jira/browse/TRAFODION-1644 > Project: Apache Trafodion > Issue Type: Bug > Components: db-utility-backup-restore, sql-general >Affects Versions: 2.0-incubating >Reporter: Gao, Rui-Xian >Assignee: Suresh Subbiah >Priority: Minor > > currently, 'initialize trafodion, drop' doesn't drop all TRAFODION objects, > we need cleanup _DTM_ objects from hbase shell. > >>initialize trafodion, drop; > --- SQL operation complete. > hbase(main):002:0> list 'TRAFODION.*' > TABLE > TRAFODION._DTM_.TLOG0_CONTROL_POINT > TRAFODION._DTM_.TLOG0_LOG_0 > TRAFODION._DTM_.TLOG0_LOG_1 > TRAFODION._DTM_.TLOG0_LOG_2 > TRAFODION._DTM_.TLOG0_LOG_3 > TRAFODION._DTM_.TLOG0_LOG_4 > TRAFODION._DTM_.TLOG0_LOG_5 > TRAFODION._DTM_.TLOG0_LOG_6 > TRAFODION._DTM_.TLOG0_LOG_7 > TRAFODION._DTM_.TLOG0_LOG_8 > TRAFODION._DTM_.TLOG0_LOG_9 > TRAFODION._DTM_.TLOG0_LOG_a > TRAFODION._DTM_.TLOG0_LOG_b > TRAFODION._DTM_.TLOG0_LOG_c > TRAFODION._DTM_.TLOG0_LOG_d > TRAFODION._DTM_.TLOG0_LOG_e > TRAFODION._DTM_.TLOG0_LOG_f > TRAFODION._DTM_.TLOG1_CONTROL_POINT > TRAFODION._DTM_.TLOG1_LOG_0 > TRAFODION._DTM_.TLOG1_LOG_1 > TRAFODION._DTM_.TLOG1_LOG_2 > TRAFODION._DTM_.TLOG1_LOG_3 > TRAFODION._DTM_.TLOG1_LOG_4 > TRAFODION._DTM_.TLOG1_LOG_5 > TRAFODION._DTM_.TLOG1_LOG_6 > TRAFODION._DTM_.TLOG1_LOG_7 > TRAFODION._DTM_.TLOG1_LOG_8 > TRAFODION._DTM_.TLOG1_LOG_9 > TRAFODION._DTM_.TLOG1_LOG_a > TRAFODION._DTM_.TLOG1_LOG_b > TRAFODION._DTM_.TLOG1_LOG_c > TRAFODION._DTM_.TLOG1_LOG_d > TRAFODION._DTM_.TLOG1_LOG_e > TRAFODION._DTM_.TLOG1_LOG_f > TRAFODION._DTM_.TLOG2_CONTROL_POINT > TRAFODION._DTM_.TLOG2_LOG_0 > TRAFODION._DTM_.TLOG2_LOG_1 > TRAFODION._DTM_.TLOG2_LOG_2 > TRAFODION._DTM_.TLOG2_LOG_3 > TRAFODION._DTM_.TLOG2_LOG_4 > TRAFODION._DTM_.TLOG2_LOG_5 > TRAFODION._DTM_.TLOG2_LOG_6 > TRAFODION._DTM_.TLOG2_LOG_7 > TRAFODION._DTM_.TLOG2_LOG_8 > TRAFODION._DTM_.TLOG2_LOG_9 > TRAFODION._DTM_.TLOG2_LOG_a > TRAFODION._DTM_.TLOG2_LOG_b > TRAFODION._DTM_.TLOG2_LOG_c > TRAFODION._DTM_.TLOG2_LOG_d > TRAFODION._DTM_.TLOG2_LOG_e > TRAFODION._DTM_.TLOG2_LOG_f > 51 row(s) in 0.0320 seconds > => ["TRAFODION._DTM_.TLOG0_CONTROL_POINT", "TRAFODION._DTM_.TLOG0_LOG_0", > "TRAFODION._DTM_.TLOG0_LOG_1", "TRAFODION._DTM_.TLOG0_LOG_2", > "TRAFODION._DTM_.TLOG0_LOG_3", "TRAFODION._DTM_.TLOG0_LOG_4", > "TRAFODION._DTM_.TLOG0_LOG_5", "TRAFODION._DTM_.TLOG0_LOG_6", > "TRAFODION._DTM_.TLOG0_LOG_7", "TRAFODION._DTM_.TLOG0_LOG_8", > "TRAFODION._DTM_.TLOG0_LOG_9", "TRAFODION._DTM_.TLOG0_LOG_a", > "TRAFODION._DTM_.TLOG0_LOG_b", "TRAFODION._DTM_.TLOG0_LOG_c", > "TRAFODION._DTM_.TLOG0_LOG_d", "TRAFODION._DTM_.TLOG0_LOG_e", > "TRAFODION._DTM_.TLOG0_LOG_f", "TRAFODION._DTM_.TLOG1_CONTROL_POINT", > "TRAFODION._DTM_.TLOG1_LOG_0", "TRAFODION._DTM_.TLOG1_LOG_1", > "TRAFODION._DTM_.TLOG1_LOG_2", "TRAFODION._DTM_.TLOG1_LOG_3", > "TRAFODION._DTM_.TLOG1_LOG_4", "TRAFODION._DTM_.TLOG1_LOG_5", > "TRAFODION._DTM_.TLOG1_LOG_6", "TRAFODION._DTM_.TLOG1_LOG_7", > "TRAFODION._DTM_.TLOG1_LOG_8", "TRAFODION._DTM_.TLOG1_LOG_9", > "TRAFODION._DTM_.TLOG1_LOG_a", "TRAFODION._DTM_.TLOG1_LOG_b", > "TRAFODION._DTM_.TLOG1_LOG_c", "TRAFODION._DTM_.TLOG1_LOG_d", > "TRAFODION._DTM_.TLOG1_LOG_e", "TRAFODION._DTM_.TLOG1_LOG_f", > "TRAFODION._DTM_.TLOG2_CONTROL_POINT", "TRAFODION._DTM_.TLOG2_LOG_0", > "TRAFODION._DTM_.TLOG2_LOG_1", "TRAFODION._DTM_.TLOG2_LOG_2", > "TRAFODION._DTM_.TLOG2_LOG_3", "TRAFODION._DTM_.TLOG2_LOG_4", > "TRAFODION._DTM_.TLOG2_LOG_5", "TRAFODION._DTM_.TLOG2_LOG_6", > "TRAFODION._DTM_.TLOG2_LOG_7", "TRAFODION._DTM_.TLOG2_LOG_8", > "TRAFODION._DTM_.TLOG2_LOG_9", "TRAFODION._DTM_.TLOG2_LOG_a", > "TRAFODION._DTM_.TLOG2_LOG_b", "TRAFODION._DTM_.TLOG2_LOG_c", > "TRAFODION._DTM_.TLOG2_LOG_d", "TRAFODION._DTM_.TLOG2_LOG_e", > "TRAFODION._DTM_.TLOG2_LOG_f"] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1665) [MTDCS] connection failed with mtdcs on
[ https://issues.apache.org/jira/browse/TRAFODION-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian updated TRAFODION-1665: - Environment: platform: suse11 connect info : 10.10.10.176:23400 esgynDB version :esgynDB-20151121_0900-bin driver version: 1119 was:suse11 > [MTDCS] connection failed with mtdcs on > --- > > Key: TRAFODION-1665 > URL: https://issues.apache.org/jira/browse/TRAFODION-1665 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-dcs >Affects Versions: 2.0-incubating > Environment: platform: suse11 > connect info : 10.10.10.176:23400 > esgynDB version :esgynDB-20151121_0900-bin > driver version: 1119 >Reporter: Gao, Rui-Xian >Priority: Blocker > > connection failed with mtdcs on, and it returns > hostname(TCP:suse-9.novalocal/23404) instead of ip address. >State: S1T00 >Native Error: 0 >Error: [Trafodion ODBC Driver] TIMEOUT EXPIRED. Platform: UNIX, Transport: > TCPIP, Api: SQLCONNECT, Error type: DRIVER, Process: > TCP:suse-9.novalocal/23404:ODBC, Operation: OPEN_SESSION, function: CONNECT, > error: 110, error_detail: 0, error text:Connection timed out. >The InConnectionString is: > ="DSN=TRAF_DSN176_ANSI;UID=trafodion;PWD=traf123;" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1653) [MTDCS] coast tests core dumped at 'operator new' when Multithread DCS is on
[ https://issues.apache.org/jira/browse/TRAFODION-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian updated TRAFODION-1653: - Environment: platform: suse11 connect info : 10.10.10.176:23400 esgynDB version :esgynDB-20151121_0900-bin driver version: 1119 was:suse11 > [MTDCS] coast tests core dumped at 'operator new' when Multithread DCS is on > > > Key: TRAFODION-1653 > URL: https://issues.apache.org/jira/browse/TRAFODION-1653 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-dcs >Affects Versions: 2.0-incubating > Environment: platform: suse11 > connect info : 10.10.10.176:23400 > esgynDB version :esgynDB-20151121_0900-bin > driver version: 1119 >Reporter: Gao, Rui-Xian > > When MTDCS is on, several tests will run into segmentation fault. Here is the > stack trace -- > Core was generated by `./coast -d TRAF_ANSI_176 -u trafodion -p traf123 -c > ASCII -m linux64 -f API SQLSetCursorName' > (gdb) bt > #0 0x7f31ea0d4885 in raise () from /lib64/libc.so.6 > #1 0x7f31ea0d5e61 in abort () from /lib64/libc.so.6 > #2 0x7f31ea9128ad in __gnu_cxx::__verbose_terminate_handler() () from > /usr/lib64/libstdc++.so.6 > #3 0x7f31ea910986 in ?? () from /usr/lib64/libstdc++.so.6 > #4 0x7f31ea9109b3 in std::terminate() () from /usr/lib64/libstdc++.so.6 > #5 0x7f31ea910bf3 in __cxa_throw () from /usr/lib64/libstdc++.so.6 > #6 0x7f31ea9110ed in operator new(unsigned long) () from > /usr/lib64/libstdc++.so.6 > #7 0x7f31ea911189 in operator new[](unsigned long) () from > /usr/lib64/libstdc++.so.6 > #8 0x7f31ec3a2a97 in copy_ERROR_DESC_LIST (pname=0x7ffee1597e20, > curptr=@0x7ffee1597d78: 0x7cf430 "", msg_total_len=@0x7ffee1597d84: 12, > swap=78 'N') > at ./Interface/odbcs_drvr.cpp:537 > #9 0x7f31ec3a40a2 in odbc_SQLDrvr_EndTransaction_pst_ (tag_=0x7aa6e0, > dialogueId=1621953250, > transactionOpt=0, exception_=0x7ffee1597e30, sqlWarning=0x7ffee1597e20) > at ./Interface/odbcs_drvr.cpp:1239 > #10 0x7f31ec3df80f in ENDTRANSACT (srvrCallContext=0x7aa6e0) at > ./cli/netconnect.cpp:827 > #11 0x7f31ec3dd63f in ThreadControlProc (pParam=0x7aa6e0) at > ./cli/drvrnet.cpp:166 > #12 0x7f31ec3add16 in CConnect::EndTran (this=0x7aa390, CompletionType=0) > at ./cli/cconnect.cpp:2607 > #13 0x7f31ec3eccd3 in ODBC::EndTran (HandleType=2, Handle=0x7aa390, > CompletionType=0) > at ./cli/sqlhandle.cpp:187 > #14 0x7f31ec3e455e in NeoEndTran (HandleType=2, Handle=0x7aa390, > CompletionType=0) > at ./cli/neofunc.cpp:225 > #15 0x7f31ec420d17 in ODBC::fun_transact (hdbc=0x7aa390, fType=0) > at ./DrvrManager/dmfunctions.cpp:594 > #16 0x7f31ec429b7b in SQLTransact (henv=0x7ccc40, hdbc=0x7aa390, fType=0) > at ./DrvrManager/dmmapping.cpp:989 > #17 0x004ca7e4 in TestSQLSetCursorName (pTestInfo=0x7a9ad0, > MX_MP_SPECIFIC=0) > at ../../../../src/coast/coast_unified/src/setgetcu.c:1204 > #18 0x004338f4 in Run21Tests () at > ../../../../src/coast/coast_unified/src/COAST.cpp:748 > ---Type to continue, or q to quit--- > #19 0x0043453d in main (argc=14, argv=0x7ffee159a398) > at ../../../../src/coast/coast_unified/src/COAST.cpp:452 > (gdb) frame 8 > #8 0x7f31ec3a2a97 in copy_ERROR_DESC_LIST (pname=0x7ffee1597e20, > curptr=@0x7ffee1597d78: 0x7cf430 "", msg_total_len=@0x7ffee1597d84: 12, > swap=78 'N') > at ./Interface/odbcs_drvr.cpp:537 > 537 ./Interface/odbcs_drvr.cpp: No such file or directory. > (gdb) p pname->_length > $1 = 1193297228 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1658) [MTDCS] with MultiThread DCS on, coast core dumped at memcpy when there is parameter in prepare statement
[ https://issues.apache.org/jira/browse/TRAFODION-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian updated TRAFODION-1658: - Environment: platform: suse11 connect info : 10.10.10.176:23400 esgynDB version :esgynDB-20151121_0900-bin driver version: 1119 was:suse11 > [MTDCS] with MultiThread DCS on, coast core dumped at memcpy when there is > parameter in prepare statement > - > > Key: TRAFODION-1658 > URL: https://issues.apache.org/jira/browse/TRAFODION-1658 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-dcs >Affects Versions: 2.0-incubating > Environment: platform: suse11 > connect info : 10.10.10.176:23400 > esgynDB version :esgynDB-20151121_0900-bin > driver version: 1119 >Reporter: Gao, Rui-Xian > > with MultiThread DCS on, odbc coast core dumped at memcpy when there is > parameter in prepare statement. > Here is the test code -- > SQLExecDirect(hstmt,(SQLTCHAR*)ExecDirStr[i+iend],SQL_NTS); //sql statement: > create table XIK0RPULR5(QJAAFUO4BQ int) NO PARTITION > SQLPrepare(hstmt,(SQLTCHAR*)ExecDirStr[i+iend+iend], SQL_NTS); // sql > statement: insert into XIK0RPULR5 values (?) > Here is the stack trace -- > #0 0x7f4674cf64d9 in memcpy () from /lib64/libc.so.6 > #1 0x7f4676f6ef8f in FormatSQLDescSeq (ODBCDesc=0x7ffd97fae3f0, > SQLDesc=0x7ea338 "\001", > SQLDescLength=8, SQLDataPtr=@0x7ffd97fae408: 0x7e5cf0 "", swap=78 'N', > sqlQueryType=256) > at ./Interface/odbcs_drvr.cpp:228 > #2 0x7f4676f72624 in odbc_SQLDrvr_Prepare_pst_ (tag_=0x7dc780, > setStmtOptions=0x0, > returnCode=0x7ffd97fae44c, sqlWarningOrError=@0x7ffd97fae440: 0x0, > sqlQueryType=0x7ffd97fae43c, > stmtHandle=0x7ffd97fae438, estimatedCost=0x7ffd97fae434, > inputParams=@0x7ffd97fae428: 0x7eb6c0 "\020", inputDesc=0x7ffd97fae410, > outputColumns=@0x7ffd97fae408: 0x7e5cf0 "", outputDesc=0x7ffd97fae3f0) > at ./Interface/odbcs_drvr.cpp:1881 > #3 0x7f4676facf61 in SQLPREPARE_ (srvrCallContext=0x7dc780) at > ./cli/netstmt.cpp:78 > #4 0x7f4676faa592 in ThreadControlProc (pParam=0x7dc780) at > ./cli/drvrnet.cpp:139 > #5 0x7f4676f91da3 in CStmt::SendSQLCommand (this=0x7dc5a0, SkipProcess=0, > StatementText=0x7ea400 "INSERT INTO SQLBINDPARAM9 VALUES (?)", > TextLength=36) > at ./cli/cstmt.cpp:1353 > #6 0x7f4676f91fce in CStmt::Prepare (this=0x7dc5a0, > StatementText=0x7ea400 "INSERT INTO SQLBINDPARAM9 VALUES (?)", > TextLength=36) > at ./cli/cstmt.cpp:1433 > #7 0x7f4676fba1e4 in ODBC::Prepare (StatementHandle=0x7dc5a0, > StatementText=0x7ea400 "INSERT INTO SQLBINDPARAM9 VALUES (?)", > TextLength=36) > at ./cli/sqlstmt.cpp:169 > #8 0x7f4676fb4a44 in NeoPrepare (StatementHandle=0x7dc5a0, > StatementText=0x559420 "INSERT INTO SQLBINDPARAM9 VALUES (?)", > TextLength=-3, isWideCall=false) > at ./cli/neofunc.cpp:1119 > #9 0x7f4676ffb7c8 in SQLPrepare_common (StatementHandle=0x7dc5a0, > StatementText=0x559420 "INSERT INTO SQLBINDPARAM9 VALUES (?)", > TextLength=-3, isWideCall=false) > at ./DrvrManager/drvrmanager.cpp:2202 > #10 0x7f4676ffb8be in SQLPrepare (StatementHandle=0x7dc5a0, > StatementText=0x559420 "INSERT INTO SQLBINDPARAM9 VALUES (?)", > TextLength=-3) > ---Type to continue, or q to quit--- > at ./DrvrManager/drvrmanager.cpp:2255 > #11 0x0042cb5c in TestMXSQLBindParameter (pTestInfo=0x7a9ad0) > at ../../../../src/coast/coast_unified/src/bindpara.c:3256 > #12 0x004335d7 in Run21Tests () at > ../../../../src/coast/coast_unified/src/COAST.cpp:668 > #13 0x0043446d in main (argc=14, argv=0x7ffd97fba0c8) > at ../../../../src/coast/coast_unified/src/COAST.cpp:452 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1660) [MTDCS] ODBC: with MultiThread DCS on, API GetCatalogs will cause dcsserver down
[
https://issues.apache.org/jira/browse/TRAFODION-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gao, Rui-Xian updated TRAFODION-1660:
-
Environment:
platform: suse11
connect info : 10.10.10.176:23400
esgynDB version :esgynDB-20151121_0900-bin
driver version: 1119
was:suse11
> [MTDCS] ODBC: with MultiThread DCS on, API GetCatalogs will cause dcsserver
> down
>
>
> Key: TRAFODION-1660
> URL: https://issues.apache.org/jira/browse/TRAFODION-1660
> Project: Apache Trafodion
> Issue Type: Bug
> Components: connectivity-dcs
>Affects Versions: 2.0-incubating
> Environment: platform: suse11
> connect info : 10.10.10.176:23400
> esgynDB version :esgynDB-20151121_0900-bin
> driver version: 1119
>Reporter: Gao, Rui-Xian
>Priority: Critical
> Attachments: gettypei.c, hs_err_pid58858.log
>
>
> ODBC test GetTypeInfo will cause dcsserver down when MTDCS is on, the root
> cause is API GETCATALOGS.
> Here is the test code that can reproduce the problem(no matter what the data
> type is, it always fails at the second time) --
> j = 0;
> while (j < 2)
> {
> _stprintf(Heading,_T("Test Positive functionality of
> SQLGetTypeInfo for data type:
> %s\n"),SQLTypeToChar(TypeInfo[j].DATA_TYPE,TempBuf));
> TESTCASE_BEGINW(Heading);
> returncode = SQLGetTypeInfo(hstmt,TypeInfo[j].DATA_TYPE);
> LogMsg(NONE,_T("SQLGetTypeInfo(hstmt,j=%d\n"),j);
> if(!CHECKRC(SQL_SUCCESS,returncode,"SQLGetTypeInfo"))
> {
> LogMsg(SHORTTIMESTAMP,_T("SQLGetTypeInfo Failed
> !\n"));
> TEST_FAILED;
> LogAllErrors(henv,hdbc,hstmt);
> }
> TESTCASE_END;
> j++;
> }
> Error info in test log (Api: GETCATALOGS) --
> 13:14:31 Test Positive functionality of SQLGetTypeInfo for data type:
> SQL_WCHAR
> SQLGetTypeInfo(hstmt,j=1
> 13:14:31 ***ERROR: SQLGetTypeInfo: Expected: SQL_SUCCESS Actual: SQL_ERROR
>File: ../../../../src/coast/coast_unified/src/gettypei.c Line: 166
> 13:14:31 SQLGetTypeInfo Failed !
>State: 08S01
>Native Error: 98
>Error: [Trafodion ODBC Driver] COMMUNICATION LINK FAILURE. THE SERVER
> TIMED OUT OR DISAPPEARED. Platform: UNIX, Transport: TCPIP, Api: GETCATALOGS,
> Error type: DRIVER, Process: TCP:suse-9.novalocal/23405:ODBC, Operation:
> DO_WRITE_READ, function: RECV, error: 104, error_detail: 0, error text:recv()
> returned zero bytes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TRAFODION-1656) [MTDCS] When MultiThread DCS is on, server-side do nothing while receiving disconnecting request until connection timeout
[ https://issues.apache.org/jira/browse/TRAFODION-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian updated TRAFODION-1656: - Environment: platform: suse11 connect info : 10.10.10.176:23400 esgynDB version :esgynDB-20151121_0900-bin driver version: 1119 was:suse11 > [MTDCS] When MultiThread DCS is on, server-side do nothing while receiving > disconnecting request until connection timeout > - > > Key: TRAFODION-1656 > URL: https://issues.apache.org/jira/browse/TRAFODION-1656 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-dcs >Affects Versions: 2.0-incubating > Environment: platform: suse11 > connect info : 10.10.10.176:23400 > esgynDB version :esgynDB-20151121_0900-bin > driver version: 1119 >Reporter: Gao, Rui-Xian >Priority: Critical > > server takes almost 30secs to become available after disconnection. It's > because server actually did nothing after receiving disconnecting request > until connection time out. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1665) [MTDCS] connection failed with mtdcs on
Gao, Rui-Xian created TRAFODION-1665: Summary: [MTDCS] connection failed with mtdcs on Key: TRAFODION-1665 URL: https://issues.apache.org/jira/browse/TRAFODION-1665 Project: Apache Trafodion Issue Type: Bug Components: connectivity-dcs Affects Versions: 2.0-incubating Environment: suse11 Reporter: Gao, Rui-Xian Priority: Blocker connection failed with mtdcs on, and it returns hostname(TCP:suse-9.novalocal/23404) instead of ip address. State: S1T00 Native Error: 0 Error: [Trafodion ODBC Driver] TIMEOUT EXPIRED. Platform: UNIX, Transport: TCPIP, Api: SQLCONNECT, Error type: DRIVER, Process: TCP:suse-9.novalocal/23404:ODBC, Operation: OPEN_SESSION, function: CONNECT, error: 110, error_detail: 0, error text:Connection timed out. The InConnectionString is: ="DSN=TRAF_DSN176_ANSI;UID=trafodion;PWD=traf123;" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1661) [MTDCS] ODBC: SQLNumResultCols returns wrong result set after prepare
Gao, Rui-Xian created TRAFODION-1661:
Summary: [MTDCS] ODBC: SQLNumResultCols returns wrong result set
after prepare
Key: TRAFODION-1661
URL: https://issues.apache.org/jira/browse/TRAFODION-1661
Project: Apache Trafodion
Issue Type: Bug
Components: client-odbc-linux
Affects Versions: 2.0-incubating
Environment: suse11
Reporter: Gao, Rui-Xian
When MultiThread DCS is on, SQLNumResultCols returns 0 after prepare but
actually there are 29 columns.
Here is the test step--
SQLAllocStmt((SQLHANDLE)hdbc, &hstmt);
SQLExecDirect(hstmt,(SQLTCHAR*)ExecDirStr[0],SQL_NTS); //cleanup
SQLExecDirect(hstmt,(SQLTCHAR*)ExecDirStr[1],SQL_NTS); // create table
SQLExecDirect(hstmt,(SQLTCHAR*)ExecDirStr[2],SQL_NTS); //insert into table
SQLPrepare(hstmt,(SQLTCHAR*)ExecDirStr[3], SQL_NTS); //select from table
SQLNumResultCols(hstmt, &numcol);
Here are the sql queries it's actually running --
1. create table
create table DTXMEHOWL8(AY0_B4PLCS CHAR(10) CHARACTER SET ISO88591,OWL8X0SIB_
VARCHAR(10) CHARACTER SET ISO88591,FTAYUNM65D DECIMAL(10,5),TXMEHOWL8X
DECIMAL(5,2) UNSIGNED,SIB_BOWACN NUMERIC(10,5),KPLGYIRJ9J NUMERIC(5,2)
UNSIGNED,QSUQR27KCZ SMALLINT,FHG1V3DZEV SMALLINT UNSIGNED,P4FTAYUNM6
INTEGER,R6ZVBCUFWV INTEGER UNSIGNED,GFDUWMDNXE REAL,EKOANMRHKH FLOAT,JTJZL513OG
DOUBLE PRECISION,QIYXP2QIST DATE,ACNKPLGYIR TIME,J9JQSUQR27
TIMESTAMP,KCZFHG1V3D BIGINT,ZEVP4FTAYU LONG VARCHAR CHARACTER SET
ISO88591,NM65DTXMEH NUMERIC(19,0),BOWACNKPLG NUMERIC(19,6),YIRJ9JQSUQ
NUMERIC(128,0),R27KCZFHG1 NUMERIC(128,128),V3DZEVP4FT
NUMERIC(128,64),AYUNM65DTX NUMERIC(10,5) UNSIGNED,MEHOWL8X0S NUMERIC(18,5)
UNSIGNED,IB_BOWACNK NUMERIC(30,10) UNSIGNED,PLGYIRJ9JQ CHAR(10) CHARACTER SET
UCS2,SUQR27KCZF VARCHAR(10) CHARACTER SET UCS2,HG1V3DZEVP LONG VARCHAR
CHARACTER SET UCS2) NO PARTITION;
2. insert data
insert into DTXMEHOWL8
values('2qIstay0|_','B}4pl:`C$#',-1234.567,987.12,-1234.567,987.12,-934,3520,-12000,56343,123.45E2,123.45E3,123.45E4,{d
'1993-07-01'},{t '09:45:30'},{ts '1993-08-02 08:44:31.001'},456789,'
AC\n:Kplg',1234567890123456789,1234567890123.456789,1234567890123456789012345678901234567890,0.123456789012345678901234567890123456789,1234567890.123456789012345678901234567890123456789,12345.56789,1234567890123.56789,12345678901234567890.0123456789,'YI$rj/9JQ?','suq`;R>27k','^cZf|]HG1"');
3. prepare --
select
AY0_B4PLCS,OWL8X0SIB_,FTAYUNM65D,TXMEHOWL8X,SIB_BOWACN,KPLGYIRJ9J,QSUQR27KCZ,FHG1V3DZEV,P4FTAYUNM6,R6ZVBCUFWV,GFDUWMDNXE,EKOANMRHKH,JTJZL513OG,QIYXP2QIST,ACNKPLGYIR,J9JQSUQR27,KCZFHG1V3D,ZEVP4FTAYU,NM65DTXMEH,BOWACNKPLG,YIRJ9JQSUQ,R27KCZFHG1,V3DZEVP4FT,AYUNM65DTX,MEHOWL8X0S,IB_BOWACNK,PLGYIRJ9JQ,SUQR27KCZF,HG1V3DZEVP
from DTXMEHOWL8;
4. SQLNumResultCols(hstmt, &numcol);
returns 0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TRAFODION-1660) [MTDCS] ODBC: with MultiThread DCS on, API GetCatalogs will cause dcsserver down
[
https://issues.apache.org/jira/browse/TRAFODION-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gao, Rui-Xian updated TRAFODION-1660:
-
Attachment: hs_err_pid58858.log
attached jvm log on server
> [MTDCS] ODBC: with MultiThread DCS on, API GetCatalogs will cause dcsserver
> down
>
>
> Key: TRAFODION-1660
> URL: https://issues.apache.org/jira/browse/TRAFODION-1660
> Project: Apache Trafodion
> Issue Type: Bug
> Components: connectivity-dcs
>Affects Versions: 2.0-incubating
> Environment: suse11
>Reporter: Gao, Rui-Xian
>Priority: Critical
> Attachments: gettypei.c, hs_err_pid58858.log
>
>
> ODBC test GetTypeInfo will cause dcsserver down when MTDCS is on, the root
> cause is API GETCATALOGS.
> Here is the test code that can reproduce the problem(no matter what the data
> type is, it always fails at the second time) --
> j = 0;
> while (j < 2)
> {
> _stprintf(Heading,_T("Test Positive functionality of
> SQLGetTypeInfo for data type:
> %s\n"),SQLTypeToChar(TypeInfo[j].DATA_TYPE,TempBuf));
> TESTCASE_BEGINW(Heading);
> returncode = SQLGetTypeInfo(hstmt,TypeInfo[j].DATA_TYPE);
> LogMsg(NONE,_T("SQLGetTypeInfo(hstmt,j=%d\n"),j);
> if(!CHECKRC(SQL_SUCCESS,returncode,"SQLGetTypeInfo"))
> {
> LogMsg(SHORTTIMESTAMP,_T("SQLGetTypeInfo Failed
> !\n"));
> TEST_FAILED;
> LogAllErrors(henv,hdbc,hstmt);
> }
> TESTCASE_END;
> j++;
> }
> Error info in test log (Api: GETCATALOGS) --
> 13:14:31 Test Positive functionality of SQLGetTypeInfo for data type:
> SQL_WCHAR
> SQLGetTypeInfo(hstmt,j=1
> 13:14:31 ***ERROR: SQLGetTypeInfo: Expected: SQL_SUCCESS Actual: SQL_ERROR
>File: ../../../../src/coast/coast_unified/src/gettypei.c Line: 166
> 13:14:31 SQLGetTypeInfo Failed !
>State: 08S01
>Native Error: 98
>Error: [Trafodion ODBC Driver] COMMUNICATION LINK FAILURE. THE SERVER
> TIMED OUT OR DISAPPEARED. Platform: UNIX, Transport: TCPIP, Api: GETCATALOGS,
> Error type: DRIVER, Process: TCP:suse-9.novalocal/23405:ODBC, Operation:
> DO_WRITE_READ, function: RECV, error: 104, error_detail: 0, error text:recv()
> returned zero bytes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TRAFODION-1660) [MTDCS] ODBC: with MultiThread DCS on, API GetCatalogs will cause dcsserver down
[
https://issues.apache.org/jira/browse/TRAFODION-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gao, Rui-Xian updated TRAFODION-1660:
-
Attachment: gettypei.c
attached test code
> [MTDCS] ODBC: with MultiThread DCS on, API GetCatalogs will cause dcsserver
> down
>
>
> Key: TRAFODION-1660
> URL: https://issues.apache.org/jira/browse/TRAFODION-1660
> Project: Apache Trafodion
> Issue Type: Bug
> Components: connectivity-dcs
>Affects Versions: 2.0-incubating
> Environment: suse11
>Reporter: Gao, Rui-Xian
>Priority: Critical
> Attachments: gettypei.c
>
>
> ODBC test GetTypeInfo will cause dcsserver down when MTDCS is on, the root
> cause is API GETCATALOGS.
> Here is the test code that can reproduce the problem(no matter what the data
> type is, it always fails at the second time) --
> j = 0;
> while (j < 2)
> {
> _stprintf(Heading,_T("Test Positive functionality of
> SQLGetTypeInfo for data type:
> %s\n"),SQLTypeToChar(TypeInfo[j].DATA_TYPE,TempBuf));
> TESTCASE_BEGINW(Heading);
> returncode = SQLGetTypeInfo(hstmt,TypeInfo[j].DATA_TYPE);
> LogMsg(NONE,_T("SQLGetTypeInfo(hstmt,j=%d\n"),j);
> if(!CHECKRC(SQL_SUCCESS,returncode,"SQLGetTypeInfo"))
> {
> LogMsg(SHORTTIMESTAMP,_T("SQLGetTypeInfo Failed
> !\n"));
> TEST_FAILED;
> LogAllErrors(henv,hdbc,hstmt);
> }
> TESTCASE_END;
> j++;
> }
> Error info in test log (Api: GETCATALOGS) --
> 13:14:31 Test Positive functionality of SQLGetTypeInfo for data type:
> SQL_WCHAR
> SQLGetTypeInfo(hstmt,j=1
> 13:14:31 ***ERROR: SQLGetTypeInfo: Expected: SQL_SUCCESS Actual: SQL_ERROR
>File: ../../../../src/coast/coast_unified/src/gettypei.c Line: 166
> 13:14:31 SQLGetTypeInfo Failed !
>State: 08S01
>Native Error: 98
>Error: [Trafodion ODBC Driver] COMMUNICATION LINK FAILURE. THE SERVER
> TIMED OUT OR DISAPPEARED. Platform: UNIX, Transport: TCPIP, Api: GETCATALOGS,
> Error type: DRIVER, Process: TCP:suse-9.novalocal/23405:ODBC, Operation:
> DO_WRITE_READ, function: RECV, error: 104, error_detail: 0, error text:recv()
> returned zero bytes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (TRAFODION-1660) [MTDCS] ODBC: with MultiThread DCS on, API GetCatalogs will cause dcsserver down
Gao, Rui-Xian created TRAFODION-1660:
Summary: [MTDCS] ODBC: with MultiThread DCS on, API GetCatalogs
will cause dcsserver down
Key: TRAFODION-1660
URL: https://issues.apache.org/jira/browse/TRAFODION-1660
Project: Apache Trafodion
Issue Type: Bug
Components: connectivity-dcs
Affects Versions: 2.0-incubating
Environment: suse11
Reporter: Gao, Rui-Xian
Priority: Critical
ODBC test GetTypeInfo will cause dcsserver down when MTDCS is on, the root
cause is API GETCATALOGS.
Here is the test code that can reproduce the problem(no matter what the data
type is, it always fails at the second time) --
j = 0;
while (j < 2)
{
_stprintf(Heading,_T("Test Positive functionality of
SQLGetTypeInfo for data type:
%s\n"),SQLTypeToChar(TypeInfo[j].DATA_TYPE,TempBuf));
TESTCASE_BEGINW(Heading);
returncode = SQLGetTypeInfo(hstmt,TypeInfo[j].DATA_TYPE);
LogMsg(NONE,_T("SQLGetTypeInfo(hstmt,j=%d\n"),j);
if(!CHECKRC(SQL_SUCCESS,returncode,"SQLGetTypeInfo"))
{
LogMsg(SHORTTIMESTAMP,_T("SQLGetTypeInfo Failed !\n"));
TEST_FAILED;
LogAllErrors(henv,hdbc,hstmt);
}
TESTCASE_END;
j++;
}
Error info in test log (Api: GETCATALOGS) --
13:14:31 Test Positive functionality of SQLGetTypeInfo for data type: SQL_WCHAR
SQLGetTypeInfo(hstmt,j=1
13:14:31 ***ERROR: SQLGetTypeInfo: Expected: SQL_SUCCESS Actual: SQL_ERROR
File: ../../../../src/coast/coast_unified/src/gettypei.c Line: 166
13:14:31 SQLGetTypeInfo Failed !
State: 08S01
Native Error: 98
Error: [Trafodion ODBC Driver] COMMUNICATION LINK FAILURE. THE SERVER TIMED
OUT OR DISAPPEARED. Platform: UNIX, Transport: TCPIP, Api: GETCATALOGS, Error
type: DRIVER, Process: TCP:suse-9.novalocal/23405:ODBC, Operation:
DO_WRITE_READ, function: RECV, error: 104, error_detail: 0, error text:recv()
returned zero bytes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TRAFODION-1653) [MTDCS] coast tests core dumped at 'operator new' when Multithread DCS is on
[ https://issues.apache.org/jira/browse/TRAFODION-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian updated TRAFODION-1653: - Component/s: (was: client-odbc-linux) connectivity-dcs > [MTDCS] coast tests core dumped at 'operator new' when Multithread DCS is on > > > Key: TRAFODION-1653 > URL: https://issues.apache.org/jira/browse/TRAFODION-1653 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-dcs >Affects Versions: 2.0-incubating > Environment: suse11 >Reporter: Gao, Rui-Xian > > When MTDCS is on, several tests will run into segmentation fault. Here is the > stack trace -- > Core was generated by `./coast -d TRAF_ANSI_176 -u trafodion -p traf123 -c > ASCII -m linux64 -f API SQLSetCursorName' > (gdb) bt > #0 0x7f31ea0d4885 in raise () from /lib64/libc.so.6 > #1 0x7f31ea0d5e61 in abort () from /lib64/libc.so.6 > #2 0x7f31ea9128ad in __gnu_cxx::__verbose_terminate_handler() () from > /usr/lib64/libstdc++.so.6 > #3 0x7f31ea910986 in ?? () from /usr/lib64/libstdc++.so.6 > #4 0x7f31ea9109b3 in std::terminate() () from /usr/lib64/libstdc++.so.6 > #5 0x7f31ea910bf3 in __cxa_throw () from /usr/lib64/libstdc++.so.6 > #6 0x7f31ea9110ed in operator new(unsigned long) () from > /usr/lib64/libstdc++.so.6 > #7 0x7f31ea911189 in operator new[](unsigned long) () from > /usr/lib64/libstdc++.so.6 > #8 0x7f31ec3a2a97 in copy_ERROR_DESC_LIST (pname=0x7ffee1597e20, > curptr=@0x7ffee1597d78: 0x7cf430 "", msg_total_len=@0x7ffee1597d84: 12, > swap=78 'N') > at ./Interface/odbcs_drvr.cpp:537 > #9 0x7f31ec3a40a2 in odbc_SQLDrvr_EndTransaction_pst_ (tag_=0x7aa6e0, > dialogueId=1621953250, > transactionOpt=0, exception_=0x7ffee1597e30, sqlWarning=0x7ffee1597e20) > at ./Interface/odbcs_drvr.cpp:1239 > #10 0x7f31ec3df80f in ENDTRANSACT (srvrCallContext=0x7aa6e0) at > ./cli/netconnect.cpp:827 > #11 0x7f31ec3dd63f in ThreadControlProc (pParam=0x7aa6e0) at > ./cli/drvrnet.cpp:166 > #12 0x7f31ec3add16 in CConnect::EndTran (this=0x7aa390, CompletionType=0) > at ./cli/cconnect.cpp:2607 > #13 0x7f31ec3eccd3 in ODBC::EndTran (HandleType=2, Handle=0x7aa390, > CompletionType=0) > at ./cli/sqlhandle.cpp:187 > #14 0x7f31ec3e455e in NeoEndTran (HandleType=2, Handle=0x7aa390, > CompletionType=0) > at ./cli/neofunc.cpp:225 > #15 0x7f31ec420d17 in ODBC::fun_transact (hdbc=0x7aa390, fType=0) > at ./DrvrManager/dmfunctions.cpp:594 > #16 0x7f31ec429b7b in SQLTransact (henv=0x7ccc40, hdbc=0x7aa390, fType=0) > at ./DrvrManager/dmmapping.cpp:989 > #17 0x004ca7e4 in TestSQLSetCursorName (pTestInfo=0x7a9ad0, > MX_MP_SPECIFIC=0) > at ../../../../src/coast/coast_unified/src/setgetcu.c:1204 > #18 0x004338f4 in Run21Tests () at > ../../../../src/coast/coast_unified/src/COAST.cpp:748 > ---Type to continue, or q to quit--- > #19 0x0043453d in main (argc=14, argv=0x7ffee159a398) > at ../../../../src/coast/coast_unified/src/COAST.cpp:452 > (gdb) frame 8 > #8 0x7f31ec3a2a97 in copy_ERROR_DESC_LIST (pname=0x7ffee1597e20, > curptr=@0x7ffee1597d78: 0x7cf430 "", msg_total_len=@0x7ffee1597d84: 12, > swap=78 'N') > at ./Interface/odbcs_drvr.cpp:537 > 537 ./Interface/odbcs_drvr.cpp: No such file or directory. > (gdb) p pname->_length > $1 = 1193297228 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1656) [MTDCS] When MultiThread DCS is on, server-side do nothing while receiving disconnecting request until connection timeout
[ https://issues.apache.org/jira/browse/TRAFODION-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian updated TRAFODION-1656: - Summary: [MTDCS] When MultiThread DCS is on, server-side do nothing while receiving disconnecting request until connection timeout (was: When MultiThread DCS is on, server-side do nothing while receiving disconnecting request until connection timeout) > [MTDCS] When MultiThread DCS is on, server-side do nothing while receiving > disconnecting request until connection timeout > - > > Key: TRAFODION-1656 > URL: https://issues.apache.org/jira/browse/TRAFODION-1656 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-dcs >Affects Versions: 2.0-incubating > Environment: suse11 >Reporter: Gao, Rui-Xian >Priority: Critical > > server takes almost 30secs to become available after disconnection. It's > because server actually did nothing after receiving disconnecting request > until connection time out. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1653) [MTDCS] coast tests core dumped at 'operator new' when Multithread DCS is on
[ https://issues.apache.org/jira/browse/TRAFODION-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian updated TRAFODION-1653: - Summary: [MTDCS] coast tests core dumped at 'operator new' when Multithread DCS is on (was: coast tests core dumped at 'operator new' when Multithread DCS is on) > [MTDCS] coast tests core dumped at 'operator new' when Multithread DCS is on > > > Key: TRAFODION-1653 > URL: https://issues.apache.org/jira/browse/TRAFODION-1653 > Project: Apache Trafodion > Issue Type: Bug > Components: client-odbc-linux >Affects Versions: 2.0-incubating > Environment: suse11 >Reporter: Gao, Rui-Xian > > When MTDCS is on, several tests will run into segmentation fault. Here is the > stack trace -- > Core was generated by `./coast -d TRAF_ANSI_176 -u trafodion -p traf123 -c > ASCII -m linux64 -f API SQLSetCursorName' > (gdb) bt > #0 0x7f31ea0d4885 in raise () from /lib64/libc.so.6 > #1 0x7f31ea0d5e61 in abort () from /lib64/libc.so.6 > #2 0x7f31ea9128ad in __gnu_cxx::__verbose_terminate_handler() () from > /usr/lib64/libstdc++.so.6 > #3 0x7f31ea910986 in ?? () from /usr/lib64/libstdc++.so.6 > #4 0x7f31ea9109b3 in std::terminate() () from /usr/lib64/libstdc++.so.6 > #5 0x7f31ea910bf3 in __cxa_throw () from /usr/lib64/libstdc++.so.6 > #6 0x7f31ea9110ed in operator new(unsigned long) () from > /usr/lib64/libstdc++.so.6 > #7 0x7f31ea911189 in operator new[](unsigned long) () from > /usr/lib64/libstdc++.so.6 > #8 0x7f31ec3a2a97 in copy_ERROR_DESC_LIST (pname=0x7ffee1597e20, > curptr=@0x7ffee1597d78: 0x7cf430 "", msg_total_len=@0x7ffee1597d84: 12, > swap=78 'N') > at ./Interface/odbcs_drvr.cpp:537 > #9 0x7f31ec3a40a2 in odbc_SQLDrvr_EndTransaction_pst_ (tag_=0x7aa6e0, > dialogueId=1621953250, > transactionOpt=0, exception_=0x7ffee1597e30, sqlWarning=0x7ffee1597e20) > at ./Interface/odbcs_drvr.cpp:1239 > #10 0x7f31ec3df80f in ENDTRANSACT (srvrCallContext=0x7aa6e0) at > ./cli/netconnect.cpp:827 > #11 0x7f31ec3dd63f in ThreadControlProc (pParam=0x7aa6e0) at > ./cli/drvrnet.cpp:166 > #12 0x7f31ec3add16 in CConnect::EndTran (this=0x7aa390, CompletionType=0) > at ./cli/cconnect.cpp:2607 > #13 0x7f31ec3eccd3 in ODBC::EndTran (HandleType=2, Handle=0x7aa390, > CompletionType=0) > at ./cli/sqlhandle.cpp:187 > #14 0x7f31ec3e455e in NeoEndTran (HandleType=2, Handle=0x7aa390, > CompletionType=0) > at ./cli/neofunc.cpp:225 > #15 0x7f31ec420d17 in ODBC::fun_transact (hdbc=0x7aa390, fType=0) > at ./DrvrManager/dmfunctions.cpp:594 > #16 0x7f31ec429b7b in SQLTransact (henv=0x7ccc40, hdbc=0x7aa390, fType=0) > at ./DrvrManager/dmmapping.cpp:989 > #17 0x004ca7e4 in TestSQLSetCursorName (pTestInfo=0x7a9ad0, > MX_MP_SPECIFIC=0) > at ../../../../src/coast/coast_unified/src/setgetcu.c:1204 > #18 0x004338f4 in Run21Tests () at > ../../../../src/coast/coast_unified/src/COAST.cpp:748 > ---Type to continue, or q to quit--- > #19 0x0043453d in main (argc=14, argv=0x7ffee159a398) > at ../../../../src/coast/coast_unified/src/COAST.cpp:452 > (gdb) frame 8 > #8 0x7f31ec3a2a97 in copy_ERROR_DESC_LIST (pname=0x7ffee1597e20, > curptr=@0x7ffee1597d78: 0x7cf430 "", msg_total_len=@0x7ffee1597d84: 12, > swap=78 'N') > at ./Interface/odbcs_drvr.cpp:537 > 537 ./Interface/odbcs_drvr.cpp: No such file or directory. > (gdb) p pname->_length > $1 = 1193297228 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1658) [MTDCS] with MultiThread DCS on, coast core dumped at memcpy when there is parameter in prepare statement
Gao, Rui-Xian created TRAFODION-1658: Summary: [MTDCS] with MultiThread DCS on, coast core dumped at memcpy when there is parameter in prepare statement Key: TRAFODION-1658 URL: https://issues.apache.org/jira/browse/TRAFODION-1658 Project: Apache Trafodion Issue Type: Bug Components: connectivity-dcs Affects Versions: 2.0-incubating Environment: suse11 Reporter: Gao, Rui-Xian with MultiThread DCS on, odbc coast core dumped at memcpy when there is parameter in prepare statement. Here is the test code -- SQLExecDirect(hstmt,(SQLTCHAR*)ExecDirStr[i+iend],SQL_NTS); //sql statement: create table XIK0RPULR5(QJAAFUO4BQ int) NO PARTITION SQLPrepare(hstmt,(SQLTCHAR*)ExecDirStr[i+iend+iend], SQL_NTS); // sql statement: insert into XIK0RPULR5 values (?) Here is the stack trace -- #0 0x7f4674cf64d9 in memcpy () from /lib64/libc.so.6 #1 0x7f4676f6ef8f in FormatSQLDescSeq (ODBCDesc=0x7ffd97fae3f0, SQLDesc=0x7ea338 "\001", SQLDescLength=8, SQLDataPtr=@0x7ffd97fae408: 0x7e5cf0 "", swap=78 'N', sqlQueryType=256) at ./Interface/odbcs_drvr.cpp:228 #2 0x7f4676f72624 in odbc_SQLDrvr_Prepare_pst_ (tag_=0x7dc780, setStmtOptions=0x0, returnCode=0x7ffd97fae44c, sqlWarningOrError=@0x7ffd97fae440: 0x0, sqlQueryType=0x7ffd97fae43c, stmtHandle=0x7ffd97fae438, estimatedCost=0x7ffd97fae434, inputParams=@0x7ffd97fae428: 0x7eb6c0 "\020", inputDesc=0x7ffd97fae410, outputColumns=@0x7ffd97fae408: 0x7e5cf0 "", outputDesc=0x7ffd97fae3f0) at ./Interface/odbcs_drvr.cpp:1881 #3 0x7f4676facf61 in SQLPREPARE_ (srvrCallContext=0x7dc780) at ./cli/netstmt.cpp:78 #4 0x7f4676faa592 in ThreadControlProc (pParam=0x7dc780) at ./cli/drvrnet.cpp:139 #5 0x7f4676f91da3 in CStmt::SendSQLCommand (this=0x7dc5a0, SkipProcess=0, StatementText=0x7ea400 "INSERT INTO SQLBINDPARAM9 VALUES (?)", TextLength=36) at ./cli/cstmt.cpp:1353 #6 0x7f4676f91fce in CStmt::Prepare (this=0x7dc5a0, StatementText=0x7ea400 "INSERT INTO SQLBINDPARAM9 VALUES (?)", TextLength=36) at ./cli/cstmt.cpp:1433 #7 0x7f4676fba1e4 in ODBC::Prepare (StatementHandle=0x7dc5a0, StatementText=0x7ea400 "INSERT INTO SQLBINDPARAM9 VALUES (?)", TextLength=36) at ./cli/sqlstmt.cpp:169 #8 0x7f4676fb4a44 in NeoPrepare (StatementHandle=0x7dc5a0, StatementText=0x559420 "INSERT INTO SQLBINDPARAM9 VALUES (?)", TextLength=-3, isWideCall=false) at ./cli/neofunc.cpp:1119 #9 0x7f4676ffb7c8 in SQLPrepare_common (StatementHandle=0x7dc5a0, StatementText=0x559420 "INSERT INTO SQLBINDPARAM9 VALUES (?)", TextLength=-3, isWideCall=false) at ./DrvrManager/drvrmanager.cpp:2202 #10 0x7f4676ffb8be in SQLPrepare (StatementHandle=0x7dc5a0, StatementText=0x559420 "INSERT INTO SQLBINDPARAM9 VALUES (?)", TextLength=-3) ---Type to continue, or q to quit--- at ./DrvrManager/drvrmanager.cpp:2255 #11 0x0042cb5c in TestMXSQLBindParameter (pTestInfo=0x7a9ad0) at ../../../../src/coast/coast_unified/src/bindpara.c:3256 #12 0x004335d7 in Run21Tests () at ../../../../src/coast/coast_unified/src/COAST.cpp:668 #13 0x0043446d in main (argc=14, argv=0x7ffd97fba0c8) at ../../../../src/coast/coast_unified/src/COAST.cpp:452 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1656) When MultiThread DCS is on, server-side do nothing while receiving disconnecting request until connection timeout
Gao, Rui-Xian created TRAFODION-1656: Summary: When MultiThread DCS is on, server-side do nothing while receiving disconnecting request until connection timeout Key: TRAFODION-1656 URL: https://issues.apache.org/jira/browse/TRAFODION-1656 Project: Apache Trafodion Issue Type: Bug Components: connectivity-dcs Affects Versions: 2.0-incubating Environment: suse11 Reporter: Gao, Rui-Xian Priority: Critical server takes almost 30secs to become available after disconnection. It's because server actually did nothing after receiving disconnecting request until connection time out. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1653) coast tests core dumped at 'operator new' when Multithread DCS is on
[ https://issues.apache.org/jira/browse/TRAFODION-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian updated TRAFODION-1653: - Affects Version/s: 2.0-incubating > coast tests core dumped at 'operator new' when Multithread DCS is on > > > Key: TRAFODION-1653 > URL: https://issues.apache.org/jira/browse/TRAFODION-1653 > Project: Apache Trafodion > Issue Type: Bug > Components: client-odbc-linux >Affects Versions: 2.0-incubating > Environment: suse11 >Reporter: Gao, Rui-Xian > > When MTDCS is on, several tests will run into segmentation fault. Here is the > stack trace -- > Core was generated by `./coast -d TRAF_ANSI_176 -u trafodion -p traf123 -c > ASCII -m linux64 -f API SQLSetCursorName' > (gdb) bt > #0 0x7f31ea0d4885 in raise () from /lib64/libc.so.6 > #1 0x7f31ea0d5e61 in abort () from /lib64/libc.so.6 > #2 0x7f31ea9128ad in __gnu_cxx::__verbose_terminate_handler() () from > /usr/lib64/libstdc++.so.6 > #3 0x7f31ea910986 in ?? () from /usr/lib64/libstdc++.so.6 > #4 0x7f31ea9109b3 in std::terminate() () from /usr/lib64/libstdc++.so.6 > #5 0x7f31ea910bf3 in __cxa_throw () from /usr/lib64/libstdc++.so.6 > #6 0x7f31ea9110ed in operator new(unsigned long) () from > /usr/lib64/libstdc++.so.6 > #7 0x7f31ea911189 in operator new[](unsigned long) () from > /usr/lib64/libstdc++.so.6 > #8 0x7f31ec3a2a97 in copy_ERROR_DESC_LIST (pname=0x7ffee1597e20, > curptr=@0x7ffee1597d78: 0x7cf430 "", msg_total_len=@0x7ffee1597d84: 12, > swap=78 'N') > at ./Interface/odbcs_drvr.cpp:537 > #9 0x7f31ec3a40a2 in odbc_SQLDrvr_EndTransaction_pst_ (tag_=0x7aa6e0, > dialogueId=1621953250, > transactionOpt=0, exception_=0x7ffee1597e30, sqlWarning=0x7ffee1597e20) > at ./Interface/odbcs_drvr.cpp:1239 > #10 0x7f31ec3df80f in ENDTRANSACT (srvrCallContext=0x7aa6e0) at > ./cli/netconnect.cpp:827 > #11 0x7f31ec3dd63f in ThreadControlProc (pParam=0x7aa6e0) at > ./cli/drvrnet.cpp:166 > #12 0x7f31ec3add16 in CConnect::EndTran (this=0x7aa390, CompletionType=0) > at ./cli/cconnect.cpp:2607 > #13 0x7f31ec3eccd3 in ODBC::EndTran (HandleType=2, Handle=0x7aa390, > CompletionType=0) > at ./cli/sqlhandle.cpp:187 > #14 0x7f31ec3e455e in NeoEndTran (HandleType=2, Handle=0x7aa390, > CompletionType=0) > at ./cli/neofunc.cpp:225 > #15 0x7f31ec420d17 in ODBC::fun_transact (hdbc=0x7aa390, fType=0) > at ./DrvrManager/dmfunctions.cpp:594 > #16 0x7f31ec429b7b in SQLTransact (henv=0x7ccc40, hdbc=0x7aa390, fType=0) > at ./DrvrManager/dmmapping.cpp:989 > #17 0x004ca7e4 in TestSQLSetCursorName (pTestInfo=0x7a9ad0, > MX_MP_SPECIFIC=0) > at ../../../../src/coast/coast_unified/src/setgetcu.c:1204 > #18 0x004338f4 in Run21Tests () at > ../../../../src/coast/coast_unified/src/COAST.cpp:748 > ---Type to continue, or q to quit--- > #19 0x0043453d in main (argc=14, argv=0x7ffee159a398) > at ../../../../src/coast/coast_unified/src/COAST.cpp:452 > (gdb) frame 8 > #8 0x7f31ec3a2a97 in copy_ERROR_DESC_LIST (pname=0x7ffee1597e20, > curptr=@0x7ffee1597d78: 0x7cf430 "", msg_total_len=@0x7ffee1597d84: 12, > swap=78 'N') > at ./Interface/odbcs_drvr.cpp:537 > 537 ./Interface/odbcs_drvr.cpp: No such file or directory. > (gdb) p pname->_length > $1 = 1193297228 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1653) coast tests core dumped at 'operator new' when Multithread DCS is on
Gao, Rui-Xian created TRAFODION-1653: Summary: coast tests core dumped at 'operator new' when Multithread DCS is on Key: TRAFODION-1653 URL: https://issues.apache.org/jira/browse/TRAFODION-1653 Project: Apache Trafodion Issue Type: Bug Components: client-odbc-linux Environment: suse11 Reporter: Gao, Rui-Xian When MTDCS is on, several tests will run into segmentation fault. Here is the stack trace -- Core was generated by `./coast -d TRAF_ANSI_176 -u trafodion -p traf123 -c ASCII -m linux64 -f API SQLSetCursorName' (gdb) bt #0 0x7f31ea0d4885 in raise () from /lib64/libc.so.6 #1 0x7f31ea0d5e61 in abort () from /lib64/libc.so.6 #2 0x7f31ea9128ad in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib64/libstdc++.so.6 #3 0x7f31ea910986 in ?? () from /usr/lib64/libstdc++.so.6 #4 0x7f31ea9109b3 in std::terminate() () from /usr/lib64/libstdc++.so.6 #5 0x7f31ea910bf3 in __cxa_throw () from /usr/lib64/libstdc++.so.6 #6 0x7f31ea9110ed in operator new(unsigned long) () from /usr/lib64/libstdc++.so.6 #7 0x7f31ea911189 in operator new[](unsigned long) () from /usr/lib64/libstdc++.so.6 #8 0x7f31ec3a2a97 in copy_ERROR_DESC_LIST (pname=0x7ffee1597e20, curptr=@0x7ffee1597d78: 0x7cf430 "", msg_total_len=@0x7ffee1597d84: 12, swap=78 'N') at ./Interface/odbcs_drvr.cpp:537 #9 0x7f31ec3a40a2 in odbc_SQLDrvr_EndTransaction_pst_ (tag_=0x7aa6e0, dialogueId=1621953250, transactionOpt=0, exception_=0x7ffee1597e30, sqlWarning=0x7ffee1597e20) at ./Interface/odbcs_drvr.cpp:1239 #10 0x7f31ec3df80f in ENDTRANSACT (srvrCallContext=0x7aa6e0) at ./cli/netconnect.cpp:827 #11 0x7f31ec3dd63f in ThreadControlProc (pParam=0x7aa6e0) at ./cli/drvrnet.cpp:166 #12 0x7f31ec3add16 in CConnect::EndTran (this=0x7aa390, CompletionType=0) at ./cli/cconnect.cpp:2607 #13 0x7f31ec3eccd3 in ODBC::EndTran (HandleType=2, Handle=0x7aa390, CompletionType=0) at ./cli/sqlhandle.cpp:187 #14 0x7f31ec3e455e in NeoEndTran (HandleType=2, Handle=0x7aa390, CompletionType=0) at ./cli/neofunc.cpp:225 #15 0x7f31ec420d17 in ODBC::fun_transact (hdbc=0x7aa390, fType=0) at ./DrvrManager/dmfunctions.cpp:594 #16 0x7f31ec429b7b in SQLTransact (henv=0x7ccc40, hdbc=0x7aa390, fType=0) at ./DrvrManager/dmmapping.cpp:989 #17 0x004ca7e4 in TestSQLSetCursorName (pTestInfo=0x7a9ad0, MX_MP_SPECIFIC=0) at ../../../../src/coast/coast_unified/src/setgetcu.c:1204 #18 0x004338f4 in Run21Tests () at ../../../../src/coast/coast_unified/src/COAST.cpp:748 ---Type to continue, or q to quit--- #19 0x0043453d in main (argc=14, argv=0x7ffee159a398) at ../../../../src/coast/coast_unified/src/COAST.cpp:452 (gdb) frame 8 #8 0x7f31ec3a2a97 in copy_ERROR_DESC_LIST (pname=0x7ffee1597e20, curptr=@0x7ffee1597d78: 0x7cf430 "", msg_total_len=@0x7ffee1597d84: 12, swap=78 'N') at ./Interface/odbcs_drvr.cpp:537 537 ./Interface/odbcs_drvr.cpp: No such file or directory. (gdb) p pname->_length $1 = 1193297228 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-1652) SQLDriverConnect can't get catalog name
Gao, Rui-Xian created TRAFODION-1652: Summary: SQLDriverConnect can't get catalog name Key: TRAFODION-1652 URL: https://issues.apache.org/jira/browse/TRAFODION-1652 Project: Apache Trafodion Issue Type: Bug Components: client-odbc-windows Affects Versions: 2.0-incubating Environment: windows7 windows8 Reporter: Gao, Rui-Xian SQLDriverConnect returned empty catalog name returncode = SQLDriverConnect(hdbc,NULL,(SQLCHAR*)ConnectStringIn,sizeof(ConnectStringIn), (SQLCHAR*)ConnectStringOut,sizeof(ConnectStringOut),&ConnStrLengthOut, SQL_DRIVER_NOPROMPT); LogMsg(SHORTTIMESTAMP + LINEAFTER, "ConnectStringOut is :%s\n", ConnectStringOut); output -- ConnectStringOut is :DSN=TRAF_DSN145_W7;SERVER=TCP:10.10.10.145/23400;UID=trafodion;PWD=traf123;CATALOG=;SCHEMA=RACHEL_ODBCTEST_W7; -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1644) 'initialize trafodion,drop' doesn't drop _DTM_ objects
[ https://issues.apache.org/jira/browse/TRAFODION-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gao, Rui-Xian updated TRAFODION-1644: - Priority: Minor (was: Major) > 'initialize trafodion,drop' doesn't drop _DTM_ objects > -- > > Key: TRAFODION-1644 > URL: https://issues.apache.org/jira/browse/TRAFODION-1644 > Project: Apache Trafodion > Issue Type: Bug > Components: db-utility-backup-restore, sql-general >Affects Versions: 2.0-incubating >Reporter: Gao, Rui-Xian >Assignee: Suresh Subbiah >Priority: Minor > > currently, 'initialize trafodion, drop' doesn't drop all TRAFODION objects, > we need cleanup _DTM_ objects from hbase shell. > >>initialize trafodion, drop; > --- SQL operation complete. > hbase(main):002:0> list 'TRAFODION.*' > TABLE > TRAFODION._DTM_.TLOG0_CONTROL_POINT > TRAFODION._DTM_.TLOG0_LOG_0 > TRAFODION._DTM_.TLOG0_LOG_1 > TRAFODION._DTM_.TLOG0_LOG_2 > TRAFODION._DTM_.TLOG0_LOG_3 > TRAFODION._DTM_.TLOG0_LOG_4 > TRAFODION._DTM_.TLOG0_LOG_5 > TRAFODION._DTM_.TLOG0_LOG_6 > TRAFODION._DTM_.TLOG0_LOG_7 > TRAFODION._DTM_.TLOG0_LOG_8 > TRAFODION._DTM_.TLOG0_LOG_9 > TRAFODION._DTM_.TLOG0_LOG_a > TRAFODION._DTM_.TLOG0_LOG_b > TRAFODION._DTM_.TLOG0_LOG_c > TRAFODION._DTM_.TLOG0_LOG_d > TRAFODION._DTM_.TLOG0_LOG_e > TRAFODION._DTM_.TLOG0_LOG_f > TRAFODION._DTM_.TLOG1_CONTROL_POINT > TRAFODION._DTM_.TLOG1_LOG_0 > TRAFODION._DTM_.TLOG1_LOG_1 > TRAFODION._DTM_.TLOG1_LOG_2 > TRAFODION._DTM_.TLOG1_LOG_3 > TRAFODION._DTM_.TLOG1_LOG_4 > TRAFODION._DTM_.TLOG1_LOG_5 > TRAFODION._DTM_.TLOG1_LOG_6 > TRAFODION._DTM_.TLOG1_LOG_7 > TRAFODION._DTM_.TLOG1_LOG_8 > TRAFODION._DTM_.TLOG1_LOG_9 > TRAFODION._DTM_.TLOG1_LOG_a > TRAFODION._DTM_.TLOG1_LOG_b > TRAFODION._DTM_.TLOG1_LOG_c > TRAFODION._DTM_.TLOG1_LOG_d > TRAFODION._DTM_.TLOG1_LOG_e > TRAFODION._DTM_.TLOG1_LOG_f > TRAFODION._DTM_.TLOG2_CONTROL_POINT > TRAFODION._DTM_.TLOG2_LOG_0 > TRAFODION._DTM_.TLOG2_LOG_1 > TRAFODION._DTM_.TLOG2_LOG_2 > TRAFODION._DTM_.TLOG2_LOG_3 > TRAFODION._DTM_.TLOG2_LOG_4 > TRAFODION._DTM_.TLOG2_LOG_5 > TRAFODION._DTM_.TLOG2_LOG_6 > TRAFODION._DTM_.TLOG2_LOG_7 > TRAFODION._DTM_.TLOG2_LOG_8 > TRAFODION._DTM_.TLOG2_LOG_9 > TRAFODION._DTM_.TLOG2_LOG_a > TRAFODION._DTM_.TLOG2_LOG_b > TRAFODION._DTM_.TLOG2_LOG_c > TRAFODION._DTM_.TLOG2_LOG_d > TRAFODION._DTM_.TLOG2_LOG_e > TRAFODION._DTM_.TLOG2_LOG_f > 51 row(s) in 0.0320 seconds > => ["TRAFODION._DTM_.TLOG0_CONTROL_POINT", "TRAFODION._DTM_.TLOG0_LOG_0", > "TRAFODION._DTM_.TLOG0_LOG_1", "TRAFODION._DTM_.TLOG0_LOG_2", > "TRAFODION._DTM_.TLOG0_LOG_3", "TRAFODION._DTM_.TLOG0_LOG_4", > "TRAFODION._DTM_.TLOG0_LOG_5", "TRAFODION._DTM_.TLOG0_LOG_6", > "TRAFODION._DTM_.TLOG0_LOG_7", "TRAFODION._DTM_.TLOG0_LOG_8", > "TRAFODION._DTM_.TLOG0_LOG_9", "TRAFODION._DTM_.TLOG0_LOG_a", > "TRAFODION._DTM_.TLOG0_LOG_b", "TRAFODION._DTM_.TLOG0_LOG_c", > "TRAFODION._DTM_.TLOG0_LOG_d", "TRAFODION._DTM_.TLOG0_LOG_e", > "TRAFODION._DTM_.TLOG0_LOG_f", "TRAFODION._DTM_.TLOG1_CONTROL_POINT", > "TRAFODION._DTM_.TLOG1_LOG_0", "TRAFODION._DTM_.TLOG1_LOG_1", > "TRAFODION._DTM_.TLOG1_LOG_2", "TRAFODION._DTM_.TLOG1_LOG_3", > "TRAFODION._DTM_.TLOG1_LOG_4", "TRAFODION._DTM_.TLOG1_LOG_5", > "TRAFODION._DTM_.TLOG1_LOG_6", "TRAFODION._DTM_.TLOG1_LOG_7", > "TRAFODION._DTM_.TLOG1_LOG_8", "TRAFODION._DTM_.TLOG1_LOG_9", > "TRAFODION._DTM_.TLOG1_LOG_a", "TRAFODION._DTM_.TLOG1_LOG_b", > "TRAFODION._DTM_.TLOG1_LOG_c", "TRAFODION._DTM_.TLOG1_LOG_d", > "TRAFODION._DTM_.TLOG1_LOG_e", "TRAFODION._DTM_.TLOG1_LOG_f", > "TRAFODION._DTM_.TLOG2_CONTROL_POINT", "TRAFODION._DTM_.TLOG2_LOG_0", > "TRAFODION._DTM_.TLOG2_LOG_1", "TRAFODION._DTM_.TLOG2_LOG_2", > "TRAFODION._DTM_.TLOG2_LOG_3", "TRAFODION._DTM_.TLOG2_LOG_4", > "TRAFODION._DTM_.TLOG2_LOG_5", "TRAFODION._DTM_.TLOG2_LOG_6", > "TRAFODION._DTM_.TLOG2_LOG_7", "TRAFODION._DTM_.TLOG2_LOG_8", > "TRAFODION._DTM_.TLOG2_LOG_9", "TRAFODION._DTM_.TLOG2_LOG_a", > "TRAFODION._DTM_.TLOG2_LOG_b", "TRAFODION._DTM_.TLOG2_LOG_c", > "TRAFODION._DTM_.TLOG2_LOG_d", "TRAFODION._DTM_.TLOG2_LOG_e", > "TRAFODION._DTM_.TLOG2_LOG_f"] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
