SQL CLUSTER NAME REMAIN IN A FAILED STATE

We have the following configuration in our enterprise;
- Two physical servers ( both running windows server 2008 R2)
- The physical servers have been clustered (CLUSTER1).
- Six Virtual Machines ( two for each tier of our SharePoint 2010 installation)
- Two web front ends, two application servers, two database servers.
- The two database servers (running windows server 2008 R2) have been clustered (SQLCLUSTER2) and point to a SAN.
After an unexpected power failure, the SQLCLUSTER2 has refused to come online. The IP Address comes "Online" when turned on manually. The disks also come online when turned on manually using "Bring this resource online". But once the
Cluster name is attempted to be brought online all other resources turn into "failed" state and the entire SharePoint portal becomes unavailable. See image below
Note: We have recently had a problem with one of our Domain Controller and had to be decommissioned one of the two(2) DC's. My investigation reveals that the decommissioned DC was used to create the Cluster Name Object (CNO) SQLCLUSTER2.
I have been battling to restore the cluster to normalcy for over a week now. But periodically (after some hours) all the resources turn to "failed" state and down goes our SharePoint portal.
Please any assistance anyone can offer to help resolve this issue would be highly welcomed.

Hi Pedro Fuentes,
Please refer the following article to check whether your CNO permission is correct.
Error during installation of an SQL server Failover Cluster Instance
http://blogs.msdn.com/b/psssql/archive/2013/09/30/error-during-installation-of-an-sql-server-failover-cluster-instance.aspx
The similar thread:
Sql Server 2008 R2 Clustered Setup fails with The cluster resource 'SQL Server' could not be brought online
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/04ee7ddd-f94a-4410-9ce4-cf25178e09da/sql-server-2008-r2-clustered-setup-fails-with-the-cluster-resource-sql-server-could-not-be-brought?forum=sqlsetupandupgrade
SQL Server Instance is not coming online on windows 2008 R2 cluster
http://social.technet.microsoft.com/Forums/windowsserver/en-US/c7a8ad00-53be-409e-ac54-0a709e62e7bb/sql-server-instance-is-not-coming-online-on-windows-2008-r2-cluster?forum=winserverClustering
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

SQL cluster name on a Windows Failover Cluster

Hello,
I am installing a SQL cluster (first timer) using Windows server and SQL (both 2008 R2)
Windows failover cluster is setup and functioning. I am now installing the SQL failover cluster part.
Question: What should be the "SQL server network name", should it be the same as my Windows cluster name or different name ?
Thanks for your help,
Luca

It should be different, this is known as the virtual SQL Server name in earlier versions of SQL Server failover clusters.
SQL Server Network Name —
Specify a network name for the new SQL Server failover cluster. This is the name that is used to identify your failover cluster on the network.
https://msdn.microsoft.com/en-us/library/ms179530.aspx?f=255&MSPPError=-2147217396
This will be the name used to identify your cluster on the network. This is the name that will be available on the
network for the clients to connect SQL instance.
http://www.mssqltips.com/sqlservertip/1709/install-sql-server-2008-on-a-windows-server-2008-cluster-part-3/

Install db using sapinst on sql cluster

I'm having an issue installing the ep6 db using sapinst on a sql cluster. sapinst wants to install to the localhost/default, but I need to specify the "virtual" sql cluster name.
Is there a workaround using sapinst, or is there some special way one needs to backup/restore onto the cluster from another machine..
any ideas?
jm

<snip>
Marty McCormick
Posts: 17
Registered: 2/25/04
Hi Gabor-
Although it's not supported, you can get EP6 SP2 to work with clustered SQL server 2000 on a virtual MSCS cluster. (We have it working here on Win2003)
The instructions were posted somewhere on this discussion board before, but here they are again:
1) Install SQL as a default local instance with the DB files on a clustered drive. Make sure to choose custom install and select Binary 850 collation.
2) Select a clustered drive for the SQL data files.
3) Install SQL SP3
4) Install SQL hotfix xxxx
5) Run instcoll.exe on the local instance to upgrade to 850 BIN2
6) Run SAPinst, choose ?Database? and allow the setup to create the databases PCD and WCM
7) Detach the databases (Right click on the DB in SQL Enterprise Manger and Detach)
8) Upgrade the local SQL instance to a clustered instance (Note: when running sql setup again, make sure there is no other default instance running on the other node or you will not have the upgrade option). You will have to give the SQL install an instance name at this point.
9) Re-install SQL SP3
10) Re-install hotfix xxx
11) Re-run instcoll.exe (Note: You will have to do this while SQL services are running. Instcoll will prompt you to stop them using the SQL Services Manager, follow the instructions Instcoll displays).
12) Attach the PCD and WCM databases.
13) Run SAPInst on your portal servers and point the install at the clustered SQL virtual server name / instance.
General comments:
There are 3 main considerations when installing EP6 with a clustered SQL backend:
1) You can only run SAPinst ? Database (creates PCD and WCM databases, SAPPCD and SAPWCM users) against a local non-named instance of SQL (SAPinst used the local SQL pipe to connect)
2) Instcoll.exe will NOT run against a SQL installation that has the two EP6 databases (PCD/WCM) attached, hence the need to detach them before running setup / instcoll.
3) Be very careful with collations. After the upgrade to cluster operation the collation will not be the same. If you attach the PCD and WCM databases to a SQL server running the wrong collation YOU WILL CORRUP THE DATABASES!
</snip>

