Update set taking too long to commit for tables under table rotationIssue The Customer can raise an issue when trying to add a field in a table (e,g sys_email) which is under table rotation, can have a long transaction. This can happen while creating the field manually as well as using an update set.ReleaseAnyCauseThis is because the field creation will trigger ONLINE ALTER or DIRECT alter on the table, which will be applied on all the tables that are under table rotation. For example, if the sys_email table is rotated, it will have shards sys_email, sys_email001, sys_email002... sys_email135 . Adding a field/multiple fields in the sys_email table, the alter will be applied on all the tables under the same transaction, and based on the table data, this can continue for a long time due to the large number of tables.ResolutionIt is not recommended to add fields on such tables; if absolutely necessary, this can be attempted in off-business hours to prevent disruptions for functionality.