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.




Problem running the Upgrade_v3-1.sql script

migration

Hi all,

I am trying to upgrade Gemini but when I run the Upgradev3-1.sql script I get the following errors:

(1 row(s) affected)

(1 row(s) affected)

(1 row(s) affected)

Msg 2705, Level 16, State 4, Line 5

Column names in each table must be unique. Column name 'parentcomponentid' in table 'geminicomponents' is specified more than once.

Msg 3726, Level 16, State 1, Line 5

Could not drop object 'geminiprojectlabels' because it is referenced by a FOREIGN KEY constraint.

Msg 2714, Level 16, State 6, Line 2

There is already an object named 'geminiprojectlabels' in the database.

Msg 2705, Level 16, State 4, Line 2

Column names in each table must be unique. Column name 'projectlabelid' in table 'geminiprojects' is specified more than once.

Msg 2705, Level 16, State 4, Line 5

Column names in each table must be unique. Column name 'apikey' in table 'geminiusers' is specified more than once.

I have been following the instructions in the migration maunal without success.

Can anyone help with this please?

Thanks.

Brett.
bkel1977
· 1 		bkel1977
Tuesday, June 16, 2009, 2:38:26 PM
Replies (8)
helpful
0
not helpful

From which version are you upgrading?

 
Saar Cohen
· 5000 		Saar Cohen
Tuesday, June 16, 2009, 2:43:54 PM
helpful
0
not helpful

Hi,

I am upgrading from Version 2.1

I first ran the script to upgrade to version 2.2 then the create scripts, etc. as laid out in the migration manual.

Thanks.

Brett.
bkel1977
· 1 		bkel1977
Tuesday, June 16, 2009, 4:30:53 PM
helpful
0
not helpful

Ok, you do not need to run the 3.1 script only the 3.0.0 step 1 etc...
Saar Cohen
· 5000 		Saar Cohen
Tuesday, June 16, 2009, 5:45:46 PM
helpful
0
not helpful

I skipped the 3.1 script and went straight to the 3.5 script but I get errors on that one too.

Also, things like issue comments are not migrated to the new tables.
bkel1977
· 1 		bkel1977
Wednesday, June 17, 2009, 10:54:55 AM
helpful
0
not helpful

The last script you should run is the 3.0.0 step 1 or 2.

You should not run others after.

Did you get any errors when running the 3.0.0 step 1?
Mark Wing
· 9108 		Mark Wing
Wednesday, June 17, 2009, 11:39:12 AM
helpful
0
not helpful

I have ran the step 1 script without any errors. The application seems to work but the comments still do not appear in the application. After checking the new table, they are not being imported.
bkel1977
· 1 		bkel1977
Wednesday, June 17, 2009, 12:22:45 PM
helpful
0
not helpful

Can you please run the following command on your Gemini database:

 SELECT commentid, CASE WHEN u.userid IS NULL THEN -1 ELSE ic.userid end, issueid, projid, ic.comment, ic.username, isprivate, isclosing, ic.created FROM issuecomments ic LEFT JOIN geminiusers u ON ic.userid = u.userid
  WHERE issueid IN (SELECT issueid FROM geminiissues) and projid in (select projectid from gemini_projects)

Do you get any comments back? If not please check the project id for the comments in the old table.
Mark Wing
· 9108 		Mark Wing
Wednesday, June 17, 2009, 12:32:15 PM
helpful
0
not helpful

Hi,

There was an issue with some project IDs being 0 ao I have corrected this and the upgrade seems to be working correctly.

Thanks.
bkel1977
· 1 		bkel1977
Wednesday, June 17, 2009, 1:53:20 PM