SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SP3 upgrade on SQL 2008 issue


SP3 upgrade on SQL 2008 issue

Author
Message
sqldba4u
sqldba4u
Ten Centuries
Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)

Group: General Forum Members
Points: 1431 Visits: 285
Hi,

Recently we tried upgrading SQL 2008 cluster instance from SP2 to SP3. After patching done on passive node, we tried connecting to SQL instance through SSMS, but got the error "Login failed for user. Server is in script upgrade mode. Only administrator can connect at this time".

Can someone please let me know the reason and its solution?

Regards.
george sibbald
george sibbald
SSC-Forever
SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)

Group: General Forum Members
Points: 44336 Visits: 13705
this is normal behaviour and hopefully upgrade script mode has completed by now.

the last phase of patching a SQL2008+ cluster node is to fail over to the node, at that point SQL comes up and completes the patch by going into script upgrade mode, no one is allowed to log on until this completes. How long this takes will vary depending on how many databases are on the server and anything that affects the speed of the server. Would normally complete in a few minutes.

If you look at the SQL errorlog through notepad you will see SQL running scripts against the databases. When you see the message 'recovery is complete' you will be able to log on.

---------------------------------------------------------------------
sqldba4u
sqldba4u
Ten Centuries
Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)Ten Centuries (1.4K reputation)

Group: General Forum Members
Points: 1431 Visits: 285
It took around 8 hours to become normal. I dont think in a production environment, we can afford this much downtime. Is it a bug or anyway realted due to OS version? In my case its Windows Server 2008 r2.

Regards.
george sibbald
george sibbald
SSC-Forever
SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)SSC-Forever (44K reputation)

Group: General Forum Members
Points: 44336 Visits: 13705
8 hours is way over the top, take a look through the errorlog to see which parts took so long. I am not aware of any OS dependencies or bugs that affect this so reporting to MS is probably worthwhile.

If you have a lot of databases that definitely affects the time this takes to run (though I have a server with over 300 and the script upgrade phase was still just a few minutes).

Only other thing I can think of is the database log files having large no of VLFs affecting database recovery time. How long does a node usually take to start up?

---------------------------------------------------------------------
Summer90
Summer90
SSChampion
SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)SSChampion (12K reputation)

Group: General Forum Members
Points: 12925 Visits: 3899
That is WAY too long. Should take minutes. Look at the SQL Server log and see what happened and the Windows event log for clues as to what was going on at the time.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum







































































































































































SQLServerCentral


Search