Can't use an oracle database

Jeroen Wyseur October 21, 2012

When I try to use an oracle database I get the following error during creation of the schema:

The Hibernate SessionFactory could not be created. The database schema may not have been correctly applied

Hide details

The Hibernate SessionFactory could not be created. The database schema may not have been correctly applied

com.atlassian.stash.internal.migration.DefaultMigrationService.createSessionFactory(DefaultMigrationService.java:514)

com.atlassian.stash.internal.migration.DefaultMigrationService.startMigration(DefaultMigrationService.java:937)

com.atlassian.stash.internal.migration.DefaultMigrationService.migrate(DefaultMigrationService.java:163)

...

Missing column: is_local in CONFLUENCE.CWD_GROUP

org.hibernate.mapping.Table.validateColumns(Table.java:276)

org.hibernate.cfg.Configuration.validateSchema(Configuration.java:1343)

org.hibernate.tool.hbm2ddl.SchemaValidator.validate(SchemaValidator.java:139)

...

However the tables are created in the schema. With a local database everything seems to work and we have JIRA and Confluence working with the same database.

Oracle version 11.2.0.1.0, normally connecting through LDAP but I looked up the exact host since I can't use ldap with Stash.

2 answers

0 votes
LeonardoL
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.
October 23, 2012

Hey Jeroen,

I'm sharing the resolution here for future references of community users, ok?

"Apparently if you give the stash user the dba role, it doesn't work as it should.
Removing the DBA role (keeping connect and resource) solved the problem."

Cheers,

Leonardo.

0 votes
Jeroen Wyseur October 23, 2012

Ok for me. That was what I intended with posting the resolution.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events