Occasionally you would like to have the roles you have available on your source instance on your target instance. This article describes a few options to do just that.


Data preservers are primarily intended to preserve system settings and themes, such as instance-specific authentication settings. Do not use data preservers to transfer large sets of data, such as user groups. If you must preserve table data such as users, groups, and roles, consider exporting the records to a file and importing it after the clone is complete. More information can be found in our documentation topic: Data preservation on cloning target instances.




Test Case

Preserve the ‘itil’ role when cloning. This is the link to the ‘itil’ role:


OPTION 1: On target clone instance, export data from various tables to .xml, perform clone, then import all .xmls back onto the target clone instance. You can use these links:

  • /
  • /
  • /

NOTE: Depending on the testing being performed and customizations to roles and ACLs, these tables will likely be optional:

  • /
  • /
  • /
  • /
  • /
  • /
  • /

OPTION 2: Create table exclusions and data preservers.

On the source clone instance, create data preservers (see the documentation topic in the "Note" above).

You can know request a clone. The final result will be all roles were cloned over to the target clone instance. However, the ‘itil’ role on the target instance remains the same.

Applicable Versions


Additional Information

Depending on the size of a database, this can cause clone performance issues and lead to the clone process to fail completely.

KB0717012 - Clone results based on Exclusion and Preserver configuration

KB0716394 - Preserve the Users [sys_user] table when cloning

Exclude a table from cloning

Data preservation on cloning target instances

Article Information

Last Updated:2019-08-02 21:01:45