Jira 9.12.8 Full Reindex Stuck at 0%

Question

Hi everyone,

I’m running Jira version 9.12.8 and recently encountered an issue where Jira can no longer reindex. When I run a full reindex, it remains stuck at 0% indefinitely (even after several days).

I enabled index debugging in Logging and Profiling, and based on the logs it appears that Jira is actually processing the index. However, the progress in the UI never updates, and no errors appear in the logs.

For context, my database is Oracle. Everything worked fine with a single schema, but after importing a new schema into a new service name on the same Oracle database, reindexing stopped working.

Here are some sample lines from the log:

2025-11-22 14:35:06,596+0330 IssueIndexer:thread-41 DEBUG [c.a.j.issue.index.DefaultWorklogDocumentFactory] Indexing worklog: issueId=2607915, worklogId=4022175, version=1

2025-11-22 14:35:07,800+0330 IssueIndexer:thread-15 DEBUG [c.a.j.issue.index.DefaultCommentDocumentFactory] Indexing comment: issueId=2609228, commentId=7125365, version=6

2025-11-22 14:35:10,405+0330 IssueIndexer:thread-13 DEBUG [c.a.j.issue.index.DefaultChangeHistoryDocumentFactory] Indexing changeHistoryGroup: issueId=2609350, changeHistoryGroupId=-1, version=26

Has anyone experienced this issue or knows what might be causing it? Any help would be greatly appreciated.

Rilwan Ahmed · Answer

Hi @mahsa ah ,

Can you explain in more detail, what exactly is done when you say "For context, my database is Oracle. Everything worked fine with a single schema, but after importing a new schema into a new service name on the same Oracle database, reindexing stopped working."

Meantime,

Ensure Jira DB user has full privileges in the new service.

Ensure all tables are owned by the Jira user in that service.

Ensure dbconfig.xml correctly references the intended schema and service.

unknown · Answer

Hello @mahsa ah

You say you are using 'Jira' and your question is tagged as being for Jira Server. Is that correct, or are you actually using Jira Data Center?

Jeremy Hermes · Answer

A few thoughts:

* I would suggest that you upgrade, i.e. in a lower environment where you can reproduce the issue
There were several indexes fixes/tweaks in the past few months to 9.12 (and more importantly CVEs patched) - the latest is 9.12.29
9.12 is EOL next week though - so maybe 10.3 is better

* I don't know what a second schema would impact anything, but you want to look at the compatibility and bug fix list over last few patches
https://confluence.atlassian.com/adminjiraserver103/supported-platforms-1489806894.html is the compatibility for 10.3 :D  
* I did have a similar problem a year or two ago - we had implemented a Scriptrunner scripted custom field that was triggering on a reindex, and running a rather lengthy query on each issue that made our reindex crawl (stay at 0% for 12 hours) That was the day I learned about "isIndexAvailable()" (and where snippets might be better than a scripted field heh)

Hope this helps,
Jeremy