Cluster windows 2008 NODE MAJORITY

hallo, i have a windows 2008 cluster with three nodes (A-B-C) in NODE MAJORITY (default windows). I have installed oracle 10g rel. 2 Node A is active with DB1 , node B is active with DB2, node C isi passive for node A or B.
have installed failsafe and , apparently , the resource move from node A to C, and resource move from node B to C.
But when i open Failsafe panel if the services OracleMSCService is not on node with Node Majority it's not open.
I want to configure the service to move with Cluster Node Majority. How to do ??
or i obliged to create a cluster with NODE MAJORITY and DISK QUORUM ???
or i obliged o reduce the cluster at two node with disk quorum ????
IS VERY URGENT , FRIDAY THE CLUSTER GOES TO PRODUCTION

DUPLICATE POSTING
{message:id=4173094}
This is not acceptable usage of OTN. Please cease with posting the exact same message in multiple OTN forums.

Similar Messages

2 node cluster windows 2008 R2 cluster won't form

Hi,
I'm trying to build a 2 node cluster and having no luck at all.   My validation works great but when I go to create the cluster it fails on the forming cluster section after about 2 minutes.   I seem to have everything in order and can't
figure out the problem.   Here is what is in the cluster log.
000010b0.00001108::2010/08/26-20:43:54.067 INFO [CHANNEL 192.168.210.236:~59824~] graceful close, status (of previous failure, may not indicate problem) ERROR_SUCCESS(0)
000010b0.00001108::2010/08/26-20:43:54.067 ERR   [SM] Caught GracefulClose(1226)' because of 'channel to remote endpoint 192.168.210.236:~59824~ is closed' authenticating.
000010b0.000012d8::2010/08/26-20:43:54.067 INFO [SV] Authentication and authorization were successful
000010b0.000012d8::2010/08/26-20:43:54.067 DBG   [SM] SrvCtxt initialized with package Kerberos, MaxTokenSize = 12000, RequiredCtxAttrib = 133122, HandShakeTimeout = 30000
000010b0.00001108::2010/08/26-20:43:54.067 DBG   [SM] Handling auth handshake posted by thread id 4824
000010b0.00001108::2010/08/26-20:43:54.067 DBG   [CHANNEL 192.168.210.236:~59824~]/recv: Attempting to perform I/O on closed stream.
000010b0.00001108::2010/08/26-20:43:54.067 DBG   [CHANNEL 192.168.210.236:~59824~] Not closing handle because it is invalid.
000010b0.00001108::2010/08/26-20:43:54.067 INFO [CHANNEL 192.168.210.236:~59824~] graceful close, status (of previous failure, may not indicate problem) ERROR_SUCCESS(0)
000010b0.00001108::2010/08/26-20:43:54.067 ERR   [SM] Caught GracefulClose(1226)' because of 'channel to remote endpoint 192.168.210.236:~59824~ is closed' authenticating.
000010b0.000012d8::2010/08/26-20:43:54.067 DBG   [CHANNEL 192.168.210.236:~59824~] Not closing handle because it is invalid.
000010b0.0000106c::2010/08/26-20:44:52.906 INFO [CS] Service Stopping...
000010b0.0000106c::2010/08/26-20:44:52.906 INFO [CORE] Node quorum state is 'Not yet formed or joined a cluster'. Form/join status with other nodes is as follows:
000010b0.0000106c::2010/08/26-20:44:52.906 INFO [NODE] Node 1: Farthest reported progress joining with node iQCXSQL2 (id 2) is: Authenticate Initial Connection at time 2010/08/26-20:43:54.004: status 802 [SV] Authentication failed
000010b0.0000106c::2010/08/26-20:44:52.906 INFO [CORE] Node 1: Proposed View is <ViewChanged joiners=() downers=(1) newView=101() oldView=001(1) joiner=false form=false/>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO [RGP] Node 1: Stable_`0 => Opening`1
000010b0.0000106c::2010/08/26-20:44:52.906 INFO <class mscs::detail::ConsensusMessage>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <senderId> 1 </senderId>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <bestEpochSeen> 0 </bestEpochSeen>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <lastStableView> 001(1) </lastStableView>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <proposedView> 101() </proposedView>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <stage> Opening`1 </stage>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <inStage> () </inStage>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <inStagePrev> () </inStagePrev>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <joiners> () </joiners>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <trimmedNodes> (1) </trimmedNodes>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <innerScreen> () </innerScreen>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <pruningResult> () </pruningResult>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <matrix>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO      <ConnectivityMatrix>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO        <row id='0'00000000000000000000000000000000/>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO      </ConnectivityMatrix>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    </matrix>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <gemBlob> <counted_ptr p = 'nullptr'/> </gemBlob>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO </class mscs::detail::ConsensusMessage>
000010b0.000006fc::2010/08/26-20:44:52.906 INFO [RGP] Node 1: Timer Tick Started
000010b0.0000106c::2010/08/26-20:44:52.906 DBG   [NODE] Node 1: eating message sent to the dead node 2
000010b0.0000106c::2010/08/26-20:44:52.906 INFO [RGP] Node 1: Just sent farewell regroup message
000010b0.000010b8::2010/08/26-20:44:52.906 DBG   [NODE] Node 1: just about to send a message of size 0 to 1
000010b0.000010b8::2010/08/26-20:44:52.906 DBG   [NODE] Node 1: message to node 1 sent
000010b0.000010b8::2010/08/26-20:44:52.906 DBG   [NODE] Node 1: just about to send a message of size 361 to 1
000010b0.000010b8::2010/08/26-20:44:52.906 DBG   [NODE] Node 1: message to node 1 sent
000010b0.000006fc::2010/08/26-20:44:53.218 INFO [RGP] Node 1: Timer Tick Started
000010b0.0000106c::2010/08/26-20:44:53.420 INFO [DM]: Shutting down, so unloading the cluster database.
000010b0.0000106c::2010/08/26-20:44:53.420 INFO [DM] Shutting down, so unloading the cluster database (waitForLock: true).
000010b0.0000106c::2010/08/26-20:44:53.420 DBG   [DM] Unloading Hive, Key \Registry\Machine\Cluster, discardCurrentChanges true
000010b0.0000106c::2010/08/26-20:44:53.420 INFO [CS] Service Stopped...
000010b0.0000106c::2010/08/26-20:44:53.420 INFO [CS] About to exit service...
Just to make sure I have given both nodes every permission under the sun. I have tried creating the cluster computer in AD beforehand and disabling the computer and I have tried letting clustering services create the computer to no avail.
Please help!

Here is the complete log Edwin.   Thank you.
000010b0.0000121c::2010/08/26-20:41:52.722 INFO -----------------------------+ LOG BEGIN +-----------------------------
000010b0.0000121c::2010/08/26-20:41:52.722 INFO [CS] Starting clussvc as a service
000010b0.0000121c::2010/08/26-20:41:52.722 INFO [CS] cluster service logging level is 5
000010b0.000012d0::2010/08/26-20:41:52.738 INFO [CS] Creating cluster node <vector len='1'>
000010b0.000012d0::2010/08/26-20:41:52.738 INFO      <item>ClusSvc</item>
000010b0.000012d0::2010/08/26-20:41:52.738 INFO </vector>
000010b0.00000fd8::2010/08/26-20:41:52.738 INFO [StartupConfig]: Initializing.
000010b0.00000fd8::2010/08/26-20:41:52.738 INFO [StartupConfig]: Local node name: iQCXSQL1.
000010b0.00000fd8::2010/08/26-20:41:52.738 INFO [StartupConfig]: Initializing NetFT adapter management information.
000010b0.00000fd8::2010/08/26-20:41:52.738 INFO [NETFT] Initializing NetFT driver manager
000010b0.00000fd8::2010/08/26-20:41:52.738 INFO [CORE] Initializing.
000010b0.00000fd8::2010/08/26-20:41:52.738 INFO [GEM] Initializing.
000010b0.00000fd8::2010/08/26-20:41:52.738 INFO [MM] Initializing.
000010b0.00000fd8::2010/08/26-20:41:52.738 INFO [MRR] Node 1: Initializing.
000010b0.00000fd8::2010/08/26-20:41:52.738 INFO [Causal] Node 1: Initializing.
000010b0.00000fd8::2010/08/26-20:41:52.738 INFO [EM] Initializing.
000010b0.00000fd8::2010/08/26-20:41:52.738 INFO [GUM] Node 1: Initializing.
000010b0.00000fd8::2010/08/26-20:41:52.738 INFO [DM] Node 1: Initializing.
000010b0.00000fd8::2010/08/26-20:41:52.800 INFO [CLFS] Initializing CLFS logger.
000010b0.00000fd8::2010/08/26-20:41:52.800 DBG   [CLFS] Largest written record has size 131072 bytes
000010b0.00000fd8::2010/08/26-20:41:52.800 DBG   [CLFS] Deleting old marshalling area.
000010b0.00000fd8::2010/08/26-20:41:52.800 DBG   [CLFS] Marshaling area resized
000010b0.00000fd8::2010/08/26-20:41:52.800 INFO [TM] Initializing.
000010b0.00000fd8::2010/08/26-20:41:52.800 INFO [JPM] Node 1: Initializing.
000010b0.00000fd8::2010/08/26-20:41:52.800 INFO [VER]: Initializing.
000010b0.00000fd8::2010/08/26-20:41:52.800 INFO [CCM] Initializing.
000010b0.00000fd8::2010/08/26-20:41:52.800 INFO [FTI] Initializing.
000010b0.00000fd8::2010/08/26-20:41:52.800 INFO [ReM] Initializing.
000010b0.00000fd8::2010/08/26-20:41:52.800 INFO [HM]: Initializing.
000010b0.00000fd8::2010/08/26-20:41:52.800 INFO [NETFT] Starting NetFT eventing for FTI
000010b0.00000fd8::2010/08/26-20:41:52.816 DBG   [NETFTAPI] received NsiInitialNotification
000010b0.00000fd8::2010/08/26-20:41:52.816 DBG   [NETFTAPI] received NsiInitialNotification
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO [NETFT] FTI NetFT event handler ready for events.
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO [IM] Initializing.
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO [NM] Initializing.
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO [NSM] Initializing.
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO [CM] Initializing.
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO [RCM] Initializing.
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO [QUORUM] Node 1: Initializing.
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO [STARTUP] Node 1: startup config
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO <StartupConfig localNodeId='1' testMode='false' newCluster='true'
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO      <ClusterName> iqcxcluster </ClusterName>
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO      <PaxosTag> 0:0:0 </PaxosTag>
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO      <ConfiguredNodes> (1 2) </ConfiguredNodes>
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO      <NodeWeights> (1 2) </NodeWeights>
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO      <Nodes>
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO          <Node name='iQCXSQL1' id='1'/>
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO          <Node name='iQCXSQL2' id='2'/>
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO      </Nodes>
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO      <LocalHiveFile> C:\Windows\Cluster\CLUSDB </LocalHiveFile>
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO      <LocalHiveKey> Cluster </LocalHiveKey>
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO      <ParametersKey> System\\CurrentControlSet\\Services\ClusSvc\Parameters </ParametersKey>
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO      <Virtual IPv6> fe80::c14f:8b1f:d265:9b42%22:~3343~ </Virtual IPv6>
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO      <Virtual IPv4> 169.254.1.247:~3343~ </Virtual IPv4>
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO      <NoVersionCheck> false </NoVersionCheck>
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO      <Cookie> 3529ace1-67e4-4107-8940-c725883fab51 </Cookie>
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO      <ClusterGuid> d4a97f31-178f-4726-993c-c0c5ff8407dc </ClusterGuid>
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO      <RetainNetFTConnSecurity> false </RetainNetFTConnSecurity>
000010b0.00000fd8::2010/08/26-20:41:52.816 INFO </StartupConfig>
000010b0.000012d0::2010/08/26-20:41:52.816 INFO [CS] Node object creation completed.
000010b0.000012d0::2010/08/26-20:41:52.816 INFO [CS] Starting cluster node
000010b0.000012d0::2010/08/26-20:41:52.816 INFO [CS] Cluster Service started
000010b0.000012d0::2010/08/26-20:41:52.816 INFO [CS] The current time is 2010/08/26-16:41:52.816
000010b0.000012d0::2010/08/26-20:41:52.816 INFO [CS] Using virtual IPv6 Address fe80::c14f:8b1f:d265:9b42%22:~3343~
000010b0.000012d0::2010/08/26-20:41:52.816 INFO [CS] Using virtual IPv4 Address 169.254.1.247:~3343~
000010b0.000012d0::2010/08/26-20:41:52.816 INFO [CS] Max Licensed nodes is set 16
000010b0.000012d0::2010/08/26-20:41:52.816 INFO [NETFT] Disabling IP autoconfiguration on the NetFT adapter.
000010b0.000012d0::2010/08/26-20:41:52.816 INFO [NETFT] Disabling DHCP on the NetFT adapter.
000010b0.000012d0::2010/08/26-20:41:52.816 DBG   [NETFT] Disabling DHCP on NetFT interface name ethernet_2.
000010b0.000012d0::2010/08/26-20:41:52.816 INFO [CS] Starting DM
000010b0.000012d0::2010/08/26-20:41:52.816 INFO [DM] Node 1: Reading quorum config
000010b0.000012d0::2010/08/26-20:41:52.816 INFO [DM] Node 1: new cluster. generating new hive
000010b0.000012d0::2010/08/26-20:41:52.816 DBG   [DM] Unloading Hive, Key \Registry\Machine\Cluster, discardCurrentChanges true
000010b0.000012d8::2010/08/26-20:41:52.816 DBG   [NETFTAPI] received NsiAddInstance for 169.254.1.247
000010b0.000010a0::2010/08/26-20:41:52.816 INFO [CS] Disabling connection security.
000010b0.000012d0::2010/08/26-20:41:52.816 INFO [DM] Key \Registry\Machine\Cluster does not appear to be loaded (status STATUS_OBJECT_NAME_NOT_FOUND(c0000034))
000010b0.000012d0::2010/08/26-20:41:52.816 DBG   [DM] Unloading Hive, Key \Registry\Machine\Cluster, discardCurrentChanges true
000010b0.000012d0::2010/08/26-20:41:52.816 INFO [DM] Key \Registry\Machine\Cluster does not appear to be loaded (status STATUS_OBJECT_NAME_NOT_FOUND(c0000034))
000010b0.000012d0::2010/08/26-20:41:52.816 DBG   [DM] Creating Hive, Key Cluster, FilePath C:\Windows\Cluster\CLUSDB
000010b0.000010a0::2010/08/26-20:41:52.816 INFO [NETFT] Adding connection security permit filters for the NetFT adapter.
000010b0.000010a0::2010/08/26-20:41:52.816 INFO [NETFT] Adding FWPM filter Failover Cluster Permit Inbound Transport IPv4
000010b0.000010a0::2010/08/26-20:41:52.831 INFO [NETFT] Adding FWPM filter Failover Cluster Permit Inbound Transport IPv6
000010b0.000010a0::2010/08/26-20:41:52.831 INFO [NETFT] Adding FWPM filter Failover Cluster Permit Outbound Transport IPv4
000010b0.000010a0::2010/08/26-20:41:52.831 INFO [NETFT] Adding FWPM filter Failover Cluster Permit Outbound Transport IPv6
000010b0.000010a0::2010/08/26-20:41:52.831 INFO [NETFT] Adding FWPM filter Failover Cluster Permit ALE Accept IPv4 Universal
000010b0.000010a0::2010/08/26-20:41:52.831 INFO [NETFT] Adding FWPM filter Failover Cluster Permit ALE Accept IPv6 Universal
000010b0.000010a0::2010/08/26-20:41:52.831 INFO [NETFT] Adding FWPM filter Failover Cluster Permit ALE Accept IPv4 LIPS
000010b0.000010a0::2010/08/26-20:41:52.831 INFO [NETFT] Adding FWPM filter Failover Cluster Permit ALE Accept IPv6 LIPS
000010b0.000010a0::2010/08/26-20:41:52.831 DBG   [CS] Done with connection security
000010b0.000012d0::2010/08/26-20:41:52.847 DBG   [DM] Saving temp Hive
000010b0.000012d0::2010/08/26-20:41:52.847 DBG   [DM] Unloading temp Hive
000010b0.000012d0::2010/08/26-20:41:52.847 DBG   [DM] Deleting temp Hive
000010b0.000012d0::2010/08/26-20:41:52.847 INFO [DM] Loading Hive, Key Cluster, FilePath C:\Windows\Cluster\CLUSDB
000010b0.000012d0::2010/08/26-20:41:52.878 INFO [DM] Paxos Tag Read from Hive: 0:0:0
000010b0.000012d0::2010/08/26-20:41:52.878 DBG   [DM] Beginning transaction
000010b0.000012d0::2010/08/26-20:41:52.878 INFO [QUORUM] unique node id for new node 1 is 00000000-0000-0000-0000-000000000001
000010b0.000012d0::2010/08/26-20:41:52.878 INFO [QUORUM] unique node id for new node 2 is 00000000-0000-0000-0000-000000000002
000010b0.000012d0::2010/08/26-20:41:52.878 DBG   [CLFS] Deleting old marshalling area.
000010b0.000012d0::2010/08/26-20:41:52.878 DBG   [CLFS] Marshaling area resized
000010b0.000012d0::2010/08/26-20:41:52.878 DBG   [CLFS] Logger wrote 2820 bytes
000010b0.000012d0::2010/08/26-20:41:52.878 DBG   [DM] Committed transaction 0:0:1
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [DM] Populating StartupConfig data from local hive.
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [DM] Node 1: startup configuration loaded:
000010b0.000012d0::2010/08/26-20:41:52.894 INFO <StartupConfig localNodeId='1' testMode='false' newCluster='true'
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <ClusterName> iqcxcluster </ClusterName>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <PaxosTag> 0:0:1 </PaxosTag>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <ConfiguredNodes> (1 2) </ConfiguredNodes>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <NodeWeights> (1 2) </NodeWeights>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <Nodes>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO          <Node name='iQCXSQL1' id='1'/>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO          <Node name='iQCXSQL2' id='2'/>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      </Nodes>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <LocalHiveFile> C:\Windows\Cluster\CLUSDB </LocalHiveFile>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <LocalHiveKey> Cluster </LocalHiveKey>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <ParametersKey> System\\CurrentControlSet\\Services\ClusSvc\Parameters </ParametersKey>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <Virtual IPv6> fe80::c14f:8b1f:d265:9b42%22:~3343~ </Virtual IPv6>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <Virtual IPv4> 169.254.1.247:~3343~ </Virtual IPv4>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <NoVersionCheck> false </NoVersionCheck>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <Cookie> 3529ace1-67e4-4107-8940-c725883fab51 </Cookie>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <ClusterGuid> d4a97f31-178f-4726-993c-c0c5ff8407dc </ClusterGuid>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <RetainNetFTConnSecurity> false </RetainNetFTConnSecurity>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO </StartupConfig>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [CS] Starting MM
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [MM] Starting.
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [GEM] Node 1: Resume (newView = 001(1), previousView = 000())
000010b0.000012d0::2010/08/26-20:41:52.894 DBG   [GEM] Node 1: SendNextMessage
000010b0.000012d0::2010/08/26-20:41:52.894 DBG   [GEM] Node 1: No more messages in queue
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [StartupConfig] Writing new StartupConfig entries to ObjectManager
000010b0.000012d0::2010/08/26-20:41:52.894 DBG   [StartupConfig] Writing node iQCXSQL2 (id = 2) to ObjectManager
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [QUORUM] unique node id for new node 2 is 00000000-0000-0000-0000-000000000002
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [MQ-iQCXSQL2] Starting
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [MQ-iQCXSQL2] Clearing 0 unsent and 0 unacknowledged messages.
000010b0.000012d0::2010/08/26-20:41:52.894 INFO <ObjectManager>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO    <ROOT id='.root' name='.root'>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <GEMA id='GemAgent' name='GemAgent1'/>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <MRRA id='MrrAgent1' name='MrrAgent1'/>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <CAUS id='CausalAgent' name='CausalAgent'/>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <EVTM id='EventManager' name='EventManager'/>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <GUMA id='GumAgent1' name='GumAgent1'/>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <JPMA id='JpmAgent' name='JpmAgent'/>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <IMSC id='[IM-1] ' name='[IM-1] '/>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <RPCS id='[RPC-1] ' name='[RPC-1] '/>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <RCMA id='RcmAgent' name='RcmAgent'/>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <QRMA id='QuorumAgent1' name='QuorumAgent1'/>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <DCMA id='DcmAgent' name='DcmAgent'/>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <VSSR id='Cluster VSS Writer' name='Cluster VSS Writer'/>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <CLUS id='iqcxcluster' name='iqcxcluster'/>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <DEAD id='.Dead' name='.Dead'>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO        <NODE id='2' name='iQCXSQL2'/>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      </DEAD>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <LIVE id='.Live' name='.Live'/>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <JOIN id='.Joiners' name='.Joiners'/>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO      <MBRA id='MembershipAgent' name='MembershipAgent'/>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO    </ROOT>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO </ObjectManager>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [MM] Node 1: got a network stream to 1. Creating new NodeObject
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [QUORUM] unique node id for new node 1 is 00000000-0000-0000-0000-000000000001
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [MQ-iQCXSQL1] Starting
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [MQ-iQCXSQL1] Clearing 0 unsent and 0 unacknowledged messages.
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [NODE] Node 1: n1 node object adding stream
000010b0.000012d0::2010/08/26-20:41:52.894 DBG   [NODE] Node 1: n1 node object got a channel
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [NODE] Node 1: Highest version with n1 = Major 0 Minor 0 Upgrade 0 ClusterVersion 0x00000000, lowest = Major 0 Minor 0 Upgrade 0 ClusterVersion 0x00000000
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [NODE] Node 1: Done processing new stream to n1.
000010b0.00000e50::2010/08/26-20:41:52.894 INFO [PULLER iQCXSQL1] Just about to start reading from <LoopbackStream name='iQCXSQL1'/>
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [CS] Starting QM
000010b0.000012d0::2010/08/26-20:41:52.894 DBG   [NETFT] Halt Notification set
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [CS] Starting TM
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [NETFT] Starting NetFT eventing for TM
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [NETFT] TM NetFT event handler ready for events.
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [CS] Starting IM
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [NETFT] Starting NetFT eventing for IM
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [NETFT] IM NetFT event handler ready for events.
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [CS] Starting NM
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [CS] Starting api server
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [API] Api Onlined
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [API] UseProtseq ncalrpc => 0
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [API] UseProtseq ncadg_ip_tcp => 0
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [API] InqBindings => 0
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [API] RpcEpRegister => 0
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [API] RpcServerRegister => 0
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [API] Initializing
000010b0.000012d0::2010/08/26-20:41:52.894 INFO [API] Adding Mgmt API SPNs to node's Computer Object
000010b0.000012d0::2010/08/26-20:41:52.972 INFO [API] Successfully added Mgmt API SPNs to node's Computer Object
000010b0.000012d0::2010/08/26-20:41:52.972 ERR   [API] DmQueryString failed to retrieve the security   descriptor status 2, default security descriptor will be used for authorizing client connections
000010b0.000012d0::2010/08/26-20:41:52.972 INFO [API] Successfully built the default cluster SD.
000010b0.000012d0::2010/08/26-20:41:52.972 INFO [CS] Bringing API Online
000010b0.000012d0::2010/08/26-20:41:52.972 INFO [CORE] Node 1: New View is <ViewChanged joiners=(1) downers=() newView=001(1) oldView=000() joiner=true form=true/> (Start Dispatch)
000010b0.000012d0::2010/08/26-20:41:52.972 INFO [MRR] Node 1: Process view 001(1)
000010b0.000012d0::2010/08/26-20:41:52.972 INFO [RCM] rcm::RcmAgent::ProcessView: Ignoring view change (won't attempt to move orphaned groups), since I'm not in RCM view yet.
000010b0.000012d0::2010/08/26-20:41:52.972 DBG   [GEM] Node 1: message added to send queue
000010b0.000012d0::2010/08/26-20:41:52.972 DBG   [GEM] Node 1: SendNextMessage
000010b0.000012d0::2010/08/26-20:41:52.972 DBG   [GEM] Node 1: delivering message 1:1
000010b0.000012d0::2010/08/26-20:41:52.972 INFO [CORE] EmitReadyForState for node 1
000010b0.000012d0::2010/08/26-20:41:52.972 INFO [CORE] Issuing NeedStateViewChanged((1))
000010b0.000012d0::2010/08/26-20:41:52.972 DBG   [GEM] Node 1: ProcessAck from node 1 (already acked ())
000010b0.000012d0::2010/08/26-20:41:52.972 DBG   [GEM] Node 1: SendNextMessage
000010b0.000012d0::2010/08/26-20:41:52.972 DBG   [GEM] Node 1: No more messages in queue
000010b0.000012d0::2010/08/26-20:41:52.972 DBG   [NODE] Node 1: eating message sent to the dead node 2
000010b0.000012d0::2010/08/26-20:41:52.972 INFO [QUORUM] Node 1: I am the form/join coordinator (offline and lowest number node). Launching worker to request quorum config from other nodes
000010b0.000012d0::2010/08/26-20:41:52.972 DBG   [MRR] Node 1: insert request record for RID 1
000010b0.000012d0::2010/08/26-20:41:52.972 DBG   [MRR] SendRequest(<message action='qrm/request-info' GemId='0' target='QRMA' sender='-1'mrr='1'/>)
000010b0.000012d0::2010/08/26-20:41:52.972 DBG   [CORE] Node 1: sending qrm/request-info to QRMA at iQCXSQL1
000010b0.000010b8::2010/08/26-20:41:52.972 DBG   [NODE] Node 1: just about to send a message of size 109 to 1
000010b0.000012d0::2010/08/26-20:41:52.972 INFO [CORE] Node 1: New View is <ViewChanged joiners=(1) downers=() newView=001(1) oldView=000() joiner=true form=true/> (Stop Dispatch)
000010b0.000012d0::2010/08/26-20:41:52.972 INFO [CS] Starting HM Server
000010b0.000010b8::2010/08/26-20:41:52.972 DBG   [NODE] Node 1: message to node 1 sent
000010b0.000012d0::2010/08/26-20:41:52.972 INFO [NODE] Node 1: New join with n2: stage: 'Listen for Connection'
000010b0.000012d0::2010/08/26-20:41:52.972 INFO [CS] Starting JPM (attempting connections to other cluster nodes)
000010b0.000012d0::2010/08/26-20:41:52.972 DBG   [JPM] Node 1: Dead node mentioned iQCXSQL1
000010b0.000012d0::2010/08/26-20:41:52.972 DBG   [JPM] Node 1: Dead node mentioned iQCXSQL2
000010b0.000012d0::2010/08/26-20:41:52.972 INFO [CS] Subscribing for VSS requests
000010b0.000012d0::2010/08/26-20:41:52.972 INFO [VSS] Initializing Cluster VSS Writer at the command of the VSS framework.
000010b0.00000e50::2010/08/26-20:41:52.972 INFO [QUORUM] Node 1: received request for quorum info. Replying with quorum state <QuorumConfig tag='0:0:1' set='(1 2)' weights='(1 2)'/>
000010b0.00000e50::2010/08/26-20:41:52.972 DBG   [CORE] Node 1: sending mrr/reply to MRRA at iQCXSQL1
000010b0.000010b8::2010/08/26-20:41:52.972 DBG   [NODE] Node 1: just about to send a message of size 0 to 1
000010b0.000010b8::2010/08/26-20:41:52.972 DBG   [NODE] Node 1: message to node 1 sent
000010b0.000012d8::2010/08/26-20:41:52.972 DBG   [JPM] Node 1: Building contact data for node iQCXSQL2.
000010b0.000010b8::2010/08/26-20:41:52.972 DBG   [NODE] Node 1: just about to send a message of size 278 to 1
000010b0.000010b8::2010/08/26-20:41:52.972 DBG   [NODE] Node 1: message to node 1 sent
000010b0.000012d8::2010/08/26-20:41:52.972 INFO [JPM] Node 1: Scheduling DNS query for node name iQCXSQL2
000010b0.000012d8::2010/08/26-20:41:52.972 DBG   [JPM] Node 1: no valid contact endpoints yet for node iQCXSQL2.
000010b0.00000e50::2010/08/26-20:41:52.972 DBG   [MRR] Node 1: processing reply <message action='mrr/reply' GemId='0' target='MRRA' sender='1'mrr='1'/>
000010b0.00000e50::2010/08/26-20:41:52.972 DBG   [MRR] Node 1: Request RID 1 is completed
000010b0.0000119c::2010/08/26-20:41:52.972 INFO [QUORUM] Node 1: setting next best epoch to 0
000010b0.0000119c::2010/08/26-20:41:52.972 DBG   [QC] Calculating quorum: Configured nodes count = 2, Node weights count = 2, Quorum witness configured = false, Intersection count = 1
000010b0.0000119c::2010/08/26-20:41:52.972 INFO [QUORUM] Node 1: Coordinator: no quorum yet. do nothing
000010b0.000012d8::2010/08/26-20:41:52.972 INFO [JPM] Node 1: Found possible contact address 192.168.210.236:~0~ for node iQCXSQL2 via DNS.
000010b0.000012d0::2010/08/26-20:41:52.987 INFO [CS] Starting the Watchdog Monitor
000010b0.000012d0::2010/08/26-20:41:52.987 INFO [WM] Monitoring the kernel-mode watchdog.
000010b0.000012d0::2010/08/26-20:41:52.987 INFO [CS] Reporting to SCM that cluster service has started.
000010b0.000012d8::2010/08/26-20:41:53.019 INFO [NM] Received request from client address ::1.
000010b0.000012d8::2010/08/26-20:41:53.019 DBG   [API] Authenticated client--Client: IQCX\iqcxsql1 Interface: b97db8b2-4c63-11cf-bff6-08002be23f2f Server:
[email protected] Level: RPC_C_AUTHN_LEVEL_PKT_PRIVACY Service: RPC_C_AUTHN_WINNT Protocol Sequence: ncacn_ip_tcp Client Address: ::1 Network Option: .
000010b0.0000119c::2010/08/26-20:41:53.986 DBG   [JPM] Node 1: contacts size for node iQCXSQL2 is 1, current index 0
000010b0.0000119c::2010/08/26-20:41:53.986 DBG   [JPM] Node 1: Trying to connect to node iQCXSQL2 (IP: 192.168.210.236:~0~)
000010b0.0000119c::2010/08/26-20:41:53.986 DBG   [HM] Trying to connect to iQCXSQL2 at 192.168.210.236:~3343~
000010b0.000012d8::2010/08/26-20:41:53.986 INFO [CONNECT] 192.168.210.236:~3343~: Established connection to remote endpoint 192.168.210.236:~3343~.
000010b0.000012d8::2010/08/26-20:41:53.986 INFO [NODE] Node 1: New join with n2: stage: 'Attempt Initial Connection'
000010b0.000012d8::2010/08/26-20:41:53.986 INFO [SV] Securing route from (192.168.210.239:~49538~) to remote iQCXSQL2 (192.168.210.236:~3343~).
000010b0.000012d8::2010/08/26-20:41:53.986 INFO [SV] Got a new outgoing stream to iQCXSQL2 at 192.168.210.236:~3343~
000010b0.000012d8::2010/08/26-20:41:53.986 DBG   [SM] Joiner: Initialized with SPN = iQCXSQL2, Package = Kerberos, RequiredCtxAttrib = 83990, HandShakeTimeout = 30000
000010b0.000013f0::2010/08/26-20:41:53.986 DBG   [SM] Handling auth handshake posted by thread id 4824
000010b0.000013f0::2010/08/26-20:41:53.986 DBG   [SM] Joiner: ISC returned status = 590610 output Blob size 1388
000010b0.000013f0::2010/08/26-20:41:53.986 DBG   [SM] Joiner: Received SSPI blob from the Sponsor of size 96
000010b0.000013f0::2010/08/26-20:41:53.986 DBG   [SM] Joiner: ISC returned status = 590610 output Blob size 1388
000010b0.000013f0::2010/08/26-20:41:53.986 DBG   [SM] Joiner: Received SSPI blob from the Sponsor of size 96
000010b0.000013f0::2010/08/26-20:41:53.986 DBG   [SM] Joiner: ISC returned status = -2146893022 output Blob size 12000
000010b0.000012d8::2010/08/26-20:41:53.986 INFO [NODE] Node 1: New join with n2: stage: 'Authenticate Initial Connection' status HrError(0x80090322) reason: '[SV] Authentication failed'
000010b0.000012d8::2010/08/26-20:41:53.986 DBG   [CHANNEL 192.168.210.236:~3343~] Close().
000010b0.000012d8::2010/08/26-20:41:53.986 WARN cxl::ConnectWorker::operator (): HrError(0x80090322)' because of '[SV] Authentication or Authorization Failed'
000010b0.00000ea8::2010/08/26-20:41:54.048 INFO [ACCEPT] 0.0.0.0:~3343~: Accepted inbound connection from remote endpoint 192.168.210.236:~59820~.
000010b0.000012d8::2010/08/26-20:41:54.048 INFO [SV] Securing route from (192.168.210.239:~3343~) to remote (192.168.210.236:~59820~).
000010b0.000012d8::2010/08/26-20:41:54.048 INFO [SV] Got a new incoming stream from 192.168.210.236:~59820~
000010b0.000012d8::2010/08/26-20:41:54.048 DBG   [SM] SrvCtxt initialized with package Kerberos, MaxTokenSize = 12000, RequiredCtxAttrib = 165910, HandShakeTimeout = 30000
000010b0.00001108::2010/08/26-20:41:54.048 DBG   [SM] Handling auth handshake posted by thread id 4824
000010b0.00001108::2010/08/26-20:41:54.048 DBG   [SM] Sponsor: Received SSPI blob from the Joiner of size 1411
000010b0.00001108::2010/08/26-20:41:54.048 DBG   [SM] Sponsor: SSPI ASC returned status = 590610
000010b0.00001108::2010/08/26-20:41:54.048 DBG   [SM] Sponsor: Sending SSPI blob of size 96 to Joiner
000010b0.00001108::2010/08/26-20:41:54.048 DBG   [SM] Sponsor: Received SSPI blob from the Joiner of size 1411
000010b0.00001108::2010/08/26-20:41:54.048 DBG   [SM] Sponsor: SSPI ASC returned status = 590610
000010b0.00001108::2010/08/26-20:41:54.048 DBG   [SM] Sponsor: Sending SSPI blob of size 96 to Joiner
000010b0.00001108::2010/08/26-20:41:54.048 DBG   [SM] Sponsor: Received SSPI blob from the Joiner of size 12000
000010b0.00001108::2010/08/26-20:41:54.048 DBG   [SM] Sponsor: SSPI ASC returned status = 590610
000010b0.00001108::2010/08/26-20:41:54.048 DBG   [SM] Sponsor: Sending SSPI blob of size 115 to Joiner
000010b0.00001108::2010/08/26-20:41:54.048 DBG   [CHANNEL 192.168.210.236:~59820~] Close().
000010b0.00001108::2010/08/26-20:41:54.048 INFO [CHANNEL 192.168.210.236:~59820~] graceful close, status (of previous failure, may not indicate problem) ERROR_SUCCESS(0)
000010b0.00001108::2010/08/26-20:41:54.048 ERR   [SM] Caught GracefulClose(1226)' because of 'channel to remote endpoint 192.168.210.236:~59820~ is closed' authenticating.
000010b0.000012d8::2010/08/26-20:41:54.048 INFO [SV] Authentication and authorization were successful
000010b0.000012d8::2010/08/26-20:41:54.048 DBG   [SM] SrvCtxt initialized with package Kerberos, MaxTokenSize = 12000, RequiredCtxAttrib = 133122, HandShakeTimeout = 30000
000010b0.00001108::2010/08/26-20:41:54.048 DBG   [SM] Handling auth handshake posted by thread id 4824
000010b0.00001108::2010/08/26-20:41:54.048 DBG   [CHANNEL 192.168.210.236:~59820~]/recv: Attempting to perform I/O on closed stream.
000010b0.00001108::2010/08/26-20:41:54.048 DBG   [CHANNEL 192.168.210.236:~59820~] Not closing handle because it is invalid.
000010b0.00001108::2010/08/26-20:41:54.048 INFO [CHANNEL 192.168.210.236:~59820~] graceful close, status (of previous failure, may not indicate problem) ERROR_SUCCESS(0)
000010b0.00001108::2010/08/26-20:41:54.048 ERR   [SM] Caught GracefulClose(1226)' because of 'channel to remote endpoint 192.168.210.236:~59820~ is closed' authenticating.
000010b0.000012d8::2010/08/26-20:41:54.048 DBG   [CHANNEL 192.168.210.236:~59820~] Not closing handle because it is invalid.
000010b0.00001310::2010/08/26-20:42:53.995 DBG   [JPM] Node 1: contacts size for node iQCXSQL2 is 1, current index 0
000010b0.00001310::2010/08/26-20:42:53.995 DBG   [JPM] Node 1: Trying to connect to node iQCXSQL2 (IP: 192.168.210.236:~0~)
000010b0.00001310::2010/08/26-20:42:53.995 DBG   [HM] Trying to connect to iQCXSQL2 at 192.168.210.236:~3343~
000010b0.00001310::2010/08/26-20:42:53.995 INFO [CONNECT] 192.168.210.236:~3343~: Established connection to remote endpoint 192.168.210.236:~3343~.
000010b0.00001310::2010/08/26-20:42:53.995 INFO [SV] Securing route from (192.168.210.239:~49561~) to remote iQCXSQL2 (192.168.210.236:~3343~).
000010b0.00001310::2010/08/26-20:42:53.995 INFO [SV] Got a new outgoing stream to iQCXSQL2 at 192.168.210.236:~3343~
000010b0.00001310::2010/08/26-20:42:53.995 DBG   [SM] Joiner: Initialized with SPN = iQCXSQL2, Package = Kerberos, RequiredCtxAttrib = 83990, HandShakeTimeout = 30000
000010b0.000013f0::2010/08/26-20:42:53.995 DBG   [SM] Handling auth handshake posted by thread id 4880
000010b0.000013f0::2010/08/26-20:42:53.995 DBG   [SM] Joiner: ISC returned status = 590610 output Blob size 1388
000010b0.000013f0::2010/08/26-20:42:53.995 DBG   [SM] Joiner: Received SSPI blob from the Sponsor of size 96
000010b0.000013f0::2010/08/26-20:42:53.995 DBG   [SM] Joiner: ISC returned status = 590610 output Blob size 1388
000010b0.000013f0::2010/08/26-20:42:53.995 DBG   [SM] Joiner: Received SSPI blob from the Sponsor of size 96
000010b0.000013f0::2010/08/26-20:42:53.995 DBG   [SM] Joiner: ISC returned status = -2146893022 output Blob size 12000
000010b0.00001310::2010/08/26-20:42:53.995 INFO [NODE] Node 1: New join with n2: stage: 'Authenticate Initial Connection' status HrError(0x80090322) reason: '[SV] Authentication failed'
000010b0.00001310::2010/08/26-20:42:53.995 DBG   [CHANNEL 192.168.210.236:~3343~] Close().
000010b0.00001310::2010/08/26-20:42:53.995 WARN cxl::ConnectWorker::operator (): HrError(0x80090322)' because of '[SV] Authentication or Authorization Failed'
000010b0.00000ea8::2010/08/26-20:42:54.057 INFO [ACCEPT] 0.0.0.0:~3343~: Accepted inbound connection from remote endpoint 192.168.210.236:~59822~.
000010b0.00001310::2010/08/26-20:42:54.057 INFO [SV] Securing route from (192.168.210.239:~3343~) to remote (192.168.210.236:~59822~).
000010b0.00001310::2010/08/26-20:42:54.057 INFO [SV] Got a new incoming stream from 192.168.210.236:~59822~
000010b0.00001310::2010/08/26-20:42:54.057 DBG   [SM] SrvCtxt initialized with package Kerberos, MaxTokenSize = 12000, RequiredCtxAttrib = 165910, HandShakeTimeout = 30000
000010b0.00001108::2010/08/26-20:42:54.057 DBG   [SM] Handling auth handshake posted by thread id 4880
000010b0.00001108::2010/08/26-20:42:54.057 DBG   [SM] Sponsor: Received SSPI blob from the Joiner of size 1411
000010b0.00001108::2010/08/26-20:42:54.057 DBG   [SM] Sponsor: SSPI ASC returned status = 590610
000010b0.00001108::2010/08/26-20:42:54.057 DBG   [SM] Sponsor: Sending SSPI blob of size 96 to Joiner
000010b0.00001108::2010/08/26-20:42:54.057 DBG   [SM] Sponsor: Received SSPI blob from the Joiner of size 1411
000010b0.00001108::2010/08/26-20:42:54.057 DBG   [SM] Sponsor: SSPI ASC returned status = 590610
000010b0.00001108::2010/08/26-20:42:54.057 DBG   [SM] Sponsor: Sending SSPI blob of size 96 to Joiner
000010b0.00001108::2010/08/26-20:42:54.057 DBG   [SM] Sponsor: Received SSPI blob from the Joiner of size 12000
000010b0.00001108::2010/08/26-20:42:54.057 DBG   [SM] Sponsor: SSPI ASC returned status = 590610
000010b0.00001108::2010/08/26-20:42:54.057 DBG   [SM] Sponsor: Sending SSPI blob of size 115 to Joiner
000010b0.00001108::2010/08/26-20:42:54.057 DBG   [CHANNEL 192.168.210.236:~59822~] Close().
000010b0.00001108::2010/08/26-20:42:54.057 INFO [CHANNEL 192.168.210.236:~59822~] graceful close, status (of previous failure, may not indicate problem) ERROR_SUCCESS(0)
000010b0.00001108::2010/08/26-20:42:54.057 ERR   [SM] Caught GracefulClose(1226)' because of 'channel to remote endpoint 192.168.210.236:~59822~ is closed' authenticating.
000010b0.00001310::2010/08/26-20:42:54.057 INFO [SV] Authentication and authorization were successful
000010b0.00001310::2010/08/26-20:42:54.057 DBG   [SM] SrvCtxt initialized with package Kerberos, MaxTokenSize = 12000, RequiredCtxAttrib = 133122, HandShakeTimeout = 30000
000010b0.00001108::2010/08/26-20:42:54.057 DBG   [SM] Handling auth handshake posted by thread id 4880
000010b0.00001108::2010/08/26-20:42:54.057 DBG   [CHANNEL 192.168.210.236:~59822~]/recv: Attempting to perform I/O on closed stream.
000010b0.00001108::2010/08/26-20:42:54.057 DBG   [CHANNEL 192.168.210.236:~59822~] Not closing handle because it is invalid.
000010b0.00001108::2010/08/26-20:42:54.057 INFO [CHANNEL 192.168.210.236:~59822~] graceful close, status (of previous failure, may not indicate problem) ERROR_SUCCESS(0)
000010b0.00001108::2010/08/26-20:42:54.057 ERR   [SM] Caught GracefulClose(1226)' because of 'channel to remote endpoint 192.168.210.236:~59822~ is closed' authenticating.
000010b0.00001310::2010/08/26-20:42:54.057 DBG   [CHANNEL 192.168.210.236:~59822~] Not closing handle because it is invalid.
000010b0.000012d8::2010/08/26-20:43:54.004 DBG   [JPM] Node 1: contacts size for node iQCXSQL2 is 1, current index 0
000010b0.000012d8::2010/08/26-20:43:54.004 DBG   [JPM] Node 1: Trying to connect to node iQCXSQL2 (IP: 192.168.210.236:~0~)
000010b0.000012d8::2010/08/26-20:43:54.004 DBG   [HM] Trying to connect to iQCXSQL2 at 192.168.210.236:~3343~
000010b0.000012d8::2010/08/26-20:43:54.004 INFO [CONNECT] 192.168.210.236:~3343~: Established connection to remote endpoint 192.168.210.236:~3343~.
000010b0.000012d8::2010/08/26-20:43:54.004 INFO [SV] Securing route from (192.168.210.239:~49563~) to remote iQCXSQL2 (192.168.210.236:~3343~).
000010b0.000012d8::2010/08/26-20:43:54.004 INFO [SV] Got a new outgoing stream to iQCXSQL2 at 192.168.210.236:~3343~
000010b0.000012d8::2010/08/26-20:43:54.004 DBG   [SM] Joiner: Initialized with SPN = iQCXSQL2, Package = Kerberos, RequiredCtxAttrib = 83990, HandShakeTimeout = 30000
000010b0.000013f0::2010/08/26-20:43:54.004 DBG   [SM] Handling auth handshake posted by thread id 4824
000010b0.000013f0::2010/08/26-20:43:54.004 DBG   [SM] Joiner: ISC returned status = 590610 output Blob size 1388
000010b0.000013f0::2010/08/26-20:43:54.004 DBG   [SM] Joiner: Received SSPI blob from the Sponsor of size 96
000010b0.000013f0::2010/08/26-20:43:54.004 DBG   [SM] Joiner: ISC returned status = 590610 output Blob size 1388
000010b0.000013f0::2010/08/26-20:43:54.004 DBG   [SM] Joiner: Received SSPI blob from the Sponsor of size 96
000010b0.000013f0::2010/08/26-20:43:54.004 DBG   [SM] Joiner: ISC returned status = -2146893022 output Blob size 12000
000010b0.000012d8::2010/08/26-20:43:54.004 INFO [NODE] Node 1: New join with n2: stage: 'Authenticate Initial Connection' status HrError(0x80090322) reason: '[SV] Authentication failed'
000010b0.000012d8::2010/08/26-20:43:54.004 DBG   [CHANNEL 192.168.210.236:~3343~] Close().
000010b0.000012d8::2010/08/26-20:43:54.004 WARN cxl::ConnectWorker::operator (): HrError(0x80090322)' because of '[SV] Authentication or Authorization Failed'
000010b0.00000ea8::2010/08/26-20:43:54.067 INFO [ACCEPT] 0.0.0.0:~3343~: Accepted inbound connection from remote endpoint 192.168.210.236:~59824~.
000010b0.000012d8::2010/08/26-20:43:54.067 INFO [SV] Securing route from (192.168.210.239:~3343~) to remote (192.168.210.236:~59824~).
000010b0.000012d8::2010/08/26-20:43:54.067 INFO [SV] Got a new incoming stream from 192.168.210.236:~59824~
000010b0.000012d8::2010/08/26-20:43:54.067 DBG   [SM] SrvCtxt initialized with package Kerberos, MaxTokenSize = 12000, RequiredCtxAttrib = 165910, HandShakeTimeout = 30000
000010b0.00001108::2010/08/26-20:43:54.067 DBG   [SM] Handling auth handshake posted by thread id 4824
000010b0.00001108::2010/08/26-20:43:54.067 DBG   [SM] Sponsor: Received SSPI blob from the Joiner of size 1411
000010b0.00001108::2010/08/26-20:43:54.067 DBG   [SM] Sponsor: SSPI ASC returned status = 590610
000010b0.00001108::2010/08/26-20:43:54.067 DBG   [SM] Sponsor: Sending SSPI blob of size 96 to Joiner
000010b0.00001108::2010/08/26-20:43:54.067 DBG   [SM] Sponsor: Received SSPI blob from the Joiner of size 1411
000010b0.00001108::2010/08/26-20:43:54.067 DBG   [SM] Sponsor: SSPI ASC returned status = 590610
000010b0.00001108::2010/08/26-20:43:54.067 DBG   [SM] Sponsor: Sending SSPI blob of size 96 to Joiner
000010b0.00001108::2010/08/26-20:43:54.067 DBG   [SM] Sponsor: Received SSPI blob from the Joiner of size 12000
000010b0.00001108::2010/08/26-20:43:54.067 DBG   [SM] Sponsor: SSPI ASC returned status = 590610
000010b0.00001108::2010/08/26-20:43:54.067 DBG   [SM] Sponsor: Sending SSPI blob of size 115 to Joiner
000010b0.00001108::2010/08/26-20:43:54.067 DBG   [CHANNEL 192.168.210.236:~59824~] Close().
000010b0.00001108::2010/08/26-20:43:54.067 INFO [CHANNEL 192.168.210.236:~59824~] graceful close, status (of previous failure, may not indicate problem) ERROR_SUCCESS(0)
000010b0.00001108::2010/08/26-20:43:54.067 ERR   [SM] Caught GracefulClose(1226)' because of 'channel to remote endpoint 192.168.210.236:~59824~ is closed' authenticating.
000010b0.000012d8::2010/08/26-20:43:54.067 INFO [SV] Authentication and authorization were successful
000010b0.000012d8::2010/08/26-20:43:54.067 DBG   [SM] SrvCtxt initialized with package Kerberos, MaxTokenSize = 12000, RequiredCtxAttrib = 133122, HandShakeTimeout = 30000
000010b0.00001108::2010/08/26-20:43:54.067 DBG   [SM] Handling auth handshake posted by thread id 4824
000010b0.00001108::2010/08/26-20:43:54.067 DBG   [CHANNEL 192.168.210.236:~59824~]/recv: Attempting to perform I/O on closed stream.
000010b0.00001108::2010/08/26-20:43:54.067 DBG   [CHANNEL 192.168.210.236:~59824~] Not closing handle because it is invalid.
000010b0.00001108::2010/08/26-20:43:54.067 INFO [CHANNEL 192.168.210.236:~59824~] graceful close, status (of previous failure, may not indicate problem) ERROR_SUCCESS(0)
000010b0.00001108::2010/08/26-20:43:54.067 ERR   [SM] Caught GracefulClose(1226)' because of 'channel to remote endpoint 192.168.210.236:~59824~ is closed' authenticating.
000010b0.000012d8::2010/08/26-20:43:54.067 DBG   [CHANNEL 192.168.210.236:~59824~] Not closing handle because it is invalid.
000010b0.0000106c::2010/08/26-20:44:52.906 INFO [CS] Service Stopping...
000010b0.0000106c::2010/08/26-20:44:52.906 INFO [CORE] Node quorum state is 'Not yet formed or joined a cluster'. Form/join status with other nodes is as follows:
000010b0.0000106c::2010/08/26-20:44:52.906 INFO [NODE] Node 1: Farthest reported progress joining with node iQCXSQL2 (id 2) is: Authenticate Initial Connection at time 2010/08/26-20:43:54.004: status 802 [SV] Authentication failed
000010b0.0000106c::2010/08/26-20:44:52.906 INFO [CORE] Node 1: Proposed View is <ViewChanged joiners=() downers=(1) newView=101() oldView=001(1) joiner=false form=false/>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO [RGP] Node 1: Stable_`0 => Opening`1
000010b0.0000106c::2010/08/26-20:44:52.906 INFO <class mscs::detail::ConsensusMessage>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <senderId> 1 </senderId>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <bestEpochSeen> 0 </bestEpochSeen>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <lastStableView> 001(1) </lastStableView>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <proposedView> 101() </proposedView>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <stage> Opening`1 </stage>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <inStage> () </inStage>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <inStagePrev> () </inStagePrev>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <joiners> () </joiners>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <trimmedNodes> (1) </trimmedNodes>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <innerScreen> () </innerScreen>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <pruningResult> () </pruningResult>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <matrix>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO      <ConnectivityMatrix>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO        <row id='0'00000000000000000000000000000000/>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO      </ConnectivityMatrix>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    </matrix>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO    <gemBlob> <counted_ptr p = 'nullptr'/> </gemBlob>
000010b0.0000106c::2010/08/26-20:44:52.906 INFO </class mscs::detail::ConsensusMessage>
000010b0.000006fc::2010/08/26-20:44:52.906 INFO [RGP] Node 1: Timer Tick Started
000010b0.0000106c::2010/08/26-20:44:52.906 DBG   [NODE] Node 1: eating message sent to the dead node 2
000010b0.0000106c::2010/08/26-20:44:52.906 INFO [RGP] Node 1: Just sent farewell regroup message
000010b0.000010b8::2010/08/26-20:44:52.906 DBG   [NODE] Node 1: just about to send a message of size 0 to 1
000010b0.000010b8::2010/08/26-20:44:52.906 DBG   [NODE] Node 1: message to node 1 sent
000010b0.000010b8::2010/08/26-20:44:52.906 DBG   [NODE] Node 1: just about to send a message of size 361 to 1
000010b0.000010b8::2010/08/26-20:44:52.906 DBG   [NODE] Node 1: message to node 1 sent
000010b0.000006fc::2010/08/26-20:44:53.218 INFO [RGP] Node 1: Timer Tick Started
000010b0.0000106c::2010/08/26-20:44:53.420 INFO [DM]: Shutting down, so unloading the cluster database.
000010b0.0000106c::2010/08/26-20:44:53.420 INFO [DM] Shutting down, so unloading the cluster database (waitForLock: true).
000010b0.0000106c::2010/08/26-20:44:53.420 DBG   [DM] Unloading Hive, Key \Registry\Machine\Cluster, discardCurrentChanges true
000010b0.0000106c::2010/08/26-20:44:53.420 INFO [CS] Service Stopped...
000010b0.0000106c::2010/08/26-20:44:53.420 INFO [CS] About to exit service...

