Advanced Roadmaps plugin fails to load after Data Center license activation
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
After activating the Data Center license, Advanced Roadmaps plugin fails to start and displays as disabled in the ⚙ > Manage Apps > Manage apps page.
Environment
- Jira Data Center 9.0.0 and any higher version
- Oracle Database
Diagnosis
During Jira startup , you can notice the below error in the atlassian-jira.log related to the Advanced Roadmaps plugin table "AO_D9132D_SCENARIO_ISSUE_LABEL" :
Caused by: Error : 1430, Position : 49, Sql = ALTER TABLE "AO_D9132D_SCENARIO_ISSUE_LABEL" ADD "LEBAL" VARCHAR(255), OriginalSql = ALTER TABLE "AO_D9132D_SCENARIO_ISSUE_LABEL" ADD "LEBAL" VARCHAR(255), Error Msg = ORA-01430: column being added already exists in table at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:513)The portfolio plugins associated with Advanced Roadmaps are present under the shared_home/plugins/installed_plugins folder:
portfolio-plugin-x.x.x.jar team-management-plugin-x.x.x.jar jira-portfolio-x.x.x.jarWhen you describe the "AO_D9132D_SCENARIO_ISSUE_LABEL" table on the database using the below SQL query, you can observe the column name LABEL in the table type is set to CLOB:
DESCRIBE "AO_D9132D_SCENARIO_ISSUE_LABEL";
Cause
Due to some reason the column name LABEL is set to type CLOB instead of type VARCHAR(255).
Solution
Always back up your data before performing any modification to the database. If possible, try your modifications on a test server.
- Stop Jira running on all the nodes
- Alter the column LABEL of table "AO_D9132D_SCENARIO_ISSUE_LABEL" from CLOB datatype to varchar(255). Please reach out to your database admin team to update the column type
- Start Jira on each node 1 by 1
- Confirm that the issue is resolved by:
- Going to the ⚙ > Manage Apps > Manage apps page to confirm that Advance Roadmaps for Jira is now showing as enabled
- Trying to access Advanced Roadmaps plans