• FEATURES
  • PRICING
  • MARKETPLACE
  • CASE STUDIES
  • BLOG
    •

    Liquibase Exception on new deploy

    Technical Questions
    #1

    I am able to deploy OpenSpecimen from the downloaded installable, but when I build an installable from source (using ant create_zip), I get the following when trying to do a deploy_all from the created installable. Has anyone run into this?

    C:\openspecimenteam\OpenSpecimen_v1.0.1_Installable\build.xml:981: The following
    error occurred while executing this line:
    C:\openspecimenteam\OpenSpecimen_v1.0.1_Installable\build.xml:1583: The followin
    g error occurred while executing this line:
    C:\openspecimenteam\OpenSpecimen_v1.0.1_Installable\build.xml:1667: The followin
    g error occurred while executing this line:
    C:\openspecimenteam\OpenSpecimen_v1.0.1_Installable\build.xml:5400: liquibase.ex
    ception.MigrationFailedException: Migration failed for change set ./SQL/liquibas
    e_xml/dashboard_scripts.xml::2::catissue:
    Reason: liquibase.exception.DatabaseException: Error executing SQL ALTER TA
    BLE LABELSQL MODIFY IDENTIFIER BIGINT(20) AUTO_INCREMENT: Cannot change colu
    mn ‘IDENTIFIER’: used in a foreign key constraint ‘FK_LABELSQL’ of table ‘opensp
    ecimen101.labelsqlassoc’:
    Caused By: Error executing SQL ALTER TABLE LABELSQL MODIFY IDENTIFI ER BIGINT(20) AUTO_INCREMENT: Cannot change column ‘IDENTIFIER’: used in a fore
    ign key constraint ‘FK_LABELSQL’ of table ‘openspecimen101.labelsqlassoc’:
    Caused By: Cannot change column ‘IDENTIFIER’: used in a foreign key co
    nstraint ‘FK_LABELSQL’ of table ‘openspecimen101.labelsqlassoc’

    #2

    Hello Bob,

    I too couldn’t build OS from source code, I run into several errors. Not sure what the errors were, since it has been several months; I will see if I documented it somewhere.

    One of the things that I have noticed after being able to finally build from source code, was that both the 13 queries and the bulk upload that were there in the downloaded installable copy were not there in the OS built from source code. So I may have run into a different set of errors.

    After spending several days on it and getting nowhere, I just decided to stick to the downloaded installable zip file.

    Nadia

    #3

    Hi @bob_lange, @Nan_Halabi,

    We have run deploy_all from source code locally, didn’t get any issue, it ran successfully. From this error we are not able to figure out the exact cause. It will be better if you can describe the exact steps and the complete deployment log file.
    Deploy_all target is meant to be run on fresh database. For deployment steps, please refer how to build from source code?

    ~Nitesh

    #4

    deploy.log (18.7 KB)
    deploy_output.txt (8.4 KB)

    I dumped the output of the ant task to the attached deploy.log file. Additionally, I included the output from the command line as deploy_output.txt.

    I took the follwoing steps:

    1. Downloaded the code tagged as OS-v1.0.1 from github.
    2. Opened the project in Eclipse and got it to build successfully.
    3. Ran ant create_zip from the directory (and from Eclipse on a different try with the same result).
    4. Unzipped the installable created above.
    5. Created the database schema in my MySQL database (local to the install of OpenSpecimen). I dropped it first on subsequent tries as it partially build the database. I also chose a different name for it in case something somehow lingered after the drop.
    6. Ran deploy_all
    #5

    Just to be clear, this is a deployment on my local workstation for development/debugging purposes.

    #6

    The error above was my own fault. I had a later version of MySQL. I installed MySQL v5.1.67 and that error no longer occurs.