Jira application does not start up - missing chunk number 0 for toast value 3995689 in pg_toast

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

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

When a user tries to start the Jira application, it does not start up and throws an error. 

Environment

  • Jira Software v8.x and above.

Diagnosis


On reviewing the Atlassian-jira.log,  "ERROR: missing chunk number 0 for toast value 3995689 in pg_toast_2619 " observed:

Caused by: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, JOB_ID, JOB_RUNNER_KEY, SCHED_TYPE, INTERVAL_MILLIS, FIRST_RUN, CRON_EXPRESSION, TIME_ZONE, NEXT_RUN, VERSION, PARAMETERS FROM public.clusteredjob WHERE JOB_ID=? *(ERROR: missing chunk number 0 for toast value 3995689 in pg_toast_2619)
*	at org.ofbiz.core.entity.jdbc.SQLProcessor.executeQuery(SQLProcessor.java:533)
	at org.ofbiz.core.entity.GenericDAO.createEntityListIterator(GenericDAO.java:881)
	
	... 33 more
Caused by: org.postgresql.util.PSQLException: ERROR: missing chunk number 0 for toast value 3995689 in pg_toast_2619	at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2553)
	at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2285)
	at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:323)
	at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:473)
	
	... 38 more
2022-02-28 11:53:28,392+0530 JIRA-Bootstrap ERROR      [c.a.jira.health.HealthChecks] We couldn't start JIRA



Cause

  • Corrupted index on tables/data corruption in TOAST tables. corruption in your TOAST tables.

Solution

The error does seem to indicate that something is not right on the database side. please refer to:




Last modified on Jun 22, 2023

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.