We hope you'll join us for our 4/23 webinar on using data tables to apply reference ranges and AE codes in OC4. For more information and to register, visit https://register.gotowebinar.com/register/2882170018956684555

Upgrade from 3.1.4.1 til 3.13 fails - liquibase

I have an old 3.1.4.1 installation on postgres 8.4, Windows. I want to upgrade to 3.13, but the liquibase table update process fills the tomcat stderr logs with 312 entries of this sort:

dec. 15, 2017 9:07:37 AM liquibase.database.structure.SqlDatabaseSnapshot readColumns
INFO: Could not find table or view crf_version_idx_crf for column crf_id
dec. 15, 2017 9:07:38 AM liquibase.database.structure.SqlDatabaseSnapshot readColumns
INFO: Could not find table or view discrepancy_note_idx_entity_type for column entity_type
dec. 15, 2017 9:07:38 AM liquibase.database.structure.SqlDatabaseSnapshot readColumns
INFO: Could not find table or view discrepancy_note_idx_parent for column discrepancy_note_id
dec. 15, 2017 9:07:38 AM liquibase.database.structure.SqlDatabaseSnapshot readColumns
INFO: Could not find table or view event_definition_crf_idx_crf for column crf_id
dec. 15, 2017 9:07:38 AM liquibase.database.structure.SqlDatabaseSnapshot readColumns
INFO: Could not find table or view event_definition_crf_idx_parent_null for column parent_id
dec. 15, 2017 9:07:38 AM liquibase.database.structure.SqlDatabaseSnapshot readColumns
INFO: Could not find table or view event_definition_crf_idx_parent_zero for column parent_id
dec. 15, 2017 9:07:38 AM liquibase.database.structure.SqlDatabaseSnapshot readColumns
INFO: Could not find table or view event_definition_crf_idx_study_event_definition for column study_event_definition_id

It is like liquibase expects something that is not present in the 1.3.4.1 version of the OpenClinica database definition, and instead of OpenClinica creating these missing views, it all just results in a

SEVERE: Context [/OpenClinica] startup failed due to previous errors

Do I have to use intermediary versions for performing this upgrade?

Comments

  • BinaryVisionBinaryVision Posts: 42
    Those notices are normal before it applies the migration schemas. Here's a small sample of what you should see upgrading from 3.1.4 to 3.11 (haven't tried 3.13 but should be the same). Could not find throws for each object missing, then the webapp applies every migration changeset from 3.3 up to 3.11+ one by one.

    INFO: Could not find table or view uniq_study_oid for column oc_oid
    Dec 12, 2017 9:58:33 AM liquibase.database.structure.SqlDatabaseSnapshot readColumns
    INFO: Could not find table or view uniq_study_subject_oid for column oc_oid
    Dec 12, 2017 9:58:35 AM liquibase.database.template.JdbcTemplate comment
    INFO: Changeset migration/3.3/2014-04-15-OC-4822.xml::2010-04-15-OC-4822-1::jnyayapathi::(MD5Sum: 7e8d6c8d02fe016884b0d0ade2d259)
    Dec 12, 2017 9:58:35 AM liquibase.database.template.JdbcTemplate comment
    INFO: Add Column
    Dec 12, 2017 9:58:35 AM liquibase.database.template.JdbcTemplate comment
    INFO: Changeset migration/3.3/2014-04-15-OC-4822.xml::2010-04-15-OC-4822-2::jnyayapathi::(MD5Sum: f8bbbfde7b985adb4d66d4b9aeb2c4)
    Dec 12, 2017 9:58:35 AM liquibase.database.template.JdbcTemplate comment
    INFO: Add Column
    Dec 12, 2017 9:58:35 AM liquibase.database.template.JdbcTemplate comment
    INFO: Changeset migration/3.3/2014-04-15-OC-4822.xml::2010-04-15-OC-4822-3::jnyayapathi::(MD5Sum: 8fae3398fe1b33715af9fa4d5ac971)
    Dec 12, 2017 9:58:35 AM liquibase.database.template.JdbcTemplate comment
    INFO: Add Column


    Does it ever begin to apply the first Changeset Xml?
  • janus141janus141 Posts: 2
    No, it did not. The OpenClinica service stopped after the series of messages from liquibase. Tried of course more than once, as I also thought it had to be done incrementally.

    I fixed the problem, though, by performing upgrades in consequitive steps from 3.2 to 3.6, then skipped to 3.9 (was getting boring) and then applied the 3.13 version. Everything is working as it should now.
    It might have been overkill to do 8 upgrades, but in the process I also discovered some errors in the data in the database. I found 2 set of duplicate non-repeating events which I had to clear out of the way to finalize the 3.13 version.

    Best regards,
    Janus
Sign In or Register to comment.