Cluster resource 'SQL Network Name (SQLCLUS1)' of type 'Network Name' in clustered role 'SQL Server (DB1)' failed.

Cluster resource 'SQL Network Name (SQLCLUS1)' of type 'Network Name' in clustered role 'SQL Server (DB1)' failed.
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster
Manager or the Get-ClusterResource Windows PowerShell cmdlet.
I keep getting this error message. Can someone please help. Thank You.
Kranp.

Hi Kranp,
As the issue is more related to Windows Server high availability
, I recommend you post the question in the
Windows Server High Availability (Clustering)
forum. It is appropriate and more experts will assist you.
Besides, there are similar threads regarding to the above error for your reference.
2012 Cluster service name failing
SQL 2012 Failover Cluster - unable to start because
of 'Network Name' failed
Issues with resource creation on W2K12 SQL
failover cluster, confirm procedures
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason: The handle is invalid.

I'm stuck here trying to figure this error out.
2003 domain, 2012 hyper v core 3 nodes. (I have two of these hyper V groups, hvclust2012 is the problem group, hvclust2008 is okay)
In Failover Cluster Manager I see these errors, "Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason: The handle is invalid."
I restarted the host node that was listed in having the error then another node starts showing the errors.
I tried to follow this site: http://blog.subvertallmedia.com/2012/12/06/repairing-a-failover-cluster-in-windows-server-2012-live-migration-fails-dns-cluster-name-errors/
Then this error shows up when doing the repair: there was an error repairing the active directory object for 'Cluster Name'
I looked at our domain controller and noticed I don't have access to local users and groups. I can access our other hvclust2008 (both clusters are same version 2012).
<image here>
I came upon this thread: http://social.technet.microsoft.com/Forums/en-US/85fc2ad5-b0c0-41f0-900e-df1db8625445/windows-2012-cluster-resource-name-fails-dns-registration-evt-1196?forum=winserverClustering
Now, I'm stuck on adding a managed service account (mas). I'm not sure if I'm way off track to fix this. Any advice? Thanks in advance!
<image here>

Thanks Elton,
I restarted 3 hosts after applying the hotfix. Then I did the steps below and got stuck on step 5. That is when I get the error (image above). There
was an error repairing the active directory object for 'Cluster Name'. For more data, see 'Information Details'.
To reset the password on the affected name resource, perform the following steps:
From Failover Cluster Manager, locate the name resource.
Right-click on the resource, and click Properties.
On the Policies tab, select If resource fails, do not restart, and then click OK.
Right-click on the resource, click More Actions, and then click Simulate Failure.
When the name resource shows "Failed," right-click on the resource, click More Actions, and then click Repair.
After the name resource is online, right-click on the resource, and then click Properties.
On the Policies tab, select If resource fails, attempt restart on current node, and then click OK.
Thanks

How to get Cluster Name in SQL

Hi
I've created a cluster model and I have renamed some of the clusters under the compare tab using the ODM tool.
When I query the clusters of the model in SQL I only get the cluster numbers. How can I get the new name/label that I assigned using the ODM tool?
Thanks
Brendan

Hi
How did you query the clusters of the model in SQL?
For example, this query will return the cluster ids and cluster names:
SELECT a.ID, a.CLUSTER_ID
FROM TABLE(DBMS_DATA_MINING.GET_MODEL_DETAILS_OC('CLUS_OC_1_15',NULL,NULL,1,0,0)) a
Denny

SQL Cluster with FQDN only (no instance names)

