Record not found in sys_user_list after Cloning Prod to Dev Instance

[Renee-17]

I recently had Prod Cloned to Dev and then performed an upgrade from Tokyo to Vancouver Patch 7. 

During the clone, I wanted to keep the user information for Dev in tact so I add the following tables to the Excluders and Preservers list

1. sys_user_role_contains
2. sys_group_has_role
3. sys_user_grmember
4. sys_user_group
5. sys_user_has_role
6. sys_user

I also added 10 members to the PreservedUserGroup found in sys_user_group.list

I was able to login fine after the clone, however, I noticed that when I navigate to the sys_user_list and click on a user, I get the message "Record Not Found" for almost all users for a select few.  Mainly the admin users but not all and midserver user.  Not even all users on PreservedUserGroup made it.  I can't make out why I can only see the User Records for a few of the users in Dev after the clone....as I don't think this has anything to do with the upgrade to Vancouver although, I'm not quite sure.

Any insight into what is happening?

[James Chun]

Hey @Renee-17,

Can you please provide the details of how you set up the exclusion and preserver on the User table?

Also, when you requested a clone, did you specify a clone profile?

In regards to your question, excluding a parent table will exclude its child tables as well - https://docs.servicenow.com/bundle/washingtondc-platform-administration/page/administer/managing-dat...

IMPORTANT -  note that there is a retention period of instance backup. Because of your 'corrupted' data, I think you should restore the backup and re-do the clone. If so, make sure you don't leave it until the last minute, otherwise, there may be no backup to restore to.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0992741

Cheers

[Renee-17]

Thanks James.  Maybe something was corrupted during the process.  I ended up performing a Full Clone yesterday and all looks better.  I'm just make the necessary updates, after the clone, to the dev server.

[Martin Grosskop]

As I understand it, when you Exclude a table from a Clone it does not leave the data in the table on the target side.

According to the documentation, when you exclude it creates an empty but usable table on the target instance

[Renee-17]

Yes.  That is my understanding also.  But I also include the identical tables in Preservers list.  I referenced the following articles:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0817569

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0717012

[Mark Roethof]

Hi there,

Please read KB0712483:

Description

When configuring a clone on the source instance, if any of the following tables are added on the clone exclude list and not preserved, the table will not be excluded on the target :

• sys_user
• sys_db_object
• sys_dictionary
• sys_user_has_role
• sys_user_role
• sys_user_group
• sys_user_grmember
• sys_group_has_role
• sys_user_role_contains
• sys_group_has_skill
• sys_user_group_type
• sys_user_group_visibility
• customer_contact

This is due to the property "cid.clone.cannot.be.empty.tables.after.clone" which has a list of critical tables that should not be excluded. This property contains a list of tables that, if they are excluded, must also be preserved to avoid complications to the target instance. For example if you excluded sys_db_object and didn't preserve it, you would have no table records on the target instance.