existing data from V1.8 did not show in V3.1
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 |
|
Tuesday, June 2, 2009, 8:30:10 AM |
0
|
Did you run the upgrade scripts from 1.8 to 2.1? |
||||
|
0
|
I run this scripts: |
||||
|
0
|
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. |
||||
|
0
|
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. |
||||
|
0
|
Yes, you should run the scripts using the Gemini user. |
||||
|
0
|
Hi, |
||||
|
0
|
Do you want to send your database to support at countersoft dot com? We wil be able to see what is wrong. |
||||
|
0
|
the database is 32MB after zipped. Do you have any FTP? or can i posted in here? |
||||
|
0
|
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 |
||||
|
0
|
Hi Support, |
||||
|
0
|
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. |
||||
|
0
|
Ok, we have now looked at the upgrade and did not get all the errors you are getting.
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.
|
||||
|
0
|
Hi, |
||||
|
0
|
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. |
||||
|
0
|
"The reason you are getting errors with step 1 is because of issue types mismatch." |
||||
|
0
|
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. |
||||
|