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.

Support Article

BIX pr_extract_time is dropped during upgrade to Pega 7.1.7

SA-7419

Summary



You are upgrading a system that has BIX installed to Pega 7.1.7 and as part of the upgrade the pr_extract_time table is being dropped.

Error Messages



drop table pega.pr_extract_time

Steps to Reproduce



Run
    generateddl.bat --action upgrade
to get the schema changes needed for the upgrade.


Root Cause



The root cause of this problem is a backwards compatibility defect in Pegasystems’ code/rules.  Prior to Pega 7.1.7 the pr_extract_time table was created during the installation of core Pega. Starting from Pega 7.1.7 it needs to be created as part of the installation of BIX.  Since the core Pega upgrade no longer needs this table it is dropping it.

Resolution



This issue is resolved through the following Local-change: 

If you have not yet completed the upgrade, remove the dropping of this table from the generated DDL before applying it.


 If the upgrade is completed and the table has already been dropped, recreate it as part of the installation of BIX 7.1.7.  If you look in the readme in the AdditionalProducts/BIX directory you will see there is a note telling you to create these tables if they are not present.

FOLDERS:

config - Contains configuration settings for BIX connectivity and startup.
lib - Contains jar files required for BIX execution.
rulesets - Contains the Pega-BIX:06-03-01.
schema - Contains required PRPC database schema changes.

Apply them manually to create the tables pr_extract_time and pr_sys_queues_bix if not already present in PegaDATA schema.

If you would like the existing content of this table you will need to either use database tools to copy the old table and its content to your new rules schema or run the script to create the table and then manually insert the data. If you do not care about the content of the table then just run the appropriate script found in the schema directory for your database to recreate the needed tables.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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