Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

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.

  1. 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>
  2. Update the properties that are applicable for the new database type. For further information about the properties in this file, see /wiki/spaces/MD82/pages/3768342, /wiki/spaces/MD82/pages/3768344 or /wiki/spaces/MD82/pages/3786555 in the /wiki/spaces/MD82/pages/3768324. 

  3. 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>

  4. 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.


  5. Create the new database.

    For an Oracle database, follow the steps in /wiki/spaces/MD82/pages/3768354 in the /wiki/spaces/MD82/pages/3768324.

    For an Oracle database in Amazon Web Services, follow the steps in /wiki/spaces/MD82/pages/3768366 in the /wiki/spaces/MD82/pages/3768324.

    For a PostgreSQL database , follow the steps in /wiki/spaces/MD82/pages/3768387 in the /wiki/spaces/MD82/pages/3768324. 

    For a SAP HANA database, follow the steps in /wiki/spaces/MD82/pages/3768393 in the /wiki/spaces/MD82/pages/3768324.

  6. 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.

  7. Stop all batch workflows and let them finish execution.

  8. Shut down all connected Desktops.

  9. If you want to see which Desktops that are connected, you can use the following command:

    $ mzsh mzadmin/<password> pico -view

  10. Shut down all EC/ECSAs.

    $ mzsh shutdown platform <ec name> <ecsa name>

  11. 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

  12. Restart the platform. 

    $ mzsh restart platform

  13. Start all EC/ECSAs that were previously shut down.

    $ mzsh startup <ec names> <ecsa names>

  14. Enable the workflow groups.

  • No labels