JIRA has loss of functionality and ORA-00600 error is in the logs

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

It can affect different functionalities in JIRA a message similar as the following appears in the atlassian-jira.log:

][name,test][creator,null] (SQL Exception while executing the following:UPDATE jiraworkflows SET workflowname=?, creatorname=?, DESCRIPTOR=?, ISLOCKED=? WHERE ID=? (ORA-00600: internal error code, arguments: [25027], [7], [0], [], [], [], [], [], [], [], [], []
))
	at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.store(DefaultOfBizDelegator.java:357)
	at com.atlassian.jira.workflow.OfBizWorkflowDescriptorStore.saveWorkflow(OfBizWorkflowDescriptorStore.java:95)
	at com.atlassian.jira.workflow.CachingWorkflowDescriptorStore.saveWorkflow(CachingWorkflowDescriptorStore.java:129)
	at com.atlassian.jira.workflow.JiraWorkflowFactory.saveWorkflow(JiraWorkflowFactory.java:61)

Cause

This is the generic internal error number for Oracle program exceptions. It indicates that a process has encountered a low-level, unexpected condition (source). Causes of this message include:

  • Timeouts
  • File corruption
  • Failed data checks in memory
  • Hardware, memory, or I/O errors
  • Incorrectly restored files

Resolution

Contact Oracle support to further investigate the cause of this issue. Additionally, we have reports that moving the data to a different table space can potentially solve this issue. Example:

alter table JIRA.JIRADRAFTWORKFLOWS move lob (DESCRIPTOR) store as (tablespace JIRA_DATA);
Last modified on Mar 30, 2016

Was this helpful?

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