Applying schema change: cmdb$par1 - Batch Altering table while trying to commit update set
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2023 05:50 AM
Greetings! I'm wondering if anyone can help identify why we are receiving the following message each time we try to commit an update set from a subprod environment to our dev environment. No matter what's in the update set, we receive this message and cannot move forward with the update set commit.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2023 01:58 PM
Hi @ACobb
This message shows up when you alter the table that can result in a schema change
There are various changes that can/may result in a table alter as listed below -
- Modifying the datatype of a column in a table
- Adding new column/columns to a table
- Removing an existing column from a table
- Drop a table from a the database
- Checking the 'unique' checkbox from the dictionary record of a field
- Adding, removing or modifying an index of a table directly from the database (This operation can only be performed by support)
You can refer below article for more details
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0714575