HPE NonStop SQL/MX Error – 1762 Database database-name is not available.

In this blog post, let’s learn about the error message “1762 Database database-name is not available.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

1762 Database database-name is not available.

Reason for the Error

In the tenant mode, the application is trying to access a catalog of other databases.

In the non-tenant mode, the application is trying to drop a catalog or schema of the database, which is configured as a tenant.

Solution

In the tenant mode, use the catalog associated with the database the application has connected to or the catalog of a shared database.

In the nontenant mode, use the catalog which is not configured as a tenant database

Leave A Reply

Your email address will not be published. Required fields are marked *

You May Also Like

In this blog post, let’s learn about the client error message “EngineNotSupported with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022
In this blog post, let’s learn about the client error message “EngineVersionNotSupported with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022
In this blog post, let’s learn about the client error message “IncorrectDBClusterLockMode with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022