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.




existing data from V1.8 did not show in V3.1

web-app

Hi All,

I have upgrade gemini V1.8 to v3.1. Problem is that data from v1.8 did not show on the new gemini v.3.1

I have this error when run script on v3.1 step 1
Invalid column name 'components'.
Msg 207, Level 16, State 1, Line 386
Invalid column name 'versions'.
Msg 207, Level 16, State 1, Line 386
Invalid column name 'resources'.
Msg 207, Level 16, State 1, Line 386
Invalid column name 'issuetype'.
Msg 207, Level 16, State 1, Line 386
Invalid column name 'issuepriority'.
Msg 207, Level 16, State 1, Line 386
Invalid column name 'issuestatus'.
Msg 207, Level 16, State 1, Line 386
Invalid column name 'issueresolution'.
Msg 207, Level 16, State 1, Line 407
Invalid column name 'comment'.
infrastructure
· 1 		infrastructure
Tuesday, June 2, 2009, 8:30:10 AM
Replies (16)
helpful
0
not helpful

Did you run the upgrade scripts from 1.8 to 2.1?
Mark Wing
· 9108 		Mark Wing
Tuesday, June 2, 2009, 10:02:28 AM
helpful
0
not helpful

I run this scripts:

Upgradev1-9
Error msg:
Msg 3701, Level 11, State 5, Line 2
Cannot drop the procedure 'geminigetlut2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Line 3
Cannot drop the procedure 'geminimoveversiondown', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Line 4
Cannot drop the procedure 'geminimoveversionup', because it does not exist or you do not have permission.

UnicodeUpgrade
Error msg:
Msg 3701, Level 11, State 7, Line 152
Cannot drop the index 'issueresolutionlut.inddesc', because it does not exist or you do not have permission.

Upgradev2-1
Error Msg:
Msg 207, Level 16, State 1, Procedure geminigetlutentries, Line 10
Invalid column name 'tstamp'.
Msg 207, Level 16, State 1, Procedure geminigetlutentries, Line 15
Invalid column name 'tstamp'.
Msg 207, Level 16, State 1, Procedure geminigetlutentries, Line 20
Invalid column name 'tstamp'.
Msg 207, Level 16, State 1, Procedure geminigetlutentries, Line 25
Invalid column name 'tstamp'.
Msg 207, Level 16, State 1, Procedure geminigetlutentries, Line 30
Invalid column name 'tstamp'.
Msg 207, Level 16, State 1, Procedure geminigetlutentries, Line 37
Invalid column name 'tstamp'.
Msg 207, Level 16, State 1, Procedure geminigetlutentries, Line 44
Invalid column name 'tstamp'.
Msg 207, Level 16, State 1, Procedure geminigetlutentries, Line 52
Invalid column name 'tstamp'.
Msg 207, Level 16, State 1, Procedure geminigetlut1, Line 8
Invalid column name 'tstamp'.
Msg 207, Level 16, State 1, Procedure geminigetlut1, Line 12
Invalid column name 'tstamp'.
Msg 207, Level 16, State 1, Procedure geminigetlut1, Line 15
Invalid column name 'tstamp'.
Msg 207, Level 16, State 1, Procedure geminigetlut1, Line 20
Invalid column name 'tstamp'.
Msg 207, Level 16, State 1, Procedure geminigetlut1, Line 28
Invalid column name 'tstamp'.
Msg 207, Level 16, State 1, Procedure geminigetlut1, Line 31
Invalid column name 'tstamp'.
Msg 207, Level 16, State 1, Procedure geminigetissueupdatedata, Line 11
Invalid column name 'tstamp'.
Msg 207, Level 16, State 1, Procedure geminigetissueupdatedata, Line 17
Invalid column name 'tstamp'.
Msg 207, Level 16, State 1, Procedure geminigetissueupdatedata, Line 23
Invalid column name 'tstamp'.
Msg 207, Level 16, State 1, Procedure geminigetissueupdatedata, Line 29
Invalid column name 'tstamp'.
Msg 207, Level 16, State 1, Procedure geminigetissueupdatedata, Line 32
Invalid column name 'tstamp'.
Msg 207, Level 16, State 1, Procedure geminigetissueupdatedata, Line 39
Invalid column name 'tstamp'.
Msg 207, Level 16, State 1, Procedure geminigetissueupdatedata, Line 42
Invalid column name 'tstamp'.
Msg 207, Level 16, State 1, Procedure issuesview, Line 25
Invalid column name 'tstamp'.
Msg 207, Level 16, State 1, Procedure geminigetprojectsummary, Line 9
Invalid column name 'projarchived'.

Upgradev2-2
NO ERROR

CreateTables
NO ERROR

CreateViews
NO ERROR

CreateProcs
NO ERROR

Upgradev3-0-Step1
Error Msg:
Msg 207, Level 16, State 1, Line 205
Invalid column name 'projarchived'.
Msg 207, Level 16, State 1, Line 274
Invalid column name 'isclosing'.
Msg 207, Level 16, State 1, Line 364
Invalid column name 'lookupsortfield'.
Msg 207, Level 16, State 1, Line 386
Invalid column name 'components'.
Msg 207, Level 16, State 1, Line 386
Invalid column name 'versions'.
Msg 207, Level 16, State 1, Line 386
Invalid column name 'resources'.
Msg 207, Level 16, State 1, Line 386
Invalid column name 'issuetype'.
Msg 207, Level 16, State 1, Line 386
Invalid column name 'issuepriority'.
Msg 207, Level 16, State 1, Line 386
Invalid column name 'issuestatus'.
Msg 207, Level 16, State 1, Line 386
Invalid column name 'issueresolution'.
Msg 207, Level 16, State 1, Line 407
Invalid column name 'comment'.
infrastructure
· 1 		infrastructure
Wednesday, June 3, 2009, 4:03:12 AM
helpful
0
not helpful