Is it possible to setup a SQL failover cluster with multiple instances but basically be named the "default instance".
Right now I have three instances: AAA, BBB, and CCC. With failover clusters you associate each SQL instance with its own Drive, its own cluster name, etc. So right now this is how you connect:
aaa.db.domain.com\AAA
bbb.db.domain.com\BBB
ccc.db.domain.com\CCC
Is there a way that you can make it where people can connect by not providing an instance name? Because there is always only one instance per virtual server / fqdn:
aaa.db.domain.com
bbb.db.domain.com
ccc.db.domain.com
I hope I explained well enough. Thanks in advance!

So Azure is not using a regular SQL server? I figured they were just using SQL 2014 or such because they offer Azure services for on-premisis now in your own datacenter.
SQL Azure is definitely not the same as an on-premises SQL Server.
For features and limitation for Azure SQL Database, please see:
http://msdn.microsoft.com/en-us/library/azure/ff394115.aspx
http://msdn.microsoft.com/library/azure/jj879332.aspx
Thanks.
Tracy Cai
TechNet Community Support

Cluster resource 'SQL Server' in Resource Group 'MSSQL' failed.

Hi All,
Last week we face problem on SQL server 2005 Cluster server.
SQL cluster was down with below issue.
Event 1069 : Cluster resource 'SQL Server' in Resource Group 'MSSQL' failed.
Event 19019 : [sqsrvres] CheckServiceAlive: Service is dead
[sqsrvres] OnlineThread: service stopped while waiting for QP.
[sqsrvres] OnlineThread: Error 1 bringing resource online
Kindly any one provide resolution for my above issue.

I have checked in event viewer Application error side error:
Event 19019 : [sqsrvres]
CheckServiceAlive: Service is dead
[sqsrvres] OnlineThread: service stopped while waiting for QP.
[sqsrvres] OnlineThread: Error 1 bringing resource online
System error :
Event 1069 : Cluster resource 'SQL Server' in Resource
Group 'MSSQL' failed.
Before this no error is there in event viewer

SCC Cluster name failed to come online on perticular node

Hi all,
I'm working on a 2-node SCC cluster that I've had up and running for quite a while. For some reason now, I cannot move one of my CMS' to a particular node. I am getting two events in the event viewer: 1207 & 1069.
1207 from event viewer is:
Cluster network name resource 'Network Name (EXG)' cannot be brought online. The computer object associated with the resource could not be updated in domain 'ADI.local' for the following reason:
Unable to obtain the Primary Cluster Name Identity token.
The text for the associated error code is: An attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client.
The cluster identity 'CLUS$' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain.
"EXG" is Exchange application instance (CMS)Network name which is failing on perticular node. Find cluster log below for more info
So, my question is, does anyone know what needs to be done in Active Directory to rectify this problem?
-------- Cluster log ----------
00001824.000025f4::2012/10/16-23:39:11.550 WARN [RES] Network Name <Network Name (EXG)>: Trying to remove credentials for LocalSystem returned status C0000225, STATUS_NOT_FOUND is a non-critical failure for a remove operation
00001824.000025f4::2012/10/16-23:39:11.613 INFO [RES] Network Name <Network Name (EXG)>: Initiating the Network Name operation : 'Verifying computer object associated with network name resource EXG'
00001824.000025f4::2012/10/16-23:39:11.613 INFO [RES] Network Name <Network Name (EXG)>: Trying to find computer account EXG object GUID(6a0d9900d2122d4480ea5acc1653e0be) on any available domain controller.
00001824.000025f4::2012/10/16-23:39:11.738 INFO [RES] Network Name <Network Name (EXG)>: Found computer account EXG on domain controller
domain.com 00001824.000025f4::2012/10/16-23:39:11.738 INFO [RES] Network Name <Network Name (EXG)>: Trying to obtain the VSToken for Core Cluster Name resource
00001824.000025f4::2012/10/16-23:39:11.784 ERR   [RES] Network Name <Network Name (EXG)>: Can't acquire crypto context for container 814f67ea-6f38-41ed-a331-a421cb4de9cc-Netname Resource Data with provider "1\Microsoft Enhanced Cryptographic
Provider v1.0". status 2148073494.
00001824.000025f4::2012/10/16-23:39:11.784 ERR   [RES] Network Name <Network Name (EXG)>: Unable to decrypt Core netname resource's ResourceData, status 2148073494.
00001824.000025f4::2012/10/16-23:39:11.784 INFO [RES] Network Name <Network Name (EXG)>: GetCoreNetnameObject_VSToken returning status 2148073494
00001824.000025f4::2012/10/16-23:39:11.784 ERR   [RES] Network Name <Network Name (EXG)>: This Netname resource can not be brought online, Failed getting token for CNO
00001824.000025f4::2012/10/16-23:39:11.800 WARN [RES] Network Name <Network Name (EXG)>: Trying to remove credentials for LocalSystem returned status C0000225, STATUS_NOT_FOUND is a non-critical failure for a remove operation
00001824.000025f4::2012/10/16-23:39:11.800 ERR   [RHS] Online for resource Network Name (EXG) failed.

