A direct upgrade from 10.1.400 to 10.1.600.3 doesn’t seem to work. The 10.1.600 DB conversion fails because it’s expecting some of the 10.1.500 schema changes to already be in place. The work around I used was to install the 10.1.500.20 admin console on my laptop and run the 10.1.400 to 10.1.500 db conversion first. Then the 10.1.600 db conversion worked fine. If I get an SCR I’ll post it here.
Carson
I recently upgraded our test system from 10.1.400.18 to 10.1.600.2 – it failed on one step on the conversion, Ice.ChgLog primary key validations failing. I have an open support ticket, but it was a quick resolution to remove duplicate records (it’s only the change log anyway).
Interesting. Mine was a 10.1.400.11 to 10.1.600.3 and I got a ton of DB conversion errors.
“Solved” by running it through the 10.500 db migration from my laptop before the 10.600 migration.
What did the error state? I have done several 10.1.400 - 600 direct upgrades, since the day 600 was released, and have not encountered this issue. Assuming you followed the Epicor instructions did you do the in-place upgrade where the admin console prompts you to take actions or the manual approach?
I suppose I took a manual approach. The server had 10.1.600.3 installed that was an test upgrade from .500. Production is still on .400 so I restored the .400 DB to .600 and upgraded the DB. I’ll find the exact errors and post them. Basically it was the sql scripts that make the schema changes that failed.
Oh… Does it generate the scripts when the initial upgrade is installed? Since I initially did a .400 to .500 then a .500 to .600 maybe it only had the scripts for the .500 to .600 upgrade.
Sounds plausible - whether it generates them, or whether it just copies the ones it needs.
This should not be the case, 10.1.600 includes the same scripts at 10.1.500 so there is no need to install and upgrade 10.1.500 first. If you can recreate and send in a support ticket, I am happy to have my team review.
Here’s the full back story on it:
Installed 10.1.500 on a new server.
Restored the 10.1.400 db and ran the db upgrade.
Then 10.1.600 came out and I installed .600 on the new server and ran the .500 to .600 db upgrade.
Everything was fine here.
Restored a new copy of 10.1.400 and ran the upgrade and the upgrade failed.
There error’s were:
Error Upgrade Process ModifyPEGLJrnDtl.sql Cannot find the object “Erp.PEGLJrnDtl” because it does not exist or you do not have permissions.
if not exists (select 1 from information_schema.co
Error Upgrade Process ModifyPEGLJrnDtl.sql Cannot find the object “Erp.PEGLJrnDtl” because it does not exist or you do not have permissions.
if not exists (select 1 from information_schema.co
Error Upgrade Process ModifyPEGLJrnDtl.sql Cannot find the object “IM.IMPEGLJrnDtl” because it does not exist or you do not have permissions.
if not exists (select 1 from information_schema.co
Error Upgrade Process ModifyPEGLJrnDtl.sql Cannot find the object “IM.IMPEGLJrnDtl” because it does not exist or you do not have permissions.
if not exists (select 1 from information_schema.co
Error Upgrade Process ModifyPEGLJrnDtl.sql Cannot find the object “Erp.PEGLJrnDtl” because it does not exist or you do not have permissions.
if not exists (select 1 from information_schema.co
Error Upgrade Process ModifyPEGLJrnDtl.sql Cannot find the object “IM.IMPEGLJrnDtl” because it does not exist or you do not have permissions.
if not exists (select 1 from information_schema.co
Error Upgrade Process UpdateLabelType.sql Invalid column name ‘LabelType’.
update Erp.PkgControlLabelType
set LabelType = 'G
Thanks I have a current ticket open CS0000433313 .
Reviving this conversation to hopefully reduce the trial and error process.
We are moving from 10.0.700.4 to 10.1.600.4. I don’t see anywhere in the documentation the steps needed to upgrade the database. Does anyone know what intermediate versions I will have to upgrade to?
Try it direct. For me I think it had to do with do a .500 to .600 then trying .400 to .600.
Worked direct. Thanks Carson.