Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,363,011
Community Members
 
Community Events
168
Community Groups

I get Constraint Violations when I want to delete s.th. in Fisheye Reviews.

Hello,
when I try to delete s.th. in my Fisheye Reviews I get following Exception:

2014-02-17 15:54:19,323 ERROR - Exception "org.hibernate.exception.ConstraintViolationException: could not delete: [com.cenqua.crucible.model.FileRevisionExtraInfo#2775]" (javax.servlet.ServletException) while processing "/fisheye.git/js
on/cru/CR-174/editRevisionsFromRevisionAjax/" (Referer:"https://domain/fisheye.git/cru/CR-174")

Caused by: org.hibernate.exception.ConstraintViolationException: could not delete: [com.cenqua.crucible.model.FileRevisionExtraInfo#2775]
Caused by: java.sql.SQLException: ORA-02292: integrity constraint (ORA_FF_GIT.FKD3011B4773591D1A) violated - child record found

How can I solve this problem?

Regards, Juergen

2 answers

1 accepted

0 votes
Answer accepted

Hi Nick,

Nope. I tried other things first.

First, I restarted Fisheye. This did not fix the problem. Then, I found similar failure as described in CRUC-6097 in the log:

Caused by: com.atlassian.crowd.exception.OperationFailedException: Could not execute JDBC batch update; nested exception is org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update

I decided to upgrade Fisheye from 2.10.7. to 3.3.0. before trying CRUC-6079. Fisheye executed some sql scripts on first start. All SQL script completed successfully.

The upgrade seems to be solved the problems. We tested several reviews. Everything works fine now. Also the old reviews work. I think the upgrade solved the data inconsistency in database too.

Thank you
Regards, Juergen

0 votes
Nick Atlassian Team Feb 17, 2014

Hey Jürgen,

Have you maybe hit this bug ? https://jira.atlassian.com/browse/CRUC-6079

If so, we will be trying to fix that for the upcoming 3.4 release.

Cheers,

nick

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events