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.




sql error : missing gemini_errorlog table when migrating from 2.1 to 3.6

web-app

Hi,

I have a 2.1 installation of Gemini running and I wish to migrate it to 3.6
Here's the order the 3.6 package sql scripts are run:
- Upgradev2-2.sql
- Create
Tables.sql
- CreateViews.sql
- Create
Procs.sql
- Upgradev3.0-step1.sql
- Upgrade
v3.0-step2.sql

The problem occurs when Upgradev3.0-step1.sql is launched. The involved statement is the first one :
DELETE FROM gemini
errorlog
The geminierrorlog table doesn't exist ! I searched the CreateTables.sql and all other sql in the zip but there's no Create Table statement for this table.

Can you help me please?
Thanks

PS : The same problem occurs for table gemini_projectrepository in the same sql script (line 229).

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

Create_tables.sql creates these new tables. Aer you sure you have run it?

Please check the owner of the new tables.


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

Hello,

I've just downloaded 3.6 package from www.coutersoft.com homepage and i cannot find any occurence of geminierrorlog in the file CreateTables.sql located in Gemini Database directory.

Can anyone confirm ?

Thanks


dav_natixis
· 1
dav_natixis
helpful
0
not helpful

You are right, I do apologies!

Forgot that we have changed these 2 tables in 3.6. You can comment out the error log block:

/

DELETE FROM gemini_errorlog

SET IDENTITY_INSERT gemini_errorlog ON

INSERT INTO gemini_errorlog (srn, errormessage, stacktrace, otherinfo, created)

SELECT srn, errormessage, stacktrace, otherinfo, created FROM errorlog

SET IDENTITY_INSERT gemini_errorlog OFF

/

 

As for the repository, replace it with:

--**************************

-- Project Documents

--**************************

SET IDENTITYINSERT geminiprojectdocuments ON

INSERT INTO geminiprojectdocuments (documentid, parentdocumentid, projectid, documentname, documentdesc, isfolder, contenttype, documentdata, created, contentlength)

SELECT nodeid, parentnodeid, projid, nodetext, tooltip, isfolder, contenttype, nodedata, GETDATE(), ISNULL(DATALENGTH(nodedata),0) FROM projectrepository

WHERE projid IN (SELECT projectid FROM geminiprojects)

SET IDENTITYINSERT geminiprojectdocuments OFF


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

Forgot to mention not to run the last section of the upgrade script:

--**************************

-- Project Documents

--**************************

SET IDENTITYINSERT geminiprojectdocuments ON

....

 

As this has already run by the earlier chaneg.

Latest script attached.


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

Yes, i noticed there was a duplicate command.

Thanks!


dav_natixis
· 1
dav_natixis
helpful
0
not helpful

Hello,

Does it mean the package will be up to date on your homepage as soon as it is resolved ?

Regards


dav_natixis
· 1
dav_natixis
helpful
0
not helpful

3.6.1 will include this latest script and should be out by tomorrow.


Mark Wing
· 9108
Mark Wing