Jira log has error duplicate key?

[Timothy Harris]

We did a migration from JIRA cloud to a JIRA 7.3 server. I am seeing the following error in the log.

An exception occured while rendering the web panel: com.pyxis.greenhopper.jira:greenhopper-epics-issue-web-panel (null)

com.atlassian.activeobjects.internal.ActiveObjectsSqlException: There was a SQL exception thrown by the Active Objects library:

Database:

 - name:PostgreSQL

 - version:9.5.5

 - minor version:5

 - major version:9

Driver:

 - name:PostgreSQL Native Driver

 - version:PostgreSQL 9.1 JDBC4 (build 903)

org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "AO_60DB71_LEXORANK_pkey"

  Detail: Key ("ID")=(13) already exists.

Any ideas as to what to do about this?

[dmytrome_RG]

We have the same problem, any news?

[dmytrome_RG]

I found solution in article https://confluence.atlassian.com/jirakb/unable-to-create-jira-portfolio-plans-or-jira-software-boards-after-restoring-from-database-backup-postgresql-and-oracle-specific-958444511.html

Note!
Not forgot ; in the of last query

alter sequence "AO_60DB71_LEXORANK_ID_seq" restart 10203;

[Sakshi Mittal]

Hi ,

I am running into the same problem. could you solve it?

Regards

Sakshi

[Mike Rocheleau]

I have the exact same scenario, migrated from Cloud to Server 7.3 and same issues, on Postgres 9.3.  It seems to trigger everytime I try to view an Epic issue, the Greenhopper panel throws generic errors and logs show duplicate key.  

Running Integrity Checker doesn't fix anything, shows everything's good no problems.