You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Create a database named 'db_iemr'.
Provide necessary privileges.
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
The text was updated successfully, but these errors were encountered:
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
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
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
The text was updated successfully, but these errors were encountered: