x

script upgrade mode

A cumulative patch was recently installed to both nodes of our 2-node active/passive cluster, which upgraded the version from 10.50.1600 to 10.50.1790. Since the patch, whenever the SQL service changes nodes, it enters "script upgrade mode", just after starting the databases. A massive script executes which floods the application log with object drops & creates that appear to be associated with an msdb upgrade.

The first few lines of the log are included below.

The process completes after about 3 minutes and then the server functions normally. Prior to this change, a failover only took about 20 seconds. Both nodes have been rebooted.

Is this behavior typical? I am requesting ideas about why this might be happening, and how to resolve it. thank you!


---log example---

Dropping signature from: sp_modify_dtscategory

Dropping signature from: sp_sqlagent_notify
Dropping signature from: sp_ssis_setpackageroles
Dropping signature from: sp_enum_dtscategories
Dropping signature from: sp_is_sqlagent_starting
Dropping signature from: sp_ssis_getpackageroles
Dropping signature from: sp_log_dtspackage_begin
Dropping signature from: sp_ssis_getfolder
Setting database option RECOVERY to SIMPLE for database msdb.

Setting database option TRUSTWORTHY to ON for database msdb.
Checking the size of MSDB...

Error: 18401, Severity: 14, State: 1.
Login failed for user 'NT AUTHORITY\SYSTEM'. Reason: Server is in script upgrade mode. Only administrator can connect at this time. [CLIENT: xxxxx]

Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.

Deleting cached auto-generated T-SQL Data Collection packages from msdb...
End of DC pre-upgrade steps.
Starting DAC pre-upgrade steps ...

----------------------------------------
Execution of PREINSTMSDB100.SQL complete
----------------------------------------
----------------------------------
Starting execution of INSTMSDB.SQL
----------------------------------
Data Collector state before upgrade: 0
DC pre-upgrade steps...
Check if Data collector config table exists...
DMF pre-upgrade steps...
Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
Check if syssubsystems table exists...

Alter table systargetservers...

Alter table sysdownloadlist...

Alter table sysjobhistory...

Creating table temp_sysjobschedules
DBCC TRACEOFF 1717, server process ID (SPID) 13. This is an informational message only; no user action is required.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Using 'xpstar.dll' version '2009.100.1600' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.

Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
Setting database option COMPATIBILITY_LEVEL to 100 for database msdb.
Database 'master' is upgrading script 'sqlagent100_msdb_upgrade.sql' from level 0 to level 2.
----------------------------------------
Starting execution of PREINSTMSDB100.SQL
----------------------------------------
Error: 18401, Severity: 14, State: 1.
Login failed for user xxxx. Reason: Server is in script upgrade mode. Only administrator can connect at this time. [CLIENT: xxxx]

User 'sa' is changing database script level entry 5 to a value of 2.
User 'sa' is changing database script level entry 6 to a value of 2.
User 'sa' is changing database script level entry 6 to a value of 0.
Running SQL Server 2005 SP2 to SQL Server 2008 upgrade script
----------------------------------------------------------------

User 'sa' is changing database script level entry 4 to a value of 2.
MSDB format is: SQL Server 2008
Database 'master' is upgrading script 'msdb_upgrade_discovery.sql' from level 171050560 to level 171050750.

----------------------------------------------------------------
msdb_upgrade_discovery starting
more ▼

asked Jan 06 '12 at 10:33 AM in Default

worachek gravatar image

worachek
11 1 1 1

10.50.1790 was actually a security update, I don't believe it was released as a CU. Anyway, after the patch was installed did the install log show that the installation completed, or any errors?
Jan 06 '12 at 10:47 AM Shawn_Melton

Hi Worachek,

Did you get to resolve this issue? I am experiencing the same issue with 2 different patch levels on each node in the passive/active cluster. Failover now takes 3 minutes vs 20 seconds. Please provide details if you have resolved.

Thanks
May 14 '12 at 12:12 PM jbelling
(comments are locked)
10|1200 characters needed characters left

1 answer: sort voted first

You might consider applying SP1 for SQL Server 2008 R2, it includes the security patch from the MS11-049 (10.50.1790). I am not sure how you applied the patch previously but the process for patch installs on clustered servers changed with SQL 2008, there was a good write up [here][1].

[1]: http://www.sqlha.com/2011/05/10/patching-clustered-sql-server-instances-with-sql-server-2008-and-sql-server-2008-r2/
more ▼

answered Jan 06 '12 at 11:02 AM

Shawn_Melton gravatar image

Shawn_Melton
5.3k 17 21 29

(comments are locked)
10|1200 characters needed characters left
Your answer
toggle preview:

Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

New code box

There's a new way to format code on the site - the red speech bubble logo will automatically format T-SQL for you. The original code box is still there for XML, etc. More details here.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

SQL Server Central

Need long-form SQL discussion? SQLserverCentral.com is the place.

Topics:

x673
x562
x85

asked: Jan 06 '12 at 10:33 AM

Seen: 2838 times

Last Updated: May 14 '12 at 12:13 PM