Migrating Jira from Oracle to SQL Server

[Espen Sandall]

Hi, we're in the process of migrating our Jira 8.5.3 instance from Oracle 12C to SQL Server 2017, using XML export/import - as recommended here.

Our first attempt failed with an easy-to-solve case of duplicate records, as the SQL Server collation type is case-insensitive.

On our second attempt, the import process seemed to complete, but errors related to a ranking field when trying to re-index seems to confirm that the creation of one or more active objects failed during import.

Have anyone else done, or tried, a similar database migration? If so, I would appreciate very much to hear from you! :-)

And not just regarding Jira - as we plan to migrate our Confluence instance next!

Sincerely,
Espen

[Anna-BigPicture]

Hi @Espen Sandall

BigGantt connects to databases through Jira. So if Jira works properly, our plugin will work properly as well.
You can disable BigGantt before migration to ensure that nothing interferes with the process and enables it afterward.

Best, 

Anna
Softwareplant

[Espen Sandall]

Thank you Anna, for a reassuring comment! :-)

Removing the biggantt-jar file from the installed-plugins folder before starting Jira against the new database did indeed stop the upgrade tasks from being triggered (and hence no related errors).

Unfortunately, we still have not in starting up with a new SQL Server database without a major error - related to the creation of Active Objects. (There is currently some confusion regarding schema-name.) So we have not yet verified that BigGantt (or anything else) will work properly after the migration.

BR, Espen

[Anna-BigPicture]

Hello @Espen Sandall
You are welcome! Just let me know in this thread if you have any problem with BigGantt after reinstalling it. 

Best,
Anna

[Espen Sandall]

The plugin BigGantt caused problems even before the import started.

On startup against the new, empty database, a series of 'BigGantt database upgrade tasks' caused in total 3 sql execution errors.

Then, trying the import, the plugin 'Test Management 4 Jira' caused an error after import reached 90%.

Import seemed to reach 100% anyway, but was not in a usable state, as re-indexing would not start.

Does anyone know if the installed-plugins folder should be deleted before switching to the new database?
For the next attempt, we will at least remove these to plugins - and hopefully re-install them after a successful import.

ES