mxosrvr failing to write to repos session and aggr metric table when we test connection from odbc administrator, errors in master log

[Aruna Sadashiva]

After trying etst connection from odbc administrator on Windows, the following errors are logged in the master log file and there are no rows inserted into the metric session and aggr tables. The test connection succeeds.

2015-04-27 17:54:28,169, ERROR, SQL, Node Number: 0, CPU: 3, PIN: 20885, Process Name: $Z030H1Q, SQLCODE: 15001, QID: MXID11003020885212296917167849521000000000306U3333300_483_STMT_PUBLICATION, *** ERROR[15001] A syntax error occurred at or before:
insert into Trafodion."_REPOS_".metric_query_aggr_table values(0,0,0,20885,2088
5,3,0,0,'16.235.158.28',0,'$Z030H1Q','MXID1100302088521229691716784952100000000
0406U3333300',CONVERTTIMESTAMP(212296917268168600),CONVERTTIMESTAMP(21229691726
8168603),60000,33333,'DB__ROOT','NONE','SARUNA2','saruna','Trafodion ODBC Data
Source 'amethyst' Configuration',0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
               ^ (332 characters from start of SQL statement)
2015-04-27 17:54:28,169, ERROR, MXOSRVR, Node Number: 3, CPU: 3, PIN:20885, Process Name:$Z030H1Q , , ,A NonStop Process Service error Failed to write statistics: insert into Trafodion."_REPOS_".metric_query_aggr_table values(0,0,0,20885,20885,3,0,0,'16.235.158.28',0,'$Z030H1Q','MXID11003020885212296917167849521000000000406U3333300',CONVERTTIMESTAMP(212296917268168600),CONVERTTIMESTAMP(212296917268168603),60000,33333,'DB__ROOT','NONE','SARUNA2','saruna','Trafodion ODBC Data Source 'amethyst' Configuration',0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0)----Error detail - *** ERROR[15001] A syntax error occurred at or before:
insert into Trafodion."_REPOS_".metric_query_aggr_table values(0,0,0,20885,2088
5,3,0,0,'16.235.158.28',0,'$Z030H1Q','MXID1100302088521229691716784952100000000
0406U3333300',CONVERTTIMESTAMP(212296917268168600),CONVERTTIMESTAMP(21229691726
8168603),60000,33333,'DB__ROOT','NONE','SARUNA2','saruna','Trafodion ODBC Data
Source 'amethyst' Configuration',0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
               ^ (332 characters from start of SQL statement) [2015-04-27 17:54:28] has occurred.

2015-04-27 17:54:33,241, ERROR, SQL, Node Number: 0, CPU: 3, PIN: 20885, Process Name: $Z030H1Q, SQLCODE: 15001, QID: MXID11003020885212296917167849521000000000306U3333300_487_STMT_PUBLICATION, *** ERROR[15001] A syntax error occurred at or before:
insert into Trafodion."_REPOS_".metric_session_table values(0,0,0,20885,20885,3
,0,0,'16.235.158.28',0,'$Z030H1Q','MXID1100302088521229691716784952100000000040
6U3333300','END',CONVERTTIMESTAMP(212296917268168600),CONVERTTIMESTAMP(21229691
7273198784),33333,'DB__ROOT','NONE','SARUNA2','saruna','Trafodion ODBC Data Sou
rce 'amethyst' Configuration',0,0,0,0,0,0,0,0,0,0,0,0,0,0,5827,29,0,0,0,0,0);
            ^ (329 characters from start of SQL statement)
2015-04-27 17:54:33,241, ERROR, MXOSRVR, Node Number: 3, CPU: 3, PIN:20885, Process Name:$Z030H1Q , , ,A NonStop Process Service error Failed to write statistics: insert into Trafodion."_REPOS_".metric_session_table values(0,0,0,20885,20885,3,0,0,'16.235.158.28',0,'$Z030H1Q','MXID11003020885212296917167849521000000000406U3333300','END',CONVERTTIMESTAMP(212296917268168600),CONVERTTIMESTAMP(212296917273198784),33333,'DB__ROOT','NONE','SARUNA2','saruna','Trafodion ODBC Data Source 'amethyst' Configuration',0,0,0,0,0,0,0,0,0,0,0,0,0,0,5827,29,0,0,0,0,0)----Error detail - *** ERROR[15001] A syntax error occurred at or before:
insert into Trafodion."_REPOS_".metric_session_table values(0,0,0,20885,20885,3
,0,0,'16.235.158.28',0,'$Z030H1Q','MXID1100302088521229691716784952100000000040
6U3333300','END',CONVERTTIMESTAMP(212296917268168600),CONVERTTIMESTAMP(21229691
7273198784),33333,'DB__ROOT','NONE','SARUNA2','saruna','Trafodion ODBC Data Sou
rce 'amethyst' Configuration',0,0,0,0,0,0,0,0,0,0,0,0,0,0,5827,29,0,0,0,0,0);
            ^ (329 characters from start of SQL statement) [2015-04-27 17:54:33] has occurred.

[Judy Zhao (hongxia-zhao)]

In fixing bug 1449195 ,I found that the application name is in following format: Trafodion ODBC Data Source+’DATA SOURCE NAME‘ Configuration when I test connection from MS ODBC Administrator. For example it is: Trafodion ODBC Data Source 'JuneOne' Configuration . Here JuneOne is the Data Source name.
While if I connect from Trafci, the application name is TRAFCI.
The APPLICATION_NAME is one column of table
TRAFODION."_REPOS_".METRIC_QUERY_AGGR_TABLE and TRAFODION."_REPOS_".METRIC_SESSION_TABLE.
Currently we can't get the application name as "Trafodion ODBC Data Source 'JuneOne' Configuration " from the tables without the fixing.
While with the fixing ,we will get the application name as above.

So I have another question :
It is ODBC driver that send the application name to server side. So can connectivity guys help to check if the string is correct or not?
If the name is incorrect, maybe need to file another bug for that.