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.




Error during 2.2.6 - 3.5.4 upgrade (while running Upgrade_v3-1.sql)

migration

When running the Upgrade 3-1 script, I received the following error:  (Yes, correct DB instance and DB this time... And I confirmed that I'm carefully following the upgrade script order as well.)

 

(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 'gemini
projectlabels' 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 'gemini
projects' 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.

 

Starting with base 2.2.6 DB, I have run the following scripts:

  • CreateTables.sql
  • CreateViews.sql
  • CreateProcs.sql
  • Upgradev3-0-Step1.sql
  • Upgradev3-0-Step2.sql
  • Upgrade_v3-1.sql
  • TCooper
    · 1
    TCooper
    Replies (3)
    helpful
    0
    not helpful

    You don't have to run any script after the step 2 (which is optional as well).

    Please restore your database and re-run the scripts in the order you had in the post but without the 3.1 upgrdae.


    Saar Cohen
    · 5000
    Saar Cohen
    helpful
    0
    not helpful

    I can certainly do that.  I am confused, though. 

     

    Why does the Gemini Migration Guide say (on page 6) that I need to run those scripts?  It's section 7. Execute Database Migration Scripts- Part 2


    TCooper
    · 1
    TCooper
    helpful
    0
    not helpful

    Thank you for highlighting this. We will update the migration guide.
    The create tables script already creates a 3.5.4 database.


    Mark Wing
    · 9108
    Mark Wing