Hello,
How this is done ? I couldn't find any documentation, and i struggle with the issue
"ERR [RES] Network Name <Cluster Name>: Can't acquire context handle for container 24263d98-4b17-4cff-866c-80f90ea0623f-Netname Resource Data with provider "1\Microsoft Enhanced Cryptographic
Provider v1.0". status 0X80090016."
ERR [RES] Network Name <Cluster Name>: Unable to Decrypt the password. status 2148073494."
Thanks for the help

SQL Cluster - Unable to obtain IP Address from System Center IP Pool

Hi everyone,
we are trying to deploy a SQL cluster into a windows azure pack tenant cloud.
Our azure pack environment contains:
- 4X Hyper-V server in a failover cluster
- 1X SCVMM server
- multiple WAP server
Steps we have done:
-   Windows failover cluster is installed and configured successfully
-   Quorum disk was configured successfully
-   SQL server 2014 installation (via static IP) is successfully. But routing between the VMs is not possible.
-   SQL server 2014 installation (via DHCP) fails at the end of the installation with following error:
       -> We used DHCP to obtain an IP from the scvmm IP pool.
(01) 2015-04-22 15:29:11 Slp: Running Action: cluster_ip_address_cluster_config_Cpu64
(01) 2015-04-22 15:29:11 Slp: Action Data:
(01) 2015-04-22 15:29:11 Slp:   Feature = SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64
(01) 2015-04-22 15:29:11 Slp:   Scenario = install
(01) 2015-04-22 15:29:11 Slp:   Timing = ConfigNonRC
(01) 2015-04-22 15:29:11 Slp:   ConfigObjectType = Microsoft.SqlServer.Configuration.ClusterConfiguration.ClusterIPAddressPrivateConfigObject
(01) 2015-04-22 15:29:11 Slp:   FeatureName = SQL_Engine_Core_Inst
(01) 2015-04-22 15:29:11 Slp:   FeatureCpuType = Cpu64
(01) 2015-04-22 15:29:11 Slp:   FeaturePackageId = sql_engine_core_inst
(01) 2015-04-22 15:29:11 Slp:   FeatureClusterState = CompleteFailoverCluster
(01) 2015-04-22 15:29:11 Slp: Creating IPv4 address 'SQL IP Address 1 (SQLADFS)'.
(01) 2015-04-22 15:29:11 Slp: Creating cluster resource 'SQL IP Address 1 (SQLADFS)' of type 'IP Address' in group 'SQL Server (ADFS)'
(01) 2015-04-22 15:29:11 Slp: Bringing IP address resource 'Type='IP Address' NetworkName='Cluster Network 1' Group='SQL Server (ADFS)' Resource='SQL IP Address 1 (SQLADFS)'' online
(01) 2015-04-22 15:29:11 Slp: Bringing cluster resource 'SQL IP Address 1 (SQLADFS)' online
(01) 2015-04-22 15:29:12 Slp: Prompting user if they want to retry this action due to the following failure:
(01) 2015-04-22 15:29:12 Slp: ----------------------------------------
(01) 2015-04-22 15:29:12 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
(01) 2015-04-22 15:29:12 Slp: Inner exceptions are being indented
(01) 2015-04-22 15:29:12 Slp:
(01) 2015-04-22 15:29:12 Slp: Exception type: Microsoft.SqlServer.Configuration.Cluster.ResourceOnlineException
(01) 2015-04-22 15:29:12 Slp:     Message:
(01) 2015-04-22 15:29:12 Slp:         The cluster resource 'SQL IP Address 1 (SQLADFS)' could not be brought online. Error: There was a failure to call cluster code from a provider. Exception message: Generic failure
. Status code: 5023. Description: The group or resource is not in the correct state to perform the requested operation.
(01) 2015-04-22 15:29:12 Slp:         .
(01) 2015-04-22 15:29:12 Slp:     HResult : 0x86d8003a
(01) 2015-04-22 15:29:12 Slp:         FacilityCode : 1752 (6d8)
(01) 2015-04-22 15:29:12 Slp:         ErrorCode : 58 (003a)
(01) 2015-04-22 15:29:12 Slp:     Data:
(01) 2015-04-22 15:29:12 Slp:       resourceName = SQL IP Address 1 (SQLADFS)
(01) 2015-04-22 15:29:12 Slp:       errorMessage = There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5023. Description: The group or resource is not in the correct state
to perform the requested operation.
(01) 2015-04-22 15:29:12 Slp:       WatsonData = Microsoft.SqlServer.Configuration.Cluster.ResourceOnlineException@58
(01) 2015-04-22 15:29:12 Slp:       DisableRetry = true
(01) 2015-04-22 15:29:12 Slp:     Inner exception type: Microsoft.SqlServer.Configuration.Cluster.ClusterProviderDetailedException
(01) 2015-04-22 15:29:12 Slp:         Message:
(01) 2015-04-22 15:29:12 Slp:                 There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5023. Description: The
group or resource is not in the correct state to perform the requested operation.
(01) 2015-04-22 15:29:12 Slp:                 .
(01) 2015-04-22 15:29:12 Slp:         HResult : 0x86d70002
(01) 2015-04-22 15:29:12 Slp:                 FacilityCode : 1751 (6d7)
(01) 2015-04-22 15:29:12 Slp:                 ErrorCode : 2 (0002)
(01) 2015-04-22 15:29:12 Slp:         Data:
(01) 2015-04-22 15:29:12 Slp:           ExceptionMessage = Generic failure
(01) 2015-04-22 15:29:12 Slp:           StatusCode = 5023
(01) 2015-04-22 15:29:12 Slp:           Description = The group or resource is not in the correct state to perform the requested operation.
(01) 2015-04-22 15:29:12 Slp:           WatsonData = Microsoft.SqlServer.Configuration.Cluster.ClusterProviderDetailedException@2
(01) 2015-04-22 15:29:12 Slp:         Stack:
(01) 2015-04-22 15:29:12 Slp:                 at Microsoft.SqlServer.Configuration.Cluster.WmiClusterResource.Online(Int32 timeout)
(01) 2015-04-22 15:29:12 Slp:                 at Microsoft.SqlServer.Configuration.Cluster.ClusterResource.Online(Int32 timeout)
(01) 2015-04-22 15:29:12 Slp:         Inner exception type: System.Management.ManagementException
(01) 2015-04-22 15:29:12 Slp:             Message:
(01) 2015-04-22 15:29:12 Slp:                         Generic failure
(01) 2015-04-22 15:29:12 Slp:             HResult : 0x80131501
(01) 2015-04-22 15:29:12 Slp:             Data:
(01) 2015-04-22 15:29:12 Slp:               WmiErrorCode = Failed
(01) 2015-04-22 15:29:12 Slp:               WatsonData = Failed@5023
(01) 2015-04-22 15:29:12 Slp:               Description = The group or resource is not in the correct state to perform the requested operation.
(01) 2015-04-22 15:29:12 Slp:               ErrorType = 1
(01) 2015-04-22 15:29:12 Slp:               Operation = ExecMethod
(01) 2015-04-22 15:29:12 Slp:               ParameterInfo = MSCluster_Resource.Name="SQL IP Address 1 (SQLADFS)"
(01) 2015-04-22 15:29:12 Slp:               ProviderName = WinMgmt
(01) 2015-04-22 15:29:12 Slp:               StatusCode = 5023
(01) 2015-04-22 15:29:12 Slp:             Stack:
(01) 2015-04-22 15:29:12 Slp:                         at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
(01) 2015-04-22 15:29:12 Slp:                         at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject
inParameters, InvokeMethodOptions options)
(01) 2015-04-22 15:29:12 Slp:                         at Microsoft.SqlServer.Configuration.WMIInterop.Resource.BringOnline(UInt32 TimeOut)
(01) 2015-04-22 15:29:12 Slp:                         at Microsoft.SqlServer.Configuration.Cluster.WmiClusterResource.Online(Int32 timeout)
(01) 2015-04-22 15:29:12 Slp: ----------------------------------------
We have tried to reinstall the servers multiple times, without result.
Can anyone assist us in this case?
Thanks
Kind Regards
Julian

