Well, it is a hickup on the code of 2.2.x and don't think it will be fixed. That version no longer supported for fixes or updates.
Hope you were working with a copy of the 1.9 data directory (as recommended).
Here's what you could check ... if you have any 1.9 course backups they are in datafolder/courseidnumber/backupdata/ then backup...blah.zip.
Move all of those backup...blah.zip's out of of the data directory to a place for archiving.
Here's what you could try with the problem course/file ...
The course ID folder is 335. Jot down the name of that course so you can find it later. Make an archive of that folder - zip will do.
Go into that folder (leave the folder intact) and *move* out into an archive space that large 1.3 Gig file.
Using a new DB, do the migration. It might complain about a file missing, but it's been recorded in the DB mdl_files table. After successfully migrating to the 2. turn on file system repositories.
In your converted moodledata folder (it has now been changed drastically), create a folder called 'repository'. Make sure ownership/permissions are set so that apache user/group can read/write on it.
Inside the repository directory unzip the 335 course ID folder you archived earlier. It should unzip creating a '335' folder. Then go to the course that had that ID in the 1.9 and create a file system instance for that course. Call it 'old files' and point to the 335 folder. Your 1.3 Gig zip will be in there and accessible to Moodle 2 to relink. *Must relink*.
It's work but one can eventually get through the migration.
Might check all the 1.9 course ID folders for other large files like that in advance of attempting the migration again. If you find others, same process.
'spirit of sharing', Ken