Oracle Database java.io.IOException: Disc quota exceeded

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs 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

Symptoms

JIRA throws a lot of fail-to-process messages for the incoming mail handler. The following appears in the atlassian-jira.log:

1 2 3 4 5 6 log4j:ERROR Failed to flush writer, java.io.IOException: Disc quota exceeded 2014-05-27 20:22:28,195 localhost-startStop-1 INFO [core.entity.jdbc.DatabaseUtil] Database Product Name is Oracle 2014-05-27 20:23:10,125 localhost-startStop-1 INFO [atlassian.jira.startup.DatabaseLauncher] Database transactions enabled: true 2014-05-27 20:23:10,136 localhost-startStop-1 INFO [atlassian.jira.startup.DatabaseLauncher] Using JIRA's default for database transaction isolation level: 2 2014-05-27 20:23:10,199 localhost-startStop-1 INFO [atlassian.jira.startup.JiraStartupLogger]

Cause

The allocated space for Oracle database has hit its limit, or no more disk space available for the allocated JIRA directory.

Workaround

  • Based on this article, Oracle - Disc quota exceeded, it seems that you can try to delete files to bring disk usage under the limit, or

  • Server Administrator can use the edquota(1M) command to increase the user's disk limit

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.