10-16-2013 09:04 AM
I just upgraded my Enterprise Vault environment to 10.0.4 CHF1 and have run into an issue when upgrading the DA customer DB's. The DA database is hosted on a SQL 2005 standard edition server. When attempting to upgrade the cusomter DB's I get the following error: "Online index operations can only be performed in Enterprise edition of SQL server." The State then says "UpgradeFailed" and I cant get past it. Any ideas? I will open a case with support but thought I'd post here too. I tried putting the DB in single-user mode and restarting the EVAM service, but the same thing happens.
Solved! Go to Solution.
10-16-2013 10:50 AM
Ok, I figured it out. The following two sql update scripts need to be modified (I'm sure Symantec will release a v2 update to fix this issue once I update the case with my findings). So, once you install CHF1 on the Discovery Accelerator server and if your SQL server is NOT Enterprise Edition, you need to change the following two files before upgrading the Cusotmer DB's.
C:\Program Files (x86)\Enterprise Vault Business Accelerator\
AcceleratorDatabase.sql, line 76098, ONLINE = OFF
AcceleratorDatabaseSchemaUpdateV10SP4.sql, line 289, ONLINE = OFF
After modifying the files, you can successfully upgrade the DA cusomter databases.
10-16-2013 10:42 AM
Well done for figuring it out - not so good that it was released with the problem in the first place :(
10-16-2013 10:50 AM
Ok, I figured it out. The following two sql update scripts need to be modified (I'm sure Symantec will release a v2 update to fix this issue once I update the case with my findings). So, once you install CHF1 on the Discovery Accelerator server and if your SQL server is NOT Enterprise Edition, you need to change the following two files before upgrading the Cusotmer DB's.
C:\Program Files (x86)\Enterprise Vault Business Accelerator\
AcceleratorDatabase.sql, line 76098, ONLINE = OFF
AcceleratorDatabaseSchemaUpdateV10SP4.sql, line 289, ONLINE = OFF
After modifying the files, you can successfully upgrade the DA cusomter databases.
10-17-2013 04:42 AM
Thank you for notifying us of this issue, BigPhil. We'll be opening an Engineering Track (Etrack) with Engineering about this issue to either get a fix or (maybe and) get their blessing to publicly provide customers with replacement files having the fix that you found.
10-18-2013 03:18 AM
Saved my day BigPhil.
Thanks for sharing!
10-21-2013 06:59 AM
Thanks for the spot...we'll re-release with this fixed in the next couple of days. In the meantime, you're fine to modify "ONLINE = OFF" or indeed remove the line
"WITH (ONLINE = ON, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, FILLFACTOR = 90) ON [PRIMARY] "
from both the AcceleratorDatabaseSchemaUpdateV10SP4.sql and AcceleratorDatabase.sql for the tblHashToDiscoveredItem index being created.
Chris
10-23-2013 01:52 PM
Just to finish off, we've re-released the cumulative hotfix so that it no longer has this issue. For those stuck in limbo (if you haven't manually resolved the situation already) please refer to the following technote for further information:
http://www.symantec.com/business/support/index?page=content&id=TECH211817
Chris