Can I reimport a batch update set?

[magee]

We recently cloned down to our dev instance from PROD. We had update sets in our dev instance that we exported (batch update set). So one batch update w/ about 12 update sets (some large, some small).

I reimported the import set and in the middle/end of the update set import, our dev server was restarted. It's a dev instance so not a big deal.

My coworker says, 'hey I'm going into my update set (one of the child update sets part of the batch update), and the updates are not in there'.

Hmm, so I go into sys_update_xml and the some of the update records have an update set identified, some do not. My guess is that the update did not 100% commit because of the server restart, thus leaving the Update Set name blank on some of the update records in sys_update_xml.

So my question is, what can I do here?

1. Back out the batch update set and reimport the batch update set?

2. Ask our server guys to clone prod back down to my dev instance and reimport my batch update set?

3. Reimport the batch update set and pray for no duplicate records?

4. Other?

[Dr Atul G- LNG]

Hi @magee 

1. Back out the batch update set and reimport the batch update set?

Atul: For the safe side, yes, reimport is a good option to avoid any issue after clone.

2. Ask our server guys to clone prod back down to my dev instance and reimport my batch update set?

Atul: No, once you clone the Dev from prod, your all work will be gone. 

3. Reimport the batch update set and pray for no duplicate records.

Atul: Yes, reimport fresh and use that only for commit.

[magee]

I'm confused. Do I back out the original batch update first or do I not back out the original batch update first?

[Dr Atul G- LNG]

Dont back out, back out will be more risky.