Upgrade PostgreSQL Schema

If required, before a Prognosis Server upgrade, it may be required to upgrade the PostgreSQL database schema for internal tables that are used by various features. These include, but not limited to

  • High Availability
  • Call Recording Assurance

When instructed, follow these steps to upgrade the database schema on the Prognosis Server. This should be performed prior to upgrading the software otherwise it may be likely that the database will not be compatible with the newer version. 

In a HA environment, it is only required to upgrade the PostgreSQL schema on the Active server. All changes will be synchronized to the Passive server automatically.

Upgrade Procedure

Download the latest 'Pre-upgrade Prognosis 11.9' bundled zip file from the IR Community website by signing on and then going to:

Software → Downloads → Prognosis 11.9 Installer & Patches

Unzip the pre-upgrade bundle into a temporary folder <path-to-temp-folder>.

Open a Command Prompt with Administrative privileges.

Change to the configuration folder and execute the irpgmigrate tool:

> cd <Prognosis_Home>\Server\Configuration
> <path-to-temp-folder>\irpgmigrate\irpgmigrate.exe "<Prognosis_Home>\PostgreSQL\postgres" <path-to-temp-folder>

This will configure and upgrade the PostgreSQL database to the latest version

Troubleshooting

Password Authentication Failure

- Upgrade PostgreSQL schema...

[ERROR] AssertionError [ERR_ASSERTION]: ifError got unwanted exception: password authentication failed for user "prognosis"

If you receive this error it is because the PQL:prognosis entry in the PASSWORDS Configuration for PostgreSQL is incorrect. Re-enter the correct credentials in the PASSWORDS Configuration and try again.

ECONNREFUSED

- Upgrade PostgreSQL schema...

[ERROR] AssertionError [ERR_ASSERTION]: ifError got unwanted exception: connect ECONNREFUSED 127.0.0.1:5432

If you receive this error it is because the PrognosisPostgreSQL service is stopped or the PostgreSQL port has been changed. Read Changing the PostgreSQL Port, then restart the PrognosisPostgres service and try again.

Provide feedback on this article