Skip to main content
This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.
LinkedIn
Copied!

Table of Contents

Interaction History tables are not upgraded after migration

Some application processes (for example data flow runs) might fail after migrating to a newer Pega Platform™ version as a result of missing tables or columns in the Interaction History schema.   

Cause

The root cause of the issue is that the Pega Platform upgrade process does not include externally hosted Interaction History schema.

Solution

Extend the existing Interaction History tables by adding new columns or dimension tables. By expanding the tables, you ensure that the updated Interaction History schema corresponds to the format that is expected by Pega Platform.

Extending Interaction History

These steps provide sample scripts for extending the Interaction History schema in a Postgres database with columns or dimension tables. For other database types, customize the scripts appropriately.

When you upgrade your application through multiple product versions, run the script for each version up to the target version. For example, when upgrading from Pega 7.2.2 to 7.4.0, first run the 7.3.0 to 7.3.1 script, and then the 7.3.1 to 7.4.0 script
Upgrading from Pega 7.2.2 to 7.3.0

No actions required.

Upgrading from Pega Platform 7.3.0 to 7.3.1

Create new tables and columns to ensure that your Interaction History schema is compatible with the Pega Platform 7.3.1 standard.

  1. Create the pr_data_ih_dim_journey dimension table by running the following script:
    CREATE TABLE <external_schem_name>.pr_data_ih_dim_journey (
    
    pzid numeric(19) NOT NULL,
    
    pxcreatedatetime timestamp NOT NULL,
    
    pyjourney varchar(255) NULL,
    
    pystep varchar(255) NULL,
    
    pystage varchar(255) NULL,
    
    CONSTRAINT pr_data_ih_dim_journey_pk PRIMARY KEY (pzid)
    
    );
    
  2. Add the pzjourneyid column in the pr_data_ih_fact table by running the following script:
    ALTER TABLE <external_schema_name>.pr_data_ih_fact
    
    ADD COLUMN pzjourneyid numeric(19);
    
  3. Add the pylabel column in the pr_data_ih_dim_action table by running the following script:
    ALTER TABLE <external_schema_name>.pr_data_ih_dim_action
    
    ADD COLUMN pylabel varchar(255);
    
Upgrading from Pega Platform 7.3.1 to 7.4.0

Create a new column to ensure that your Interaction History schema is compatible with the Pega Platform 7.4.0 standard.

  • Add the pysubjecttype column in the pr_data_ih_dim_customer table by running the following script:
    ALTER TABLE <external_schema_name>.pr_data_ih_dim_customer
    
    ADD COLUMN pysubjecttype varchar(255);
    
Upgrading from Pega Platform 7.4.0 to 7.4.1

No actions required.

Upgrading from Pega Platform 7.4.1 to 8.1.0

No actions required.

Upgrading from Pega Platform 8.1.0 to 8.2.0

No actions required.

Upgrading from Pega 8.2.0 to 8.3.0

No actions required.

Did you find this content helpful?

Related Content

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us