[jira] [Created] (TRAFODION-2124) ERROR[8433] is returned while select from table (statistics(NULL, 'ACTIVE_QUERIES=30')) with Queries having Chinese Characters running.
Elaine_WangLing created TRAFODION-2124: -- Summary: ERROR[8433] is returned while select from table (statistics(NULL, 'ACTIVE_QUERIES=30')) with Queries having Chinese Characters running. Key: TRAFODION-2124 URL: https://issues.apache.org/jira/browse/TRAFODION-2124 Project: Apache Trafodion Issue Type: Bug Components: sql-exe Affects Versions: 2.1-incubating Environment: Release 2.1.0 & Release 2.2.0 Reporter: Elaine_WangLing [Pre-condition] 1. create table used this DDL create table qa_elaine.JDBC_T_CHAR18 ( BIZ_TYPE CHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT DEFAULT NULL NOT SERIALIZED, CALL_TYPECHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT DEFAULT NULL NOT SERIALIZED, ROAMTYPE LARGEINT DEFAULT NULL NOT SERIALIZED, IMSI CHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT DEFAULT NULL NOT SERIALIZED, MSISDN CHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT NO DEFAULT NOT NULL NOT DROPPABLE NOT SERIALIZED, OTHER_PARTY CHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT DEFAULT NULL NOT SERIALIZED, THIRD_PARTY CHAR(30 CHARS) CHARACTER SET UTF8 COLLATE DEFAULT DEFAULT NULL NOT SERIALIZED, START_TIME CHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT DEFAULT NULL NOT SERIALIZED, END_TIME CHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT DEFAULT NULL NOT SERIALIZED, CALL_DURATION LARGEINT DEFAULT NULL NOT SERIALIZED, MSC CHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT DEFAULT NULL NOT SERIALIZED, TRUNK_GROUPOUT CHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT DEFAULT NULL NOT SERIALIZED, TRUNK_GROUPINCHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT DEFAULT NULL NOT SERIALIZED, CALLING_LAC CHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT DEFAULT NULL NOT SERIALIZED, CALLED_LAC CHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT DEFAULT NULL NOT SERIALIZED, CALLING_CELL CHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT DEFAULT NULL NOT SERIALIZED, CALLED_CELL CHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT DEFAULT NULL NOT SERIALIZED, HOME_AREA_CODE CHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT DEFAULT NULL NOT SERIALIZED, VISIT_AREA_CODE CHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT DEFAULT NULL NOT SERIALIZED, CALLED_HOME_CODE CHAR(30 CHARS) CHARACTER SET UTF8 COLLATE DEFAULT DEFAULT NULL NOT SERIALIZED, CALLED_CODE CHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT DEFAULT NULL NOT SERIALIZED, THIRD_HOME_CODE CHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT DEFAULT NULL NOT SERIALIZED, THIRD_CODE CHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT DEFAULT NULL NOT SERIALIZED, FORWARDCAUSE CHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT DEFAULT NULL NOT SERIALIZED, VPN_FLAG CHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT DEFAULT NULL NOT SERIALIZED, LONG_TYPE LARGEINT DEFAULT NULL NOT SERIALIZED, CARRY_TYPE CHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT DEFAULT NULL NOT SERIALIZED, CARRIER_CD CHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT DEFAULT NULL NOT SERIALIZED, CFEE LARGEINT DEFAULT NULL NOT SERIALIZED, ACCT_ITEM_TYPE_A LARGEINT DEFAULT NULL NOT SERIALIZED, LFEE LARGEINT DEFAULT NULL NOT SERIALIZED, ACCT_ITEM_TYPE_B LARGEINT DEFAULT NULL NOT SERIALIZED, FEE_ADD LARGEINT DEFAULT NULL NOT SERIALIZED, ACCT_ITEM_TYPE_C LARGEINT DEFAULT NULL NOT SERIALIZED, SERVID CHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT DEFAULT NULL NOT SERIALIZED, BILLING_MODE CHAR(30 CHARS) CHARACTER SET UTF8 COLLATEDEFAULT DEFAULT NULL NOT SERIALIZED, EVENT_TYPE LARGEINT DEFAULT NULL NOT SERIALIZED, PRODUCT_ID CHAR(30 CHARS) CHARACTER SET UTF8 COLLATE
[jira] [Commented] (TRAFODION-1605) sqstart hangs if ulimits not correct
[ https://issues.apache.org/jira/browse/TRAFODION-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388610#comment-15388610 ] ASF GitHub Bot commented on TRAFODION-1605: --- GitHub user traflm opened a pull request: https://github.com/apache/incubator-trafodion/pull/615 [TRAFODION-1605] sqstart hangs if ulimits not correct add ulimit checking in sqstart if not proper setup as Trafodion installer does, print WARNING/ERROR This should only happen in dev environment as described in the JIRA. Installer already handle this, so a WARNING/ERROR print should be enough. You can merge this pull request into a Git repository by running: $ git pull https://github.com/traflm/incubator-trafodion TRAFODION-1605-1 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafodion/pull/615.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #615 commit da42f9f94b13f4b6be6d46eb20e97e4352607b75 Author: Liu Ming Date: 2016-07-21T23:20:20Z [TRAFODION-1605] sqstart hangs if ulimits not correct > sqstart hangs if ulimits not correct > > > Key: TRAFODION-1605 > URL: https://issues.apache.org/jira/browse/TRAFODION-1605 > Project: Apache Trafodion > Issue Type: Bug > Components: Build Infrastructure >Reporter: Roberta Marton >Assignee: liu ming > > If someone downloads a source tar file or uses the Trafodion git repository, > after building they need to install the results on their system. If the > ulimits on the system are not sufficient, then sqlci start hangs. The > customer has to kill sqlci and then kill all the processes in flight. > This happens when you perform the build instructions and choose the > "install_local_hadoop" option. The Trafodion Installer should already be > checking for this situation. > Perhaps add a check before sqlci starts to make sure the correct limits are > set. > Recommended limits: > ulimit –a > core file size(blocks, -c) 100 > data seg size(kbytes, -d) unlimited > scheduling priority(-e) 0 > file size (blocks, -f) unlimited > pending signals(-i) 515196 > max locked memory (kbytes, -l) 49595556 > max memory size (kbytes, -m) unlimited > open files (-n) 32000 > pipe size (512 bytes, -p) 8 > POSIX message queues (bytes, -q) 819200 > real-time priority (-r) 0 > stack size (kbytes, -s) 10240 > cpu time (seconds, -t) unlimited > max user processes (-u) 267263 > virtual memory (kbytes, -v) unlimited > file locks (-x) unlimited -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2091) hdfsFS filesystem usage causies abnormal behavior in Trafodion
[ https://issues.apache.org/jira/browse/TRAFODION-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388598#comment-15388598 ] ASF GitHub Bot commented on TRAFODION-2091: --- Github user asfgit closed the pull request at: https://github.com/apache/incubator-trafodion/pull/614 > hdfsFS filesystem usage causies abnormal behavior in Trafodion > --- > > Key: TRAFODION-2091 > URL: https://issues.apache.org/jira/browse/TRAFODION-2091 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-general >Affects Versions: 2.1-incubating >Reporter: Sandhya Sundaresan >Assignee: Sandhya Sundaresan > > Several components use the libhdfs API to perform operations on hdfs files in > Trafodion. Some places use the JNI API as well to access hdfs. > The inconsistency observed was ehen one component cached and kept the hdfsFS > hande for it's use another part of the code would perform a "close" or a > dsconnect and prematurely close the hdfsFS handle which is currently being > used. The reason is that the hdfs layer seems to cache the hdfsFS handle > underneathThe solution now is to keep a list of hdfsFS handles at the global > context level. All disconnect calls and JNI close calls are remmoved. The > hdfHS handles will get cleaned up either at context destructor time or at > endSession time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-1605) sqstart hangs if ulimits not correct
[ https://issues.apache.org/jira/browse/TRAFODION-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388592#comment-15388592 ] ASF GitHub Bot commented on TRAFODION-1605: --- Github user traflm closed the pull request at: https://github.com/apache/incubator-trafodion/pull/597 > sqstart hangs if ulimits not correct > > > Key: TRAFODION-1605 > URL: https://issues.apache.org/jira/browse/TRAFODION-1605 > Project: Apache Trafodion > Issue Type: Bug > Components: Build Infrastructure >Reporter: Roberta Marton >Assignee: liu ming > > If someone downloads a source tar file or uses the Trafodion git repository, > after building they need to install the results on their system. If the > ulimits on the system are not sufficient, then sqlci start hangs. The > customer has to kill sqlci and then kill all the processes in flight. > This happens when you perform the build instructions and choose the > "install_local_hadoop" option. The Trafodion Installer should already be > checking for this situation. > Perhaps add a check before sqlci starts to make sure the correct limits are > set. > Recommended limits: > ulimit –a > core file size(blocks, -c) 100 > data seg size(kbytes, -d) unlimited > scheduling priority(-e) 0 > file size (blocks, -f) unlimited > pending signals(-i) 515196 > max locked memory (kbytes, -l) 49595556 > max memory size (kbytes, -m) unlimited > open files (-n) 32000 > pipe size (512 bytes, -p) 8 > POSIX message queues (bytes, -q) 819200 > real-time priority (-r) 0 > stack size (kbytes, -s) 10240 > cpu time (seconds, -t) unlimited > max user processes (-u) 267263 > virtual memory (kbytes, -v) unlimited > file locks (-x) unlimited -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2109) Load with log error rows returns the following error at times
[ https://issues.apache.org/jira/browse/TRAFODION-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388446#comment-15388446 ] ASF GitHub Bot commented on TRAFODION-2109: --- Github user selvaganesang closed the pull request at: https://github.com/apache/incubator-trafodion/pull/593 > Load with log error rows returns the following error at times > - > > Key: TRAFODION-2109 > URL: https://issues.apache.org/jira/browse/TRAFODION-2109 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-exe >Affects Versions: 1.3-incubating >Reporter: Selvaganesan Govindarajan >Assignee: Selvaganesan Govindarajan > Fix For: 2.1-incubating > > > load with log error rows into > select * from hive.hive. > *** ERROR[2034] $Z0014JQ:5192: Operating system error 201 while communicating > with server process $Z021FS0:425. > > *** ERROR[2034] $Z0014JQ:5192: Operating system error 201 while communicating > with server process $Z021FS0:425. > > *** ERROR[2034] $Z0014JQ:5192: Operating system error 201 while communicating > with server process $Z021FS0:425. > > --- 0 row(s) loaded. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2123) JAVA_HOME check error when using OPEN-JDK
Amanda Moran created TRAFODION-2123: --- Summary: JAVA_HOME check error when using OPEN-JDK Key: TRAFODION-2123 URL: https://issues.apache.org/jira/browse/TRAFODION-2123 Project: Apache Trafodion Issue Type: Bug Components: installer Reporter: Amanda Moran Assignee: Amanda Moran Priority: Minor When using open-jdk as java for JAVA_HOME installer will throw an error during version checking but will not exit. /home/jenkins/workspace/jdbc_test-cdh/traf_inst/installer/traf_config_check: line 436: [[: ": syntax error: operand expected (error token is """) /home/jenkins/workspace/jdbc_test-cdh/traf_inst/installer/traf_config_check: line 441: [[: ": syntax error: operand expected (error token is """) /home/jenkins/workspace/jdbc_test-cdh/traf_inst/installer/traf_config_check: line 448: [[: .: syntax error: operand expected (error token is ".") Install will continue and everything is fine (open jdk is fine to be used) but the error looks scary. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2091) hdfsFS filesystem usage causies abnormal behavior in Trafodion
[ https://issues.apache.org/jira/browse/TRAFODION-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388402#comment-15388402 ] ASF GitHub Bot commented on TRAFODION-2091: --- GitHub user sandhyasun opened a pull request: https://github.com/apache/incubator-trafodion/pull/614 Fix for leftover debug code causing several "connection refused" log messages related to [TRAFODION-2091] Removing some leftover debug code causing several "connection refused" messages in mon*.log files during regression runs.Related to [TRAFODION-2091] You can merge this pull request into a Git repository by running: $ git pull https://github.com/sandhyasun/incubator-trafodion sort_scratch Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafodion/pull/614.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #614 commit a6df821c654798bf48792de237dff15e96a35182 Author: Sandhya Sundaresan Date: 2016-07-21T20:42:07Z Remvoving some leftover debug code causing several "connection refused" messages in mon*.log files during regression runs.Related to [TRAFODION-2091] > hdfsFS filesystem usage causies abnormal behavior in Trafodion > --- > > Key: TRAFODION-2091 > URL: https://issues.apache.org/jira/browse/TRAFODION-2091 > Project: Apache Trafodion > Issue Type: Bug > Components: sql-general >Affects Versions: 2.1-incubating >Reporter: Sandhya Sundaresan >Assignee: Sandhya Sundaresan > > Several components use the libhdfs API to perform operations on hdfs files in > Trafodion. Some places use the JNI API as well to access hdfs. > The inconsistency observed was ehen one component cached and kept the hdfsFS > hande for it's use another part of the code would perform a "close" or a > dsconnect and prematurely close the hdfsFS handle which is currently being > used. The reason is that the hdfs layer seems to cache the hdfsFS handle > underneathThe solution now is to keep a list of hdfsFS handles at the global > context level. All disconnect calls and JNI close calls are remmoved. The > hdfHS handles will get cleaned up either at context destructor time or at > endSession time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2122) daily build master executor logs contain update statement exception
[ https://issues.apache.org/jira/browse/TRAFODION-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388155#comment-15388155 ] ASF GitHub Bot commented on TRAFODION-2122: --- GitHub user hegdean opened a pull request: https://github.com/apache/incubator-trafodion/pull/613 [TRAFODION-2122] daily build master executor logs contain update statement exception You can merge this pull request into a Git repository by running: $ git pull https://github.com/hegdean/incubator-trafodion wrkbrnch Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafodion/pull/613.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #613 commit 9f6edc66e3ee2aafea736ee409699791b87fdd37 Author: Anuradha Hegde Date: 2016-07-21T18:19:14Z [TRAFODION-2122] daily build master executor logs contain update statement exception Fixed the extra newline from sqcheck > daily build master executor logs contain update statement exception > > > Key: TRAFODION-2122 > URL: https://issues.apache.org/jira/browse/TRAFODION-2122 > Project: Apache Trafodion > Issue Type: Bug > Components: connectivity-mxosrvr >Affects Versions: 2.1-incubating >Reporter: Anuradha Hegde >Assignee: Anuradha Hegde > Fix For: 2.1-incubating > > > During analysis of master exec logs of daily build, the following message is > reported.. The update statement of metric query table is missing a comma > 2016-07-20 17:49:26,044, ERROR, MXOSRVR, Node Number: 0, CPU: 0, PIN:19960, > Process Name:$Z000GAA , , ,A NonStop Process Service error Failed to write > statistics: update Trafodion."_REPOS_".metric_query_table set STATEMENT_TYPE= > 'SQL_OTHER',STATEMENT_SUBTYPE= '',AGGREGATE_TOTAL= 0,STATS_ERROR_CODE= > 0,QUERY_ELAPSED_TIME= 104993409,SQL_PROCESS_BUSY_TIME= > 5257702,DISK_PROCESS_BUSY_TIME= 0,DISK_IOS= 0,NUM_SQL_PROCESSES= > 1,SQL_SPACE_ALLOCATED= 32,SQL_SPACE_USED= 5,SQL_HEAP_ALLOCATED= > 7,SQL_HEAP_USED= 2,TOTAL_MEM_ALLOC= 7,MAX_MEM_USED= 32756,NUM_REQUEST_MSGS= > 0,NUM_REQUEST_MSG_BYTES= 0,NUM_REPLY_MSGS= 0,NUM_REPLY_MSG_BYTES= > 0,ROWS_RETURNED_TO_MASTER= 0,EXEC_END_UTC_TS= > CONVERTTIMESTAMP(212335796966036136),MASTER_EXECUTION_TIME= > 6950943,MASTER_ELAPSED_TIME= 104993357,QUERY_STATUS= > 'COMPLETED',QUERY_SUB_STATUS= 'N/A',ERROR_CODE= 0,SQL_ERROR_CODE= > 0,ERROR_TEXT= '',LAST_ERROR_BEFORE_AQR= 0,DELAY_TIME_BEFORE_AQR_SEC= > 0,TOTAL_NUM_AQR_RETRIES= 0,MSG_BYTES_TO_DISK= 0,MSGS_TO_DISK= > 0,ROWS_ACCESSED= 0,ROWS_RETRIEVED= 0,NUM_ROWS_IUD= 0,PROCESSES_CREATED= > 0,PROCESS_CREATE_BUSY_TIME= 0,OVF_FILE_COUNT= 0,OVF_SPACE_ALLOCATED= > 32,OVF_SPACE_USED= 5,OVF_BLOCK_SIZE= 0,OVF_WRITE_READ_COUNT= > 0,OVF_WRITE_COUNT= 0,OVF_BUFFER_BLOCKS_WRITTEN= 0,OVF_BUFFER_BYTES_WRITTEN= > 0,OVF_READ_COUNT= 0,OVF_BUFFER_BLOCKS_READ= 0,OVF_BUFFER_BYTES_READ= > 0,NUM_NODES= 0,UDR_PROCESS_BUSY_TIME= 5257702,PERTABLE_STATS= > 0LAST_UPDATED_TIME= CONVERTTIMESTAMP(212335796966036168) where QUERY_ID = > 'MXID11199602123357961293524621006U409jdbc_test_2385_SQL_CUR_9' > and EXEC_START_UTC_TS = CONVERTTIMESTAMP(212335796861042732)Error detail > - *** ERROR[15001] A syntax error occurred at or before: > ...D_TO_MASTER= 0,EXEC_END_UTC_TS= > CONVERTTIMESTAMP(212335796966036136),MASTER_ > EXECUTION_TIME= 6950943,MASTER_ELAPSED_TIME= 104993357,QUERY_STATUS= > 'COMPLETED > ',QUERY_SUB_STATUS= 'N/A',ERROR_CODE= 0,SQL_ERROR_CODE= 0,ERROR_TEXT= > '',L > AST_ERROR_BEFORE_AQR= 0,DELAY_TIME_BEFORE_AQR_SEC= 0,TOTAL_NUM_AQR_RETRIES= > 0,M > SG_BYTES_TO_DISK= 0,MSGS_TO_DISK= 0,ROWS_ACCESSED= 0,ROWS_RETRIEVED= > 0,NUM_ROWS > _IUD= 0,PROCESSES_CREATED= 0,PROCESS_CREATE_BUSY_TIME= 0,OVF_FILE_COUNT= > 0,OVF_ > SPACE_ALLOCATED= 32,OVF_SPACE_USED= 5,OVF_BLOCK_SIZE= 0,OVF_WRITE_READ_COUNT= > 0 > ,OVF_WRITE_COUNT= 0,OVF_BUFFER_BLOCKS_WRITTEN= 0,OVF_BUFFER_BYTES_WRITTEN= > 0,OV > F_READ_COUNT= 0,OVF_BUFFER_BLOCKS_READ= 0,OVF_BUFFER_BYTES_READ= 0,NUM_NODES= > 0 > ,UDR_PROCESS_BUSY_TIME= 5257702,PERTABLE_STATS= 0LAST_UPDATED_TIME= > CONVERTTIME > ^ (1251 > characters from start of SQL statement) [2016-07-20 17:49:26] has occurred. > 2016-07-20 17:49:26,044, ERROR, MXOSRVR, Node Number: 0, CPU: 0, PIN:19960, > Process Name:$Z000GAA , , ,A NonStop Process Service error Failed to write > statistics: update Trafodion."_REPOS_".metric_query_table set STATEMENT_TYPE= > 'SQL_OTHER',STATEMENT_SUBTYPE= '',AGGREGATE_TOTAL= 0,STATS_ERROR_CODE= > 0,QUERY_ELAPSED_TIME= 104993409,SQL_PROCESS_BUSY_TIME= > 5257702,DISK_PROCESS_BUSY_TIME= 0,DISK_IOS= 0,
[jira] [Created] (TRAFODION-2122) daily build master executor logs contain update statement exception
Anuradha Hegde created TRAFODION-2122: - Summary: daily build master executor logs contain update statement exception Key: TRAFODION-2122 URL: https://issues.apache.org/jira/browse/TRAFODION-2122 Project: Apache Trafodion Issue Type: Bug Components: connectivity-mxosrvr Affects Versions: 2.1-incubating Reporter: Anuradha Hegde Assignee: Anuradha Hegde Fix For: 2.1-incubating During analysis of master exec logs of daily build, the following message is reported.. The update statement of metric query table is missing a comma 2016-07-20 17:49:26,044, ERROR, MXOSRVR, Node Number: 0, CPU: 0, PIN:19960, Process Name:$Z000GAA , , ,A NonStop Process Service error Failed to write statistics: update Trafodion."_REPOS_".metric_query_table set STATEMENT_TYPE= 'SQL_OTHER',STATEMENT_SUBTYPE= '',AGGREGATE_TOTAL= 0,STATS_ERROR_CODE= 0,QUERY_ELAPSED_TIME= 104993409,SQL_PROCESS_BUSY_TIME= 5257702,DISK_PROCESS_BUSY_TIME= 0,DISK_IOS= 0,NUM_SQL_PROCESSES= 1,SQL_SPACE_ALLOCATED= 32,SQL_SPACE_USED= 5,SQL_HEAP_ALLOCATED= 7,SQL_HEAP_USED= 2,TOTAL_MEM_ALLOC= 7,MAX_MEM_USED= 32756,NUM_REQUEST_MSGS= 0,NUM_REQUEST_MSG_BYTES= 0,NUM_REPLY_MSGS= 0,NUM_REPLY_MSG_BYTES= 0,ROWS_RETURNED_TO_MASTER= 0,EXEC_END_UTC_TS= CONVERTTIMESTAMP(212335796966036136),MASTER_EXECUTION_TIME= 6950943,MASTER_ELAPSED_TIME= 104993357,QUERY_STATUS= 'COMPLETED',QUERY_SUB_STATUS= 'N/A',ERROR_CODE= 0,SQL_ERROR_CODE= 0,ERROR_TEXT= '',LAST_ERROR_BEFORE_AQR= 0,DELAY_TIME_BEFORE_AQR_SEC= 0,TOTAL_NUM_AQR_RETRIES= 0,MSG_BYTES_TO_DISK= 0,MSGS_TO_DISK= 0,ROWS_ACCESSED= 0,ROWS_RETRIEVED= 0,NUM_ROWS_IUD= 0,PROCESSES_CREATED= 0,PROCESS_CREATE_BUSY_TIME= 0,OVF_FILE_COUNT= 0,OVF_SPACE_ALLOCATED= 32,OVF_SPACE_USED= 5,OVF_BLOCK_SIZE= 0,OVF_WRITE_READ_COUNT= 0,OVF_WRITE_COUNT= 0,OVF_BUFFER_BLOCKS_WRITTEN= 0,OVF_BUFFER_BYTES_WRITTEN= 0,OVF_READ_COUNT= 0,OVF_BUFFER_BLOCKS_READ= 0,OVF_BUFFER_BYTES_READ= 0,NUM_NODES= 0,UDR_PROCESS_BUSY_TIME= 5257702,PERTABLE_STATS= 0LAST_UPDATED_TIME= CONVERTTIMESTAMP(212335796966036168) where QUERY_ID = 'MXID11199602123357961293524621006U409jdbc_test_2385_SQL_CUR_9' and EXEC_START_UTC_TS = CONVERTTIMESTAMP(212335796861042732)Error detail - *** ERROR[15001] A syntax error occurred at or before: ...D_TO_MASTER= 0,EXEC_END_UTC_TS= CONVERTTIMESTAMP(212335796966036136),MASTER_ EXECUTION_TIME= 6950943,MASTER_ELAPSED_TIME= 104993357,QUERY_STATUS= 'COMPLETED ',QUERY_SUB_STATUS= 'N/A',ERROR_CODE= 0,SQL_ERROR_CODE= 0,ERROR_TEXT= '',L AST_ERROR_BEFORE_AQR= 0,DELAY_TIME_BEFORE_AQR_SEC= 0,TOTAL_NUM_AQR_RETRIES= 0,M SG_BYTES_TO_DISK= 0,MSGS_TO_DISK= 0,ROWS_ACCESSED= 0,ROWS_RETRIEVED= 0,NUM_ROWS _IUD= 0,PROCESSES_CREATED= 0,PROCESS_CREATE_BUSY_TIME= 0,OVF_FILE_COUNT= 0,OVF_ SPACE_ALLOCATED= 32,OVF_SPACE_USED= 5,OVF_BLOCK_SIZE= 0,OVF_WRITE_READ_COUNT= 0 ,OVF_WRITE_COUNT= 0,OVF_BUFFER_BLOCKS_WRITTEN= 0,OVF_BUFFER_BYTES_WRITTEN= 0,OV F_READ_COUNT= 0,OVF_BUFFER_BLOCKS_READ= 0,OVF_BUFFER_BYTES_READ= 0,NUM_NODES= 0 ,UDR_PROCESS_BUSY_TIME= 5257702,PERTABLE_STATS= 0LAST_UPDATED_TIME= CONVERTTIME ^ (1251 characters from start of SQL statement) [2016-07-20 17:49:26] has occurred. 2016-07-20 17:49:26,044, ERROR, MXOSRVR, Node Number: 0, CPU: 0, PIN:19960, Process Name:$Z000GAA , , ,A NonStop Process Service error Failed to write statistics: update Trafodion."_REPOS_".metric_query_table set STATEMENT_TYPE= 'SQL_OTHER',STATEMENT_SUBTYPE= '',AGGREGATE_TOTAL= 0,STATS_ERROR_CODE= 0,QUERY_ELAPSED_TIME= 104993409,SQL_PROCESS_BUSY_TIME= 5257702,DISK_PROCESS_BUSY_TIME= 0,DISK_IOS= 0,NUM_SQL_PROCESSES= 1,SQL_SPACE_ALLOCATED= 32,SQL_SPACE_USED= 5,SQL_HEAP_ALLOCATED= 7,SQL_HEAP_USED= 2,TOTAL_MEM_ALLOC= 7,MAX_MEM_USED= 32756,NUM_REQUEST_MSGS= 0,NUM_REQUEST_MSG_BYTES= 0,NUM_REPLY_MSGS= 0,NUM_REPLY_MSG_BYTES= 0,ROWS_RETURNED_TO_MASTER= 0,EXEC_END_UTC_TS= CONVERTTIMESTAMP(212335796966036136),MASTER_EXECUTION_TIME= 6950943,MASTER_ELAPSED_TIME= 104993357,QUERY_STATUS= 'COMPLETED',QUERY_SUB_STATUS= 'N/A',ERROR_CODE= 0,SQL_ERROR_CODE= 0,ERROR_TEXT= '',LAST_ERROR_BEFORE_AQR= 0,DELAY_TIME_BEFORE_AQR_SEC= 0,TOTAL_NUM_AQR_RETRIES= 0,MSG_BYTES_TO_DISK= 0,MSGS_TO_DISK= 0,ROWS_ACCESSED= 0,ROWS_RETRIEVED= 0,NUM_ROWS_IUD= 0,PROCESSES_CREATED= 0,PROCESS_CREATE_BUSY_TIME= 0,OVF_FILE_COUNT= 0,OVF_SPACE_ALLOCATED= 32,OVF_SPACE_USED= 5,OVF_BLOCK_SIZE= 0,OVF_WRITE_READ_COUNT= 0,OVF_WRITE_COUNT= 0,OVF_BUFFER_BLOCKS_WRITTEN= 0,OVF_BUFFER_BYTES_WRITTEN= 0,OVF_READ_COUNT= 0,OVF_BUFFER_BLOCKS_READ= 0,OVF_BUFFER_BYTES_READ= 0,NUM_NODES= 0,UDR_PROCESS_BUSY_TIME= 5257702,PERTABLE_STATS= 0LAST_UPDATED_TIME= CONVERTTIMESTAMP(212335796966036168) where QUERY_ID = 'MXID11199602123357961293524621006U409jdbc_test_2385_SQL_CUR_9' and EXEC_START_UTC_TS = CONVERTTIMESTAMP(212335796861042732)Error detail - ***
[jira] [Assigned] (TRAFODION-2121) add support of HIVE data type of DECIMAL
[ https://issues.apache.org/jira/browse/TRAFODION-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming reassigned TRAFODION-2121: --- Assignee: liu ming > add support of HIVE data type of DECIMAL > > > Key: TRAFODION-2121 > URL: https://issues.apache.org/jira/browse/TRAFODION-2121 > Project: Apache Trafodion > Issue Type: Sub-task > Components: sql-cmp >Reporter: liu ming >Assignee: liu ming > > support hive datatype DECIMAL and DECIMAL(p,s) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2121) add support of HIVE data type of DECIMAL
liu ming created TRAFODION-2121: --- Summary: add support of HIVE data type of DECIMAL Key: TRAFODION-2121 URL: https://issues.apache.org/jira/browse/TRAFODION-2121 Project: Apache Trafodion Issue Type: Sub-task Reporter: liu ming support hive datatype DECIMAL and DECIMAL(p,s) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-1605) sqstart hangs if ulimits not correct
[
https://issues.apache.org/jira/browse/TRAFODION-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387819#comment-15387819
]
ASF GitHub Bot commented on TRAFODION-1605:
---
Github user traflm commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/597#discussion_r71720083
--- Diff: core/sqf/sql/scripts/sqstart ---
@@ -245,6 +245,63 @@ function checkKerberos {
return 0
}
+function printExpectedUlimt {
+
+echoLog "desired \"ulimit -a\" output: "
+echoLog "="
+echoLog "core file size (blocks, -c) 100"
+echoLog "data seg size (kbytes, -d) unlimited"
+echoLog "scheduling priority (-e) 0"
+echoLog "file size (blocks, -f) unlimited"
+echoLog "pending signals (-i) 515196"
+echoLog "max locked memory (kbytes, -l) 49595556"
+echoLog "max memory size (kbytes, -m) unlimited"
+echoLog "open files (-n) 32000"
+echoLog "pipe size (512 bytes, -p) 8"
+echoLog "POSIX message queues (bytes, -q) 819200"
+echoLog "real-time priority (-r) 0"
+echoLog "stack size (kbytes, -s) 10240"
+echoLog "cpu time (seconds, -t) unlimited"
+echoLog "max user processes (-u) 267263"
+echoLog "virtual memory (kbytes, -v) unlimited"
+echoLog "file locks (-x) unlimited"
+echoLog "="
+
+}
+
+function checkUlimit {
+
+ #check ulimit -u
+ userProc=`cat /proc/sys/kernel/pid_max`
+ if [[ $userProc -gt 65535 ]] ; then
+echoLog "WARNING: detect issue during startup, please make sure your
ulimit setup correctly"
+echoLog "WARNING: max user processes is smaller than 267263"
--- End diff --
I will change it
> sqstart hangs if ulimits not correct
>
>
> Key: TRAFODION-1605
> URL: https://issues.apache.org/jira/browse/TRAFODION-1605
> Project: Apache Trafodion
> Issue Type: Bug
> Components: Build Infrastructure
>Reporter: Roberta Marton
>Assignee: liu ming
>
> If someone downloads a source tar file or uses the Trafodion git repository,
> after building they need to install the results on their system. If the
> ulimits on the system are not sufficient, then sqlci start hangs. The
> customer has to kill sqlci and then kill all the processes in flight.
> This happens when you perform the build instructions and choose the
> "install_local_hadoop" option. The Trafodion Installer should already be
> checking for this situation.
> Perhaps add a check before sqlci starts to make sure the correct limits are
> set.
> Recommended limits:
> ulimit –a
> core file size(blocks, -c) 100
> data seg size(kbytes, -d) unlimited
> scheduling priority(-e) 0
> file size (blocks, -f) unlimited
> pending signals(-i) 515196
> max locked memory (kbytes, -l) 49595556
> max memory size (kbytes, -m) unlimited
> open files (-n) 32000
> pipe size (512 bytes, -p) 8
> POSIX message queues (bytes, -q) 819200
> real-time priority (-r) 0
> stack size (kbytes, -s) 10240
> cpu time (seconds, -t) unlimited
> max user processes (-u) 267263
> virtual memory (kbytes, -v) unlimited
> file locks (-x) unlimited
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TRAFODION-1605) sqstart hangs if ulimits not correct
[
https://issues.apache.org/jira/browse/TRAFODION-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387817#comment-15387817
]
ASF GitHub Bot commented on TRAFODION-1605:
---
Github user traflm commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/597#discussion_r71719997
--- Diff: core/sqf/sql/scripts/sqstart ---
@@ -245,6 +245,63 @@ function checkKerberos {
return 0
}
+function printExpectedUlimt {
+
+echoLog "desired \"ulimit -a\" output: "
+echoLog "="
+echoLog "core file size (blocks, -c) 100"
+echoLog "data seg size (kbytes, -d) unlimited"
+echoLog "scheduling priority (-e) 0"
+echoLog "file size (blocks, -f) unlimited"
+echoLog "pending signals (-i) 515196"
+echoLog "max locked memory (kbytes, -l) 49595556"
+echoLog "max memory size (kbytes, -m) unlimited"
+echoLog "open files (-n) 32000"
+echoLog "pipe size (512 bytes, -p) 8"
+echoLog "POSIX message queues (bytes, -q) 819200"
+echoLog "real-time priority (-r) 0"
+echoLog "stack size (kbytes, -s) 10240"
+echoLog "cpu time (seconds, -t) unlimited"
+echoLog "max user processes (-u) 267263"
+echoLog "virtual memory (kbytes, -v) unlimited"
+echoLog "file locks (-x) unlimited"
+echoLog "="
+
+}
+
+function checkUlimit {
+
+ #check ulimit -u
+ userProc=`cat /proc/sys/kernel/pid_max`
+ if [[ $userProc -gt 65535 ]] ; then
+echoLog "WARNING: detect issue during startup, please make sure your
ulimit setup correctly"
--- End diff --
Yes, I agree.
> sqstart hangs if ulimits not correct
>
>
> Key: TRAFODION-1605
> URL: https://issues.apache.org/jira/browse/TRAFODION-1605
> Project: Apache Trafodion
> Issue Type: Bug
> Components: Build Infrastructure
>Reporter: Roberta Marton
>Assignee: liu ming
>
> If someone downloads a source tar file or uses the Trafodion git repository,
> after building they need to install the results on their system. If the
> ulimits on the system are not sufficient, then sqlci start hangs. The
> customer has to kill sqlci and then kill all the processes in flight.
> This happens when you perform the build instructions and choose the
> "install_local_hadoop" option. The Trafodion Installer should already be
> checking for this situation.
> Perhaps add a check before sqlci starts to make sure the correct limits are
> set.
> Recommended limits:
> ulimit –a
> core file size(blocks, -c) 100
> data seg size(kbytes, -d) unlimited
> scheduling priority(-e) 0
> file size (blocks, -f) unlimited
> pending signals(-i) 515196
> max locked memory (kbytes, -l) 49595556
> max memory size (kbytes, -m) unlimited
> open files (-n) 32000
> pipe size (512 bytes, -p) 8
> POSIX message queues (bytes, -q) 819200
> real-time priority (-r) 0
> stack size (kbytes, -s) 10240
> cpu time (seconds, -t) unlimited
> max user processes (-u) 267263
> virtual memory (kbytes, -v) unlimited
> file locks (-x) unlimited
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TRAFODION-1605) sqstart hangs if ulimits not correct
[
https://issues.apache.org/jira/browse/TRAFODION-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387784#comment-15387784
]
ASF GitHub Bot commented on TRAFODION-1605:
---
Github user selvaganesang commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/597#discussion_r71716869
--- Diff: core/sqf/sql/scripts/sqstart ---
@@ -245,6 +245,63 @@ function checkKerberos {
return 0
}
+function printExpectedUlimt {
+
+echoLog "desired \"ulimit -a\" output: "
+echoLog "="
+echoLog "core file size (blocks, -c) 100"
+echoLog "data seg size (kbytes, -d) unlimited"
+echoLog "scheduling priority (-e) 0"
+echoLog "file size (blocks, -f) unlimited"
+echoLog "pending signals (-i) 515196"
+echoLog "max locked memory (kbytes, -l) 49595556"
+echoLog "max memory size (kbytes, -m) unlimited"
+echoLog "open files (-n) 32000"
+echoLog "pipe size (512 bytes, -p) 8"
+echoLog "POSIX message queues (bytes, -q) 819200"
+echoLog "real-time priority (-r) 0"
+echoLog "stack size (kbytes, -s) 10240"
+echoLog "cpu time (seconds, -t) unlimited"
+echoLog "max user processes (-u) 267263"
+echoLog "virtual memory (kbytes, -v) unlimited"
+echoLog "file locks (-x) unlimited"
+echoLog "="
+
+}
+
+function checkUlimit {
+
+ #check ulimit -u
+ userProc=`cat /proc/sys/kernel/pid_max`
+ if [[ $userProc -gt 65535 ]] ; then
+echoLog "WARNING: detect issue during startup, please make sure your
ulimit setup correctly"
+echoLog "WARNING: max user processes is smaller than 267263"
--- End diff --
Please change the message accordingly. pid_max shouldn't be greater than
65535
> sqstart hangs if ulimits not correct
>
>
> Key: TRAFODION-1605
> URL: https://issues.apache.org/jira/browse/TRAFODION-1605
> Project: Apache Trafodion
> Issue Type: Bug
> Components: Build Infrastructure
>Reporter: Roberta Marton
>Assignee: liu ming
>
> If someone downloads a source tar file or uses the Trafodion git repository,
> after building they need to install the results on their system. If the
> ulimits on the system are not sufficient, then sqlci start hangs. The
> customer has to kill sqlci and then kill all the processes in flight.
> This happens when you perform the build instructions and choose the
> "install_local_hadoop" option. The Trafodion Installer should already be
> checking for this situation.
> Perhaps add a check before sqlci starts to make sure the correct limits are
> set.
> Recommended limits:
> ulimit –a
> core file size(blocks, -c) 100
> data seg size(kbytes, -d) unlimited
> scheduling priority(-e) 0
> file size (blocks, -f) unlimited
> pending signals(-i) 515196
> max locked memory (kbytes, -l) 49595556
> max memory size (kbytes, -m) unlimited
> open files (-n) 32000
> pipe size (512 bytes, -p) 8
> POSIX message queues (bytes, -q) 819200
> real-time priority (-r) 0
> stack size (kbytes, -s) 10240
> cpu time (seconds, -t) unlimited
> max user processes (-u) 267263
> virtual memory (kbytes, -v) unlimited
> file locks (-x) unlimited
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TRAFODION-1605) sqstart hangs if ulimits not correct
[
https://issues.apache.org/jira/browse/TRAFODION-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15387776#comment-15387776
]
ASF GitHub Bot commented on TRAFODION-1605:
---
Github user selvaganesang commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/597#discussion_r71716181
--- Diff: core/sqf/sql/scripts/sqstart ---
@@ -245,6 +245,63 @@ function checkKerberos {
return 0
}
+function printExpectedUlimt {
+
+echoLog "desired \"ulimit -a\" output: "
+echoLog "="
+echoLog "core file size (blocks, -c) 100"
+echoLog "data seg size (kbytes, -d) unlimited"
+echoLog "scheduling priority (-e) 0"
+echoLog "file size (blocks, -f) unlimited"
+echoLog "pending signals (-i) 515196"
+echoLog "max locked memory (kbytes, -l) 49595556"
+echoLog "max memory size (kbytes, -m) unlimited"
+echoLog "open files (-n) 32000"
+echoLog "pipe size (512 bytes, -p) 8"
+echoLog "POSIX message queues (bytes, -q) 819200"
+echoLog "real-time priority (-r) 0"
+echoLog "stack size (kbytes, -s) 10240"
+echoLog "cpu time (seconds, -t) unlimited"
+echoLog "max user processes (-u) 267263"
+echoLog "virtual memory (kbytes, -v) unlimited"
+echoLog "file locks (-x) unlimited"
+echoLog "="
+
+}
+
+function checkUlimit {
+
+ #check ulimit -u
+ userProc=`cat /proc/sys/kernel/pid_max`
+ if [[ $userProc -gt 65535 ]] ; then
+echoLog "WARNING: detect issue during startup, please make sure your
ulimit setup correctly"
--- End diff --
Thanks @traflm for the change. This is an error condition. Because you
have a way to flag it as ERROR, can you please change this to ERROR.
> sqstart hangs if ulimits not correct
>
>
> Key: TRAFODION-1605
> URL: https://issues.apache.org/jira/browse/TRAFODION-1605
> Project: Apache Trafodion
> Issue Type: Bug
> Components: Build Infrastructure
>Reporter: Roberta Marton
>Assignee: liu ming
>
> If someone downloads a source tar file or uses the Trafodion git repository,
> after building they need to install the results on their system. If the
> ulimits on the system are not sufficient, then sqlci start hangs. The
> customer has to kill sqlci and then kill all the processes in flight.
> This happens when you perform the build instructions and choose the
> "install_local_hadoop" option. The Trafodion Installer should already be
> checking for this situation.
> Perhaps add a check before sqlci starts to make sure the correct limits are
> set.
> Recommended limits:
> ulimit –a
> core file size(blocks, -c) 100
> data seg size(kbytes, -d) unlimited
> scheduling priority(-e) 0
> file size (blocks, -f) unlimited
> pending signals(-i) 515196
> max locked memory (kbytes, -l) 49595556
> max memory size (kbytes, -m) unlimited
> open files (-n) 32000
> pipe size (512 bytes, -p) 8
> POSIX message queues (bytes, -q) 819200
> real-time priority (-r) 0
> stack size (kbytes, -s) 10240
> cpu time (seconds, -t) unlimited
> max user processes (-u) 267263
> virtual memory (kbytes, -v) unlimited
> file locks (-x) unlimited
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (TRAFODION-2119) create table report strange WARNING when using store by and allow_nullable_unique_key_constraint CQD
[ https://issues.apache.org/jira/browse/TRAFODION-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming reassigned TRAFODION-2119: --- Assignee: liu ming > create table report strange WARNING when using store by and > allow_nullable_unique_key_constraint CQD > > > Key: TRAFODION-2119 > URL: https://issues.apache.org/jira/browse/TRAFODION-2119 > Project: Apache Trafodion > Issue Type: Bug >Reporter: liu ming >Assignee: liu ming > > cqd allow_nullable_unique_key_constraint 'on' ; > create table T_RH_DZSP > ( > s_orgcode CHAR(12) character set utf8, > s_applydate CHAR(8) character set utf8, > s_packnovarchar(8) character set utf8, > s_trecode CHAR(10) character set utf8, > s_trename varchar(60) character set utf8, > s_taxorgcodevarchar(12) character set utf8, > s_paybnkno varchar(12) character set utf8, > s_trano varchar(8) character set utf8, > s_orimsgno CHAR(4) character set utf8, > f_traamtnumeric(18,2), > s_payeropnbnkno varchar(12) character set utf8, > payeropbkname varchar(60) character set utf8, > s_handorgname varchar(200) character set utf8, > s_payacct varchar(32) character set utf8, > s_taxvouno varchar(20) character set utf8, > s_billdate CHAR(8) character set utf8, > s_taxpaycodevarchar(20) character set utf8, > s_taxpaynamevarchar(200) character set utf8, > c_budgettypeCHAR(1) character set utf8, > c_trimflag CHAR(1) character set utf8, > s_etpcode varchar(20) character set utf8, > s_etpname varchar(200) character set utf8, > s_etptype varchar(20) character set utf8, > s_bdgsbtcodevarchar(30) character set utf8, > s_bdgsbtnamevarchar(60) character set utf8, > s_limit CHAR(8) character set utf8, > s_taxtypecode CHAR(10) character set utf8, > s_taxkindname varchar(60) character set utf8, > c_bdglevel CHAR(1) character set utf8, > c_bdglevelname varchar(60) character set utf8, > s_taxstartdate CHAR(8) character set utf8, > s_taxenddateCHAR(8) character set utf8, > s_astflag varchar(35) character set utf8, > c_taxtype CHAR(1) character set utf8, > s_acct CHAR(8) character set utf8, > s_trastate CHAR(2) character set utf8, > s_remarkvarchar(60) character set utf8, > s_remark1 varchar(60) character set utf8, > s_remark2 varchar(60) character set utf8, > s_inputerid varchar(18) character set utf8, > ts_sysupdatevarchar(100) character set utf8, > s_seq varchar(100) character set utf8 > ) > store by (S_APPLYDATE) > salt using 48 partitions on (S_APPLYDATE) > ATTRIBUTES ALIGNED FORMAT > HBASE_OPTIONS > ( > DATA_BLOCK_ENCODING = 'FAST_DIFF', > -- COMPRESSION = 'SNAPPY', > MEMSTORE_FLUSH_SIZE = '1073741824' > ); > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > *** WARNING[8402] A string overflow occurred during the evaluation of a > character expression. > ***
[jira] [Created] (TRAFODION-2120) DCS master won't start if extra blank between node name and server numbers in file servers
Feng Qiang created TRAFODION-2120: - Summary: DCS master won't start if extra blank between node name and server numbers in file servers Key: TRAFODION-2120 URL: https://issues.apache.org/jira/browse/TRAFODION-2120 Project: Apache Trafodion Issue Type: Bug Components: connectivity-dcs Affects Versions: 2.1-incubating Reporter: Feng Qiang Priority: Minor the servers file in dcs conf dir, if there's extra blank between node name and number, dcs master won't start. esg08 8 esg09 8 esg10 8 esg11 8 esg12 8 esg13 8 esg14 8 esg15 8 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1869) 'initialized trafodion' failed on CentOS 7.2
[ https://issues.apache.org/jira/browse/TRAFODION-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jian Jin updated TRAFODION-1869: Assignee: Weiqing Xu (was: liu ming) > 'initialized trafodion' failed on CentOS 7.2 > > > Key: TRAFODION-1869 > URL: https://issues.apache.org/jira/browse/TRAFODION-1869 > Project: Apache Trafodion > Issue Type: Bug >Reporter: liu ming >Assignee: Weiqing Xu > > On CentOS 7.2, install Trafodion then run 'initialize trafodion' > >>initialize trafodion; > *** ERROR[2034] $Z000HQ0:48: Operating system error 201 while communicating > with server process $Z000I2H:52. > *** ERROR[2013] Server process tdm_arkcmp could not be created on \\NSK - > Operating system error 201. > *** ERROR[2002] Internal error: cannot create compiler. > *** ERROR[2005] Internal error: from compilation, no errors in diagnostics > yet for statement: control query shape hold; > *** ERROR[8822] The statement was not prepared. > --- SQL operation failed with errors. > related core is from tdm_arkcmp > Core was generated by `tdm_arkcmp SQMON1.1 0 0 022137 $Z000I2H > 192.168.0.10:56579 4 0'. > Program terminated with signal 11, Segmentation fault. > #0 0x in ?? () > Missing separate debuginfos, use: debuginfo-install trafodion-2.0.1-1.x86_64 > trafodion-2.0.1-devel.x86_64 > (gdb) bt > #0 0x in ?? () > #1 0x7f44a8552fc6 in SB_Thread::Sthr::time () at > /home/centos/traf-plus/core/sqf/export/include/seabed/int/thread.inl:115 > #2 0x7f44adebeef4 in fs_int_fs_file_awaitiox (pp_filenum=0x1603034, > ppp_buf=0x7ffe5d71b208, pp_xfercount=0x7ffe5d71b1f4, > pp_tag=0x7ffe5d71b1f8, pv_timeout=6, pp_segid=0x7ffe5d71b206, > pv_int=false, pv_ts=false) at fsi.cpp:1301 > #3 0x7f44adeb8a80 in BAWAITIOX (pp_filenum=0x1603034, > ppp_buf=0x7ffe5d71b5f8, pp_xfercount=0x7ffe5d71b60c, pp_tag=0x7ffe5d71b5f0, > pv_timeout=6, pp_segid=0x0) at fs.cpp:563 > #4 0x7f44b5d629e7 in GuaReceiveControlConnection::wait (this=0x1603020, > timeout=6, eventConsumed=, ipcAwaitiox=0x0) > at ../common/IpcGuardian.cpp:2692 > #5 0x7f44b5d643d8 in GuaReceiveControlConnection::waitForMaster > (this=0x1603020) at ../common/IpcGuardian.cpp:3603 > #6 0x00406366 in main () > (gdb) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2119) create table report strange WARNING when using store by and allow_nullable_unique_key_constraint CQD
liu ming created TRAFODION-2119: --- Summary: create table report strange WARNING when using store by and allow_nullable_unique_key_constraint CQD Key: TRAFODION-2119 URL: https://issues.apache.org/jira/browse/TRAFODION-2119 Project: Apache Trafodion Issue Type: Bug Reporter: liu ming cqd allow_nullable_unique_key_constraint 'on' ; create table T_RH_DZSP ( s_orgcode CHAR(12) character set utf8, s_applydate CHAR(8) character set utf8, s_packnovarchar(8) character set utf8, s_trecode CHAR(10) character set utf8, s_trename varchar(60) character set utf8, s_taxorgcodevarchar(12) character set utf8, s_paybnkno varchar(12) character set utf8, s_trano varchar(8) character set utf8, s_orimsgno CHAR(4) character set utf8, f_traamtnumeric(18,2), s_payeropnbnkno varchar(12) character set utf8, payeropbkname varchar(60) character set utf8, s_handorgname varchar(200) character set utf8, s_payacct varchar(32) character set utf8, s_taxvouno varchar(20) character set utf8, s_billdate CHAR(8) character set utf8, s_taxpaycodevarchar(20) character set utf8, s_taxpaynamevarchar(200) character set utf8, c_budgettypeCHAR(1) character set utf8, c_trimflag CHAR(1) character set utf8, s_etpcode varchar(20) character set utf8, s_etpname varchar(200) character set utf8, s_etptype varchar(20) character set utf8, s_bdgsbtcodevarchar(30) character set utf8, s_bdgsbtnamevarchar(60) character set utf8, s_limit CHAR(8) character set utf8, s_taxtypecode CHAR(10) character set utf8, s_taxkindname varchar(60) character set utf8, c_bdglevel CHAR(1) character set utf8, c_bdglevelname varchar(60) character set utf8, s_taxstartdate CHAR(8) character set utf8, s_taxenddateCHAR(8) character set utf8, s_astflag varchar(35) character set utf8, c_taxtype CHAR(1) character set utf8, s_acct CHAR(8) character set utf8, s_trastate CHAR(2) character set utf8, s_remarkvarchar(60) character set utf8, s_remark1 varchar(60) character set utf8, s_remark2 varchar(60) character set utf8, s_inputerid varchar(18) character set utf8, ts_sysupdatevarchar(100) character set utf8, s_seq varchar(100) character set utf8 ) store by (S_APPLYDATE) salt using 48 partitions on (S_APPLYDATE) ATTRIBUTES ALIGNED FORMAT HBASE_OPTIONS ( DATA_BLOCK_ENCODING = 'FAST_DIFF', -- COMPRESSION = 'SNAPPY', MEMSTORE_FLUSH_SIZE = '1073741824' ); *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation of a character expression. *** WARNING[8402] A string overflow occurred during the evaluation o
