Preserve Update Sets when Cloning

[James Rostron1]

Hi,

I've read many other posts about this but am not seeing the same results.

in Cloning Instances and Update Sets it advises to export update sets to the target instance then import them back. When i do this my update sets can only be previewed or loaded so not sure how i would then get them back to dev so i could carry on writing to the local update set.

I need a method of preserving 2 x non-completed update sets from Dev before i clone over the Dev instance.

Can i simply add the sys_update_set table to the 'exclude table'?

Do i also need to add sys_update_xml?

Lastly do i need to add anything to the 'preserve data' module?

Thanks,

James

[James Rostron1]

Thanks Sebastiaan,

I 100% understand the process you've detailed, and this is what I have tried but when I import an XML to my local update set table (right click>import XML), it is added to the "Retrieved Update Sets" list and my only options are to then preview and commit. Does that make sense?

In other words it doesn't go into local update sets to change the status to "in progress".

[Sebastiaan de V · Accepted solution]

jamesrostron you have no choice but to do it like that. Since you made a clone, you need to (re)apply the changes in your exported update set. Once you committed a retrieved update set, it will (also) appear in the local update sets, not before.The XML export you make is the Update Set (of course including all customer updates), which is then imported as a "new" updated set after the cloning.   The procedure is described here: Save an update set as a local XML file

[James Rostron1]

Thanks Sebastiaan, now i understand

[michaelcory]

Hi jaspalsinghchot, 

I have followed these steps and am now wondering what to do with the two Update sets that were merged but still "In Progress".  Can they simple be set to "Completed"?  Otherwise I have the Merged Update Set and two other displaying as "In Progress"

Steps to preserve Update Sets in DEV prior to cloning DEV from PROD:

1. Export Update Set to XML and Save file locally
2. Clone PROD to DEV
3. Upgrade DEV to new version
4. Import saved Update Sets back to DEV (Load and Commit)
5. Set the Imported Update Set Status back to "In Progress"
6. Create a new Update Set
7. Merge the Imported Update Set with the newly created Update Set
8. Leave the Status of the Merged Update Set to "In Progress"
9. Can the Status of the two Merged Update Sets be changed from "In Progress" to "Complete"?