-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
None
-
17
-
Steps to reproduce:
SQL Server
- Create a database 'atlassian'
- Create a schema name 'stash' in the database
- Create a user 'stash' with the default schema 'stash'
- Connect Stash server with SQL server database 'atlassian'
All the tables are created in the default schema 'dbo' except for AO tables created in schema 'stash'
Oracle
- Create a database user 'stash'
- Grant all the permission to the user 'stash' on the schema 'stash'
- Grant another access permission to the user 'stash' on the schema 'crowd' (schema 'crowd' has been used by Crowd application)
- Migrate Stash database from HSQLDB to Oracle through the UI
It will fail with the following error:2014-02-07 12:09:03,235 ERROR [http-bio-7990-exec-7] 728x27x0 jv58e6 10.123.16.180 "POST /setup HTTP/1.1" c.a.s.i.db.DefaultDatabaseManager Failed to obtain session factory org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactoryPrototype' defined in class path resource [stash-context.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Missing column: is_allow_all in CROWD.CWD_APP_DIR_MAPPING at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1512) ~[spring-beans-3.2.5.RELEASE.jar:3.2.5.RELEASE] at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1129) ~[spring-context-3.2.5.RELEASE.jar:3.2.5.RELEASE] at com.atlassian.stash.internal.db.DefaultDatabaseManager.createSessionFactory(DefaultDatabaseManager.java:337) [stash-service-impl-2.10.1.jar:na] at com.atlassian.stash.internal.db.DefaultDatabaseManager.prepareDatabase(DefaultDatabaseManager.java:158) [stash-service-impl-2.10.1.jar:na]
it seems that Stash somehow try to use the schema 'crowd' cause the database user 'stash' have access permission to it.
- relates to
-
BSERV-9814 Upgrading fails due to "'DF_cwd_application_address_remote_address_mask' is not a constraint."
- Closed
-
BSERV-7082 PostgreSQL user default schema does not work
- Closed
-
BSERV-9135 As an admin, I want the PostgreSQL documentation to explicitly mention that the default public schema has to be used, so that the migration to a PostgreSQL is easier to follow
- Closed
-
BSERV-4482 Support Oracle usage of different schema without DDL permissions
- Gathering Interest
- is related to
-
SSP-9070 Loading...