Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




running errors on upgrade_v3-0-step1

beta

From Upgradev3-0-Step1.sql running on sql 2000 server.
My db is 2.2.6 gemini version.


(53 row(s) affected)


(52 row(s) affected)


(1 row(s) affected)


(0 row(s) affected)


(112 row(s) affected)


(4 row(s) affected)


(2 row(s) affected)


(1 row(s) affected)


(469 row(s) affected)


(3 row(s) affected)


(470 row(s) affected)


(1 row(s) affected)


(469 row(s) affected)


(10 row(s) affected)


(2 row(s) affected)


(10 row(s) affected)


(7 row(s) affected)


(1 row(s) affected)


(1 row(s) affected)


(1 row(s) affected)


(1 row(s) affected)


(1 row(s) affected)


(1 row(s) affected)


(1 row(s) affected)


(1 row(s) affected)


(1 row(s) affected)


(1 row(s) affected)


(1 row(s) affected)


(1 row(s) affected)


(1 row(s) affected)


(17 row(s) affected)


(1 row(s) affected)


(1 row(s) affected)


(1 row(s) affected)


(3 row(s) affected)


(1 row(s) affected)


(3 row(s) affected)


(11 row(s) affected)


(1 row(s) affected)


(1 row(s) affected)


(1 row(s) affected)


(1 row(s) affected)


(14 row(s) affected)


(4 row(s) affected)


(1 row(s) affected)


(4 row(s) affected)


(11 row(s) affected)


(1 row(s) affected)


(1 row(s) affected)


(1 row(s) affected)


(1 row(s) affected)


(1 row(s) affected)


(15 row(s) affected)


(6 row(s) affected)

Server: Msg 547, Level 16, State 1, Line 1
DELETE statement conflicted with COLUMN REFERENCE constraint 'gemini
issueworkflowitemtransitionissueworkflowitemidfk'. The conflict occurred in database 'GEMINI3', table 'geminiissueworkflowitemtransition', column 'issueworkflowitemid'.
The statement has been terminated.

(9 row(s) affected)

Server: Msg 547, Level 16, State 1, Line 1
DELETE statement conflicted with COLUMN REFERENCE constraint 'gemini
issueworkflowitemissuestatusidfk'. The conflict occurred in database 'GEMINI3', table 'geminiissueworkflowitem', column 'issuestatusid'.
The statement has been terminated.
Server: Msg 2627, Level 14, State 1, Line 163
Violation of PRIMARY KEY constraint 'gemini
issuestatusstatusidpk'. Cannot insert duplicate key in object 'geminiissuestatus'.
The statement has been terminated.

(5 row(s) affected)


(5 row(s) affected)


(4 row(s) affected)


(4 row(s) affected)


(0 row(s) affected)


(413 row(s) affected)


(0 row(s) affected)


(4459 row(s) affected)


(0 row(s) affected)


(6946 row(s) affected)


(0 row(s) affected)


(5756 row(s) affected)


(0 row(s) affected)


(61 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(412 row(s) affected)


(0 row(s) affected)


(5 row(s) affected)


(0 row(s) affected)

Server: Msg 547, Level 16, State 1, Line 243
INSERT statement conflicted with COLUMN FOREIGN KEY constraint 'gemini
issuesissuestatusidfk'. The conflict occurred in database 'GEMINI3', table 'gemini_issuestatus', column 'statusid'.
The statement has been terminated.

(0 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(11393 row(s) affected)


(0 row(s) affected)


(32014 row(s) affected)


(3 row(s) affected)


(3 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(1654 row(s) affected)


(0 row(s) affected)


(1654 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(93 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(0 row(s) affected)


(525 row(s) affected)


(0 row(s) affected)

(1405 row(s) affected)

do I have to worry me?

lomi
· 1
lomi
Replies (12)
helpful
0
not helpful

That might impact the upgrade, we will look into this and post a fix if necessary.


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

Did you run this script twice?


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

no


lomi
· 1
lomi
helpful
0
not helpful

Will it be possible for you to send your zipped backup of 2.2.6 to support@countersoft.com ?


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

I've send you an email w/ instruction.


lomi
· 1
lomi
helpful
0
not helpful

Attached is a revised version of the upgrade script.

Thanks for your co-operation. 


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

I'm getting exactly the same errors. Can I also use the attached zip?
I compared it with the upgrade_v3-0-step1 I have and there are many differences. It seems that the attached file found above is a little old.


papadi
· 1
papadi
helpful
0
not helpful

The first error is because I have items in issuecomments table with projid=0 and there is no such project. All these issue comments have been created using svn integration add-in.
Isn't it a duplication to have projid in issuecomments?


papadi
· 1
papadi
helpful
0
not helpful

Update your table with the correct project ids.


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

I changed the migration script to use the projectID from issue table and not issuecomments or issuecommentshistory.


papadi
· 1
papadi
helpful
0
not helpful

Hi @ll

Is there a fully correct update script around or do i have to look for the position the error occurs and correct it myself?

Greetz


ArmyMan
· 1
ArmyMan
helpful
0
not helpful

The latest one is included with 3.0.4. However, you still need to fix issues of key violation if they exist.


Mark Wing
· 9108
Mark Wing