Nancy506

Results 8 comments of Nancy506

new connection failed with error 'Error getting JDBC meta data: invalid operation: permission denied for schema information)schema' #18931

yes, it is a user I do not want to grant usage to information_schema.

new connection failed with error 'Error getting JDBC meta data: invalid operation: permission denied for schema information)schema' #18931

I was able to create new connection for that user on my other laptop though, the permission issue does not seem to hinder the new connection. It is only for...

new connection failed with error 'Error getting JDBC meta data: invalid operation: permission denied for schema information)schema' #18931

[](url) ![image001](https://user-images.githubusercontent.com/34636919/216572244-b4ecadba-96c2-44d2-9e70-50264a50ef12.png)

new connection failed with error 'Error getting JDBC meta data: invalid operation: permission denied for schema information)schema' #18931

Thanks! will do. my other device is not with me right now, so bear with me for a few days.

new connection failed with error 'Error getting JDBC meta data: invalid operation: permission denied for schema information)schema' #18931

here is the log file. Thanks! [log.txt](https://github.com/dbeaver/dbeaver/files/10673139/log.txt)

new connection failed with error 'Error getting JDBC meta data: invalid operation: permission denied for schema information)schema' #18931

also this one: 2023-02-01 12:45:01.749 - Service 'org.jkiss.dbeaver.runtime.ui.UIServiceSecurity' not found

new connection failed with error 'Error getting JDBC meta data: invalid operation: permission denied for schema information)schema' #18931

Can you elaborate more on this? the driver I use is the default driver provided by DBeaver for connecting to Redshift: com.amazon.redshift..jdbc42.Driver and it works fine in my other devices....

new connection failed with error 'Error getting JDBC meta data: invalid operation: permission denied for schema information)schema' #18931

Thanks Arhayka! I have granted user access to information schema and this problem goes away. Will check the libraries in the future if similar problems occurs