JIRA startup or runtime error due to ORA-00257 archiver error. Connect internal only, until freed
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 doesn't start or has a runtime error. The following text appears in the atlassian-jira.log or catalina.out:
1
Cannot create PoolableConnectionFactory (ORA-00257: archiver error. Connect internal only, until freed.)or just
1
ORA-00257: archiver error. Connect internal only, until freedCause
The ORA-00257 error is raised when the Oracle archive destination disk or volume is full.
Resolution
Check the available space on the filesystem where the Oracle archive redo logs are stored. This can be done with the following SQL query:
1show parameter log_archiveIf the disk is full, try to free space using any of the following methods:
compressing older files
removing older archives
adding more storage
This archived thread on Oracle community forums discusses the troubleshooting in detail.
Was this helpful?