Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

EV 2007 to 8.0 upgrade and the SQL Collation error

Updated: 19 Apr 2010 | 5 comments
Erick Magnuson's picture
+2 2 Votes
Login to vote
This issue has been solved. See solution.

I'm upgrading from Enterprise Vault 2007 to 8.0.  When I run the deployment scanner I get a SQL Collation error on my VaultDirectory database.

I've seen http://seer.entsupport.symantec.com/docs/293475.htm as the method for fixing this.  However, I think that the method outlined in that article is a little overboard consider what's actually wrong with my specific database.  I have a single field in a single table with the incorrect collation.  It's EnterpriseVaultDirectory. MQUpgrade.AgentType.  First of all, the table is empty, the field AgentType has a custom collation, everything else has the default.   I know how to change the collation for this field.  I do it and run the Deployment Scanner and all it well.  My concern is that I'm missing something.  Can it really be that easy?

discussion Filed Under:

Comments

Wayne Humphrey's picture
14
May
2009
2 Votes +2
Login to vote

Yip as log as you corrected

Yip as log as you corrected the relevant table and Deployment Scanner now says there are no issues, you good to go ;)

www.quadrotech-it.com - All your EV Tools

biosphere's picture
28
May
2009
1 Vote +1
Login to vote

Most overboard indeed

The 293475 article is in my experience seriously overkill, and may even introduce new (and much more dire) issues if done improperly.

In most cases, opening the offending tables in design mode and changing their collations to db_default (or a specific one, if you really want to be on the safe side) is more than enough.

AndrewB's picture
11
Jun
2009
0 Votes 0
Login to vote

Eric, Do you remember what

Eric,
Do you remember what you did exactly? I have the collation error with the same table, MQUpgrade,  in my test environment.

Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec Platinum Partner | www.trace3.com

AndrewB's picture
11
Jun
2009
0 Votes 0
Login to vote

Nevermind. A few more clicks

Nevermind. A few more clicks into it and I found what I needed.

Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec Platinum Partner | www.trace3.com

Erick Magnuson's picture
19
Apr
2010
0 Votes 0
Login to vote

Glad you found it.  It's been

Glad you found it.  It's been awhile.  But I'm 99% sure that I simply changed the collation of the agenttype field and the process moved along to an eventual successful upgrade.