User unable to login after cloneIssue <!-- div.margin{ padding: 10px 40px 40px 30px; } table.tocTable{ border: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } table.noteTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:2; } table.internaltable { white-space:nowrap; text-align:left; border-width: 1px; border-collapse: collapse; font-size:14px; width: 85%; } table.internaltable th { border-width: 1px; padding: 5px; border-style: solid; border-color: rgb(245, 245, 245); background-color: rgb(245, 245, 245); } table.internaltable td { border-width: 1px; padding: 5px; border-style: solid; border-color: #E0E0E0; color: #000000; } .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; text-decoration:underline; } h4{ color: #646464; font-weight:BOLD; font-size:15px; text-decoration:; } h5{ color: #000000; font-weight:BOLD; font-size:13px; text-decoration:; } h6{ color: #000000; font-weight:BOLD; font-size:14px; text-decoration:; } ul{ list-style: disc outside none; margin-left: 0; } li { padding-left: 1em; } --> After cloning from prod to subprod, user is unable to login with local credentials in subprod. Logs shows following error when user attempts to login: Logging event: SNC.Auth.DB.Login.Failed with parm1: user_name=firstname.lastname@company.com and parm2: remoteAddr=xxx.xxx.xxx.xxx ReleaseAll releasesCauseThe sys_user table which has the local login credentials are overwritten when clone is done from prod to lower instance.ResolutionThe sys_user records need to be preserved and excluded to retain the local records in the lower instance table as they are. If this solution is implemented, it is recommended to also preserve the sys_user_has_role ,sys_user_role and sys_user_group tables along with the sys_user table to maintain the relationships across all the users and their roles. Also, when the sys_user records that are present in Production but not in dev, can result in records where that user record is required to have empty references. So please use this option only if you really need to preserve the records in sys_user table as is.Related LinksHow to request default admin password reset via Now Support Service Catalog