Hi Darryl,
thanks for your supply.
We don't have an DHCP in the Cloud. System Center DHCP is used for assigning IP addresses and routing inforamtion to the vms.
This works fine for assigning IP addresses to the vms.
At my current point of understanding network virtualisation with system Center, we do not have an alternative to this way of assigning IP addresses.
Kind Regards
Julian

SQL Cluster unexpected failover

So we had one of our SQL clusters unexpectedly failover recently. Second time in a few months. Two node active/passive SQL 2012 cluster running on Windows 2012 Standard.
Here's what we could cull from the application/system logs?
1. "
Cluster resource 'SQLServer' of type 'SQL Server' in clustered role 'SQLServerRole' failed.
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster
Manager or the Get-ClusterResource Windows PowerShell cmdlet."
2. "
Cluster resource 'SQLServer' (resource type 'SQL Server', DLL 'sqsrvres.dll') did not respond to a request in a timely fashion. Cluster health detection will attempt to automatically recover by terminating the Resource Hosting Subsystem (RHS) process running
this resource. This may affect other resources hosted in the same RHS process. The resources will then be restarted.
The suspect resource 'SQLServer' will be marked to run in an isolated RHS process to avoid impacting multiple resources in the event that this resource failure occurs again. Please ensure services, applications, or underlying infrastructure (such as storage
or networking) associated with the suspect resource is functioning properly."
3. "The cluster Resource Hosting Subsystem (RHS) stopped unexpectedly. An attempt will be made to restart it. This is usually associated with recovery of a crashed or deadlocked resource. Please determine which resource and resource DLL is causing
the issue and verify it is functioning properly."
4. "A timeout (30000 milliseconds) was reached while waiting for a transaction response from the MSSQLSERVER service."
Cluster.log wasn't much more helpful on the root cause either:
00000f28.00001c78::2014/12/04-21:25:54.662 INFO [RES] Network Name <Cluster Name>: Netbios: Slow Operation, FinishWithReply: 0
00000f28.00001c78::2014/12/04-21:25:54.662 INFO [RES] Network Name: [NN] got sync reply: 0
00000f28.00001c78::2014/12/04-21:25:54.662 INFO [RES] Network Name <Cluster Name>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
00000f20.00000e94::2014/12/04-21:25:55.240 INFO [RES] SQL Server Agent <SQL Server Agent>: [sqagtres] IsAlive request.
00000f20.00000e94::2014/12/04-21:25:55.240 INFO [RES] SQL Server Agent <SQL Server Agent>: [sqagtres] CheckServiceAlive: returning TRUE (success)
00001134.000001d8::2014/12/04-21:25:57.287 ERR [RES] SQL Server <SQLServer>: [sqsrvres] Failure detected, diagnostics heartbeat is lost
00001134.000001d8::2014/12/04-21:25:57.287 INFO [RES] SQL Server <SQLServer>: [sqsrvres] IsAlive returns FALSE
00001134.000001d8::2014/12/04-21:25:57.287 WARN [RHS] Resource SQLServer IsAlive has indicated failure.
00000880.0000161c::2014/12/04-21:25:57.303 INFO [NM] Received request from client address HOST-XXX-SQL02.
00000880.0000161c::2014/12/04-21:25:57.303 INFO [RCM] HandleMonitorReply: FAILURENOTIFICATION for 'SQLServer', gen(3) result 1/0.
00000880.000023a4::2014/12/04-21:25:57.303 INFO [GEM] Sending 1 messages as a batched GEM message
00000880.0000161c::2014/12/04-21:25:57.303 INFO [RCM] Res SQLServer: Online -> ProcessingFailure( StateUnknown )
00000880.0000161c::2014/12/04-21:25:57.303 INFO [RCM] TransitionToState(SQLServer) Online-->ProcessingFailure.
00000880.0000161c::2014/12/04-21:25:57.318 INFO [RCM] rcm::RcmGroup::UpdateStateIfChanged: (SQLServerRole, Online --> Pending)
00000880.00001db8::2014/12/04-21:25:57.334 INFO [GEM] Sending 1 messages as a batched GEM message
00000880.0000161c::2014/12/04-21:25:57.334 ERR [RCM] rcm::RcmResource::HandleFailure: (SQLServer)
00000880.00001db8::2014/12/04-21:25:57.334 INFO [GEM] Sending 1 messages as a batched GEM message
00000880.00000bac::2014/12/04-21:25:57.334 INFO [RCM] ignored non-local state Pending for group SQLServerRole
00000880.0000161c::2014/12/04-21:25:57.350 INFO [RCM] resource SQLServer: failure count: 1, restartAction: 2 persistentState: 1.
00000880.0000161c::2014/12/04-21:25:57.350 INFO [RCM] Greater than restartPeriod time has elapsed since first failure of SQLServer, resetting failureTime and failureCount.
00000880.0000161c::2014/12/04-21:25:57.350 INFO [RCM] Will queue immediate restart (500 milliseconds) of SQLServer after terminate is complete."
Any ideas? Anywhere we could look for more specific info? Any preventative measures we could take?
Thanks,
Ryan

