Hologres is deeply integrated with DataWorks. When you perform data analytics operations on a Hologres instance in the DataWorks console, an error may occur if you are not granted relevant permissions. This topic provides answers to some frequently asked questions (FAQ) about DataWorks permissions.

FAQ

Why is the Bind Hologres Database button unavailable on the Workspace Management page of a workspace?

  • Problem description
    When I bind a Hologres database to a workspace as a RAM user in the Computing Engine information section of the Workspace Management page in the DataWorks console, the Bind Hologres Database button is unavailable. The Bind Hologres Database button is unavailable on the Workspace Management page of a workspace
  • Cause
    • The RAM user does not have the permissions to manage the workspace.
    • The RAM user does not have development permissions on instances.
  • Solution
    • If the RAM user does not have the permissions to manage the workspace, grant the RAM user relevant permissions on the User Management page. For more information, see Manage workspace-level roles and members.
    • If the RAM user does not have development permissions on instances, log on to the Hologres console and grant the RAM user relevant permissions based on different permission models.

Why does the connectivity test fail when I bind a Hologres database to a workspace?

  • Problem description

    After I set the parameters in the Bind Hologres Database dialog box and click Test Connectivity in the DataWorks console, the connectivity test fails. The error message Test failed appears.

  • Cause
    When you bind a Hologres database, you must configure relevant information such as the type of the access account, the name of the Hologres instance, and the name of the Hologres database, as shown in the following figure. An error message appears if the information that you enter is invalid or the account does not have the permissions to perform the operation. Bind Hologres Database
  • Solution
    1. Check the status of the Hologres instance.

      Log on to the Hologres console and click Instances in the left-side navigation pane. The Hologres Instances page appears. Check whether the instance that you select from the Hologres instance name drop-down list in the Bind Hologres Database dialog box is in the Running state.

    2. Check whether the database exists.

      If the status of the instance is normal, click the Database Management tab of the instance details page to go to the Database Authorization tab. Check whether the database name that you enter in the Database name field of the Bind Hologres Database dialog box exists. If the database name does not exist, enter the name of an existing database or create a database. For more information, see Manage databases.

    3. Check whether the current account has the permissions to access the instance.

      Click the Users tab of the instance details page to go to the User Management tab. View permissions of the current account. If the current RAM user does not have the permissions to access the instance, add the user and grant relevant permissions to the user. For more information, see Manage users.

Why does the error message "Calculate engine instance already exists" or "Internal tenant system error" appear when I bind a Hologres database to a workspace?

  • Problem description

    After I set the parameters in the Bind Hologres Database dialog box and click Confirm, the error message Calculate engine instance already exists or "Internal tenant system error" appears.

  • Cause

    The name that you enter in the Instance Display Name field already exists.

  • Solution

    Enter another name in the Instance Display Name field and click Confirm.

Why does the error message "permission denied" appear when I query a table on the DataService Studio page?

  • Problem description

    I cannot query a table on the DataService Studio page in the DataWorks console. The following error message appears: Execution failed: ERROR: permission denied for table xxxx.

  • Cause

    The RAM user that configures the Hologres connection does not have the permissions to query the table.

  • Solution
    1. Check whether the information about the RAM user that configures the Hologres connection is valid.

      Log on to the DataWorks console, go to the Data Source page, and then check whether the information about the RAM user that configures the Hologres connection is valid. For more information, see Add a Hologres data source.

    2. Check whether the RAM user that configures the Hologres connection has the permissions to view the table.

      Log on to the DataWorks console, go to the Data Source page, and then check whether the RAM user that configures the Hologres connection has the permissions to view the table. For more information, see Use the RAM authorization mode to configure connections to data stores.

      For more information about DataWorks permissions and relevant authorization operations, see Permissions of built-in workspace-level roles.

Why does the error message permission denied for schema xxx appear in the production environment of a DataWorks workspace?

  • Problem description

    When I publish SQL statements to the production environment of a DataWorks workspace, the following error message appears: permission denied for schema xxx.

  • Cause

    The current account that is used to access the Hologres instance in the production environment does not have access permissions on the schema that stores objects of the Hologres instance.

  • Solution
    1. Go to the Workspace Settings page of the DataWorks workspace to check the account that is used to access the Hologres instance in the production environment. For more information, see Configure a workspace.
    2. Log on to the HoloWeb console. In the top navigation bar, click Security Center. In the left-side navigation pane, click User Management or Database Authorization and view the permissions granted to the account.
    3. If the account has no access permissions on the schema, grant the relevant permissions on the User Management or Database Authorization page. For more information, see Manage databases.