Upgrade from V2.0.3 to v2.2.7
I'm using V2.0.3 and want finally upgrade to v3.0.4. As in the Installation Guide for 3.0.4 (page 8, bullet #7) indicates I need to upgrade my DB to release 2.2.7 before upgrading to release 3.0 (I assume from 2.2.7 I can upgrade directly to 3.0.4, please correct me if my assumption is wrong).
Now, I got confused with reading bullet #8, page 9 of Installation Guide for 3.0.4. Bullet 8.5, v2.2 <-- I assume that means if you want to upgrade to release 2.2 read bullet 8.5 (page 10). Right below that section, it said "please download and review the "Gemini Migration Guide" document. Thus, I download the 3.0 Migration Guide.
I assume I should follow the instruction on page 5 of 3.0 Migration Guide. On that page, it doesn't tell me specifically that I need to download so and so file in order to upgrade to release 2.2. Bullet 5 it just tells me to execute 3 scripts, where are they and how can i get them? Excuse my questions if you think they are silly. It's my first time messing with Gemini. I'm not even familiar with using it, but I'm having a task that I need to upgrade it.
Any help (please be specific and details since i'm so new to this product) would be highly appreciated. If I need to provide more information, please let me know :)
Thanks!!
Kim
kha
· 1 |
|
Monday, October 6, 2008, 9:58:10 PM |
0
|
All you have to do is download 3.0.4 (zip). Unzip it and go to the databae upgrade folder. You will need to execute 2.1 and 2.2 sql scripts. After that run create tables (from the parent dir) followed by Upgradev3-0-Step1.sql and Upgradev3-0-Step2.sql if all is ok, run create_views and procs.sql. |
||||
|
0
|
Thanks, Mark! |
||||
|
0
|
Now I got some foreign key conflict error with executing the upgradev3-0-step1.sql script. The Migrate document, page 5 already have the Note about these kind of error. But doesn't say the way to resolve the problem. Any help is really appreciated. |
||||
|
0
|
The last 2 errors are due to projectid in the issuehistory table not being a valid id, suggest you remove these records from the history tabel. Similar issue with component, you have some components in the issues table that do not exist, excldue these issues or update them to a valid component. As for the workflow issue, can you post your current workflow?
|
||||
|
0
|
Regarding to the component error above, my original dbo.component table
doesn't have userid field, but the dbo.gemini_component has userid
field, so it automatically has the -1 value assigned to that field for
all records. Is it something expected? Will it cause any problem
moving forward? |
||||
|
0
|
Regarding to the component error above, my original dbo.component table doesn't have userid field, but the dbo.gemini_component has userid field, so it automatically has the -1 value assigned to that field for all records. Is it something expected? Will it cause any problem moving forword? |
||||
|
0
|
Make suer that your statuses in the issuestatetransitionlut are valid (status and otherstate). |
||||
|
0
|
I just restored my latest gemini db, and reran the createtables.sql script, it gave me the following error: |
||||
|
0
|
I fixed the problem by changing the line 17 in the script to DROP PROCEDURE as the first error said, it got rid of both errors and gemini_issuelinktypes table got created afterward. |
||||
|
0
|
I'm moving on with upgrade_v3-0-step1.sql and got the following errors: |
||||
|
0
|
What is the version of the restored database? Seems like it is not 2.2.7! |
||||
|
0
|
Sorry, I didn't make myself clear at the first time. |
||||
|
0
|
Step 1 of the 3.0.0 upgrade moves all the data to the new structure. Was this run successfully? Are all the issues there for 3.0.4? Comments? If yes, then just re-run the statment to move the users. |
||||
|
0
|
I started from page 5 (bullet 5) of Gemini Migration Guide document
|
||||
|
0
|
From the errors I see, it seems that you are trying to upgrade a 2.0.x database directly to 3.0.4, which can not be done! You need to run the upgrdae scripts first:
After these have run, run the upgrdae to 3.0 scripts. |
||||
|
0
|
can i call you to get help from this, i am getting more and more weird errors |
||||
|
0
|
Now, i deleted the existing db, restored the v2.0.3 db again to sql2005 server |
||||
|
0
|
I'm getting this error from executing the upgrade-v3-0-step1.sql |
||||
|
0
|
Yes, this gets created when running the 2.1 script! Make sure that you are using the same user to execute all scripts. |
||||
|
0
|
I'm seeing this error with executing the Upgrade-v3-0-step1.sql The original issues table doesn't have issuetypeid column |
||||
|
0
|
You have some issues with type id that does not exist in the issuetypes table. Suggest you find these and update them to use a valid type before running the script. |
||||
|