Hello,
Since you are using SQL Server 2012, there is an extended events trace running on the cluster that holds all of the return values from sp_server_diagnostics, check that out (.xel) to see if there is anything in there.
The error is pretty straight forward, there wasn't a timely response to the sp_server_diagnostics return set. Look for schedulers that are overwhelmed, SQL server paging a bunch of memory (outside OS pressure), someone pausing a service, etc.
Is this happening during a peak traffic or load time?
-Sean
The views, opinions, and posts do not reflect those of my company and are solely my own. No warranty, service, or results are expressed or implied.

SQL cluster 2008 R2 migration to new Hardware in VM

Hi,
We have a task to migrate existing Physical SQL Cluster DB to new Hardware but in VM. (cannot argue with the client)
hence our plan is to install new Cluster in VM with same Windows and SQL version i.e Win 2K8 R2 ENT w/SP and SQL 2K8
R2 STD w/SP and use SQL mirroring option for the DB to migrate on the new Server (keeping the downtime to as low as possible and advantage of bringing the old server online in case of any issues..)
Below points are for a single instance, couple of DB to migrate:
Keep the physical production server running
In-Parallel build New SQL Cluster in VM (keep same version windows/sql)
Keep Same drive letter for Quorum, MSDTC, DATA, LOG & Backup
Keep the same Instance Name, SQL Network Name can be different (will be changed to old network name once the PROD is shutdown)
Check all logins windows and SQL to be same on both the clusters
Copy all the jobs, SSIS packages etc.. .create the location folder as per current server on the VM SQL Cluster
Perform full backup of old cluster company-db databases or use the existing latest backup (full, differential, transaction)
Restore databases in the new cluster with no recovery so additional log file or differential backup can be restored
Create SQL Mirroring for the Database and select the principal server (old cluster) and the mirror server (new VM cluster)
Choose mirroring without witness ( no auto failover as we don’t need the old server later)
Start the mirroring – (hopefully everything synchronized and working)
During the downtime –
Stop the application/ client connection – if possible
Failover the DB through Mirroring option
Once the mirrored server becomes Principal and data is accessible – stop the mirroring
Now the new VM SQL Cluster DB is online
Shutdown the old cluster company-db (Node1 & Node2)
Come back to VM SQL Cluster and change the Network name to the old server network name (so that client connections are not affected)
Check if the DNS entries are updated with correct name and IP address
Delete DNS entries for old company-db on DNS Servers if not deleted, delete the old server SQL network name in computer object
Stop SQL Resources on the new VM SQL Cluster (take it offline all the resources)
Bring online the SQL Resource and make sure the SQL resources are online and new network name is reachable
Wait till you see machine name company-db in active directly (AD) and DNS server will have entry for company-db
Verify connectivity for company-db from outside.
If things are not going as per the plan then shut down the new VM cluster
Revert back the DNS settings
Power up the Old SQL Server
The DB will show “restoring mode” – use command to make it online “RESTORE DATABASE (dbname) WITH RECOVERY”
Check the DB
Start using the OLD server again
Troubleshoot the failed scenario ;)
Need to know if the above steps are okay, and any consideration once the new VM SQL Cluster is online.
Kindly let me know if there anything else to transfer apart from the logins, jobs, folder location etc.. !!
Many Thanks

