Skip to main content

Account restoration mysql username too long

Comments

4 comments

  • cPanelMichael
    Hello, Is "Require a username prefix on names of new databases and database users" enabled under the "SQL" tab in "WHM >> Tweak Settings" on this system? Also, could you let us know how long the account and database usernames are? Thank you.
    0
  • MarkoTitel
    Hi, thanks for quick reply It is enabled on both servers. Both servers are same version. Database username is 19 characters long on the server that is in production. Cpanel username is 15 chars long. If char number is restricted how come on the working server I never got a warning and DB creation works fine.
    0
  • cPanelMichael
    Database username is 19 characters long on the server that is in production. Cpanel username is 15 chars long.

    Hello, Documentation on this topic is available at: _MySQL Username Limit - Documentation - cPanel Documentation Here's a quote from this document: MySQL limits the database username to 16 characters. The system includes the database prefix (the first eight characters of the cPanel account's username and an underscore character) in the character count for the username. For example: [LIST]
  • A MySQL database with the db_ prefix allows usernames that contain up to 13 characters.
  • A MySQL database with the example_ prefix allows usernames that contain up to eight characters.
    Is the server where the username was created using MariaDB? If so, you may want to upgrade the destination server to use MariaDB, as it allows for longer usernames: MariaDB limits the database username to 47 characters. The system includes the database prefix (all of the cPanel account's username and an underscore character) in the character count for the username. For example: [LIST]
  • A MariaDB database with the db_ prefix allows usernames that contain up to 44 characters.
  • A MariaDB database with the example_ prefix allows usernames that contain up to 39 characters.
    Thank you.
  • 0
  • MarkoTitel
    Yes MysqlDB was instead of MariaDB. After I updated to MariaDB I had no problems. Thanks
    0

Please sign in to leave a comment.