Getting ”schema differences were found” error in upgrade process
Question ID: 107097

Hi All,

Getting below errors in upgrade process.

1) ALM-V10017: Error: A schema difference that cannot be automatically corrected has been detected: Modify Column type:BUG,BG_EI_OLD_VALUES:text–>varchar –for all tables getting same message.

2) Internal error message to RnD. Not all schema can be changed. dbVerify can not generate all needed SQLs. This usually happens when developer adds not-nullable field to Empty_DB.xml

Extra information:

3) Project is corrupted.

Please asist me how can upgrade without these issues.


Marked as spam
Posted by (Questions: 11, Answers: 7)
Asked on September 12, 2016 11:13 am
Answers (2)
Private answer

I would look into the columns listed as errant, in this case BUG table, column BG_EI_OLD_VALUES and correct this (I would guess it is either the wrong format, varchar desired and it is text or the incorrect sizing). I would check with your DBA as someone has changed this somewhere along the way for it to be reporting incorrectly. If you are still having issues, check the entire log file pertaining to the verify (as the clues are generally there), or the full upgrade log text file (and not just the little error presented to you during the upgrade process that you are providing here) and adjust accordingly. If you still can't find the issue, then you will need to open a case with your support team for this issue and it may require assistance from HP.

Good luck and hope this helps some.


Marked as spam
Posted by (Questions: 0, Answers: 770)
Answered on September 14, 2016 2:57 pm
Private answer

Since you have encountered a corrupted project error, the migration/ upgrade will need to be restarted from the beginning for this project, meaning obtain a fresh and clean copy of the repository and the db components and then start the migration from the beginning. Once these are obtained you will import the db component, correct the ownership with the sql queries to associate the new td user to the current db component. Then you will copy over the clean repository, edit the dbid.xml, and restore to the new instance/version. Next, complete the restore and then you will run the maintenance>verify options and manually correct the issues flagged (from the above statements I would expect to see at least a couple of items flagged as requiring manual correction). After correcting all issues manually, re-run the verify and check that only items being flagged as correctable by the repair function exists, if not correct the manual issues and repeat this step until only repairable by the tool issues exist. Once this is achieved, run the maintenance>repair functions. I would recommend re-running the verify after this and if all is corrected, then you may proceed forward and run the upgrade process, at which time correct completion will yield a correct and upgraded project.

Good luck and if you still experience issues, I would recommend contacting your support carrier for assistance, or if you have no service support provider you may contact Orasi for a contracting to have assistance with your matter.


Marked as spam
Posted by (Questions: 0, Answers: 770)
Answered on September 13, 2016 3:06 pm
Hi @Dan, Thank you for your response and suggestion..!! I did the same process and resolved all verify issues like (Extra columns) but at the time of performing upgrade getting errors... 1) ALM-V10017: Error: A schema difference that cannot be automatically corrected has been detected: Modify Column type:BUG,BG_EI_OLD_VALUES:text--> of lines. 2)ALM-V10055: Schema differences were found. If you face the same issue in experience please share with me. Thanks & Regards, Praveen
( at September 14, 2016 7:26 am)

Welcome back to "EyeOnTesting" brought to you by Orasi Software, Inc.

Scroll to Top