Question about cluster node majority voting

We've been having problems with a DB instance crashing regularly. This weekend when it crashed, it seems to have taken the node it was on with it, or this was a separate incident...
Right now I have 3 nodes in the cluster. 2 nodes are running 3 instances (2 on 1). The 3rd node is in a state where the OS is mostly unusable and the Cluster service will not start.
Event Log:
"The failover cluster database could not be unloaded. If restarting the cluster service does not fix the problem, please restart the machine."
Cluster Log from that machine:
00003768.000067a0::2014/01/06-03:28:05.393 INFO -----------------------------+ LOG BEGIN +-----------------------------
00003768.000067a0::2014/01/06-03:28:05.393 INFO [CS] Starting clussvc as a service
00003768.000067a0::2014/01/06-03:28:05.394 INFO [CS] cluster service logging level is 2
00003768.00004c30::2014/01/06-03:28:05.521 DBG   [NETFTAPI] received NsiInitialNotification
00003768.00004c30::2014/01/06-03:28:05.523 DBG   [NETFTAPI] received NsiInitialNotification
00003768.000031f4::2014/01/06-03:28:05.588 DBG   [NETFTAPI] received NsiAddInstance for 169.254.3.47
00003768.00004eb4::2014/01/06-03:28:05.590 ERR   [DM] Error while restoring (refreshing) the hive: STATUS_INVALID_PARAMETER(c000000d
00003768.00004eb4::2014/01/06-03:28:05.592 ERR   [DM] mscs::DmAgent::Start: STATUS_INVALID_PARAMETER(c000000d' because of 'Load(NOTHROW(), securityAttributes, discardError )'
00003768.00004eb4::2014/01/06-03:28:05.592 ERR   [DM] Node 3: failed to unload cluster hive, error 87.
00003768.00004eb4::2014/01/06-03:28:05.592 ERR   Hive unload failed (status = 87)
00003768.00004eb4::2014/01/06-03:28:05.592 ERR   FatalError is Calling Exit Process.
This is a 3 node cluster set to node majority, I don't have an available drive letter for a witness disk. Since the cluster service won't start, I'm not certain how the cluster is still running, but am thankful that it is.
A reboot might fix everything, but I'm very worried that if I reboot the server, and the cluster service still fails to start... it may prevent the entire cluster from starting and we won't be able to run the instances on the other 2 nodes.
Does the 3rd server still act as an odd-number server, even if the cluster service won't start? If I reboot and the cluster service still fails to start, will the cluster itself be able to be in an UP state and run the DB instances on the other nodes?
I already need to open a MS Support incident on the DB instance crashing, so I'd rather not have to open a 2nd one just to answer this hopefully simple question.
Thanks in advance!
Mark

I'll answer it here, since it matters fundamentally to SQL High Availability.
There are a couple of entities you are conflating here, leading to much confusion. There is a difference between the Cluster and the cluster service.
The cluster service will run on a node once the Failover Cluster Feature is installed on that node. The cluster service will run, even if a cluster is not created. It may generate errors and not participate in a Cluster if it cannot talk to the
other nodes, but it will not shut down.
The Cluster itself requires a quorum, that is a majority of votes, in order to operate. With three nodes, you should choose Node Majority quorum model, which sounds like what you have. Any two votes will count, so the third node being offline
does not matter. You can safely restart the cluster service on the failed nod, and even restart the node. Note that with the third node down, you have no redundancy. (Windows 2012 and 2012 R2 have dynamic quorum, which adjusts the quorum
count based on the last "settled" quorum vote, but that doesn't apply here).
I am concerned with your statement that you are out of drive letters. With three instances, you should have plenty of drive letters left. I suggest investigating Mount Points. You only need one drive letter per instance when using Mount
Points.
Geoff N. Hiten Principal Consultant Microsoft SQL Server MVP

3 Node Cluster with 2 node SQL Always_On

We currently have more than 20 always_on clusters i.e. all following the below configurations
Server 1, Server 2 (High Hardware Configuration i.e. 16 CPU & 30 GB RAM) & File-share Witness on a small box (2 CPU with 4 GB RAM). We have seen some situations where nodes not able to communicate with the file-share and taking the cluster resource
down
Question: Can we create a windows cluster with 2 nodes i.e. (2 big hardware configuration for SQL + 1 small hardware configuration) to make it a 3 node windows cluster and have SQL on only the first 2 nodes with Always_ON ?

Hi,
Could you apply the following updates and see if it will alleviate the symptoms?
System event log errors every 15 minutes on a Windows Server 2008 R2-based Cluster configured with Node Majority and File Share Witness quorum
http://support.microsoft.com/kb/2750820
A cluster resource remains offline after the "Run this resource in a separate Resource Monitor" option is disabled in Windows Server 2008
http://support.microsoft.com/default.aspx?scid=kb;EN-US;977837
In addition, you may update the NIC drivers and disable TCP chimney offload and check the result.
Information about the TCP Chimney Offload, Receive Side Scaling, and Network Direct Memory Access features in Windows Server 2008
http://support.microsoft.com/default.aspx?scid=kb;EN-US;951037
If still no progress, upload the cluster.log to your OneDrive and share the link here.
Understanding the Cluster Debug Log in 2008
http://blogs.technet.com/b/askcore/archive/2010/04/13/understanding-the-cluster-debug-log-in-2008.aspx
Thanks.
Tracy Cai
TechNet Community Support

Upgrade from windows 2008 R2 to windows 2012 and Quorum

Dear Sir.
I am going to upgrade hyper-v cluster of 4 nodes 2008 r2 to windows 2012 hyper-v cluster.
i am going to evict tow node and build new cluster.
should I configure new quorum for new cluster or can i use the the quorum from old system ?
thanks

Hi,
Base on my experience, you need create a new cluster when you choose migrate the cluster, so you need the new witness disk.
The
related article:
Best practices for migration of cluster windows 2008 R2 / 2012 - As melhores Praticas para migrar um Cluster de Windows 2008 para Windows 2012
http://blogs.technet.com/b/hugofe/archive/2012/12/06/best-practices-for-migration-of-cluster-windows-2008-r2-2012-as-melhores-praticas-para-migrar-um-cluster-de-windows-2008-para-windows-2012.aspx
Hope this helps.
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.

How to test node failover in Windows 2008 R2 Failover Cluster?

Can anyone give me advice on how to properly test a node failure with a 2 mode Failover Cluster in Windows 2008 R2?

To test the failover of a clustered service or application
In the Failover Cluster Manager snap-in, if the cluster that you want to configure is not displayed, in the console tree, right-click
Failover Cluster Manager, click Manage a Cluster, and then select or specify the cluster that you want.
If the console tree is collapsed, expand the tree under the cluster that you want to configure.
Expand Services and Applications, and then click the service or application for which you want to test failover.
Under Actions (on the right), click Move this service or application to another node.
As the service or application moves, the status is displayed in the results pane (center pane).
Optionally, repeat step 4 to move the service or application to an additional node or back to the original node.
Source page:
http://technet.microsoft.com/en-us/library/cc754577.aspx
Regards,
Housam Smadi

Which account is used to failover to passive node of Windows 2008 R2 2-node cluster?

When I set up drive letter for shared drives in Windows 2008 R2 2-node cluster, I accidentally used a drive letter which has already mapped automatically due to the login I used.   After I run the cluster validation tests, all the drive letters
for shared drives are changed.   I fixed this issue by disconnecting the automatic mapped drive and reassigned all the drive letters.
However, I wonder whether CNO is used to perform the failover so such issue will not occur actually. Also, what happen if someone is logged on the passive node when the failover occur and any of the drive letters assigned for the shared drives
is already mapped due to that person's login.

Hi Sebastian,
Let me clarify my question. For example, there are clustered drives W:, M:, and L:.   Active Directory Group Policy has policy for some users to have mapped drive M:.
What will happen if failover occurs when one of the users having that policy is still logged on the passive node?
What will happen if failover occurs but that user has already logged off the passive node?
AKAIK, mapped drives are tied to the current logon user not for all users.
I don't know which account is actually used for the failover process. CNO, VNO, the domain user account used to create the windows cluster, or ?
Thanks.

Windows Server 2008 R2 SP1 2-Node cluster - Replace failed node

Hi - I have a two node Windows Server 2008 R2 SP1 fail-over cluster (DHCP, File, Print) where one of the nodes have failed beyond recovery. What I would like to do is to evict the failed cluster node and install a new machine with Windows Server 2008
R2 SP1 and re use the same name and Ip adress and then join this machine as a node in the cluster.
Is there any recommended steps to do this, i'm mostly thinking about the part of re-using the same name and ip address for the new node? (e.g. is there any cleanup more than evict the node?)
Enfo Zipper
Christoffer Andersson – Principal Advisor
http://blogs.chrisse.se - Directory Services Blog

Hi,
I agree with Noah Sparks, you can evict the corrupt node, if you reinstall then add the new server system you can just join it to cluster, it shouldn’t any error.
If you have seen some the evicted node rejoin to cluster meet “The cluster node is already a member of the cluster” error, it may need pack the KB2549472
hotfix.
The related KB:
How to Evict a Node from a Windows Server 2008 Failover Cluster
http://technet.microsoft.com/en-us/library/bb676524(v=exchg.80).aspx
Cluster node cannot rejoin the cluster after the node is restarted or removed from the cluster in Windows Server 2008 R2
http://support.microsoft.com/kb/2549472
Hope this helps.
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.

VM windows 2008 Cluster on Hyperv 2012 Server FC Disk error after Live Migration of the active VM Cluster Node

Deployed a 2 nodes Windows 2008 R2 SP1 Failover Cluster on a HyperV 2012 Server cluster deployed on IBM HS23 blade.
Disk susbsystem is IBM Storwize V7000. MPIO driver installed plus IBM DDSM.
Lun presented to the VM are connected with Virtual FC Adapter and everything works fine in the cluster until we start a live migration of the VM which hold the cluster disks online.
After migration complete positively, at the moment the MPIO of the migrated VM goes crazy with a lot of errors (source: mpio eventID 16 ) and warnings (source: mpio EventID: 17) in the system event log. After that the disks becomes unavailable.
Consequently everything hangs until power off the migrated vm, so the services on the cluster switchs on the second node.
I try to set the registry key HKLM\CurrentControlSet\Services\Disk\TimeOutValue to 190 as i found on various articles but nothing seems to change....
Any idea?
vannig

Hello,
I've just been through the IBM interoperability matrix and came across this statement:
Hyper-V on x64 based systems is supported with the following guest OS: Windows 2003 32bit, Windows 2003 64bit, Windows 2008 32bit, Windows 2008 64bit.
Clustering of guest OS is not supported at this time. When using Emulex HBAs with Hyper-V please select the settings mentioned in the Host Attachment section of SVC Info Center
http://publib.boulder.ibm.com/infocenter/svc/ic/index.jsp
Thanks

Is there any way to enable eventlog replication between two nodes in windows 2008 failover cluster.

Is there any way to enable eventlog replication between two nodes in windows 2008 failover cluster.
Thanks Azam When you see answers please Mark as Answer if Helpful..vote as helpful.

Hi,
As far as I know there don’t have the log replica function between failover cluster node, if you want to have the Unified log management you can refer the following related
KB:
Configure Computers to Forward and Collect Events
http://technet.microsoft.com/en-us/library/cc748890.aspx
Hope this helps.
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.

How to install a database on a MS Windows 2008 R2 failover cluster?

Hello,
I have to install a Oracle 11g R2 database onto a MS cluster (Windows Server 2008 R2 Failover Cluster with 2 nodes and shared storage). I installed the DBMS on both nodes. On the first node, I created a tablespace, the files are on the shared storage. I can connect to that database, up to here everything is fine.
But the problem is: How do I have to configure the DBMS on the second node to use the existing database files in the case when the second node gets the Cluster IP and the shared storage? The switchover is done, all database files (in the filesystem) can be seen on the second node.
The goal is to connect to the database from an external application, regardless which node is active.
I know the "Oracle Fail Safe Manager", it is already installed on both nodes.
A link to the related documentation would be helpful, I can't find anything.
Best regards,
C. Jost
Edited by: user13250186 on 07.06.2010 09:40

Hello,
But the problem is: How do I have to configure the DBMS on the second node to use the existing database files in the case when the second node gets the >Cluster IP and the shared storage? The switchover is done, all database files (in the filesystem) can be seen on the second node.When you switch the database from one node to another one do you have any error ?
Can you connect to the database and check for the Tablespaces ?
Normally, with OFS you define Groups. In one Group you'll have the Database, the Disk, the IP address and the Listener. So when you move the Group from one node to another one, the disk will be recognized on the second node then, the database, listener, ... will start and, there's no reason to loose a datafile.
Please, find enclosed, an introduction to Oracle Fail Safe concept:
http://www.oracle.com/technology/tech/windows/failsafe/pdf/fisc32.pdf
Hope this help.
Best regards,
Jean-Valentin

How to install DB6(DB2 for LUW) on a windows 2008 R2 failover cluster NodeB

Hi Gurus,
I am building a ECC6 EhP4 cluster on windows 2008 R2, I am following the installation guide chapter 7(document name: Installation guide SAP ERP6.0 EhP4 Ready SR1 ABAP on windows: IBM DB2 for Linux, Unix and Windows). But the step listed in the guide are not so clear and I have trouble for the database installation on the second node.
What I have done is:
1. 7.4.1 Preparing the database for MSCS step1 and 3
2. 7.4.2 Windows Server 2008: Creating the sap services and application
3. 7.4.3 Installing the central services Instance for ABAP (ASCS)
4. 7.4.4 Configuring the first MSCS node
5. 7.4.5 Installing the database instance on an mscs node(as i have done 7.4.1, i got some error in this step, then i checked some note and in note 1493410, it mentioned don't do step 7.4.1, so I uninstall the DB2, and get this step finished)
6. 7.4.6 Configuring the database for MSCS
7. 7.4.7 Configuring the Additional MSCS Node
8. 7.4.8 Installing an Enqueue Replicaiton Sever
9. 7.4.9 Installing the central instance
10. 7.4.10 Installing the dialog instance
Now I got problem on the database group, I cannot fail this to the second node. the DB2 Server resource cannot bring online to the second node. I think step 1, 4 and 5 may has some issue, but I don't know how should I install this database.
note 1493410's word confusing me, below is part of that note:
Chapter "Preparing the Database for MSCS"
You must not apply this chapter at the beginning of the installation. Instead, start the installation process with the next chapter "Configuring the First MSCS Node"
Follow the instructions in chapter "Preparing the Database for MSCS" in the exit step described in the chapter "Installing the Database Instance on an MSCS Node" before executing the db2mscs tool on the additional MSCS node only.
Point "3. Install all required operating system users ..." of this chapter is obsolete.
Anyone think my cluster still have chance to be fixed or I need rebuild it from scratch again. If I need build it again, I still don't know how to do the database installation on the second node
BR,
Peter

Hi pal,
Have you identified Ips and group names on which your sap application and DB should run..
I will give a overview...
Exam ples -
NODE A                  - 192.168.x.1
NODE B                   - 192.168.x.2 are the one which you idetify physical systems
1) Identify the drives you want to map for application and DB and make a partation and name the drives
2) Initially create Microsoft cluster service which creats cluster group----
CLUSTER GROUP   - 192.168.x.3 - Cluster name could be any thing meaningful...
Quorum disk          - 192.168.x.4 - 1 Gb drive
In point 2 if you are creating Cluster service with Heart ips you will naother ips for NODE A and NODE B ( 10.0.0.1 and 10.0.0.2)
3) Test and validate cluster configuration and ensure no erros are reflected
Above activities can be done with the help of OS Admin....
Now start working with SAP installation, even before that identify 2 names and ip address for SAP installation
Application group name can be as follows --
APPLPRD - 192.168.-x..5
Database group name can be as follows -
DBPRD - 192.168.x.6
You when you identify above drives for file systems and groups , you can start installation as mentioned in th guide...
Also let us know if you atrying to install EHP4 or EHP4.. as there some corrections to be followed in EHP4..
Open a new thread if you facing futher issues...
thanks,
rahuk

Windows 2008 Failover Cluster - Cannot add a generic service

Trying to add a generic service in a failover cluster.
Select the option Services and Application and it opens the wizard and then displays the error "An error was encountered while loading the list of services. QueryServiceConfig failed. The system cannot find the file specified"
The cluster validation wizard completes successfully. Permissions do not appear to be an issue as this account can seemly do everything else so I am at a loss to understand why this API is failing when it tries to query the server for services information.
Having searched the Internet the only thing I have found was someone posting a similar issue in the Greek language Technet forum(if I recall correctly) and their comment was they rebuild their cluster.
Windows 2008 (SP2) x64 two node cluster running a non-Microsoft database. We need to add a non-Microsoft Enterpirse backup solution and this is their documented method (adding it as a generic service) - both bits of software are from big vendors.
Symantec AV, but have tried with that disabled so don't think it has anything to do with that. Something is stopping the API from reporting back but I can't find what.
Really appreciate some help before we have to log a chargable call with Microsoft support
Thank you

Hi,
Have you tried the suggestion? I want to see if the information provided was helpful. Your feedback is
very useful for the further research. Please feel free to let me know if you have addition questions.
Best regards,
Vincent Hu

Windows 2008 R2 Failover Cluster - Netapp FAS6280 Black Screen on Restart when in cluster IGROUP

Hello everyone,
I've been working on this issue for a month now and have tickets open with Netapp and Microsoft. We have not been able to resolve the issue as of yet and since I'm losing all my hair I thought I should post it...
Scenario:
Two Windows 2008 R2 Enterprise SP Fail-Over Clusters (C1 & C2)
Two Netapp FAS6280 Filers for SAN storage
8 DELL R815 servers w/ 2x QLE2562 8GB FC HBAs all paths used (9.1.9.47 - newer did not resolve)
Netapp DSM 4.0 & SnapManager 6.4.2 (we also tried 1 rev newer, 1 rev older without luck)
C1 has 2 nodes & C2 has 4 nodes.
We are trying to add new nodes into the clusters. We were originally on EMC Clariion arrays and have been migrated to the netapp. Prior to moving we had 3 nodes in C2 and added node 4.
Now we want to add 2 more nodes, one to each cluster. We were able to configure the OS and get everything installed and matching the other nodes. we can assign HBAs to a test IGROUP and assign a lun, format it use it restart all is well and normal.
As soon as we change the HBAs to the IGROUP for C1 or C2's LUNs the servers don't want to restart properly. They hang at a black screen. The little green windows start splash screen runs the bar at the bottom. it then is supposed to fade
out and come back with the grey screen saying starting windows but that doesn't always happen. Sometimes it can take 4 hours to restart, or the machine will not come back onine at all. The pre-existing nodes *do not* experience this issue.
They restart in 5-10 minutes without issue.
We know drivers are part of the issue, but the maddening part is that it all works fine until we try to add the HBAs to the existing cluster storage group. We have a suggestion to create separate IGROUPs for each cluster node and add all luns to the
separate igroups. We configured this on one node and it still restarts long. We plan to modify the other nodes during our maintenance window and try again.
On the other cluster we were able to successfully complete the validate wizard and join. everything fails over and works except the server does not come up upon restart. If I unplug the HBAs it will come up fine, then I can plug them in and the
cluster functions.
Does anyone have any other ideas for us to try? Currently support for both netapp and Microsoft appear stumped. Sunday is our Window and we plan to try reconfiguring but I'm losing optimism...
Thanks for any feedback/ideas!
-Ryan

Thanks everyone who looked at this and offered feedback.
The issue appears to be resolved after the configuration change suggested by Netapp support.
The originally recommended configuration for our storage migration was similar to how I've seen storage groups configured on EMC arrays in the past. 1 storage group / igroup with all hbas/initiators for each host in the WFC/SQL cluster added to this
group. that group then gets all LUNs assigned to it.
The change in configuration that was recommended is to have 1 storage group / igroup for each host and put all initiators/hbas for each host in their own separate group. Then assign the all LUNs to each of the individual host igroups.
There is a lack of documentation on this, but it appears to work. We had 1 hit for separate igroups but had to go through a couple of support techs to get one to confirm this.
After applying this configuration in our change window today the issue is resolved. we were able to fail all resources onto the new node and restart it without issue. The question remaining for us is why the old systems continued to work while
the new nodes did not. The old nodes were originally migrated off an EMC and the version of ONTapp at that time was 8.1.2 and they worked fine.
We had upgraded to 8.1.3 to resolve an issue with flash cache and it seems like machines that we tried to attach to this igroup after that time did not work. all drivers software etc the same. We are wondering if this is somehow related and have
asked about it.
I wanted to update this thread, and perhaps it can save someone else some trouble down the line.
-Ryan

Instances in one node runningi in Oracle Clustster on Windows 2008 r2 VM

Helo,
I have created a Oracle 11g (11.2.0.2)cluster in windows 2008 r2 Environment in Vm
I have created the dbs also and every thing was working fine.
But after restarting the nodes instences in 1 node is not starting. 1 node is up so i can connect to DB.
when i do srvctl:
instance testdb1 is running on node xd-oradbb1-vm
instance testdb2 is not running on node xd-oradbb1-vm
srvct node apps - No Errors
crsctl - Both are online No Errors
When I try to start Below is the erro I am getting
The resource action "ora.testdb.db start"
encountered the following error:
ORA-00119: invalid specification for system parameter REMOTE_LISTENER
ORA-00132:
syntax error or unresolved network name 'RIE-ORADB-SCAN:1521'
Host file entries are :
#PUBLIC
10.53.52.41     XX-ORADBN1-VM.arg.internal          XX-ORADBN1-VM
10.53.52.42     XX-ORADBN2-VM.arg.internal          XX-ORADBN2-VM
#PRIVATE
10.1.1.41     XX-ORADBN1-VM-PRIV.arg.internal     XX-ORADBN1-VM-PRIV
10.1.1.42     XX-ORADBN2-VM-PRIV.arg.internal     XX-ORADBN2-VM-PRIV
#VIRTUAL
10.53.52.43     XX-ORADBN1-VM-VIP.arg.internal          XX-ORADBN1-VM-VIP
10.53.52.44     XX-ORADBN2-VM-VIP.arg.internal          XX-ORADBN2-VM-VIP
#SCAN ID
10.53.52.45     XX-ORADB-SCAN.arg.internal          XX-ORADB-SCAN
10.53.52.46     XX-ORADB-SCAN.arg.internal          XX-ORADB-SCAN
10.53.52.47     XX-ORADB-SCAN.arg.internal          XX-ORADB-SCAN
Listener entry
LISTENER_SCAN3=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_SCAN3))))          # line added by Agent
LISTENER_SCAN2=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_SCAN2))))          # line added by Agent
LISTENER=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER))))          # line added by Agent
LISTENER_SCAN1=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_SCAN1))))          # line added by Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_SCAN1=ON          # line added by Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER=ON          # line added by Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_SCAN2=ON          # line added by Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_SCAN3=ON          # line added by Agent
Kindly help, I have created Oracle RAC Environment by refering the documents and and I am a beginner.
Thanks,
Rajesh

Node1 (In this node it is up)
D:\app\11.2.0\grid\NETWORK\ADMIN
SQLNET.AUTHENTICATION_SERVICES= (NTS)
NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)
ADR_BASE = D:\app\oraadmin
D:\app\oraadmin\product\11.2.0\dbhome_1\NETWORK\ADMIN
SQLNET.AUTHENTICATION_SERVICES = (NTS)
remote_listener=RIE-ORADB-SCAN:1521
Node2 (not up)
D:\app\11.2.0\grid\NETWORK\ADMIN
SQLNET.AUTHENTICATION_SERVICES= (NTS)
NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)
ADR_BASE = D:\app\oraadmin
D:\app\oraadmin\product\11.2.0\dbhome_1\NETWORK\ADMIN
SQLNET.AUTHENTICATION_SERVICES= (NTS)
NAMES.DIRECTORY_PATH= (TNSNAMES)
remote_listener=RIE-ORADB-SCAN:1521

Cluster windows 2008 NODE MAJORITY

Similar Messages

Maybe you are looking for