Troubleshooting
Problem
After upgrading to SCC v6.0.0.1, iFix06, on Windows Server 2008 R2, the startup failed. Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "SQL_Latin1_General_CP850_BIN" in the equal to operation.
Symptom
ERROR RecoverableDAO - The query was executed 60 times for 604 seconds.
However, the engine did not succeed in performing the database operation, because of the following.
Error :Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "SQL_Latin1_General_CP850_BIN" in
the equal to operation.
24 Jan 2017 09:45:39,418 650103 [Thread-243] ERROR RecoverableDAO - Cannot resolve the collation conflict between
"SQL_Latin1_General_CP1_CI_AS" and "SQL_Latin1_General_CP850_BIN" in the equal to operation.
Stack Trace:
com.microsoft.sqlserver.jdbc.SQLServerException: Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and
"SQL_Latin1_General_CP850_BIN" in the equal to operation.
at com.microsoft.sqlserver.jdbc.SQLServerException.
makeFromDatabaseError(SQLServerException.java:216)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult
(SQLServerStatement.java:1515)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.
doExecutePreparedStatement(SQLServerPreparedStatement.java:404)
at com.microsoft.sqlserver.jdbc.
SQLServerPreparedStatement$PrepStmtExecCmd.doExecute
(SQLServerPreparedStatement.java:350)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand
(SQLServerConnection.java:1715)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand
(SQLServerStatement.java:180)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement
(SQLServerStatement.java:155)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery
(SQLServerPreparedStatement.java:285)
at com.sterlingcommerce.scc.agent.services.jdbc.dao.alert.
AlertJdbcDAO$2.executeQuery(AlertJdbcDAO.java:146)
at com.sterlingcommerce.scc.agent.services.jdbc.dao.RecoverableDAO.
executeQuery(RecoverableDAO.java:787)
at com.sterlingcommerce.scc.agent.services.jdbc.dao.alert.AlertJdbcDAO.
addUnknownMessages(AlertJdbcDAO.java:57)
at com.sterlingcommerce.scc.agent.services.node.AlertsUtil.run
(AlertsUtil.java:156)
Cause
The Installation / Configuration failed. From the ccinstall.log:
24 Jan 2017 10:22:59,827 13416 [main] INFO DB_Config - Config Step ---
Database connection parms configuration ---
24 Jan 2017 10:22:59,827 13416 [main] INFO DB_Config -
###############################################################
24 Jan 2017 10:22:59,827 13416 [main] INFO DB_Config - DB Config already done...
24 Jan 2017 10:26:59,351 252940 [main] ERROR Install -
Stack Trace:
java.lang.NullPointerException
at com.sterlingcommerce.scc.agent.services.jdbc.DB_Config.overrideDbConnParms(DB_Config.java:1565)
at com.sterlingcommerce.scc.agent.services.jdbc.DB_Config.config(DB_Config.java:269)
at com.sterlingcommerce.scc.agent.install.InstallerHelper.configureDBParms(InstallerHelper.java:255)
at com.sterlingcommerce.scc.agent.install.SCCConfigurator.install(SCCConfig
urator.java:379)
at com.sterlingcommerce.scc.agent.install.Installer.install(Installer.java:58)
at com.sterlingcommerce.scc.agent.install.Installer.main(Installer.java:70)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
at java.lang.reflect.Method.invoke(Method.java:620)
at com.sterlingcommerce.scc.CCLauncher.main(CCLauncher.java:42)
Diagnosing The Problem
When starting Control Center after an upgrade, and we get a collation error, check to see if the installation was successful by reviewing the ccinstall.log file.
Resolving The Problem
Run / Rerun configCC.bat (configCC.sh on UNIX) to a successful completion.
Was this topic helpful?
Document Information
Modified date:
17 December 2019
UID
swg21997839