[
https://issues.apache.org/jira/browse/TRAFODION-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15768158#comment-15768158
]
Arvind Narain commented on TRAFODION-2411:
------------------------------------------
mxosrvr tries to clear compiler cache if the modification timestamp of the
registered user has changed from the earlier session. Current code calls the
following. This error outs and mxosrvr exits since the syntax for these
statements has changed.
For the concern about the session getting connected as DB__ROOT - that's the
previous authenticated session under which "connect qauser10/mypasswd" was
given - the corresponding mxosrvr for that new connection exits hence we get
"server aborted .." message. If a disconnect is done and then a "connect
qauser10/mypasswd" and teh server dies then there will not be any authenticated
session.
// Clear compiler cache by executing the following DELETE statements
//
// DELETE ALL FROM TABLE(QUERYCACHE())
// DELETE ALL FROM TABLE(NATABLECACHE())
2016-12-19 18:21:46,667, ERROR, SQL, Node Number: 0, CPU: 1, PIN: 62957,
Process Name: $Z011GDS, SQLCODE: 15001, QID:
MXID11001062957212348796438435753000000000506U3334700_650_STMT_CMP_CACHE_RESET_1,
*** ERROR[15001] A syntax error occurred at or before:
DELETE ALL FROM TABLE(QUERYCACHE());
^ (34 characters from start of SQL statement)
2016-12-19 18:21:46,667, ERROR, MXOSRVR, Node Number: 1, CPU: 1, PID:62957,
Process Name:$Z011GDS , , ,ODBC/MX client fails to connect due to error Error
while clearing internal compiler cache in setting up
the connection context COMPILER_CACHE_RESET.
2016-12-19 18:21:46,667, ERROR, MXOSRVR, Node Number: 1, CPU: 1, PID:62957,
Process Name:$Z011GDS , , ,ODBC/MX client fails to connect due to error Error
while clearing internal compiler cache in setting up
the connection context COMPILER_CACHE_RESET.
2016-12-19 18:21:46,667, ERROR, MXOSRVR, Node Number: 1, CPU: 1, PID:62957,
Process Name:$Z011GDS , , ,ODBC/MX client fails to connect due to error Fatal
Error - Server exiting in setting up
the connection context COMPILER_CACHE_RESET.
> 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)