Which user are you using to run these scirpts? It might be a different one from the owner of the Gemini objects.

Also,  you have missed upgrade 1.9.1.
Mark Wing
· 9108 		Mark Wing
Wednesday, June 3, 2009, 10:54:43 AM
helpful
0
not helpful

I run the scripts under SQL users SA which is has DB owner on the database. I noticed that the some stored proc and tables on the scripts does not exist or does not match on the actual database table or stored proc.

Also, I restore database back to V1.8 and then successfully run extra script which is V-1-9-1 and have same result for other scripts . I am still not successfull see existing data in new gemini.

Is there any changes i have to make on the scripts prior to database upgrade?
If I run the scripts under "SA" will it affect the outcome? since Default user should be "Gemini".
infrastructure
· 1 		infrastructure
Thursday, June 4, 2009, 1:46:06 AM
helpful
0
not helpful

Yes, you should run the scripts using the Gemini user.
Saar Cohen
· 5000 		Saar Cohen
Thursday, June 4, 2009, 10:01:54 AM
helpful
0
not helpful

Hi,

I have created user "gemini" and assign DBowner to gemini database but the error still there:

Msg 3701, Level 11, State 5, Line 2
Cannot drop the procedure 'geminigetlut2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Line 3
Cannot drop the procedure 'geminimoveversiondown', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Line 4
Cannot drop the procedure 'geminimoveversionup', because it does not exist or you do not have permission.

when i look at the stored proc, i could not find 'geminigetlut2', 'geminimoveversiondown', 'gemini_moveversionup' as requested on the script.

is there anything i have to do before the upgrade?

Niko
infrastructure
· 1 		infrastructure
Tuesday, June 9, 2009, 5:24:28 AM
helpful
0
not helpful

Do you want to send your database to support at countersoft dot com? We wil be able to see what is wrong.
Saar Cohen
· 5000 		Saar Cohen
Wednesday, June 10, 2009, 4:00:56 PM
helpful
0
not helpful

the database is 32MB after zipped. Do you have any FTP? or can i posted in here?
infrastructure
· 1 		infrastructure
Thursday, June 11, 2009, 12:54:27 AM
helpful
0
not helpful

We do not have FTP, can you put it on an HTTP download?

You can use yousendit.com please send the link to support at countersoft dot com
Saar Cohen
· 5000 		Saar Cohen
Thursday, June 11, 2009, 9:17:00 AM
helpful
0
not helpful

Hi Support,

I have upload to yousendit.com. I have send to support@countersoft.com.
Do you need me to show the link in here?
infrastructure
· 1 		infrastructure
Tuesday, June 16, 2009, 3:40:06 AM
helpful
0
not helpful

Please do not post the link here as it will be visible to all users.

We will get back to you once we have looked at the database.
Saar Cohen
· 5000 		Saar Cohen
Tuesday, June 16, 2009, 10:12:45 AM
helpful
0
not helpful

Ok, we have now looked at the upgrade and did not get all the errors you are getting.

  • Running 1.9 - 3 errors of "can not drop..." can be ignored.
  • Running 1.9.1 - no errors
  • Unicode - 1 error can be ignored
  • 2.0 - no erros
  • 2.1 - no errors
  • 2.2 - no errors

So we can not replicate your issues at all.

Note that you will have to update your statuses, types etc... as between 1.8 and 1.9 they have changed and not migrated.

 
Saar Cohen
· 5000 		Saar Cohen
Tuesday, June 16, 2009, 11:59:14 AM
helpful
0
not helpful

Hi,

Thank you for the quick replay and also for the input for the database error.
I just wonderin how about scripts after 2.2? Did you test it as well?

I run:
3-0-1 ------ 1 errors
3-0-Step1 ------- 1 errors
3-0-Step2 ------- 9 errors
3-1 -------- 6 errors

Regards,
Nikodemus
infrastructure
· 1 		infrastructure
Wednesday, June 17, 2009, 4:27:17 AM
helpful
0
not helpful

You should not run 3-0-1 or others just 3-0 step 1 and optionaly 2.

The reason you are getting errors with step 1 is because of issue types mismatch.
Saar Cohen
· 5000 		Saar Cohen
Wednesday, June 17, 2009, 9:43:52 PM
helpful
0
not helpful

"The reason you are getting errors with step 1 is because of issue types mismatch."
What should i do with that?

I had this error when i run step 1:
Msg 547, Level 16, State 0, Line 260
The INSERT statement conflicted with the FOREIGN KEY constraint "geminiissuesissuetypeidfk". The conflict occurred in database "GeminiV3Niko", table "dbo.geminiissuetypes", column 'typeid'.
The statement has been terminated.

and when i run SELECT statement on new table, it did not show any data migrated. but i can see there is data in old table.
infrastructure
· 1 		infrastructure
Thursday, June 18, 2009, 4:28:41 AM
helpful
0
not helpful

That is because your old table is using the old types of 1.8.

You need to change these to the new types from the types table.
Mark Wing
· 9108 		Mark Wing
Thursday, June 18, 2009, 10:19:20 AM