My Oracle Support Banner

Accessing HUE Metastore Manager in BDA 4.4.0/CDH 5.5.1 Gives Errors: "Failed to retrieve tables for database..." and "Unable to access databases. Query Server or Metastore may be down" (Doc ID 2279625.1)

Last updated on NOVEMBER 08, 2022

Applies to:

Big Data Appliance Integrated Software - Version 4.4.0 and later
Information in this document applies to any platform.


NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner. 

An error is raised on BDA V4.4.0/CDH 5.5.1 when navigating to the HUE Metastore Manager (HMS) via the web browser.

Failed to retrieve tables for database: mydb

Bad status for request TFetchResultsReq(fetchType=0, operationHandle=TOperationHandle(hasResultSet=True, modifiedRowCount=None, operationType=0, operationId=THandleIdentifier(secret=*, guid=")\*")), orientation=0, maxRows=5000): TFetchResultsResp(status=TStatus(errorCode=0, errorMessage='Expected state FINISHED, but found ERROR', sqlState=None, infoMessages=['*org.apache.hive.service.cli.HiveSQLException:Expected state FINISHED, but found ERROR:26:25', '', '', '', '', 'sun.reflect.GeneratedMethodAccessor15:invoke::-1', '', '', '', 'org.apache.hive.service.cli.session.HiveSessionProxy:access$', 'org.apache.hive.service.cli.session.HiveSessionProxy$', '', '', '', '', 'com.sun.proxy.$Proxy19:fetchResults::-1', '', '', 'org.apache.hive.service.cli.thrift.TCLIService$Processor$FetchResults

This happens for only one user and this same user also encounters errors when trying to to run a query in Hue (i.e. using a describe command):

"Expected state FINISHED, but found ERROR

Your query has the following error(s):
Unable to access databases. Query Server or Metastore may be down."

This problem happens with both Google Chrome and Internet Explorer web browsers and persists even after clearing the browser cache. The user that encounters this error is a member of a group called '<group_name>.' Other users in this same group, do not experience the error.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.