nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA backup service error

Ash_kida48

Hi All,

I'm seeing this errors in my logs

ERROR ServiceRunner Backup Service [service.services.export.ExportService] An exception while running the export service "Backup Service": Could not find column 'APPLICATION_KEYS' in previously parsed query!
java.lang.IllegalStateException: Could not find column 'APPLICATION_KEYS' in previously parsed query!

ERROR ServiceRunner Backup Service [atlassian.jira.service.ServiceRunner] An error occured while trying to run service 'Backup Service'. null

JIRA service failed to backup and moving all the backups to the corrupted folder. Any suggestions on this.

This is the service we have set up in jira.

Name/Class: Backup Service
com.atlassian.jira.service.services.export.ExportService

Properties: USE_DEFAULT_DIRECTORY: true

Delay(mins): 720

JIRA server 5.1.6 with Oracle 11g.

TIA!!

Accepted answers

somethingblue

Hi Ash,

There is a knowledge base article that may help with this titled Database operation in JIRA fails with "Could not find column <column_name> in previously parsed query" and it lists some possible causes:

Causes

Two JIRA instances are connecting to the same database, but individual database schemas. Each individual JIRA instance requires its own database on the database server. See more on our documentation for steps on connecting JIRA to Microsoft SQL Server:
If using Oracle database, granting additional permission (such as dba or 'SELECT ANY TABLE') to the user that JIRA uses to connect with the database could cause the same problem as well.
Also in Oracle, please check if the user JIRA is configured to connect the database has permissions as described here and also access permission to the tablespace.
This could also be caused by two database schemas being referenced in the same database. If this is the case, please follow the steps in this KB article to alter the schema directly in the database.

Please try the steps in Database operation in JIRA fails with "Could not find column <column_name> in previously parsed query and let me know if that helps. If it does not, let us know and we'll go from there.

Cheers,

Branden

All comments

somethingblue

Hi Ash,

Causes

Two JIRA instances are connecting to the same database, but individual database schemas. Each individual JIRA instance requires its own database on the database server. See more on our documentation for steps on connecting JIRA to Microsoft SQL Server:
If using Oracle database, granting additional permission (such as dba or 'SELECT ANY TABLE') to the user that JIRA uses to connect with the database could cause the same problem as well.
Also in Oracle, please check if the user JIRA is configured to connect the database has permissions as described here and also access permission to the tablespace.
This could also be caused by two database schemas being referenced in the same database. If this is the case, please follow the steps in this KB article to alter the schema directly in the database.

Cheers,

Branden

Ash_kida48

@somethingblue thanks for your reply right now there are two schemas running on our database server.

One schema has JIRA 5.1.6 and another schema has JIRA 7.3.8 running on the Oracle 11g server.

Recently we upgraded our JIRA dev to 7.3.8.

Ash_kida48

@somethingblue yesterday after posting this question after few minutes our JIRA went down with these errors.

Caused by: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1

ORA-01653: unable to extend table SYS.AUD$ by 8192 in tablespace SYSTEM

ORA-02002: error while writing to audit trail

ORA-00604: error occurred at recursive SQL level 1

ORA-01653: unable to extend table SYS.AUD$ by 8192 in tablespace SYSTEM

So our database administrator truncated SYS.AUD table and restarted JIRA that worked fine.

But we still have the same issue with the backup service error. Renaming schema name is the solution for it?

Thank you.

Ash_kida48

Thank for the information @somethingblue deleted our JIRA dev schema

as recommended by Atlassian. That started our Jira backup service.

Each JIRA instance must have its own database on the database server. Running multiple JIRA instances against the same database, although using individual schemas will not work.

https://confluence.atlassian.com/jirakb/database-operation-in-jira-fails-with-could-not-find-column-column_name-in-previously-parsed-query-315326688.html

Ash_kida48

This explains more

https://community.atlassian.com/t5/Jira-questions/JIRA-instance-Oracle-DB-setup/qaq-p/712356#M232727

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-server

backup