Errors showing while moving complete update set from jakaartha to madrid?

[manmathpanda]

Hi Developers,

Recently we have upgraded our dev instance and UAT instance to MADRID.

Meanwhile i have taken all my works as backup .

Now while moving update sets of jakartha version to new MADRID version , there are several erros showing as below

Type showing as error message

==========================

1)Found a local update that is newer than this one. (thinking to accept remote update)

2)Could not find a record in sp_row for column sp_row referenced in this update

3)Could not find a record in sp_theme for column theme referenced in this update

4)Could not find a record in sp_container for column sp_container referenced in this update

5)Could not find a record in sp_page for column homepage referenced in this update

6) Could not find a record in sp_instance_menu for column sp_rectangle_menu referenced in this update

Type showing as warning message

============================

7)Could not find a record in sp_dependency for column sp_dependency referenced in this update, but did find it in another uncommitted update set   ---- type showing as warning message

8)Could not find a record in sp_widget for column sp_widget referenced in this update, but did find it in another uncommitted update set

9)Could not find a record in  for column sp_angular_provider referenced in this update, but did find it in another uncommitted update set

So could any one please help me on this?

Regards,

Manmath

[vandna]

Hi,

You are getting "could not find a record" Error because system has not found an xml for these changes. That mean, these updates has not been captured in the update set.

[Deepak Ingale1]

This error is indicating that reference records are not yet committed to target system.

This is usually due to 

1) Not following the order of update set 

2) Not capturing all the configuration files in an update set

Below options would help you to solve issues

1) Capture the missing records in another update set and migrate it first to target instance followed by update set which is giving you the issue now

2) Merging of update sets on source instance is another approach, but it has its PROS and CONS

Note: Please mark reply as correct if it has answered your question or mark it as helpful if it has assisted you towards the solution

[manmathpanda]

Hi Deepak,

What ever i have done the modification i captured in update sets.

Now as my dev instance is cloned , it is not possible to find those updates again.

in this case what i will do.

Regards,

Manmath

[VigneshMC]

If dev is cloned, contact hi support , they should have backup of the dev instances and roll back to that.

Else i dont think there is any other option other than doing it all again.

Thanks