Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-33903

Upgrade task to clean up duplicate task entries

XMLWordPrintable

    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      A bug went out that caused duplicate entries in AO. In conjunction with the bugfix, we need to clean up existing clones in the AO inline tasks table. This will most likely require an upgrade task and LOTS of testing.

      This effects EAC and several OD instances.
      See related ticket.

      Diagnosis and Workarounds can be found in this KB article

            [CONFSERVER-33903] Upgrade task to clean up duplicate task entries

            Alice Wang (Inactive) added a comment -

            Hi marc.mcconnell, i believe you can kindly request support to run the SQL on your behalf.

            Alice Wang (Inactive) added a comment - Hi marc.mcconnell , i believe you can kindly request support to run the SQL on your behalf.

            Marc McConnell added a comment -

            Hi. can you tell me how this workaround would work for ondemand hosting? We don's have access to the SQL database. Thanks

            Marc McConnell added a comment - Hi. can you tell me how this workaround would work for ondemand hosting? We don's have access to the SQL database. Thanks

            jeremyjoeldunn added a comment -

            Thank you! This was helpful, and effective.

            My only suggestion for other (cautious) individuals who want to do this cleanup, would be to backup the AOTASK table before running the cleanup script, just in case.

            jeremyjoeldunn added a comment - Thank you! This was helpful, and effective. My only suggestion for other (cautious) individuals who want to do this cleanup, would be to backup the AOTASK table before running the cleanup script, just in case.

            Alice Wang (Inactive) added a comment -

            buerkle, jeremy.j.dunn please see the updated ticket description. The linked KB has sql queries that you can run to delete duplicate tasks. However, this does not cover all scenarios and it is possible for duplicate tasks to remain in some edge cases.

            Alice Wang (Inactive) added a comment - buerkle , jeremy.j.dunn please see the updated ticket description. The linked KB has sql queries that you can run to delete duplicate tasks. However, this does not cover all scenarios and it is possible for duplicate tasks to remain in some edge cases.

            jeremyjoeldunn added a comment -

            yes, I would also be willing to manually clean up the database (I'm a developer and very experienced SQL admin) but I need to know which table(s) are affected. Can Atlassian provide at-your-own-risk documentation for experienced users to self-clean the db, instead of waiting for the complex QA on this task ?

            jeremyjoeldunn added a comment - yes, I would also be willing to manually clean up the database (I'm a developer and very experienced SQL admin) but I need to know which table(s) are affected. Can Atlassian provide at-your-own-risk documentation for experienced users to self-clean the db, instead of waiting for the complex QA on this task ?

            Michael Buerkle added a comment -

            can i clean up manually by deleting entries from AO-9412A1_AOTASK or will i break something by doing that?

            Michael Buerkle added a comment - can i clean up manually by deleting entries from AO-9412A1_AOTASK or will i break something by doing that?

              alwang Alice Wang (Inactive)
              alwang Alice Wang (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              21 Start watching this issue

                Created:
                Updated:
                Resolved: