Resolving User Deletion Issue in ScaleArc 'Users & DBs'

Issue Summary:
A user reported an inability to delete a user from the 'Users & DBs' section in ScaleArc. The issue involved error messages indicating that the user could not be deleted and ScaleArc failing to connect to the primary server when adding a new user. The errors are related to SQL Server 2019's compatibility with ScaleArc 3.x, which only supports up to SQL Server 2016.

Environment:

• ScaleArc Version: 3.x
• Database: SQL Server 2019 (Note: SQL Server 2019 is not fully certified with ScaleArc 3.x. It is recommended to use ScaleArc 2020.x for full compatibility.)
• Error Logs:
  Copy code

  api.error.2021042608:2021-Apr-26 08:42:00 ClientIp=x.x.x.x HTTP_REFERER=https://x.x.x.x/api/cluster/1/user/18?apikey= DATA=" | Command sent to core = delete|user|1|T0xUUF9GaW5kQ2hpcHNNb3VzZXI=| | result = Data Not Found For Deletion | " api.error.2021042608:2021-Apr-26 08:42:00 ClientIp=x.x.x.x HTTP_REFERER=https://x.x.x.x/api/cluster/1/user/18?apikey= DATA="dprohttps://support.scalearc.com/kb/articles/461 2267 ERROR: kb2267 Failed to delete user. Data Not Found For Deletion"

Steps to Resolve:

1. Check SQL Server Compatibility:

   • Ensure you are using a ScaleArc version that supports SQL Server 2019. If you are using ScaleArc 3.x, consider upgrading to ScaleArc 2020.x for full compatibility.

2. Create a New Cluster:

   • Create a new ScaleArc cluster pointing to the same SQL Availability Group (AG) but using a different instance name and port.
   • Replicate all the configurations from the existing cluster to the new cluster.

3. Restart the Cluster:

   • Restart the new cluster to sync the core cluster process with the cluster’s SQLite configuration database.
   • This should restore user deletion and modification capabilities.

4. Switch Over to the New Cluster:

   • If a significant number of users need to be recreated, perform a high availability (HA) switch over to the new cluster, which will include the recreated users in the replicated configuration.

5. Stop and Switch Services:

   • Stop the ScaleArc services, switch the ports and instance names between the existing and new clusters, and restart the ScaleArc cluster.
   • Note: If the old cluster was configured as the HA fencing cluster, it will be automatically started as well hence you must subsequently switch over the HA fencing cluster to the new cluster, and thereafter the old cluster can be safely stopped.

6. Gather Logs and Error Messages:

   • If the issue persists, collect specific error messages or screenshots encountered during these actions, along with the version of ScaleArc you are using. You can also provide the api.error.* logs for further analysis.

Important Notes:

• SQL Server 2019 Compatibility: If you are using SQL Server 2019 with ScaleArc 3.x, it is recommended to move to ScaleArc 2020.x, as full certification for SQL Server 2019 exists in the later version.
• Cluster Sync: The core cluster process sync with the SQLite configuration database is essential for restoring normal functionality.