EV Deployment Scanner found Collation issue for Non EV database
In preparation for a EV 8 upgrade the EV 8 deployment scanner was installed on a EV 7.5 SP4 server and then run to check for errors. One of the items that came back was a couple of collation issues.
The first collation error was for the typical MQUpgrade table on the directory database. This was addressed as per the tech article - so no problem. http://www.symantec.com/business/support/index?page=content&id=TECH62799
The second collation issue is the problem. The database that the deployment scanner did a collation check on is not a EV database. To verify I looked up and matched all EV store, audit, directory, FSA reporting, monitoring database. In addition I looked at the partition table in the directory database to see if any reference for this database existed and it does not. The database name is called EVolvelive. I checked with some other admins and verified that this database is another application database and not a EV database. (See attached jpg)
So the question is... Does the deployment scanner only check the EV databases for collation issues or does it check all the databases on the SQL server for collation issues?
In the deployment scanner results it says "
At least one test for the SQL server collation has failed. SQL databases (shown below) contain entities with mixed collations. If they are Enterprise Vault Vault Store databases then they will prevent a successful upgrade. Please go to http://seer.entsupport.symantec.com/docs/293475.htm for more details."
That leads me to believe that it checks all the databases on the sql server and not only the EV databases?
it could be that its look at EV*
That's how backup exec initially did its Databases to back up for EV, so anything that started with EV it assumed was an EV database, they changed that i believe after a customer reported something similar to you.
It won't cause any issues on upgrade though, the upgrade processes will not touch that database
