I could write a long post here so, let’s start at the end of the story.
Big file (let’s call the file “Dox”) didn’t migrate…got stuck at 38 GB for a long time. The three other big files that were being processed at the same time were all done, and waiting in the OttoFMS/inbox–but not this file.
That migration was aborted, and we started started anew Just Dox, but after too long of a time That migration was aborted and then the entire deployment of 10 files was reverted. (Reverting was remarkably smooth by the way).
This file was eventually migrated after we recovered a clone of the staging version Dox. Then it took about 90 minutes.
Great.
That’s fine.
But what I need to know is where to look in the logs, for what should I look to see if a file is just stuck in hell.
If other topics have addressed this, feel free to point me there. As a note, The issue did not seem to be block vs. record migration.
Adding a couple notes. I was wrong, it was definitely into record mode at about 90min into the migration and the migrated file was at about 38 Gigs out of an eventual total size of 40 Gigs. And it was stuck.
We/I aborted the migration just short of 4 hours. So what we would like to be able to see is…maybe another log that shows details during that time. As it is the last entry was at
To date, the big expanses of empty logs when the DMT (Data Migration Tool) gets stuck on a record mode migration are the most annoying thing about the DMT. Unfortunately all of those logs are coming directly from the DMT when the DMT sends them, it seems like the DMT just doesn’t log the line until after it is done with the table. OttoFMS has no way of knowing what is going on beyond what the DMT gives us.
I wish the DMT gave us some details during the migration (possibly updates on progress or a start and end log for each table?) but even turning on verbose mode for the logs changes nothing about how it logs the table migration information.
We also have a file that is 17.5 GB in size. The first 17 GB are done in about an hour. The remaining 0.5 GB take about 12 hours to complete. It increments in kilobytes at a time. I have no idea why it happens. We have other files that are larger that complete in 3 hours. Others are the same as the 17.5 GB file (but take a bit shorter, one 7 hours, one 8 and one 10 hours)
If anybody finds a reason for this please help. Also the 17.5 GB file is just 1 table.
