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

After upgrade to 7.1.5 schema conflicts found with AES tables



Admin installed PRPC 7.1.4 and AES 7.1 on top of it. Everything was working fine and monitored PRPC instances. Upgraded to PRPC 7.1.5 without issues. However, per the PRPC schema report there are many schema changes to the existing AES tables. If Admin does a straight installation of AES 7.1 on top of PRPC 7.1.5 the table structure of the AES tables matches what we would get from installing it on 7.1.4.

Error Messages


Steps to Reproduce

1. Install AES 7.1 on PRPC 7.1.4
2.  Update to PRPC 7.1.5 
3. Run the PRPC Schema Report
4. Select 'ViewAndDownloadSchema' from 'Upgrade Data Tables' section

Root Cause



The explanation for this behavior is as follows: The PRPC Schema Report is recommending these columns be added to these tables based on some of the other properties that are already exposed on these tables.  However, AES will work fin as it is currently shipped.  It is not necessary to run the DDL that is being generated by the PRPC Schema Report.

Suggest Edit

Published June 12, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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