Changes between Version 23 and Version 24 of UserGuidelines/Admin/DataMigration/Haiti

Timestamp:

01/22/10 00:02:36 (16 years ago)

Author:

Praneeth Bodduluri

Comment:

Added migration notes

UserGuidelines/Admin/DataMigration/Haiti

@@ -232 +232 @@
 1) sqlite does seems to treat emails with different capitalizations as different entities. MySQL does not and can cause a problem during import if data is not clean.[[BR]]
 
-2) Use of the INNODB engine for the db can lead to Integrity Errors during the first run and import -> Recommend MyISAM for now.
+2) SQLite doesn't support FOREIGN KEY constraints, neither does MySQL with MyISAM tables.
+
+
+=== Migration plan ===
+
+1) Put the site in read only mode -> Disable Login, Kill existing sessions[[BR]]
+2) Export the CSV from web2py shell[[BR]]
+3) Create a MyISAM database(say name = sahana) in mysql[[BR]]
+4) Disable zzz_1st_run.py and zzz_last.py[[BR]]
+5) Switch the settings in 00_db.py to mysql and do a [[BR]]
+
+{{{
+python web2py.py -S sahana -M -N
+db.commit()
+CTRL+Z
+}}}
+
+
+6) Drop the tweets and sms data and their corresponding GIS [ Check for any pledges ][[BR]]
+
+7) Split the data into the 5 csv's as follows(say db1.csv, db2.csv,..) - Deleting other tables.[[BR]]
+
+{{{
+TABLE auth_event
+TABLE admin_theme
+TABLE s3_audit
+TABLE s3_setting
+TABLE s3_source
+TABLE appadmin_setting
+===========================
+TABLE pr_setting
+TABLE pr_pentity
+TABLE pr_person
+TABLE pr_group
+===========================
+TABLE gis_setting
+TABLE gis_marker
+TABLE gis_projection
+TABLE gis_symbology
+TABLE gis_config
+TABLE gis_feature_class
+TABLE gis_symbology_to_feature_class
+TABLE gis_location
+TABLE gis_feature_group
+TABLE gis_location_to_feature_group
+TABLE gis_feature_class_to_feature_group
+TABLE gis_apikey
+TABLE gis_track
+TABLE gis_layer_openstreetmap
+TABLE gis_layer_google
+TABLE gis_layer_yahoo
+TABLE gis_layer_gpx
+TABLE gis_layer_georss
+TABLE gis_layer_kml
+TABLE gis_layer_wms
+TABLE gis_layer_tms
+TABLE gis_layer_xyz
+TABLE gis_layer_js
+============================
+TABLE pr_contact
+TABLE or_setting
+TABLE or_sector
+TABLE or_organisation
+TABLE or_office
+TABLE or_contact
+TABLE or_project
+TABLE or_activity
+TABLE lms_setting
+TABLE lms_catalog
+TABLE rms_setting
+TABLE admin_setting
+TABLE budget_setting
+TABLE cr_setting
+TABLE dvi_setting
+TABLE dvr_setting
+TABLE hrm_setting
+TABLE mobile_setting
+TABLE mpr_setting
+TABLE msg_setting
+TABLE sync_setting
+TABLE vol_setting
+
+}}}
+
+8) Remove duplicates in the auth_user ( only Linda* when I checked) and pr_person[[BR]]
+
+9) Clean up gis_layer_js -> make multi lined records single lined[[BR]]
+
+10) In or_organisation -> remove "Medecins du Monde France" entry as "Médecins du Monde France" is treated as the same in MySQL[[BR]]
+
+11) Clean up multi lined records in or_organisation.[[BR]]
+
+12) Test import - multilined entries give a "raise SyntaxError, 'invalid file format' [[BR]]
+
+13) or_sector does not have entries 14,15,16 - which are in the database associated with some organisations - Fix them[[BR]]
+
+14) Check that the site is completely functional.[[BR]]
+
+15) Go to phpmyadmin and export the entire db as sql.[[BR]]
+
+16) Replace all MyISAM lines in the sql with INNODB[[BR]]
+
+17) Drop the datbase using phpmyadmin and import the previously created sql[[BR]]
+
+18) Test everything once.[[BR]]
+
+19) Switch this to production[[BR]]
+
+Estimated time for migration: 1 hour
 
 ----