Unable to login after patch installation

After deployment a patch, for some projects could happen that it is not possible to login the project. The debug log shows that ALM is trying to insert a row in the table BPM_ELEMENT_TYPES and getting unique constraint violation error from the database.

Failed to Connect Project; [Mercury][Oracle JDBC Driver][Oracle]ORA-00001: unique constraint (ARCHIV_IT_RELEASE_SPRINT_ARCHI.BPMET_PRIMARYKEY) violated Failed SQL: /* ~~QC */ INSERT INTO BPM_ELEMENT_TYPES (BPMET_ID, BPMET_TYPE_NAME, BPMET_IS_INCLUDED_IN_PATHS) VALUES (690, ‘epc98_function’, ‘Y’);
Stack Trace:
java.sql.SQLException: [Mercury][Oracle JDBC Driver][Oracle]ORA-00001: unique constraint (ARCHIV_IT_RELEASE_SPRINT_ARCHI.BPMET_PRIMARYKEY) violated Failed SQL: /* ~~QC */ INSERT INTO BPM_ELEMENT_TYPES
(BPMET_ID, BPMET_TYPE_NAME, BPMET_IS_INCLUDED_IN_PATHS) VALUES (690, ‘epc98_function’, ‘Y’)…

There’s a new feature ‘ARIS 9.8 support’ introduced in ALM12.21 patch02. ‘The constant ‘ArisDbSchemaVersion’ is used to indicate whether the schema for the feature are created. If it’s not, when user login, the server will generate make required schema change (mainly insert some date in several tables, such as BPM_ELEMENT_TYPES).

In the project schema under DATACONST table it might be missing a record for that feature:
Data const name ArisDbSchemaVersion with value 1.

In order to resolve this issue add the record by executing the below SQL query (please ask your DBA for assistance):

INSERT INTO DATACONST ( DC_CONST_NAME , DC_VALUE ) VALUES ( ‘ArisDbSchemaVersion’ , ‘1’ );

Advertisements