I am trying to run a delta copy following a full migration of all entities from M1 to M2. When I look at the admin config I see some extras categories but I am unable to select them, why is this?
Further to this some test copies on attributes run and say complete but only update the existing entities and not new additions (with higher Ids) so it doesnt seem to know about these.
Can you also confirm the correct ‘status’ id for the update mode to run within the ub_migrate_step within the database?
-
My main problem is that I can't run deltas and I've tried everything I can think of including playing with the status of the step, CLI, admin etc.. It appears that it doesn't recognise that there are new items in the source database, is there some sort of caching that would need to be reset? Or something to force it to look at the number of source records?I'm unfortunetely on a super tight deadline so any quick help is appreciated
31 answers
Hi there,
When I look at the admin config I see some extras categories but I am unable to select them, why is this?
Please tell me know what is the version of our module in your instance now?
Regards,
Mall.
Hello,
I am on module version: 3.1.3
3.1.3
Please bare in mind I am deep into a big big migration already so I can’t restart the process as it takes a long time to complete due to the size.
I can upgrade the extension if you think it will help? but dont want to have to restart
Hi there,
I can upgrade the extension if you think it will help?
What is the version of your M2 instance?
Regards,
Mall.
We are using
2.3.1
Hi there,
We are using
2.3.1
So, you must upgrade to latest version of our module ver.3.1.9 and then you could run delta migration in the step #4 to migrated for newly added categories in M1 as you mentioned.
php -f bin/ubdatamigration run --step=4 --mode=update
Regards,
Mall.
I ran a test on the attributes and it said it migrated 94 items but this isn’t including a bunch of new attributes added to M1. So it still doesnt seem to be working for me
I have upgraded the module and verified in setup_module that it is on 3.1.9 before the above
I have upgraded the module and verified in setup_module that it is on 3.1.9 before the above
Hi there,
I ran a test on the attributes and it said it migrated 94 items but this isn’t including a bunch of new attributes added to M1.
Lets try run delta migration in step #3 with update mode by run below CLI command:
php -f bin/ubdatamigration run --step=3 --mode=update
And tell me know how it goes.
Regards,
Mall.
It does the same thing, it completes it but with the original sync numbers not the added attributes.
Its like it isn’t detecting that there has been a change in the M1 DB. How does it do this? Using the ub_ tables?
Hi there,
Lets provide me information about your instance:
+ URL and admin credentials of your M2 site
+ SSH credentials and path to M2 folder
I will help to check further and get back you then.
Regards,
Mall.
Unfortunately I can’t do this due to data protection laws and customer data
Is there a way to force check the M1 DB for changes?
Hi there,
Is there a way to force check the M1 DB for changes?
It seem you changed M1’s database credentials after the first migration? Lets re-correct databases credentials in the configuration file of our module at path:
pub/ub-tool/protected/config/db.php
Regards,
Mall.
Yes correct, it is after migrating host. The credentials are correct in this file
Yes correct, it is after migrating host. The credentials are correct in this file
I’ve also cleared Magento cache l, restarted memcache, restarted the server and deleted the runtime/ folder
Hi there,
How many attribute sets and attributes in your M1 database? Do you see the newly added attribute listing in the setting form of step #3 of our tool?
Regards,
Mall.
That’s the thing, there are 13 attribute groups on M2 and now 26 on M1 (13 new)
none of the the new ones show up on step 3 in the admin or on the output of the cli command
Also 235 attributes on M2 and 285 on M1 -- none of these show either
Hi there,
If the M1’s database credentials was corrected. Lets recheck the PHP’s setting param named ‘max_input_var’ in your server. And then, increase value of this param to:
max_input_vars = 10000
And restart server of your M2 instance and re-check the issue.
Regards,
Mall.
This setting was already at 15000. I adjusted it to 10000, reset the instance, restarted memcache, PHP & Nginx.
Then I reran the delta. It is doing the same thing and not recognising my source data changes
Hi there,
It is doing the same thing and not recognising my source data changes
That is strange. I need a closer look to detect the root of issue you mentioned. Lets provide me information about your instance as my suggesting.
+ URL and admin credentials to back-end of your site
+ SSH credentials and path to M2 folder
I will help to check further and get back you then.
PS. Please mark your reply private or simply switch this ticket to private mode, then it’s safe to share your site info here. Only you and our technical team can access.
Regards,
Mall.
Please see your own message from 18 hours ago asking for the same thing and me explaining that I am not able to do this for legal reasons and data protection.
I manaully flushed memcache and this time on the wizard it let me check the extra categories, fingers corssed it lets me dot he same with other assets. Perhaps memcache is persistent.
I will test and let you know
I manaully flushed memcache and this time on the wizard it let me check the extra categories, fingers corssed it lets me dot he same with other assets. Perhaps memcache is persistent.
I will test and let you know
Hi there,
Yes, please move forward with the process at your end. And let us know how it works then.
Regards,
Ubertheme team
It looks to be working now, I guess it must have been memcache storing the config persistently.
Do you have any advise when we move host and start the delta again to ensure that the new credentials are picked up by the tool and the correct DB synced?
Hi there,
Do you have any advise when we move host and start the delta again to ensure that the new credentials are picked up by the tool and the correct DB synced?
After moved to new server, you should re-correct databases credentials in the config file at path: pub/ub-tool/protected/config/db.php
Regards,
Mall.