Share this page

# Upgrade PPM - PostgreSQL

You can use the `sh kUpgrade.sh` command to upgrade PPM with a PostgreSQL database. This topic provides detailed steps to upgrade PPM with a PostgreSQL database to the latest version.

To upgrade PPM with a PostgreSQL database:

1. (Optional but highly recommended) Back up your database and license.conf file.

2. Extract the ppm-<PPM version>-upgrade-pg.zip package.

   The extraction creates the upgrade_<PPM version>folder, which includes the following files:

   - upgrade directory
   - bundle.zip file
   - version.txt file
   - kUpgrade.sh file

   - ppm-<PPM version>-multi-lang.jar file

3. Stop the PPM server.

4. Run the sh kUpgrade.sh command with the following commands to upgrade the PPM file system and database.

   Parameter(*Required) | Description
   --- | ---
   *`-p`, or `--ppmhome` | Available in 24.2 and later versions Required. The folder where the PPM file system is installed. Make it sure it is consistent with the `PPM_HOME` parameter in the ppm.env file during the installation.
   `-f`, or `--filesystem` | Attach this parameter if you want to upgrade the file system only.
   `-w`, or `--db-password` | Password for the PPM database user. Optional. You can enter it later.

   Tip: If you have multiple PPM nodes across multiple physical servers, you need to upgrade the file system on each server but need to upgrade the database only once.

   During the upgrade process, PPM generates the logs in the ppm-<PPM version>-upgrade-pg/logs directory. If any problems occur during the upgrade, you can check the log file for troubleshooting.

5. Start PPM in your upgraded <PPM_Home> folder.

6. To make sure the attachments, report logs, and execution logs can still be accessed by the upgraded instance, set the paths of the following parameters to the corresponding folders under the upgraded <PPM_Home> directory:

   - com.kintana.core.server.ATTACHMENT_DIRNAME
   - com.kintana.core.server.BASE_LOG_DIR
   - com.kintana.core.server.DISTRIBUTION_LOG_DIR
   - com.kintana.core.server.PACKAGE_LOG_DIR
   - com.kintana.core.server.REPORT_DIR
   - com.kintana.core.server.REPORT_LOG_DIR
   - com.kintana.core.server.REQUEST_LOG_DIR
   - com.kintana.core.server.SCRIPT_DIR
   - com.kintana.core.server.TEMP_DIR
   - com.kintana.core.server.TRANSFER_PATH
   - com.kintana.core.server.VALIDATION_LOG_DIR
   - com.kintana.core.server.WEB_CACHE_DIR

SSH2 Client Migration when upgrading to 26.2 or later

In 26.2, the SSH2 JSch client has been replaced with the Apache SSH client. When upgrading from version 25.4 or earlier to 26.2 or later, environments using SSH must be updated.

If in an existing environment the Connection Protocol is set to SSH2, or if the Transfer Protocol is set to Secure Copy 2, perform the following:

1. Go to Workbench > Environments.

2. Open the configured environment and update the following:

   - Connection Protocol: Apache SSH2.

   - Transfer Protocol: Apache Secure Copy 2.

3. Click Save.

## See also

- Install PPM with PostgreSQL

https://admhelp.microfocus.com PPM 8942
Tips to improve your search results... OpenText™ Project and Portfolio Management Help Center PPM Help 26.2-26.3 All View Local Help Center View Online Help Center Version: