Hi @ felipemila,
Yes I recently did that same upgrade and had the same SQL error.
Since we were not doing anything with OAuth2, I did a fresh V9.2.7 install in my local dev environment and exported all the OAuth2 tables using phpadmin.
After restoring the V9.1.3 instance (following the SQL error), I then dropped all the OAuth2 tables in my V9.1.3 instance and imported the OAuth2 tables from the 9.2.7 fresh install. After that the upgrade to V9.2.7 worked.
We are still testing V9.2.7 in a hosted staging environment - so far no problems encountered.
Hope this assists. Regards,
Jeff.
Yes, you will get a big output, most of it is just keys and stuff. If you then go into your database with phpMyAdmin or Adminer you can use the SQL command function and run those without foreign key checks on and it should fix whatever missing migrations you have.