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

[Jaspal Singh]

Hi James,

I would suggest get a XML export & import once the clone is complete. Then create a new update set & then merge the one imported via XML.

For your query, "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." - Once cloned you will get the update sets in DEV & then you can commit & get it worked further.

[James Rostron1]

But if i do the clone first i will lose the 2 incomplete update sets?!

[Jaspal Singh]

Clone before importing update sets to target instance if so, then yes you will loose. Better to get an XML of update set done as the count is less in your case.

[Sebastiaan de V]

Keep in mind that the "export to XML" UI action in the update set is only available on "Completed" update set. So first, you have to set the update set to completed, export to XML, clone, import XML and then change the update set status to "In Progress" to continue development on that update set.