Hello,
Well if you don’t change the instance name (name = ABC) then its OK.
Try the following resources about transferring SQL Server logins:
http://support.microsoft.com/kb/918992/en-us
http://www.mssqltips.com/sqlservertip/2081/transfer-sql-server-jobs-task-and-transfer-sql-server-logins-task-in-ssis/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL Cluster requiremnt for Lync 2013

Hi
We are are planning to deploy Lync 2013 enterprise. Planning to use SQL cluster. Would like to clarify whether we must create a sepearte sql instance for Lync 2013 or can we use an existing shared instance to create a seperate database for Lync.
We prefer 2nd approach. Is there any issues or demerits using existing shared SQL instances?
Thanks and regards,
Aboo Arif

Hi AbooArif.
This kind of question is very common. Basically here is the Microsoft Documentation about it.
Database software support in Lync Server 2013
https://technet.microsoft.com/en-us/library/gg398990.aspx
This point is the important: "If you collocate Lync Server databases with other databases, we highly recommend assessing all factors that might affect availability and performance, as well as ensuring that, if one node fails, the remaining node can
handle the load. To verify failover capabilities, we recommend testing all failover scenarios."
We can say the following: It's recommended to use a separate SQL server for Lync, however collating Lync database with other SQL databases will work, but has an high probability of present some performance problems. Many customers prefer to use this option
considering the cost of SQL licenses.
It is important to consider all the hardware requeriments for the Lync Server BackEnd role:
https://technet.microsoft.com/en-us/library/gg398835.aspx because the normal issue when customers share the SQL server with other instances is due to performance issues. Also note
that if you have multiple front end pools, these cannot share a SQL server.
PLEASE REMEMBER, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answered"

