Does cloning delete update sets in the target instance?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2015 07:17 AM
When we implemented ServiceNow 2 months ago, we did all our development work in our DEV instance and then cloned the DEV instance to Production. The marjority of the work was captured in update sets in DEV.
Fast Forward to this week... SN applied a quarterly patch (Q4-2016 Fuji Patch 7 Hot Fix 5) on our production instance. This patch reverted many things we modified back to out-of-the box. We logged a HI incident and they confirmed that the patch updated all of these because there was no record of change in the sys_update_xml table. The same patch was applied to our DEV instance a few weeks ago without any issues.
Luckily we still have a DEV instance that is still configured pretty close to production and can re-migrate all of the update sets back to production. However, I would still like to understand what happened. Since we cloned DEV to Prod, shouldn't this table and all update sets from DEV be copied to Prod as well? Should cloning delete the update sets from the target instance?
Regards,
Johnny
Fuji Patch 7 Hot Fix 5
Reg
Re
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2015 10:54 AM
Would these be from the Source or Target instance? I checked both and we have most of the tables you are showing in your screenshot. Is there a specific one that would be for the update sets that was possibility excluded?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2015 11:31 AM
sys_update_set is the table of the update sets themselves. sys_update_xml is a table of all the changes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2015 11:50 AM
Neither of those tables are in the Excludes Tables for me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2015 11:37 AM
The Exclude Table stuff is only important for clones. You're not planning on cloning back up to prod again... right?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2015 11:51 AM
No, not planning to clone back to prod again. At this point, just trying to figure out why this issue happened and to hopefully ensure that it doesn't happen again for the next patch.
