Management Server Upgrade stops at 2% - Upgrade Database Schema. Error Occurred
search cancel

Management Server Upgrade stops at 2% - Upgrade Database Schema. Error Occurred

book

Article ID: 165150

calendar_today

Updated On:

Products

Endpoint Protection

Issue/Introduction

When attempting to upgrade the Symantec Endpoint Protection Manager (SEPM) to 14 MP1, the Management Server Upgrade shows the Server upgrade Status stopped at 2% with Upgrading Database Schema… Error occurred.

The following error is seen in the upgrade log: 


017-04-21 15:54:44.907 THREAD 23 SEVERE: java.sql.SQLException: com.microsoft.sqlserver.jdbc.SQLServerException: This index operation requires 4096 KB of memory per DOP. The total requirement of 32904 KB for DOP of 8 is greater than the sp_configure value of 704 KB set for the advanced server configuration option "index create memory (KB)".  Increase this setting or reduce DOP and rerun the query.

2017-04-21 15:54:44.907 THREAD 23 SEVERE:     at com.sygate.scm.server.db.util.DatabaseUtilities.execCommandFromScript(DatabaseUtilities.java:2005)
2017-04-21 15:54:44.907 THREAD 23 SEVERE:     at com.sygate.scm.server.db.util.DbHelper.execCommandFromScript(DbHelper.java:246)
2017-04-21 15:54:44.907 THREAD 23 SEVERE:     at com.sygate.scm.server.db.util.SqlDbHelper.upgrade(SqlDbHelper.java:1249)
2017-04-21 15:54:44.907 THREAD 23 SEVERE:     at com.sygate.scm.server.upgrade.Upgrade.upgradeDatabaseSchema(Upgrade.java:3861)
2017-04-21 15:54:44.907 THREAD 23 SEVERE:     at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:683)
2017-04-21 15:54:44.908 THREAD 23 SEVERE:     at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:123)
2017-04-21 15:54:44.908 THREAD 23 SEVERE:     at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:251)
2017-04-21 15:54:44.908 THREAD 23 SEVERE:     at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:159)
2017-04-21 15:54:44.908 THREAD 23 SEVERE:     at java.lang.Thread.run(Thread.java:745)
2017-04-21 15:54:44.927 THREAD 23 WARNING: Upgrade> updateTransactionLogFileSize>> Original log size is 2097152

2017-04-21 15:54:44.928 THREAD 23 SEVERE: java.sql.SQLException: Failed to upgrade schema: java.sql.SQLException: com.microsoft.sqlserver.jdbc.SQLServerException: This index operation requires 4096 KB of memory per DOP. The total requirement of 32904 KB for DOP of 8 is greater than the sp_configure value of 704 KB set for the advanced server configuration option "index create memory (KB)".  Increase this setting or reduce DOP and rerun the query.

2017-04-21 15:54:44.928 THREAD 23 SEVERE:     at com.sygate.scm.server.db.util.SqlDbHelper.upgrade(SqlDbHelper.java:1279)
2017-04-21 15:54:44.928 THREAD 23 SEVERE:     at com.sygate.scm.server.upgrade.Upgrade.upgradeDatabaseSchema(Upgrade.java:3861)
2017-04-21 15:54:44.928 THREAD 23 SEVERE:     at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:683)
2017-04-21 15:54:44.929 THREAD 23 SEVERE:     at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:123)
2017-04-21 15:54:44.929 THREAD 23 SEVERE:     at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:251)
2017-04-21 15:54:44.929 THREAD 23 SEVERE:     at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:159)
2017-04-21 15:54:44.929 THREAD 23 SEVERE:     at java.lang.Thread.run(Thread.java:745)

Cause

This error occurs when the MS SQL Index Creation Memory has been defined too low for the upgrading of the Schema.

Resolution

The Index Create Memory setting is an advanced SQL Server configuration setting which the SQL Server database engine uses to control the amount of maximum memory which can be allocated towards the creation of an index.

  1. Launch the Microsoft SQL Studio Manager
  2. In Object Explorer, right click the SQL Server Instance and click on Properties.
  3. In Server Properties window, click on Memory node under Select a page
  4. Under the Other memory options define the Index creation memory

 

Note:  Index creation memory (in KB, 0 = dynamic memory) 

Specifies the amount of memory (in KB) to use during index creation sorts. The default value of zero enables dynamic allocation and should work in most cases without additional adjustment; however, the user can enter a different value from 704 to 2147483647.

For further information on Index Creation Memory, review Microsoft articles below

https://msdn.microsoft.com/query/dev10.query?appId=Dev10IDEF1&l=EN-US&k=k(SQL11.SWB.SERVERPROPERTIES.MEMORY.F1)&rd=true
https://technet.microsoft.com/en-us/library/ms175123(v=sql.105).aspx

Attachments

Powered by Wolken Software