 |
|
|
|
Next: Ingres DBA Needed in Center Valley PA
|
| Author |
Message |
External
Since: Aug 19, 2004
Posts: 6
|
(Msg. 1) Posted: Mon Jan 14, 2008 5:54 pm
Post subject: Cluster Issue
Archived from groups: microsoft>public>sqlserver>clustering (more info?)
|
|
|
Hello,
I have a Wndows 2003 Sql 2005 Cluster consisting of two servers, on Failover
from node2 to node1 the application user is unable to login until the sql
server is restarted, on failover all the resourses come online but the user
is unable to access the database and if I look in SQl Server management
studio I am unable to see the properties of the DB, if I initiate a failure
of SQL server in the cluster I am still unable to access the DB but if I
restart SQL server in management studio the database comes online.
Also when I do a failover to node2, it shows all resourses are online but
the application cannot access the DB like it is not there, but I can access
the Quorum and the shared DB drive.
Thanks in advance,
Bob Smith |
|
| Back to top |
|
 | |
External
Since: Feb 23, 2005
Posts: 443
|
(Msg. 2) Posted: Tue Jan 15, 2008 10:14 am
Post subject: Re: Cluster Issue [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Definitely a problem. Check the Application log on either node (Event
logging on a cluster is cluster-wide to each node) to see if SQL is
complaining about starting up.
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Bob Smith" wrote in message
> Hello,
>
> I have a Wndows 2003 Sql 2005 Cluster consisting of two servers, on
> Failover
> from node2 to node1 the application user is unable to login until the sql
> server is restarted, on failover all the resourses come online but the
> user
> is unable to access the database and if I look in SQl Server management
> studio I am unable to see the properties of the DB, if I initiate a
> failure
> of SQL server in the cluster I am still unable to access the DB but if I
> restart SQL server in management studio the database comes online.
>
> Also when I do a failover to node2, it shows all resourses are online but
> the application cannot access the DB like it is not there, but I can
> access
> the Quorum and the shared DB drive.
>
> Thanks in advance,
> Bob Smith |
|
| Back to top |
|
| |
External
Since: Aug 19, 2004
Posts: 6
|
(Msg. 3) Posted: Tue Jan 15, 2008 10:14 am
Post subject: Re: Cluster Issue [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Hi Geoff,
Thanks for the reply, the only thing I can see is logwriter errors, which I
googled and found more questions than answers, let me ask this: Can the
Quroum and the physical disk be in different groups or should the be in the
same, mine is set the the Quorum is in the Cluster group and the Physical
disk is in group 0. By the way I see these errors on both nodes. What is best
practice for the cluster group, what resourses should exist in it: Cluster
IP, Cluster Name, MSDTC -?, Quorum -?
Thanks again,
Bob Smith
"Geoff N. Hiten" wrote:
> Definitely a problem. Check the Application log on either node (Event
> logging on a cluster is cluster-wide to each node) to see if SQL is
> complaining about starting up.
>
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "Bob Smith" wrote in message
>
> > Hello,
> >
> > I have a Wndows 2003 Sql 2005 Cluster consisting of two servers, on
> > Failover
> > from node2 to node1 the application user is unable to login until the sql
> > server is restarted, on failover all the resourses come online but the
> > user
> > is unable to access the database and if I look in SQl Server management
> > studio I am unable to see the properties of the DB, if I initiate a
> > failure
> > of SQL server in the cluster I am still unable to access the DB but if I
> > restart SQL server in management studio the database comes online.
> >
> > Also when I do a failover to node2, it shows all resourses are online but
> > the application cannot access the DB like it is not there, but I can
> > access
> > the Quorum and the shared DB drive.
> >
> > Thanks in advance,
> > Bob Smith
>
> >> Stay informed about: Cluster Issue |
|
| Back to top |
|
| |
External
Since: Feb 23, 2005
Posts: 443
|
(Msg. 4) Posted: Tue Jan 15, 2008 11:32 am
Post subject: Re: Cluster Issue [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Quorum must be in the cluster group. It is the reason the group exists.
The Quorum disk prevents split-brain problems. The Cluster group should
also have an IP Address and a Network Name Resource.
You can put the MSDTC resource in there too, but it can cause problems on
some very high volume systems.
All SQL resources should be in a different group. Note that disks are
physical resources. Logical OS partitions of the same disk cannot be split
into multiple groups.
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Bob Smith" wrote in message
>
> Hi Geoff,
>
> Thanks for the reply, the only thing I can see is logwriter errors, which
> I
> googled and found more questions than answers, let me ask this: Can the
> Quroum and the physical disk be in different groups or should the be in
> the
> same, mine is set the the Quorum is in the Cluster group and the Physical
> disk is in group 0. By the way I see these errors on both nodes. What is
> best
> practice for the cluster group, what resourses should exist in it: Cluster
> IP, Cluster Name, MSDTC -?, Quorum -?
>
> Thanks again,
> Bob Smith
>
> "Geoff N. Hiten" wrote:
>
>> Definitely a problem. Check the Application log on either node (Event
>> logging on a cluster is cluster-wide to each node) to see if SQL is
>> complaining about starting up.
>>
>> --
>> Geoff N. Hiten
>> Senior SQL Infrastructure Consultant
>> Microsoft SQL Server MVP
>>
>>
>> "Bob Smith" wrote in message
>>
>> > Hello,
>> >
>> > I have a Wndows 2003 Sql 2005 Cluster consisting of two servers, on
>> > Failover
>> > from node2 to node1 the application user is unable to login until the
>> > sql
>> > server is restarted, on failover all the resourses come online but the
>> > user
>> > is unable to access the database and if I look in SQl Server management
>> > studio I am unable to see the properties of the DB, if I initiate a
>> > failure
>> > of SQL server in the cluster I am still unable to access the DB but if
>> > I
>> > restart SQL server in management studio the database comes online.
>> >
>> > Also when I do a failover to node2, it shows all resourses are online
>> > but
>> > the application cannot access the DB like it is not there, but I can
>> > access
>> > the Quorum and the shared DB drive.
>> >
>> > Thanks in advance,
>> > Bob Smith
>>
>> >> Stay informed about: Cluster Issue |
|
| Back to top |
|
| |
External
Since: Dec 19, 2007
Posts: 3
|
(Msg. 5) Posted: Tue Jan 15, 2008 11:52 am
Post subject: Re: Cluster Issue [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Geoff,
Thanks, that is how it is setup Cluster group (Cluster IP, Cluster Name,
Disk Q and MSDTC) all other resourses are in another group, I am still
confused as too why SQL says it is online but the user/app cannot connect,
by restarting SQL server in studion management it comes online.
Thanks again,
Bob Smith
"Geoff N. Hiten" wrote in message
> Quorum must be in the cluster group. It is the reason the group exists.
> The Quorum disk prevents split-brain problems. The Cluster group should
> also have an IP Address and a Network Name Resource.
>
> You can put the MSDTC resource in there too, but it can cause problems on
> some very high volume systems.
>
> All SQL resources should be in a different group. Note that disks are
> physical resources. Logical OS partitions of the same disk cannot be
> split into multiple groups.
>
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
>
>
> "Bob Smith" wrote in message
>
>>
>> Hi Geoff,
>>
>> Thanks for the reply, the only thing I can see is logwriter errors, which
>> I
>> googled and found more questions than answers, let me ask this: Can the
>> Quroum and the physical disk be in different groups or should the be in
>> the
>> same, mine is set the the Quorum is in the Cluster group and the Physical
>> disk is in group 0. By the way I see these errors on both nodes. What is
>> best
>> practice for the cluster group, what resourses should exist in it:
>> Cluster
>> IP, Cluster Name, MSDTC -?, Quorum -?
>>
>> Thanks again,
>> Bob Smith
>>
>> "Geoff N. Hiten" wrote:
>>
>>> Definitely a problem. Check the Application log on either node (Event
>>> logging on a cluster is cluster-wide to each node) to see if SQL is
>>> complaining about starting up.
>>>
>>> --
>>> Geoff N. Hiten
>>> Senior SQL Infrastructure Consultant
>>> Microsoft SQL Server MVP
>>>
>>>
>>> "Bob Smith" wrote in message
>>>
>>> > Hello,
>>> >
>>> > I have a Wndows 2003 Sql 2005 Cluster consisting of two servers, on
>>> > Failover
>>> > from node2 to node1 the application user is unable to login until the
>>> > sql
>>> > server is restarted, on failover all the resourses come online but the
>>> > user
>>> > is unable to access the database and if I look in SQl Server
>>> > management
>>> > studio I am unable to see the properties of the DB, if I initiate a
>>> > failure
>>> > of SQL server in the cluster I am still unable to access the DB but if
>>> > I
>>> > restart SQL server in management studio the database comes online.
>>> >
>>> > Also when I do a failover to node2, it shows all resourses are online
>>> > but
>>> > the application cannot access the DB like it is not there, but I can
>>> > access
>>> > the Quorum and the shared DB drive.
>>> >
>>> > Thanks in advance,
>>> > Bob Smith
>>>
>>>
> >> Stay informed about: Cluster Issue |
|
| Back to top |
|
| |
External
Since: Feb 23, 2005
Posts: 443
|
(Msg. 6) Posted: Tue Jan 15, 2008 12:25 pm
Post subject: Re: Cluster Issue [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Maybe an IP address conflict or a dependency error. Again, the application
log should say something.
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Bob Smith" wrote in message
> Geoff,
>
> Thanks, that is how it is setup Cluster group (Cluster IP, Cluster Name,
> Disk Q and MSDTC) all other resourses are in another group, I am still
> confused as too why SQL says it is online but the user/app cannot connect,
> by restarting SQL server in studion management it comes online.
>
> Thanks again,
> Bob Smith
>
> "Geoff N. Hiten" wrote in message
>
>> Quorum must be in the cluster group. It is the reason the group exists.
>> The Quorum disk prevents split-brain problems. The Cluster group should
>> also have an IP Address and a Network Name Resource.
>>
>> You can put the MSDTC resource in there too, but it can cause problems on
>> some very high volume systems.
>>
>> All SQL resources should be in a different group. Note that disks are
>> physical resources. Logical OS partitions of the same disk cannot be
>> split into multiple groups.
>>
>> --
>> Geoff N. Hiten
>> Senior SQL Infrastructure Consultant
>> Microsoft SQL Server MVP
>>
>>
>>
>>
>> "Bob Smith" wrote in message
>>
>>>
>>> Hi Geoff,
>>>
>>> Thanks for the reply, the only thing I can see is logwriter errors,
>>> which I
>>> googled and found more questions than answers, let me ask this: Can the
>>> Quroum and the physical disk be in different groups or should the be in
>>> the
>>> same, mine is set the the Quorum is in the Cluster group and the
>>> Physical
>>> disk is in group 0. By the way I see these errors on both nodes. What is
>>> best
>>> practice for the cluster group, what resourses should exist in it:
>>> Cluster
>>> IP, Cluster Name, MSDTC -?, Quorum -?
>>>
>>> Thanks again,
>>> Bob Smith
>>>
>>> "Geoff N. Hiten" wrote:
>>>
>>>> Definitely a problem. Check the Application log on either node (Event
>>>> logging on a cluster is cluster-wide to each node) to see if SQL is
>>>> complaining about starting up.
>>>>
>>>> --
>>>> Geoff N. Hiten
>>>> Senior SQL Infrastructure Consultant
>>>> Microsoft SQL Server MVP
>>>>
>>>>
>>>> "Bob Smith" wrote in message
>>>>
>>>> > Hello,
>>>> >
>>>> > I have a Wndows 2003 Sql 2005 Cluster consisting of two servers, on
>>>> > Failover
>>>> > from node2 to node1 the application user is unable to login until the
>>>> > sql
>>>> > server is restarted, on failover all the resourses come online but
>>>> > the
>>>> > user
>>>> > is unable to access the database and if I look in SQl Server
>>>> > management
>>>> > studio I am unable to see the properties of the DB, if I initiate a
>>>> > failure
>>>> > of SQL server in the cluster I am still unable to access the DB but
>>>> > if I
>>>> > restart SQL server in management studio the database comes online.
>>>> >
>>>> > Also when I do a failover to node2, it shows all resourses are online
>>>> > but
>>>> > the application cannot access the DB like it is not there, but I can
>>>> > access
>>>> > the Quorum and the shared DB drive.
>>>> >
>>>> > Thanks in advance,
>>>> > Bob Smith
>>>>
>>>>
>>
> >> Stay informed about: Cluster Issue |
|
| Back to top |
|
| |
External
Since: Jan 28, 2008
Posts: 1
|
(Msg. 7) Posted: Mon Jan 28, 2008 2:59 pm
Post subject: Re: Cluster Issue [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Have you cluster in:
- SAN
- Into Active Directory
- The service Cluster start
- All disk resources state online
Give more details ...
"Bob Smith" wrote in message
> Hello,
>
> I have a Wndows 2003 Sql 2005 Cluster consisting of two servers, on
> Failover
> from node2 to node1 the application user is unable to login until the sql
> server is restarted, on failover all the resourses come online but the
> user
> is unable to access the database and if I look in SQl Server management
> studio I am unable to see the properties of the DB, if I initiate a
> failure
> of SQL server in the cluster I am still unable to access the DB but if I
> restart SQL server in management studio the database comes online.
>
> Also when I do a failover to node2, it shows all resourses are online but
> the application cannot access the DB like it is not there, but I can
> access
> the Quorum and the shared DB drive.
>
> Thanks in advance,
> Bob Smith >> Stay informed about: Cluster Issue |
|
| Back to top |
|
| |
| Related Topics: | SQL 2005 Cluster Installation Issue - Hi, My SQL 2005 fail over cluster installation fails with the following error: Machine : PrimaryNode Product : Microsoft SQL Server 2005 Product Version : 9.00.1399.06 Install : Failed Log File : C:\Program Files\Microsof...
Windows 2003 cluster trust issue during install? - We had a problem with one of our servers which is apart of a cluster ( NODE1 ). It required reloading and now we're back to installing SQL. When we're on NODE2, its partner, and try to install SQL, it complains about NODE1 (see logfile). However,..
MSDTC issue on a two node/two instance SQL 2005 cluster - We have a two node cluster setup with SQL 2005 SP1 over Windows Server 2003 SP1 with two active instances. We also have a separate cluster group for MSDTC with its own ip address, network name and disk. We have already checked that network DTC is..
Memory issue with SQL2005 Ent. 64bits + Cluster Win2003 64.. - We have recently installed a new cluster using 4 ways Opteron Processors boxes, we had no problems during installation! We are running an active/active configuration. Now running on production enviroment (medium load), we are experiencing some ..
How SQL2005 cluster can be installed on windows cluster? - I am new on both SQL and windows cluster. Our company is trying to deploy a HA SQL system, which I need to install SQL2005 to windows cluster. My question is: Since windows cluster will share one back end storage chassis, where should I put SQL2005 on... |
|
You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum
|
|
|
|
|
|
|
FAQ
Search
Profile
Private Messages
Log in
