|
Problem IT10349
|
Status: Closed |
NOSQL WIRE LISTENER WILL REPORT "UNABLE TO LIST DATABASES" FROM LISTDATABASES CALL IF THE USER DOES NOT HAVE CONNECT PERMISSIONS |
| product: |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 |
| Problem description: |
When executing a listDatabases call against the NOSQL Wire
Listener version 1.1.1_20140611-1642, an SQLException of "No
connect permission" is reported to the log file when the user
does not have Connect permissions granted to a particular
database. This will then be followed by an error -349 and the
message "Unable to list databases"
The same call, when issued from the older Wire Listener version
1.0.0_20140127-1642 will execute without error.
The error posted to the Wire Listener log file will be displayed
as:
2015-07-16 14:48:51 [JsonListener-1-thread-2] ERROR
com.ibm.arcs.database.univer
sal.connection.pool.BasicConnectionPool - Cannot connect to
database <database name>:
java.sql.SQLException: No connect permission.
...
...
2015-07-16 14:48:53 [JsonListener-1-thread-2] ERROR
com.ibm.nosql.informix.jsonapi.SharedDB - SQLCODE: -349
Database not selected yet.
2015-07-16 14:48:53 [JsonListener-1-thread-2] ERROR Session-2 -
Unable to list databases |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Customers running the wire listener with a user that does *
* not have permissions to connect to all databases. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to a version of the wire listener post 12.10.xC5W1. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.07.2015
09.12.2016
09.12.2016 |
| Problem solved at the following versions (IBM BugInfos) |
12.10.xC5
|
| Problem solved according to the fixlist(s) of the following version(s) |
