Uploaded image for project: 'ONE'
  1. ONE
  2. ONE-32360

Restore Jira data from Backup leaves tables without constraints

    XMLWordPrintable

Details

    • Bug
    • Status: Waiting for Release (View Workflow)
    • Critical
    • Resolution: Done
    • prod/biggantt/jiraserver/2021/02/09/8.0.20, prod/bigpicture/jiraserver/2021/02/09/8.0.20
    • None
    • None
    • No
    • Infrastructure
    • BigPicture, BigGantt
    • JIRA server, JIRA cloud
    • 163
    • 163
    • $i18n.getText("admin.common.words.hide")
      $i18n.getText("admin.common.words.show")
      var cfToHide1 = document.getElementById("rowForcustomfield_18501"); if(cfToHide1){cfToHide1.style.display="none";} var cfToHide2 = document.getElementById("rowForcustomfield_18502"); if(cfToHide2){cfToHide2.style.display="none";} var cfToHide3 = document.getElementById("rowForcustomfield_19700"); if(cfToHide3){cfToHide3.style.display="none";} var cfToHide4 = document.getElementById("rowForcustomfield_18400"); if(cfToHide4){cfToHide4.style.display="none";}
    • Sprint 2021/12, Sprint 2021/13
    • PI2021/4
    • 6 weeks, 3 days, 7 hours, 28 minutes, 35 seconds
    • 4 weeks, 3 days, 16 hours, 46 minutes, 41 seconds
    • 0
    • 0
    • 0
    • 15 minutes, 16 seconds
    • 12 weeks, 4 days, 14 hours, 20 minutes, 30 seconds

    Description

      Prerequisites:
      N/A

      Reproduction steps:
      1. Create the backup from Jira.
      2. Restore Jira from backup

      Actual result:
      Tables without constraints not null and unique.
      Indexes missing.

      Expected result:
      Tables have constraints not null and unique.
      Indexes exist.

      Workaround:

      • Option 1: perform a version upgrade
      • Option 2: force the last step of database upgrade by executing SQL (only possible on some versions)

      Option 2
      Execute the SQL (works only in BigPicture 8.0.20 / BigGantt 8.0.20):
      AO_0456E7_ - for BigPicture
      AO_8AC478_ - for BigGantt

      • PostgreSQL
        delete
        from "AO_8AC478_UPGRADE_TASK_HISTORY"
        where "VERSION"=110
        
      • MySQL
        delete
        from AO_8AC478_UPGRADE_TASK_HISTORY
        where VERSION=110
        

      In some cases it have to be replaced with update (e.g. only one row in UPGRADE_TASK_HISTORY)

      • MSSQL Version 8.0.3 BP
        update dbo.AO_0456E7_UPGRADE_TASK_HISTORY
        set VERSION=86,TECH_UNIQUENESS='0000000000000000000000000000@86@TENANT@0e94e68c-9de6-11eb-a8b3-0242ac130003@DDL'
        where VERSION=87
        

      Attachments

        Issue Links

          Activity

            People

              albert.cieslak Albert Cieślak
              dariusz.dudek Dariusz Dudek
              lukasz.debski Łukasz Dębski , grzegorz.duzy Grzegorz Duży , tomasz.ruszel Tomasz Ruszel , adam.biedruna Adam Biedruna , lukasz.michalak Łukasz Michalak , pawel.guz Pawel Guz , marta.gniadek Marta Gniadek (Inactive) , system.gerrit Gerrit , albert.cieslak Albert Cieślak , kamila.kornatko Kamila Kornatko , lukasz.barc Łukasz Barć , tomasz.szymanski Tomasz Szymański , lukasz.panek Łukasz Panek , piotr.zadora Piotr Zadora , anna.kicior Anna Kicior , martyna.turowska Martyna Turowska , dariusz.dudek Dariusz Dudek
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: