12.1.1000.157 RU1 to 12.1.2 RU 2 Update failure: Must declare the scalar variable "@tooOldDef"
I've tried to upgrade my SEPM server from SEP 12.1.1000.157 RU1 to 12.1.2 RU 2. I've got the following Error message:
...
Config schema format is upgraded from: 12.1.1.0
2012-12-04 14:51:34.891 THREAD 28 INFO: Upgrade schema started ...
2012-12-04 14:51:34.891 THREAD 28 INFO: Process SQL script file:MSSQLServerAmberRU1toAmberRU1MP1.sql
...
2012-12-04 14:51:35.565 THREAD 28 SEVERE: Upgrade.doUpgrade java.sql.SQLException: Failed to upgrade schema: java.sql.SQLException: java.sql.SQLException: Must declare the scalar variable "@tooOldDef".
...
The variable "@tooOldDef" occurs (also as "@tooolddef" in the files "Symantec Endpoint Protection Manager\bin\inst.jar in the MSSQLSErver.sql script and under "Symantec Endpoint Protection Manager\tomcat\webapps\ROOT\WEB-INF\lib\scm-server.jar in some *.sql scripts
Environment: MSSQL Server 2008, case sensitive db
Any ideas how to get this to work?
Comments 6 Comments • Jump to latest comment
was there any activity on SEPM while SEPM was upgrading.
Cheers!
Pete
Help Link: http://www.symantec.com/business/support/overview.jsp?pid=54619
No, the SEPM Service was stopped. The Upgrade itself stopps at 3%.
hope you are using the admin credentials for upgrading. can you retry the iupgrade?
Cheers!
Pete
Help Link: http://www.symantec.com/business/support/overview.jsp?pid=54619
The problem is the different spelling of @tooolddef <-> @tooOldDef in the sql scripts and the use of the case-sensitive MSSQL Server Instance. Only Symantec can solve this in his MSSQL scripts in the installation package!
Admin credentials etc. p.p. are used of course.
I had the same problem as you when i tried to upgrade from 12.1.1000.157 RU1 to 12.1.2 RU 2.
I have an case-sensative MSSQL Instance and it was as _sid_ wrote that "the problem is the different spelling of @tooolddef <-> @tooOldDef in the sql scripts and the use of the case-sensitive MSSQL Server Instance."
I was in contact with Symantec Technoical Support regarding this and they wrote:
"Unfortunatly case-sensitive SQL collation is not supported by Symantec Endpoint Protection Manager (SEPM). SEPM requires a case-insensitive SQL collation."
So the thing i did was to move the SEP db to an case-insensitive MSSQL instance.
And then the upgrade worked without any problems.
I have exactly the same problem but I do not know how to move the SEP db to an case-insensitive MSSQL instance. Any help?
Would you like to reply?
Login or Register to post your comment.