Changes between Version 19 and Version 20 of UserGuidelines/Admin/DataMigration/Haiti


Ignore:
Timestamp:
01/20/10 22:04:09 (12 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • UserGuidelines/Admin/DataMigration/Haiti

    v19 v20  
    118118}}}
    119119==== Dealing with database corruption ====
    120 We had problems with the or_organisation table - queries wouldn't complete.
     120 1. We had problems with the or_organisation table - queries wouldn't complete.
    121121
    122122The tracebacks included: {{{ValueError: invalid literal for int() with base 10: '01/14/10 1'}}}
     123
     124By commenting out each field in turn in the model, discovered that this was the timestamp column which included this data.
     125
     126(Note the file was also {{{chown root:root}}}!)
     127
    123128To fix this we needed to:
    124129 * Delete column from model
     
    157162Ctrl+D
    158163}}}
     164
     165 2. rms_sms_request table couldn't be recreated
     166
     167Since this part of the system is under active development, it was necessary to drop the table as part of the [wiki:ReleaseManagement release process].
     168 * Although normally we can re-populate the tables from their source feeds simply using:
     169{{{
     170cd /home/haiti/web2py
     171python web2py.py -S prod -M -N
     172feature_class_id = db(db.gis_feature_class.name == 'SMS').select().first().id
     173db(db.gis_location.feature_class_id == feature_class_id).delete()
     174db.rms_tweet_request.truncate()
     175db.rms_sms_request.truncate()
     176db.commit()
     177Ctrl+D
     178}}}
     179
     180However this didn't complete fully as there was still an associated view file in {{{databases/}}} & hence when model tries to create:
     181 * {{{SyntaxError: invalid table name: rms_sms_request}}}
     182
     183To resolve this
    159184=== Web Services ===
    160185Better to avoid locks & do without SSH login