Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,555,439
Community Members
 
Community Events
184
Community Groups

org.postgresql.util.PSQLException: ERROR: relation "AO_B9A0F0_APPLIED_TEMPLATE" does not exist

we are unable to setup JIRA, we have this error when crating new project :

org.postgresql.util.PSQLException: ERROR: relation "AO_B9A0F0_APPLIED_TEMPLATE" does not exist

 

6 answers

Thanks - We faced the same issue while trying to hook up an Azure postgresql db service to a Jira instance

It is related to this issue: https://jira.atlassian.com/browse/JRASERVER-64886

We used 

"ALTER DATABASE <database_name> SET search_path TO schema1,schema2;"

 

The search_path parameter sets the order in which schemas are searched using non-qualified object names.

Hi Jacobsen,

I think I am in the same boat for now, the version of Postgresql I am using is 14.1.

Once I created the new database, I created a new schema and used the workaround to set the search_path to it, but issue kept still.

Finally, the solution is in the configuration files of Postgresql.

You need to give this inofrmation :

SET search_path TO myschema,public;

 

Thank you.

This fixed my problem installing Jira 8.2.1 with Azure Database for Postgresql.

I had to use a non-default schema because Azure was adding 2 PostgreSQL extensions, which caused Jira to think the DB was not empty.

I couldn't easily remove the extensions via my Terraform modules.

So I changed my Terraform module to set the new schema name to be the same as the jiradbuser user name (default search path in PostgreSQL is "$user", public).

This fixed the "org.postgresql.util.PSQLException: ERROR: relation "AO... does not exist" errors.

0 votes
Vasiliy Zverev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jan 31, 2017

First of all - AO tables are for plugins. Since first to do is find out which plugin this table belongs to.

Go to admin panel/System/advanced and select "Plugin Data Storage". Find this table here and get plugin it belongs to.

We have a valid licence for JIRA SOFTWARE.

How can we see if this plugin is valid for this lcence ? we have just found a list of plugins...

how we can see the correct licence version ? I've just à Jira software licence and nothing else.
We use the last on 7.3 bin version 

0 votes
Vasiliy Zverev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jan 31, 2017

OA tables are for plugins. Go to admin panel / System / Plugin data storage. Here you can find plugin which uses this table. 

Then: 

  1. check that plugin version is compatible with JIRA version
  2. you have valid licance for plugin

Other option - database is not supported by JIRA. Here is list of supported databases: https://confluence.atlassian.com/adminjiraserver072/supported-platforms-828787550.html

 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events