Identity Portal fails to start

book

Article ID: 140118

calendar_today

Updated On:

Products

CA Identity Suite CA Identity Portal

Issue/Introduction

After upgrade to 14.2 Identity Portal fails to start

Error in the logs:

 [stdout] (MSC service thread 1-7) [SIGMA APPENDER - FROM WEB] 2019-11-13 12:05:28,462 - ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper - Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.

Note: This error will vary depending on your collation. 

Cause

When Identity Portal starts, it creates temp tables. Since the collation differs from the tempdb and the IP database, a conflict will occur. 

Environment

Release:


Component:

Resolution

As per Microsoft best practice that the system database(s) collation match the collation of the user-defined databases.  


IDM and IP must be SQL_Latin1_General_CP1_CI_AS and the system database(s) collations must match.


You can have your database administrator run a SQL trace when you start up portal.  This should help you determine which query has the collation conflict and which table. 

Additional Information

https://docs.microsoft.com/en-us/sql/relational-databases/policy-based-management/set-collation-of-user-defined-databases-to-match-master-model-databases?view=sql-server-ver15