Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

25861

September 30th, 2014 02:00

Catalog update error after upgrade to OME 2.0

Successfully upgraded OME 1.3 -> 2.0.

Refreshed all ranges successfully.

Catalog update reported following error:

 

Import Dell Version Control Catalog for System Update from ftp://ftp.dell.com/catalog/catalog.cab failed.Exception message: Error: 2627, Procedure: usp_PackageApplicable_Comparison_PerDevice, Message: Violation of PRIMARY KEY constraint 'PK_ApplicablePackage'. Cannot insert duplicate key in object 'Catalog.ApplicablePackage'. The duplicate key value is (-1109705571, 25, 3550833e-3dbb-f9d6-7162-0c79c477241d, 00460041-0038-0044-4600-330039003700).

 

However it looks that it went through, because now it says that catalog version is latest.

Can this be ignored?

 

2 Intern

 • 

2.8K Posts

September 30th, 2014 09:00

Thanks for the question.

I'll check around to see if this has been seen.  But it sounds like when you view the catalog version and date in the OME console, it is showing the most current?

In the past when folks have run into something similar they will use SQL Management Studio to clobber the old catalog and download the latest.  The command is:

DELETE FROM OMEssentials.Catalog.Manifest;

But if you are not comfortable with messing with the database, you might consider a support ticket to let them take a look.

The upgrade logic is supposed to run this command before the new catalog is downloaded.  

Regards,

Rob

41 Posts

October 1st, 2014 00:00

Rob,

I executed the delete statement and triggered catalog import. Now import job completed without errors.
Thanks for help!

2 Intern

 • 

2.8K Posts

October 1st, 2014 15:00

hey that's great.  Thanks for taking the time to update the thread.

Regards,

Rob

March 31st, 2017 07:00

Hi Rob,

I know this is an old post, but I've ran the suggested query and now it says that "Catalog is inaccessible".

OME version 2.2

OME was not updating the catalog - the error was "Catalog signature verification failed"

Any idea?

Thanks.

No Events found!

Top