Migrate from Serena Runtime to PostgreSQL

This section describes how to install and migrate to PostgreSQL.

Install your own PostgreSQL

Dimensions CM supports any commercial or open-source PostgreSQL distribution.

For example, you can download PostgreSQL from:

EDB Postgres

https://www.enterprisedb.com/downloads/postgres-postgresql-downloads

PostgreSQL

https://www.postgresql.org/download

For details about supported PostgreSQL versions, see the Support Matrix.

Note:

PostgreSQL installation steps: https://wiki.postgresql.org/wiki/Detailed_installation_guides
Check that "large object" support is enabled. For example, on SUSE Linux Enterprise Server, install the following:
- postgresql10-server-10.0-1.1
- postgresql10-contrib-10.0-1.1 (for the LOB support)
Check the kernel parameters:
- Shared Memory (shmmax and shmall)
- Ulimit (max processes, open files count etc)
Further information: https://www.postgresql.org/docs/current/static/kernel-resources.html?

Migration Steps

Follow these steps to migrate from the Serena-Supplied Runtime to PostgreSQL. These steps may differ if your environment has multiple machines.

Back up your existing RDBMS database using database tools. See the Administration Guide.
Back up item libraries using operating system tools.
Upgrade your current Dimensions CM system to the latest version. See Upgrade Dimensions CM.
Check that NLS_LANG matches your database character set, for example:

export NLS_LANG=AMERICAN_AMERICA.AL32UTF8

Export the PCMS_SYS schema from Oracle using the dmdba export facility, for example:

Copy code

dmdba --noschemacheck
 pcms_sys/<pcms_sys_password>@<dsn> export_dm_sys
 /EXPORT_FILE="/dumps/pcms_sys_export.sql"

Export the base database from Oracle using the dmdba export facility, for example:
Copy code
```
dmdba system/<system password>@<dsn> export_base_tables
/EXPORT_FILE="/dumps/export.sql"
/basedb=cm_typical
/target=postgresql
```
Repeat this process for each database that you want to migrate.

Export the OpenText PulseUno database from Oracle, for example:

Copy code

dmdba --noschemacheck system/<system password>@<dsn>
  export_pulse_tables
  /EXPORT_FILE="/dumps/pulse_export.sql"
  /dbname=pulse
  /target=postgresql

Uninstall your Dimensions CM server. See Uninstall OpenText Dimensions CM.
Install PostgreSQL.
Install the latest Dimensions CM server with PostgreSQL. Use your own PostgreSQL or the one bundled with the installer. See Install OpenText Dimensions CM.
Check that all processes, including PulseUno, have started:
- OpenText Common Tomcat
- Dimensions CM listener
Stop both of these services.
Drop the newly created base database:
Copy code
```
dmdba postgres/<password>@<dsn>
DLDB cm_typical
```
You only need to drop the cm_typical database if you are migrating it from Oracle to PostgreSQL.

Prepare the PulseUno database to receive your PulseUno export file. Run:

Copy code

dmdba postgres/<password>@<dsn> grant_pcms_sys pulse
dmdba --noschemacheck pulse/<pulse password>@<dsn>
  truncate_pulse_tables

Import the PCMS_SYS export file that you exported earlier:

Copy code

dmdba --noschemacheck
  pcms_sys/<pcms_sys_password>@<dsn>
  @/dumps/pcms_sys_export.sql

Import the base databases. Repeat this process for each database that you want to import.

Copy code

dmdba postgres/<password>@<dsn>
crdb cm_typical
  /toolman=dmsys
  /import="/dumps/export.sql"
  /installviews

Import the PulseUno export file, for example:

Copy code

dmdba --noschemacheck pulse/<pulse password>@<dsn>
  @/dumps/pulse_export.sql

Generate statistics for the imported databases:

Copy code

dmdba postgres/<password>@<dsn>
connect <base database name>
STATISTICS COMPUTE

Restart Dimensions CM.

Note:

PulseUno chains that you imported with the base database may not run as scheduled. Edit each chain and reconfigure its schedule.
If you migrate to a different machine, or change the database connection string, you must update all configuration and administration settings, for example:
- listener.dat and other configuration files.
- OpenText Dimensions CM server name and base database in PulseUno.
- Item library server name in the Administration Console.
Review your custom command line scripts, API programs, and web service integrations for any database specific tools and settings. For example, if you are running SQL*Plus, use the PostgreSQL interactive terminal instead.