October 15, 2007 at 6:43 am
Hi all.
I have a SQL 2005 test cluster (x64 Opteron) with 7 instances on.
I tested to put one instance in single user mode but now I cannot get it back to running normally again. Here's what I did:
1) In SQL Server Configuration Manager - Changed the startup to add ;-m (single user).
2) In SQL Server Configuration Manager - restarted the sqlserver service of instance
3) SQL Server Configuration Manager seems to hang and I killed the process. After this I can connect with Single User but cannot set the service back to multiuser. I cannot start the SSCM anymore either.
Anyone tested this scenario - over even worse - done it in production :hehe:
What I am thinking of now is to start the clustered sqlservice in Multi_user mode and have looked into http://support.microsoft.com/kb/912397 but not sure if this is correct path to follow.
Would appreciate any hints.
October 15, 2007 at 8:39 am
ah you do have to be careful with single user mode, any number of connections may grab your one and only connection.Alter database will normally put it back regardless of who has the connection.
I read a blog post on this subject - possibkly it was reporting services which grabbed the connection.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
October 15, 2007 at 11:29 am
Not sure if this applies to your case but I once had a situation with a cluster, there after removing the Builtin/admins the cluster won't start anymore. I had to start the instance in single user mode using the -f switch as well. I when added a login for the cluster service account. After that the instance started without any problems.
Markus
[font="Verdana"]Markus Bohse[/font]
October 15, 2007 at 12:33 pm
This is the funny part - cluster works - no problem. It's just that I need to get the SQL Service restarted without being in single user mode. I guess by using the cluster commands it will work fine but I am certainly not sure. Since I have in configuration manager - put the -m mark behind the exe file.
Strangely it's not documentet anywhere (I've found) where to restart a clustered SQL in single user mode as a step-by-step guide. Perhaps I'll digg more into this and create one...
Saw that it's recommended to use the commandline to do these things and now I understand... Luckily it was the testcluster.
October 16, 2007 at 1:24 am
Found out what I had to do for getting the sql services up and running.
1) Open command console from node that owns resource.
C:\>cluster res "SQL Server (DEV02)" /removecheck:"Software\Microsoft\Microsoft SQL Server\MSSQL.7\MSSQLSERVER"
Removing registry checkpoint 'Software\Microsoft\Microsoft SQL Server\MSSQL.7\MS SQLSERVER' for resource 'SQL Server (DEV02)'...
#####
Change paratmeter "SQLArg" by removing option -m on both nodes. Exit Regiedit
#####
Back to console
C:\>cluster res "SQL Server (DEV02)" /addcheck:"Software\Microsoft\Microsoft SQL Server\MSSQL.7\MSSQLSERVER"
Adding registry checkpoint 'Software\Microsoft\Microsoft SQL Server\MSSQL.7\MSSQLSERVER' for resource 'SQL Server (DEV02)'...
Start Clustered SQL Services from cluadmin
SQL Services not works ok but I cannot start the SQL Configuration Manager. Seems that it look locally instead of being "cluster aware".
Any of you have any idea?
October 16, 2007 at 8:28 am
SQL Services not works ok but I cannot start the SQL Configuration Manager. Seems that it look locally instead of being "cluster aware".
Configuration Manager is a client tool like SSMS and thus not "cluster aware". You should install the client components on both nodes.
[font="Verdana"]Markus Bohse[/font]
October 16, 2007 at 10:12 am
Not sure if you read all of the above but client tools are present locally and all of these operations have been configured locally.
Maybe reinstalling client tools will do the trick?
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply