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.




Restor database from 1.8

web-app

We had a server failer and needed to restore Gemini.

I install 2.6 on the new server just to find out that the Database backup we had is from 1.8.

Is there any way to restore 1.8 database onto Gemini 2.6?

 

 

talbengal
· 1
talbengal
Replies (8)
helpful
0
not helpful

Yes, we provide sql upgrade scripts with the Gemini installation.

See our upgrade guide: http://www.countersoft.com/Downloads/Installing%20Gemini.pdf


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

I install the 2.6 OK but the database is empty, I need to import the 1.8 database on to it.

Is there a way to do it?

All the script for updating like this one:

UPGRADE_v2-0.sql

giving me error can not find XXX .. and name of the table / view.

 

 

 


talbengal
· 1
talbengal
helpful
0
not helpful

You need to restore your 1.8 database first and run the scripts in it.


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

geting this errors:

Msg 2705, Level 16, State 4, Line 1

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

Msg 2705, Level 16, State 4, Line 2

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

Msg 3701, Level 11, State 5, Line 2

Cannot drop the procedure 'geminigetuserbyname', because it does not exist in the system catalog.

Msg 2705, Level 16, State 4, Line 5

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

and this:

(2 row(s) affected)

Warning: The table 'customfielddefs' has been created but its maximum row size (8260) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.

and this:

6 row(s) affected)

Msg 4902, Level 16, State 1, Line 1

Cannot alter table 'issuestatetransitionlut' because this table does not exist in database 'bugs'.

(5 row(s) affected)

(4 row(s) affected)

Msg 207, Level 16, State 3, Procedure issuesview, Line 3

Invalid column name 'estimatedays'.

Msg 207, Level 16, State 3, Procedure issuesview, Line 3

Invalid column name 'estimatehours'.

Msg 207, Level 16, State 3, Procedure issuesview, Line 3

Invalid column name 'estimateminutes'.

Msg 207, Level 16, State 3, Procedure issuesview, Line 3

Invalid column name 'isprivate'.

And this:

(9 row(s) affected)

Msg 207, Level 16, State 3, Procedure geminigetlutentries, Line 8

Invalid column name 'seq'.

Msg 207, Level 16, State 3, Procedure geminigetlutentries, Line 13

Invalid column name 'seq'.

Msg 207, Level 16, State 3, Procedure geminigetlutentries, Line 18

Invalid column name 'seq'.

Msg 207, Level 16, State 3, Procedure geminigetlutentries, Line 23

Invalid column name 'seq'.

Msg 207, Level 16, State 3, Procedure geminigetlutentries, Line 50

Invalid column name 'seq'.

Msg 207, Level 16, State 3, Procedure geminigetlut1, Line 12

Invalid column name 'seq'.

Msg 207, Level 16, State 3, Procedure geminigetlut1, Line 15

Invalid column name 'seq'.

Msg 207, Level 16, State 3, Procedure geminigetlut1, Line 31

Invalid column name 'seq'.

Msg 207, Level 16, State 3, Procedure geminigetissueupdatedata, Line 29

Invalid column name 'seq'.

Msg 207, Level 16, State 3, Procedure geminigetissueupdatedata, Line 32

Invalid column name 'seq'.

Msg 207, Level 16, State 3, Procedure geminigetissueupdatedata, Line 39

Invalid column name 'seq'.

Msg 207, Level 16, State 3, Procedure geminigetissueupdatedata, Line 42

Invalid column name 'seq'.

Msg 207, Level 16, State 3, Procedure issuesview, Line 3

Invalid column name 'seq'.

Msg 207, Level 16, State 3, Procedure issuesview, Line 3

Invalid column name 'estimatedays'.

Msg 207, Level 16, State 3, Procedure issuesview, Line 3

Invalid column name 'estimatehours'.

Msg 207, Level 16, State 3, Procedure issuesview, Line 3

Invalid column name 'estimateminutes'.

Msg 207, Level 16, State 3, Procedure issuesview, Line 3

Invalid column name 'isprivate'.

Msg 207, Level 16, State 3, Procedure geminigetprojectsummary, Line 63

Invalid column name 'isprivate'.

Msg 207, Level 16, State 3, Procedure geminigetprojectsummary, Line 63

Invalid column name 'seq'.

Msg 207, Level 16, State 3, Procedure geminigetprojectsummary, Line 73

Invalid column name 'isprivate'.

Msg 207, Level 16, State 3, Procedure geminigetprojectsummary, Line 73

Invalid column name 'seq'.

Msg 207, Level 16, State 3, Procedure geminigetvalidissuestatusvalues, Line 10

Invalid column name 'seq'.

Msg 207, Level 16, State 3, Procedure geminigetvalidissuestatusvalues, Line 23

Invalid column name 'seq'.

 

And this:

Warning: The table 'customfielddefs' has been created but its maximum row size (8269) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.

Warning: The table 'customfielddefs' has been created but its maximum row size (8269) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.

Warning: The table 'customfielddefs' has been created but its maximum row size (8269) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.

 

Basicly can't do it, Gemini did not pick up any of the 1200 issues I had in the 1.8 DB and none of the users


talbengal
· 1
talbengal
helpful
0
not helpful

Can you explian which scripts did you run and the order AFTER restoring the 1.8 database?


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

Follow the instruction:

Step

Action

1

Execute "UPGRADEv1-9.sql" in Gemini Issues Database (core component #2)

2

Execute "UNICODEUPGRADE.sql" in Gemini Issues Database (core component #2)

3

4

Execute "UPGRADEv2-1.sql" in Gemini Issues Database (core component #2)

5

Execute "UPGRADEv2-2.sql" in Gemini Issues Database (core component #2)

6

Execute "CREATEVIEWS.sql" in Gemini Issues Database (core component #2)

7

Execute "CREATE_PROCS.sql" in Gemini Issues Database (core component #2)

8

Execute "INSTALLCOMMON.sql" in Gemini Issues Database (core component #2)

9

Execute "INSTALLPROFILE.sql" in Gemini Issues Database (core component #2)


talbengal
· 1
talbengal
helpful
0
not helpful

Which script(s) give you the errors?


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

I will restor the db again and let you know.


talbengal
· 1
talbengal