Error ERROR [com.workpoint.server.DbVerifier] Invalid database version when starting CA PAMSC 14.1 server

Products

CA Privileged Identity Management Endpoint (PIM)

Issue/Introduction

Upon apparent successful installation of CA PAM SC 14.1, and after starting the Wildfly server, attempts at connecting to the ENTM result in error 404

Analysis of Wildfly server.log reveals that startup works fine until trying to bring up IndentityMinder.ear, in which case the following error messages appear

2022-05-03 10:01:16,657 ERROR [com.workpoint.server.DbVerifier] (MSC service thread 1-1) Invalid database version.: com.workpoint.common.exception.WorkflowException: The WorkPoint database version should be '3.5.2' for the WPDS DSN but is found to be '3.3.1.12' in the WP_INI table for SECTION_NAME=Database and KEY_NAME=version. This may mean you are running against an incompatible or outdated WorkPoint database version. Please upgrade the WorkPoint database manually, or set the auto.db.create.or.upgrade property to true in the workpoint-server.properties file and restart the server.
at com.workpoint.server.DbVerifier.verifyDB(Unknown Source) [wpServer.jar:]
at com.workpoint.server.pojo.UtilityPvtBean.verifyDBVersion(Unknown Source) [wpServer.jar:]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_212]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_212]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_212]

And this subsequently causes many errors, like for instance

2022-05-03 10:01:16,832 ERROR [com.workpoint.server.pojo.GenericServerBean] (MSC service thread 1-1) ORA-00904: "WP_PROC"."HIST_OPTIONS": invalid identifier

SQL = SELECT WP_PROC.PROC_ID, WP_PROC.PROC_DB, WP_PROC.PROC_REF, WP_PROC.NAME, WP_PROC.DURATION, WP_PROC.BUS_CAL_ID, WP_PROC.BUS_CAL_DB, WP_PROC.PRIOR_ID, WP_PROC.PRIOR_DB, WP_PROC.PRIOR_SCRIPT_ID, WP_PROC.PRIOR_SCRIPT_DB, WP_PROC.ENABLED, WP_PROC.PROC_OPT, WP_PROC.RESC_ENUM_SCRIPT_ID, WP_PROC.RESC_ENUM_SCRIPT_DB, WP_PROC.RESC_DESC_SCRIPT_ID, WP_PROC.RESC_DESC_SCRIPT_DB, WP_PROC.ROW_VERSION, WP_PROC.LU_ID, WP_PROC.LU_DATE, WP_PROC.DESCRIPTION, WP_PROC.FORM_ID, WP_PROC.FORM_DB, WP_PROC.SCHEMA_ID, WP_PROC.SCHEMA_DB, WP_PROC.CHECK_SYNTAX_SCRIPT_ID, WP_PROC.CHECK_SYNTAX_SCRIPT_DB, WP_PROC.PROC_UUID, WP_PROC.EMIT_EVENTS, WP_PROC.COMP_CODE_SCRIPT_ID, WP_PROC.COMP_CODE_SCRIPT_DB, WP_PROC.REF1, WP_PROC.REF2, WP_PROC.REF3, WP_PROC.REF4, WP_PROC.HIST_OPTIONS FROM WP_PROC ORDER BY NAME

As a result the Access Control environment is not loaded and it is impossible to start ENTM properly

Environment

PAM SC 14.1, all platforms and OS versions

Cause

The root cause for this problem is exactly the one mentioned in the error message: auto.db.create.or.upgrade property in the workpoint-server.properties file does not exist or it is set to false.

Resolution

The solution is documented in the following KB article for IdentityMinder for that specific product, which is also partially used by PAM SC:

https://knowledge.broadcom.com/external/article/98011/workpoint-database-version-errors-are-pr.html

In particular the following actions must be undertaken in the PAM SC server

Under the PAM SC server home, in directory IAM Suite\AccessControl\tools\Workpoint\conf, edit file workpoint-server.properties and check for the value of the auto.db.create.or.upgrade property. Create it if not existing and set it (or modify it in case it was already there) to true and restart the Wildfly server
It may be necessary as well to ask the DB administrator for your RDBMS to drop all tables from the Workpoint database 'WPDS' after changing the property and prior to restarting the Wildfly server