Changing Platform Database

This section describes how to change the Platform database. The new database can be of the type Oracle, PostgreSQL or SAP HANA.

Note!

Changing the database will cause the stored data to be lost.

This includes:

System log messages
Duplicate Batch processing data
Archiving data
Error Correction System data
User Access data (deprecated and configurable with Platform property)
System Statistics
Alarm data
Group Server data
License data
Workflow transactions and workflow states

Migration of the data listed above is possible, however the method for this is outside the scope of this document.

Follow these steps to change the Platform database type to an Oracle, PostgreSQL or SAP HANA database.

Create a properties file for the new database. This file contains the database related properties that are available when you install.
```
$ mzsh mzadmin/<password> db-scripts create-properties \
--properties-file <properties file>
```
Update the properties that are applicable for the new database type. For further information about the properties in this file, see Properties for Oracle, Properties for PostgreSQL or Properties for SAP HANA in the Installation Instructions.

Extract the database scripts that are required to create the new database.

$ mzsh mzadmin/<password> db-scripts extract --output-directory <db script directory> \
--properties-file <properties file>

When the database and are not installed on the same machine (the database may be installed on any machine within the network), you need to transfer the database definition files.
Create the new database.
For an Oracle database, follow the steps in Oracle Database Creation.
For a PostgreSQL database , follow the steps in PostgreSQL Database Creation.
For a SAP HANA database, follow the steps in SAP HANA Database Creation.
Disable all workflow groups from the Execution Manager in Desktop, or by entering an mzsh command, for example:
```
$ mzsh mzadmin/<password> wfgroupdisable \*
```
Note!

If you use the wfgroupdisable command, make sure that you enable all system tasks again when you are done.
Stop all batch workflows and let them finish execution.
Shut down all connected Desktops.
If you want to see which Desktops that are connected, you can use the following command:
```
$ mzsh mzadmin/<password> pico -view
```
Set up the connection to the new database.
For Oracle:
```
$ cd ./scripts/system-configure
$ ./oracle.sh
```
For PostgreSQL:
```
$ cd ./scripts/system-configure
$ ./postgresql.sh
```
For SAP HANA:
```
$ cd ./scripts/system-configure
$ ./saphana.sh
```
When the saphana.sh script is launched without any parameters, it will return a list of expected parameters, an example command output is the following:
```
<host> <port> <username> <password> <dbname> <SAP HANA JDBC driver dir>
```
The user needs to specify the mandatory parameters such as the SQL port where the tenant database is listening. The <dbname> field indicates the tenant name, while the <SAP HANA JDBC driver dir> is the name of the directory where the ngbc.jar file is stored.
Restart the platform.
```
$ mzsh restart platform
```
Start all ECs that were previously shut down.
```
$ mzsh startup <ec names> 
```
Enable the workflow groups.