HPE NonStop SQL/MX Error – 1653 External-user-name is not a valid external username.

In this blog post, let’s learn about the error message “1653 External-user-name is not a valid external username.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

1653 External-user-name is not a valid external username.

Reason for the Error

You specified a Guardian username in the CREATE USER command that is not valid. Either because it is one of the special authorization Ids ‘PUBLIC’, ‘DB_PUBLIC’, or ‘SYSTEM’, or because it contains one or more spaces, or because it has a valid Guardian username format.

Solution

Specify a valid external username in the CREATE USER command and resubmit

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