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.




migrating 2.0 to 4.1 issues : Issue not imported because Risk Level ID is invalid

install
items

This question has been already posted (I google the site and found this link : support.countersoft.com/forums/thread/8864.aspx?Ajax_CallBack=true), but the thread seem unavailable.

During the upgrade process from 2.0 to 4.1 :

I get errors on the 2-0 to 2-1 on constraint violations.

-Msg 5074, Niveau 16, État 1, Ligne 2 La index 'ProjectFollowupIndex' dépend de colonne 'assignedto'. -Msg 5074, Niveau 16, État 1, Ligne 2 La index '' dépend de colonne 'assignedto'. -Msg 5074, Niveau 16, État 1, Ligne 2 La index 'TasksFollowupIndex' dépend de colonne 'assignedto'. -Msg 4922, Niveau 16, État 9, Ligne 2 ALTER TABLE DROP COLUMN assignedto a échoué car un ou plusieurs objets accèdent à cette colonne.

I get sql results on the Upgrade_v3-0-Step1.sql script : 22.427 rows with message : 'Issue not imported because Risk Level ID is invalid'

I get sql errors on this script too, with foreign key conflicts : "gemini_timetracking_projectid_fk" and "gemini_usesettings_userid_fk"

Now in the updated webSite, I can "see" issues through "my work", but can't see theses issues in the project "items" interface.

Can you explain theses errors, and eventually provide a fix for scripts ?

Thanks.

User26762
· 1
User26762
Replies (3)
helpful
1
not helpful

I suggest re-running the whole upgrade process. The first error (upgrade 2.1) seems to be because of an idex you have created, please drop it.

The other errors are due to invalid data, which you will need to update. Update the issues table and make sure all risk ids are valid. Same applies to the time tracking projid column. Once this is doen run the upgrade 3.0 step1 script again.


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

Thanks for the informations.

Look like my network admin was in a hury. I found a named index... probably copied from the request plan optimizer. Others indexes where probably added the same way.

Regarding data for the 'Issue not imported because Risk Level ID is invalid' : these issues comes from a bridge with our hotline SI... risklevel is set to 0. I insert a new row in issuerisklevellut with id 0.

2.0 to 2.2 work now without messages. But I've always errors in the v3-0 Step1 script :

Msg 547, Niveau 16, État 0, Ligne 329 L'instruction INSERT est en conflit avec la contrainte FOREIGN KEY "geminiissuecomponentscomponentidfk". Le conflit s'est produit dans la base de données "Geminibkp", table "dbo.gemini_components", column 'componentid'. L'instruction a été arrêtée.

(0 ligne(s) affectée(s)) Msg 547, Niveau 16, État 0, Ligne 417 L'instruction INSERT est en conflit avec la contrainte FOREIGN KEY "geminitimetrackingprojectidfk". Le conflit s'est produit dans la base de données "Geminibkp", table "dbo.gemini_projects", column 'projectid'. L'instruction a été arrêtée.

(0 ligne(s) affectée(s)) Msg 547, Niveau 16, État 0, Ligne 426 L'instruction INSERT est en conflit avec la contrainte FOREIGN KEY "geminiusesettingsuseridfk". Le conflit s'est produit dans la base de données "Geminibkp", table "dbo.gemini_users", column 'userid'. L'instruction a été arrêtée.

I have had to change project main group type (from Gemini 3.0 migrations projects to software development projects), and I'm recreating users project's accesses.

In your mind, may theses error cause issues later ? Thanks.


User26762
· 1
User26762
helpful
0
not helpful

You will be missing data, so have to fix these really. Simply delete orphaned rows.


Saar Cohen
· 5000
Saar Cohen