Let us examine and look at the possible scenario that triggers the error access to system schema ‘MySQL’ is rejected. We will look at the troubleshooting steps necessary to remove the error with the support of MySQL support services at Bobcares.

ERROR 3552 (HY000): Access to System Schema ‘mysql’ Rejection.

As the MySQL base is a system in MySQL8, the —add-drop-database and —all-databases attributes clash, resulting in an error in the restoration “ERROR 3552 (HY000) at line 19044: Access to system schema error 352’mysql’  reject.”

Troubleshooting methods:

• The error SQL:

  /*!40000 DROP DATABASE IF EXISTS `mysql`*/;

  The simplest way around this is to open the dump SQL file, remove this SQL, and use sed if the file is too large.
• When dumping a broken instance with all databases and using add-drop-statement to try to preserve the data, we are likely to get the ‘access to system schema ‘mysql’ is refusal’ error.

  In this process, we will be stymied. As a result, we are no longer able to delete the MySQL system database.

  Consider that the database that we have is at 150GB, and opening it manually is not an option. The statement to remove in this case was as shown below:

  /*!40000 DROP DATABASE IF EXISTS `mysql`*/;

  In this scenario, the sed command is:

  sed -i 's/\/\*!40000 DROP DATABASE IF EXISTS `mysql`\*\/;/ /g' backup.sql

One approach to dealing with the access to system schema ‘MySQL’ rejection scenario is to first paste the statement into an empty text file, then execute the program to ensure that it works.

In this manner, we don’t spend time running a very big backup file, because the version of sed, or the operating system, may resolve the regular expression differently.

Finally, we can check whether the resolution of the error is successful or not by updating the MySQL Services.

[Need assistance with similar queries? We are here to help]

Conclusion

To conclude we have now gone through the error that access to system schema ‘MySQL’ is rejected. We have also seen the reasons and the troubleshooting method necessary to remove the error.

With the support of our MySQL support services, we have gone through all of the possible troubleshooting and configurations to deal with this error.