Preserve the Users [sys_user] table when cloningDescription<!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: -5px; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul { margin-left: 0; } li { padding-left: 1em; } hr { border-top-width: 1px; border-top-style: solid; border-top-color: #cccccc; } --> Description How to preserve the Users [sys_user] table when performing a clone. Procedure 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. Information regarding avoiding using data preservers for large data sets can be found here: Data preservation on cloning target instances On the source clone instance, create a table exclusion.On the source clone instance, create a table preserver.3. You can now request a clone. Applicable Versions All Additional Information Only sys_user records are preserved. Depending on the size of a database, this can cause clone performance issues and lead to the clone process to fail completely. Additionally, roles are not preserved. KB0717012 - Clone results based on Exclusion and Preserver configuration Exclude a table from cloning Data preservation on cloning target instances