Unable to instantiate QIssueSource schema

[angga]

Hi

i'm using jira for server. i got this error 'Unable to instantiate QIssueSource schema' when i create plan on advanced roadmap.

im using mysql 5.7 and already follow this instruction https://confluence.atlassian.com/adminjiraserver/connecting-jira-applications-to-mysql-5-7-966063305.html. But still getting error, any suggestion?

thank you

here's the detail :

java.lang.RuntimeException: Unable to instantiate QIssueSource schema.

  at com.atlassian.rm.jpo.core.issuesource.schema.QIssueSourceFactory.table:27
  at com.atlassian.rm.jpo.core.issuesource.sql.QueryDslIssueSourcePersistence.addIssueSourcesTransactional:121
  at com.atlassian.rm.jpo.core.plan.DefaultPlanService.lambda$null$1:251
  at com.atlassian.rm.common.persistence.transaction.Registry.run:35
  at com.atlassian.rm.jpo.core.plan.DefaultPlanService.lambda$createPlan$4:247
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler.inTransaction:111
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler.inNewTransaction:99
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler.inNewTransaction:89
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler.lambda$inDatabaseTransaction$3:69
  at com.atlassian.rm.common.persistence.DefaultDatabaseProvider.lambda$run$0:24
  at com.atlassian.rm.common.persistence.env.JiraDatabaseProvider.lambda$execute$0:34
  at com.atlassian.rm.common.bridges.jira.persistence.JiraDatabaseProviderBridge710.execute:59
  at com.atlassian.rm.common.persistence.env.JiraDatabaseProvider.execute:34
  at com.atlassian.rm.common.persistence.DefaultDatabaseProvider.run:24
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler.inDatabaseTransaction:68
  at com.atlassian.rm.jpo.core.plan.DefaultPlanService.createPlan:227
  at com.atlassian.rm.jpo.core.plan.jobs.PlanCreationJob.run:21
  at com.atlassian.rm.jpo.core.plan.jobs.PlanCreationJob.run:8
  at com.atlassian.rm.jpo.env.threading.AbstractTranslatedLongRunningTaskProvider$1.run:25
  at com.atlassian.rm.jpo.env.threading.JiraLongRunningExecutorRegistry$1$1.run:48
  at com.atlassian.rm.common.bridges.jira.threading.LongRunningExecutorServiceBridge710.lambda$execute$0:104
  at com.atlassian.rm.common.bridges.jira.threading.JiraSafeThreadService.lambda$execute$0:47
  at java.util.concurrent.FutureTask.run:266
  at java.util.concurrent.ThreadPoolExecutor.runWorker:1149
  at java.util.concurrent.ThreadPoolExecutor$Worker.run:624
  at java.lang.Thread.run:748

Caused by java.lang.IllegalArgumentException: Not able to find table AO_D9132D_ISSUE_SOURCE

  at com.atlassian.rm.common.pkqdsl.legacy.DefaultSchemaProvider.getSchema:61
  at com.atlassian.rm.common.bridges.jira.persistence.JiraSchemaProviderBridge710.getSchemaName:25
  at com.atlassian.rm.common.persistence.env.JiraSchemaProvider.getSchema:27
  at com.atlassian.rm.common.persistence.ActiveObjectsMediator.getSchema:34
  at com.atlassian.rm.common.persistence.EmptyActiveObjectsRelationalPathBase.<init>:36
  at com.atlassian.rm.common.persistence.EmptyActiveObjectsRelationalPathBase.<init>:25
  at com.atlassian.rm.common.persistence.ActiveObjectsRelationalPathBase.<init>:21
  at com.atlassian.rm.jpo.core.issuesource.schema.QIssueSource.<init>:27
  at com.atlassian.rm.jpo.core.issuesource.schema.QIssueSourceFactory.table:23
  at com.atlassian.rm.jpo.core.issuesource.sql.QueryDslIssueSourcePersistence.addIssueSourcesTransactional:121
  at com.atlassian.rm.jpo.core.plan.DefaultPlanService.lambda$null$1:251
  at com.atlassian.rm.common.persistence.transaction.Registry.run:35
  at com.atlassian.rm.jpo.core.plan.DefaultPlanService.lambda$createPlan$4:247
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler.inTransaction:111
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler.inNewTransaction:99
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler.inNewTransaction:89
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler.lambda$inDatabaseTransaction$3:69
  at com.atlassian.rm.common.persistence.DefaultDatabaseProvider.lambda$run$0:24
  at com.atlassian.rm.common.persistence.env.JiraDatabaseProvider.lambda$execute$0:34
  at com.atlassian.rm.common.bridges.jira.persistence.JiraDatabaseProviderBridge710.execute:59
  at com.atlassian.rm.common.persistence.env.JiraDatabaseProvider.execute:34
  at com.atlassian.rm.common.persistence.DefaultDatabaseProvider.run:24
  at com.atlassian.rm.common.persistence.transaction.TransactionHandler.inDatabaseTransaction:68
  at com.atlassian.rm.jpo.core.plan.DefaultPlanService.createPlan:227
  at com.atlassian.rm.jpo.core.plan.jobs.PlanCreationJob.run:21
  at com.atlassian.rm.jpo.core.plan.jobs.PlanCreationJob.run:8
  at com.atlassian.rm.jpo.env.threading.AbstractTranslatedLongRunningTaskProvider$1.run:25
  at com.atlassian.rm.jpo.env.threading.JiraLongRunningExecutorRegistry$1$1.run:48
  at com.atlassian.rm.common.bridges.jira.threading.LongRunningExecutorServiceBridge710.lambda$execute$0:104
  at com.atlassian.rm.common.bridges.jira.threading.JiraSafeThreadService.lambda$execute$0:47
  at java.util.concurrent.FutureTask.run:266
  at java.util.concurrent.ThreadPoolExecutor.runWorker:1149
  at java.util.concurrent.ThreadPoolExecutor$Worker.run:624
  at java.lang.Thread.run:748

===============
=== Request ===
===============

URL: /rest/jpo/1.0/plans/async/d2c838c6-92c1-4cc9-9937-7a3092de4100?_=1606074757756
Type: GET
Status: 500
Data: undefined


===================
=== Plugin Info ===
===================

Plugin build: 3.29.2

===================
=== System Info ===
===================

Jira Version: 8.13.1
Agile Version: Not present

[Daniel Ebers · Accepted solution]

Hi angga,

did you also make sure the database user has the REFERENCES permission to the database?
I am just asking because this is a common source of errors on MySQL 5.7 when not given.

Apart from that there has been a similar thread with some suggestions on how to fix.

Have you already had the chance to go them through?

Regards,
Daniel

[angga]

hi daniel

as your suggestion on my other post, now it works, i dont have to create new blank database and migrate

big thanks

angga