JIRA 4.4 issue cloning - data base error (object already exists)

Elvir Hadzic
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 21, 2011

Hello everybody,

did anyone else encounter this problem in JIRA 4.4? When we want to clone an issue, we receive the following error:

Exception: net.java.ao.sql.ActiveObjectSqlException: java.sql.SQLException: There is already an object named 'AO_60DB71_RANK_ISSUE_LINK' in the database.


Any help regarding this matter would be greatly appreciated.

Edit: for some reason it want's to create the table again:

2011-08-22 09:43:56,992 http-192.168.15.16-443-6 ERROR [username] 583x30971x1 tgqvkm [jira ip] /sr/jira.issueviews:searchrequest-xml/10272/SearchRequest-10272.xml [net.java.ao.sql] Exception executing SQL update <CREATE TABLE AO_60DB71_RANK_ISSUE_LINK (
ISSUE_ID BIGINT NOT NULL,
NEXT_ID BIGINT,
PRIMARY KEY(ISSUE_ID)

1 answer

1 accepted

1 vote
Answer accepted
Jeremy Largman
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 21, 2011

Sorry for the late response. It looks like you might have hit one of these:

Looks like upgrading either JIRA (4.4.1) or GreenHopper (5.5.7) will fix it.

Elvir Hadzic
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 4, 2011

Thanks a lot!

This solved the problem completely.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events