Cluster Name Resolution and failover

We are running a cluster consisting of two managed servers and one
          admin server on Solaris using WebLogic 6.1 SP3. The application is
          composed of EJB's only. Each managed server has been assigned a DNS
          name (host names weblogic-cluster-ma & weblogic-cluster-mb). A
          cluster address (DNS name weblogic-cluster) has been setup to
          round-robin amongst the two IP's assocaited with the managed server
          that are participating in the server.
          If I do a nslookup on the same cluster name successively, I get two
          different IP addresses.
          The behavior that I am observing is as follows:
          1. When all instances participating in the cluster are running
          everything is fine. The clients are able to connect to the machine
          using the cluster name while doing the JNDI lookup.
          2. When one of the servers participating in the cluster is down, and
          the cluster name is used to access it (the round-robin DNS name),
          depending on which machine is down, all calls either get through or
          none of them get through.
          I do not want to use the following cluster aware syntax to access the
          cluster
          t3://weblogic-cluster-ma,weblogic-cluster-mb:7001
          Instead I would like to use the cluster name
          t3://weblogic-cluster:7001 and have transparent failover.
          It would appear to me that if I have DNS return me back all the IP's
          associated with the cluster then my problem would be solved.
          for example:
          nslookup weblogic-cluster.
          216.33.240.47, 216.33.240.12
          Is this possible? How have others solved this problem.
          Thanks for your reply!


Aaravali,
          What you describe should work. However, could you clarify statement
          #2, specifically, "all calls either get through or none of them get
          through." Do you mean that the client either works or it simply fails?
          Are you failing on creating the initial context?
          Regards,
          Simon
          Developer Relations Engineer
          BEA SupportAaravali Karavali wrote:
          > We are running a cluster consisting of two managed servers and one
          > admin server on Solaris using WebLogic 6.1 SP3. The application is
          > composed of EJB's only. Each managed server has been assigned a DNS
          > name (host names weblogic-cluster-ma & weblogic-cluster-mb). A
          > cluster address (DNS name weblogic-cluster) has been setup to
          > round-robin amongst the two IP's assocaited with the managed server
          > that are participating in the server.
          >
          > If I do a nslookup on the same cluster name successively, I get two
          > different IP addresses.
          >
          > The behavior that I am observing is as follows:
          >
          > 1. When all instances participating in the cluster are running
          > everything is fine. The clients are able to connect to the machine
          > using the cluster name while doing the JNDI lookup.
          > 2. When one of the servers participating in the cluster is down, and
          > the cluster name is used to access it (the round-robin DNS name),
          > depending on which machine is down, all calls either get through or
          > none of them get through.
          >
          > I do not want to use the following cluster aware syntax to access the
          > cluster
          >
          > t3://weblogic-cluster-ma,weblogic-cluster-mb:7001
          >
          > Instead I would like to use the cluster name
          > t3://weblogic-cluster:7001 and have transparent failover.
          >
          > It would appear to me that if I have DNS return me back all the IP's
          > associated with the cluster then my problem would be solved.
          >
          > for example:
          >
          > nslookup weblogic-cluster.
          >
          > 216.33.240.47, 216.33.240.12
          >
          > Is this possible? How have others solved this problem.
          >
          > Thanks for your reply!

SQL Expression in decode function or case statement?

Can I put SQL expressions in decode function or case statement?
For example,
select le.profile, decode( select count(1) from profile_data where NAME= 'XXXX_AFTER' and object_id = le.profile, 0, 'N', 'Y')
from element le;
or
select le.profile, case WHEN ( select count(1) from profile_data where NAME= 'XXXX_AFTER' and object_id = le.profile) = 0 THEN 'N'
ELSE 'Y'
from element le;
None of the above work.
Can anyone tell me how to make it work?
Is there any workaround?
Thanks,
J

You simply needed and END to your CASE statement;
SQL> with profile_data as (
   select 'XXXX_AFTER' name, 1 object_id from dual),
     element as (
   select 1 profile from dual union all
   select 2 from dual)
select le.profile,
   case WHEN ( select count(1) from profile_data where NAME= 'XXXX_AFTER' and object_id = le.profile) = 0
   THEN 'N'
   ELSE 'Y'
   END new_col
from element le
   PROFILE N
         1 Y
         2 N

SQL CLUSTER NAME REMAIN IN A FAILED STATE

Similar Messages

Maybe you are looking for