Ensure tables sys_ux_style and sys_ux_theme are excluded from a clone back"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-26-2024 02:50 AM
How can we Ensure tables sys_ux_style and sys_ux_theme are excluded from a clone back" . I am unable to understand this .I think because of this i am unable to add required header color to my instance. Can someone help me in this..
Thank You!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-26-2024 08:55 PM
Hi @Hitesh Ramba ,
The System Clone > Exclude Tables module lists the tables that are not copied during a system clone. By default, the system excludes tables for logging, auditing, notifications, workflow contexts, and license usage.
sys_db_object and sys_db_object.* cannot be added to the exclusions.
When excluding child tables of the Task table, which use the table per hierarchy extension model, child tables are excluded. You do not need to exclude the parent Task table together with the child table.
To preserve the existing data on the target instance, see Create a data preserver. Data on tables that reference the table, such as business rules, is not excluded.
- sys_user
- sys_user_role
- sys_user_group
- sys_user_grmember
- sys_group_has_role
- sys_user_role_contains
- customer_contact (if the Customer Service Management plugin is active)
Procedure
- On the source instance, navigate to System Clone > Exclude Tables.
- Select New.
- Enter the table Name.
Entering a parent table results in the clone process also excluding its child tables. For example, excluding the Task table would also exclude the Change, Incident, and Problem tables.
- Select Submit.