We've just upgraded from 2.23 to 2.24 and the upgrade notes state that :
- Version 2.24 sets all "uid", "created" and "lastupdated" columns for metadata tables as not nullable. As a result it is recommended to first run version 2.23 on your database before running version 2.24 to allow new columns to be added and populated prior to marking them has not nullable. The system starts up fine and deploys the new 2.24 war - *no errors during startup routines* - but when it is finished I've checked dataelement, organisationunit, dataset and none of them have those 3 fields set as not nullable. The upgrade worked fine on another instance. Any suggestions? We are having many issues importing metadata from other instances and wonder if that might be part of the cause. -- *Randy Wilson* *Team Leader: **Knowledge Management, Data Use and Research* Rwanda Health System Strengthening Activity Management Sciences for Health Rwanda-Kigali Direct: +250 788308835 E-mail: rwil...@msh.org Skype: wilsonrandy_us <http://www.msh.org/> Stronger health systems. Greater health impact. <https://www.facebook.com/ManagementSciencesForHealth> <https://twitter.com/MSHHealthImpact> <https://www.youtube.com/user/MSHHealthImpact> www.msh.org -- *This message and its attachments are confidential and solely for the intended recipients. If received in error, please delete them and notify the sender via reply e-mail immediately.*
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-users Post to : dhis2-users@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-users More help : https://help.launchpad.net/ListHelp
