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

Database migration fails from hsql to SQLServer 2012

C L
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 5, 2019

Hi All,

I'm having trouble migrating to SQLServer 2012 database.  I created a new database and crucible is able to connect but every time i try to "Save & Migrate" it is failing on create tables script C:\Atlassian\fecru-4.7.0\sql\SQLSERVER2008\schema\tables_107.sql. 

I have already made sure that my database uses collation set as Latin1_General_CS_AS and enabled snapshot mode by running 

ALTER DATABASE crucible
   SET READ_COMMITTED_SNAPSHOT ON;

I have tried to setup crucible fresh again and do the database migration step first before setting other settings but it is still failing on line "problem with create tables script".  I don't know what else I can try to resolve this. This is the log:

 

Started
Starting ActiveObjects backup...
* Backing up Database Information
* Backing up Table Definitions
** Table count: 9
* Backing up Tables
** Backing up 'AO_2913F5_COMMENT_ISSUE'
** Backing up 'AO_38321B_CUSTOM_CONTENT_LINK'
** Backing up 'AO_4789DD_HEALTH_CHECK_STATUS'
** Backing up 'AO_4789DD_PROPERTIES'
** Backing up 'AO_4789DD_READ_NOTIFICATIONS'
** Backing up 'AO_4789DD_TASK_MONITOR'
** Backing up 'AO_8219D4_COMMIT_HOOK_CONFIG'
** Backing up 'AO_A0B856_WEB_HOOK_LISTENER_AO'
** Backing up 'AO_B434B9_WEB_HOOK'
ActiveObjects backup completed!
Creating table definitions...
Problem with create tables script C:\Atlassian\fecru-4.7.0\sql\SQLSERVER2008\schema\tables_107.sql
Database migration failed: com.cenqua.crucible.hibernate.CruDBException: Problem with create tables script C:\Atlassian\fecru-4.7.0\sql\SQLSERVER2008\schema\tables_107.sql

1 answer

0 votes
C L
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 8, 2019

I found out the root cause was due to the permissions to the database. Setting the database user account permissions user mapping to db_owner and server role to bulkadmin resolved this issue.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events