Jira 6.1.4 install on same postgreSQL 9.3 database but different schema

Question

Hi,

Because of enterprise policies I tried to install two jira instances on same postgre database  but different schemas. At the moment when I am supposed to save admin user I get following java exception:

java.lang.RuntimeException: com.atlassian.jira.exception.CreateException: com.atlassian.crowd.exception.runtime.OperationFailedException: No Crowd Application available. at com.atlassian.jira.web.action.setup.SetupAdminAccount.doExecute(SetupAdminAccount.java:184)

Are there any special requirements for this scenario?

Thank you.

Adrian Moerchen · Answer

You may try https://confluence.atlassian.com/display/JIRA052/Using+the+JIRA+Configuration+Toolto test the connection to the correct schema.

Andy Nguyen · Answer

Hi Dorde,

May I know how everything's going? Did you manage to resolve the issue somehow? Did you discover any relationships between jira instance, db role and schema?

Is jiraProd the first instance that worked and jiraTest the second that didn't work at first? How about jiraService?

Thanks in advance!

Đorđe · Answer

I checked that with my collegues at least five times. Another interesting point is that we already have third instance running under different schema on same database, but that is upgrade from version 5.

DB Name: jiradatabase

jira instance _____ db role ________schema

jiraService    _____ jiraService _____ jiraService

jiraTest _________jiradb_________ test

jiraProd _________jiraProd _______prod

Is there maybe rule about same name for role and schema?

Thank you for your help.