Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error Encountered While Restoring Database (Mysql 5.7) #71

Open
prasannajeet-01 opened this issue Oct 9, 2023 · 0 comments
Open

Error Encountered While Restoring Database (Mysql 5.7) #71

prasannajeet-01 opened this issue Oct 9, 2023 · 0 comments
Assignees

Comments

@prasannajeet-01
Copy link

prasannajeet-01 commented Oct 9, 2023

Description
Encountering the following error during database restoration: ERROR 1100 (HY000) at line 2259: Table 'm_ProviderServiceMapping' was not locked with LOCK TABLES

Steps to Reproduce

  1. Create a database named 'db_iemr'.
  2. Provide necessary privileges.
  3. Execute the following commands:
    mysql -h localhost -P 3306 -u root -p db_iemr < db_iemr.sql
    mysql -h localhost -P 3306 -u root -p db_iemr < db_iemr_logins_dummydata.sql

Expected Behavior
Expecting the restoration process to complete successfully without any errors.

Actual Behavior
ERROR 1100 (HY000) at line 2259: Table 'm_ProviderServiceMapping' was not locked with LOCK TABLES

Additional Context

  • MySQL Version: 5.7
  • This error occurs specifically during the restoration process for the 'm_ProviderServiceMapping' table.

Possible Solution
One possible solution is to remove the problematic insert statement for the 'm_ProviderServiceMapping' table. However, this is not a preferred solution as it may lead to data inconsistencies.

Labels

  • bug
  • database
  • restoration
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants