Database Server Conversion/Migration

The MetaKarta Data Lineage, Catalog & Governance Web Application Server requires access to a Database Server for metadata storage (metadata repository) which can be PostgreSQL, Oracle, or Microsoft SQL Server. deployed on prem or cloud.

If you wish to use another database of the same platform, e.g., PostgreSQL, then you may simply backup the existing database using the platform specify data dump action and then restore to the new database.
Then, simply re-configure the application server to connect to the new database instance.

However, if you need to use a different database platform, e.g., the new database is not PostgreSQL but instead is Oracle or Microsoft SQL Server, then you should use the database migration feature available through the Setup.bat (or Setup.sh) utility. You should invoke this utility from the command line specifying the -dm (--database-migration) command line parameter. The migration will read the existing database information from the mm.conf.properties file and the new database information from the command line parameters (using the existing command line parameters: -dc -du -dw) and attempt to migrate the existing database to the new one. Once completed, the setup utility will update the mm.conf.properties with the new database connection setting.

Steps

To reduce database size and improve the performance of the migration, clean up your repository by removing obsolete or excessive model versions by performing the steps in the Manage Repository Storage Space section before beginning the migration process. See Repository Cleanup for detailed instructions.
Create a new empty database using the database setup and requirements for the new target database platform
Stop the application server
Run the following command to start the migration process: Setup.bat -dm -dc <new database connection url> -du <new database user> -dw <new database password>
After it succeeds you may simply restart the application server and it will be connected to the new database.