Database table Need's exclude while moving to another database.

[tousif shaikh]

Hi all,

we are moving our Database and Infrastructure for confluence application.
we are moving Database from Oracle to PostgreSQL Database.
please let me know your suggestion's what are the Table which we should not include when importing database dump's. for e.g indexQueEntries or
AO table's which are Generated by confluence application.

regard's

tousif shaikh.

[Nic Brough [Adaptavist] · Accepted solution]

For what it's worth, I'm with Rahul and Andy on this - dropping any tables out is asking for failure. You need to understand what they all are before you try anything like this, and even then it's likely that the simple rule is that you should take everything, exactly as it is now.

[Rahul Aich [Nagra]]

Hi Tousif

I would not recommend being selective in migrating the database tables.

If i were you i would migrate the entire database schema (all tables). if at all any table is generated by confluence itself then it will be overwritten anyway.

Rahul

[tousif shaikh]

hey thank's rahul.

last time we had whole table data migration we found lot of issues while restarting confluence application from index table.

please refer below link.

https://answers.atlassian.com/questions/234134/confluence-indexing-throw-error-at-restart

[Andy Brook (DEV)]

I agree with Rahul, migration of selected tables is just asking for brain damage in your confluence data. AO data storage is per-plugin so unless you know intimately every plugins schema usages, not migrating them is effectively going to result in the relateed plugin failing, so don't do that.

If you are migrating databases and per-space export/import is not an option... then, you must do a full schema migration, it is non trivial. I have done this once from DB2/win32 to Postgresql/linux, the tool for the job was Talend.

[tousif shaikh]

thank you andy.