Search

Can't create clone via SnapCenter
https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/Can_t_create_clone_via_SnapCenter
SCSQL clone creation fails due to a database name conflict on the destination SQL instance even though the database has been deleted: 2021-02-02T11:52:11.0356597+00:00 WARN SnapManagerWeb_<Job_Id> PID...SCSQL clone creation fails due to a database name conflict on the destination SQL instance even though the database has been deleted: 2021-02-02T11:52:11.0356597+00:00 WARN SnapManagerWeb_<Job_Id> PID=[7132] TID=[61] Database <Target_Server_Name_Target_Database_Clone_Name> is existing on <Target_Server_Name> cannot create another database with same name
SnapCenter for SQL Plug-In is unable to enumerate SQL Server Availability Group
https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/SnapCenter_for_SQL_Plug-In_is_unable_to_enumerate_SQL_Server_Availability_Group
SnapCenter unable to enumerate SQL Availability Group. SnapCenter interface does not show a SQL Availability Group that exists, even though SnapCenter is able to enumerate disks on each node. DCOM was...SnapCenter unable to enumerate SQL Availability Group. SnapCenter interface does not show a SQL Availability Group that exists, even though SnapCenter is able to enumerate disks on each node. DCOM was unable to communicate with the computer <Windows cluster name> using any of the configured protocols; requested by PID <PID> (C:\Program Files\NetApp\SnapCenter\SnapCenter Plug-in for Microsoft SQL Server\SmSqlServiceHost.exe).
Managing Tags with the AppTemplate fails with TooManyRequests -error
https://kb.netapp.com/Cloud/BlueXP/Cloud_Manager/Managing_Tags_with_the_AppTemplate_fails_with_TooManyRequests_-error
Trying to add or modify tags for X amount of resources at once fails with the following error: Details='Response status code does not indicate success: TooManyRequests (429); Substatus: 3200; Activity...Trying to add or modify tags for X amount of resources at once fails with the following error: Details='Response status code does not indicate success: TooManyRequests (429); Substatus: 3200; ActivityId: 5caa8c42-86a9-4e5e-8579-85da07d3e44c; Reason: (Response status code does not indicate success: TooManyRequests (429); Substatus: 3200; ActivityId: 5caa8c42-86a9-4e5e-8579-85da07d3e44c; Reason: (Response status code does not indicate success: TooManyRequests
SCSQL display wrong information for AGs with similar names
https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/SCSQL_display_wrong_information_for_AGs_with_similar_names
Applies to SnapCenter Server SnapCenter plug-in for SQL (SCSQL) Issue In an environment where co-exist several SQL Availability Groups (AG) with same name: SnapCenter GUI display same data for all AGs...Applies to SnapCenter Server SnapCenter plug-in for SQL (SCSQL) Issue In an environment where co-exist several SQL Availability Groups (AG) with same name: SnapCenter GUI display same data for all AGs with the same name Backups will fail for any AG with similar name that is not the first in the list
SnapCenter - Performing a SQL tail log restore job fails
https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/SnapCenter_-_Performing_a_SQL_tail_log_restore_job_fails
Applies to SnapCenter Plugin for Microsoft SQL (SCSQL) 4 Issue If Database has corrupted data files (.mdf) the option "Create transaction log backup before restore" does not work. In this scenario tai...Applies to SnapCenter Plugin for Microsoft SQL (SCSQL) 4 Issue If Database has corrupted data files (.mdf) the option "Create transaction log backup before restore" does not work. In this scenario tail-log backup always fails with the error: "No database found to be backed up for this user. Verify login has sysadmin rights and ensure databases are in a valid state"
After upgrade to 9.7x release the system comes up with root volume not working properly
https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/After_upgrade_to_9.7x_release_the_system_comes_up_with_root_volume_not_working_properly
Applies to ONTAP 9.7 Issue Upgrading to 9.7x release may cause the system to come up with the following error: ROOT VOLUME NOT WORKING PROPERLY: RECOVERY REQUIRED
After switchback database have pending or failed services
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/After_switchback_database_have_pending_or_failed_services
Applies to ONTAP MetroCluster Microsoft Cluster Service (MSCS) Oracle Microsoft SQL Server Issue After a disaster recovery (DR) MetroCluster event switchback causes pending or failed services on Micro...Applies to ONTAP MetroCluster Microsoft Cluster Service (MSCS) Oracle Microsoft SQL Server Issue After a disaster recovery (DR) MetroCluster event switchback causes pending or failed services on Microsoft Cluster Service (MSCS) Oracle and Microsoft SQL instances
Microsoft SQL Disk overwhelmed high response times
https://kb.netapp.com/on-prem/ontap/Perf/Perf-KBs/Microsoft_SQL_Disk_overwhelmed_high_response_times
Applies to Microsoft SQL Any version of ONTAP or Data ONTAP Issue Running SQL performance metrics, Avg Disk Queue Length is over 1 An error may be reported in the running SQL logs: Disk overwhelmed: A...Applies to Microsoft SQL Any version of ONTAP or Data ONTAP Issue Running SQL performance metrics, Avg Disk Queue Length is over 1 An error may be reported in the running SQL logs: Disk overwhelmed: Avg Disk Queue Length is greater than 1 and response times are greater than 25 ms for IO sizes of 64 KB or smaller or 35 ms for IO sizes greater than 64 KB.
Active IQ Unified Manager with MySQL 8.0.22 causes NullPointerExceptions
https://kb.netapp.com/data-mgmt/AIQUM/AIQUM_Kbs/Active_IQ_Unified_Manager_with_MySQL_8.0.22_causes_NullPointerExceptions
Active IQ Unified Manager 9.7 ( AIQUM ) Active IQ Unified Manager 9.8 ( AIQUM ) After upgrade, Active IQ Unified manager does not acquire new data from the clusters due to a NullPointerExceptions show...Active IQ Unified Manager 9.7 ( AIQUM ) Active IQ Unified Manager 9.8 ( AIQUM ) After upgrade, Active IQ Unified manager does not acquire new data from the clusters due to a NullPointerExceptions shown in the ocumserver.log org.springframework.transaction.UnexpectedRollbackException: JTA transaction unexpectedly rolled back (maybe due to a timeout); nested exception is javax.transaction.RollbackException: ARJUNA016053: Could not commit transaction.
SQL cluster lost connection to iSCSI LUN intermittently
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/SQL_cluster_lost_connection_to_iSCSI_LUN_intermittently
SQL cluster lost connection to iSCSI LUN intermittently This message indicates that SQL Server has issued a read or write request from disk, and that the request has taken longer than 15 seconds to re...SQL cluster lost connection to iSCSI LUN intermittently This message indicates that SQL Server has issued a read or write request from disk, and that the request has taken longer than 15 seconds to return. You might also notice other symptoms associated with this message: high wait times for PAGEIOLATCH waits, warnings, or errors in the system event log, indications of disk latency issues in system monitor counters.
Changing the default SQL port 1433 to 59771, SMSQL connection issues with SQL DB
https://kb.netapp.com/Legacy/SnapManager/Changing_the_default_SQL_port_1433_to_59771_SMSQL_connection_issues_with_SQL_DB
Applies to SnapManager for Microsoft SQL (SMSQL) Microsoft SQL Server (SQL) Availability Group Microsoft SQL Server Configuration Manager x32 bit (SQL SCM) Issue Changing the default SQL port 1433 to ...Applies to SnapManager for Microsoft SQL (SMSQL) Microsoft SQL Server (SQL) Availability Group Microsoft SQL Server Configuration Manager x32 bit (SQL SCM) Issue Changing the default SQL port 1433 to 59771, SMSQL is no longer able to make connections to SQL DB Error: Failed to connect to server. A network-related or instance-specific error occurred while establishing a connection to SQL Server.