The import progress to create a universe stuck at "0% in progress". An error "The Workpoint adapter is not responding, perform a Workpoint Checkup" if the universe is opened.
Performing those below actions throws some more errors:
- Running Workpoint Checkup gives a lot of errors "missing essential workpoint process [xxxx]"
- Running the “Update” function for the Workpoint DB Administration fails with error "Import has failed. Exception is: Invalid TableID. TableID cannot be null!"
Eurekify logs show:
17:29:40,265 INFO [stdout] (default task-34) 2018-03-05 17:29:40,265 [default task-34] ERROR com.workpoint.server.pojo.UniqueIDUpdatePvtBean - spWP_GET_NEW_ID returned null Database value, probably because it cannot find row in WP_INI table for SECTION_NAME='Database' and KEY_NAME='ID', so cannot construct TableID.
17:38:30,140 INFO [stdout] (Query_actionq#ActionQ1#WPDS) 2018-03-05 17:38:30,140 [Query_actionq#ActionQ1#WPDS] ERROR com.workpoint.server.pojo.GenericServerBean - Could not find stored procedure 'SPWP_ASSIGN_SCRIPT_MON_ROWS'.
17:38:30,143 ERROR [org.jboss.as.ejb3.invocation] (Query_actionq#ActionQ1#WPDS) JBAS014134: EJB Invocation failed on component MonitorPvt_EJB for method public abstract com.workpoint.common.data.table.ScriptMonitorTable[] com.workpoint.server.pojo.MonitorPvt.queryScriptQMonitors(java.lang.String,java.lang.String,java.math.BigDecimal,java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.String[],java.lang.String,boolean,java.lang.String,boolean,int,boolean) throws com.workpoint.server.ejb.WorkPointEJBException: com.workpoint.server.ejb.WorkPointEJBException: An SQL Exception has occurred. Please see the server logs for details.
Identity Governance Guide R14.1 stated:
* eurekify_sdb—case-sensitive
* eurekify_ticket—case-sensitive
* WPDS (Workpoint)—case-insensitive
* Data Warehouse—case-sensitive
https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/identity-manager/14-2/platform-support-matrix.html
Dropping and re-creating the Workpoint DB with Latin1_General_CI_AI fixes the issue.
Important note: Depending on business requirement about how data should be sorted and compared, the DB Collation might need to be configured differently to accommodate that.
The default collation when a standalone IG installation creates the Workpoint database automatically is: SQL_Latin1_General_CP1250_CI_AS