Update on the OpenUpgrade migration

After some detailed review of the logs and re-watching the conference on OpenUpgrade I was able to identify key things about the way the migration take place:

  1. Carefully reviewing the error message.
  2. Understand the script is not bulletproof and seems to preffer debug than skipping errors.
  3. Keep your SQL hat at arm reach.

I was able to run openupgrade with some success but there was a lot of missed shots and even this one is still not a hit yet, but is getting closer.

The Main error had to do with two tables, res_users which hold the application users, and res_company that holds the clients.  We can first look at error log:

2013-12-17 06:49:50,310 28794 ERROR astro_migrated openerp.osv.orm: Can’t find field ‘context_tz’ in the following view parts composing the view of object model ‘res.users’:
 * res.users.form
 
Either you wrongly customized this view, or some modules bringing those views are not compatible with your current data model
2013-12-17 06:49:50,311 28794 ERROR astro_migrated openerp.osv.orm: Can’t find field ‘menu_tips’ in the following view parts composing the view of object model ‘res.users’:
* res.users.form
Either you wrongly customized this view, or some modules bringing those views are not compatible with your current data model
2013-12-17 06:49:50,312 28794 ERROR astro_migrated openerp.osv.orm: Can’t find field ‘context_lang’ in the following view parts composing the view of object model ‘res.users’:
 * res.users.form
 
Either you wrongly customized this view, or some modules bringing those views are not compatible with your current data mod
The other table is the one related with the fields property_reserve_and_surplus_account, and the security_lead. for the res.company table.

3699 ERROR astro_migrated openerp.osv.orm: Can’t find field ‘property_reserve_and_surplus_account’ in the following view parts composing the view of object model ‘res.company’:
* res.company.form.inherit

3699 ERROR astro_migrated openerp.osv.orm: Can’t find field ‘security_lead’ in the following view parts composing the view of object model ‘res.company’:
* res.company.mrp.config

The next step is to review the way the error as I login to the migrated database shows up on the screen and the actual error that sends:
ProgrammingError: column res_users.alias_id does not exist
LINE 1: …CT res_users.”menu_id”,res_users.”gmail_password”,res_users….
                                                                               ^
This error basically tells me that the res_users is wrong due to some missing information regarding the column res_user.alias_id. I still need to crack this one, but fortunately this will help me solve the rest and would be able to finally get the migration concluded.
I can almost be certain this has to do with the database and that there have been issues related with SQL queries.
Advertisements