I'm migrating Magento 1.7.2 to Magento 2.3.4 with respect to Magento data migration documentation. However I'm getting below error after post processing.
SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mgn_' doesn't exist, query was: SELECT COUNT(*) FROM mgn_
I'm unable to figure out issue, since error comes with prefix alone and no table is mentioned.
[WARNING]: Mismatch of entities in the document: mgn_inventory_source_item Source: 3311 Destination: 3307 [WARNING]: Volume Check failed [INFO][mode: data][stage: data migration][step: PostProcessing Step]: started 92% [=========================>--] Remaining Time: 1 sec In Mysql.php line 110: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mgn_' doesn't exist, query was: SELECT COUNT(*) FROM mgn_
Solved! Go to Solution.
As mentioned in above comment, this issue is with respect to latest Magento version 2.3.4. Issue has been reported and fixed in github -791.
Thank you guys for the support and suggestions.
Hello @Pkrishna
Are you using prefix on magento 1 or magento2?
if you are using into magento1 then you need to configure into config.xml file.
If you are using into magento 2 then remove it and install without prefix.
hope it will help you.
I'm using prefix in both Magento 1.7.0.2 and Magento 2.3.4. Can't I use prefix in Magento 2 ?
Hello @Pkrishna
you can use it but you must need to add into config.xml file
here you can see more info that
https://devdocs.magento.com/guides/v2.3/migration/migration-tool-configure.html
Table prefix: <source_prefix>
, <dest_prefix>
hope it will help you.
Hi @Sunil Patel ,
I have updated config.xml, as per documentation.
I have created this as issue in github -791 and testing on the provided patch. I'm currently checking on it. Will let you know once done. Thanks for your help and support.
You can consult this dev doc: https://devdocs.magento.com/guides/v2.3/migration/migration-tool-configure.html.
You need to pay attention to part 5 of Configure migration in vendor folder, please config correctly database name.
I ensured configuration is setup as per documentation. Issue appears in Magento 2.3.4 only.
As mentioned in above comment, this issue is with respect to latest Magento version 2.3.4. Issue has been reported and fixed in github -791.
Thank you guys for the support and suggestions.