08-07-2011 10:52 AM
Hi all,
We have encountered collation errors during the upgrade of Enterprise Vault (Version 8 to version 9.0.2). The odd thing is that the EV databases were initially migrated from SQL2000 tot SQL2008 and the Enterprise Vault software (version 8) was manageable. During the upgrade process the deployment scanner gave no identication of SQL incompatibility, nor SQL possible collation errors. When the upgrade process was finished, i wasn't able to start the directory service without receiving "SQL general access denied errors" in eventvwr. From that moment on it went downhill :(.
When running the deployment scanner, I noticed the SQL collation errors on all four databases (databases of EV were in Latin1….., system default was in SQL_Latin1….).
I already looked into the Symantec technotes:
- It's not an option to change the default system sql collation;
- I'm not a fan off installing another instance on the server;
- Changing the collation type by using the SQL MS does not work on the vsg databases. An export an import with the correct SQL collation has failed.
- This procedure has been executed but failed on step 10 under SQL2005/2008.
What i want to know is the following:
- I have called with Symantec support and they suggested a downgrade. Does anyone have any experience with it, as i don't find much information about it.
- How can i solve the sql collation type error without adding an instance or changing the default collation type.
Thank you for the input.
Solved! Go to Solution.
08-07-2011 12:26 PM
08-07-2011 12:26 PM
08-07-2011 03:15 PM
Thank you for your response.
I have the impression that EV isn't able to connect to the databases. The error I received after the upgrade was "Unmatched SQL collations". The databases of EV are all in the same collation, but these are different with those of the server default.
If i understand you right, the datafiles on disk remain untouched during the upgrade?
The SQL server is used for multiple production as non-production databases.. Changing default collation is not an option.
08-07-2011 03:39 PM
ok so that technote, you said it failed at step 10? a find and replace in a SQL statement?
08-07-2011 11:40 PM
Yes, he did not found these lines.
We continued with the procedure, but we weren't able to connect to the databases with EV.
08-08-2011 06:45 AM
What if you try and search the sql script for:
cast(@length as varchar(4))
According to the blog+comments it should be around line 1830 in the script.
I've used the script from the blog and edited the script with the comment before the last post to change the collation under sql 2008.
It worked when I did it at least.
08-09-2011 10:00 AM
Hi Frekac, thank you for your feedback.
I was able to restore everything back to the old version because i wasn't able to alter the script.
I noticed also the database weren't altered during the upgrade, by using these sql query's and the following technote:
I have a hunch the gap between sql2000 and sql2008 was too big (but supported in the SCL).
Therefore, I'm going to follow this procedure and see what happens:
I keep you updated with the results.
Greetz,
Ruben