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 from 6.2 to 7.2, displays 6.2 login credentials

SA-22359

Summary



After an upgrade from PRPC 6.2 SP2 to Pega 7.2, including a schema split, the engineer who was conducting the upgrade was attempting to follow the additional steps to perform the Optimize Schema in order to remove duplicate tables.

However, when they navigate to Designer Studio > System > Database they could see no Optimize Schema option.

The engineer had already confirmed that their prconfig.xml contained the following entry:


<env name="database/AutoDBSchemaChanges" value="true" />
 


Error Messages



Not Applicable.

Steps to Reproduce



Not Applicable.


Root Cause



The system will use the pxViewAndOptimizeSchema When rule to determine whether the Optimize Schema landing page should be displayed.
This in turn will check for the database/AutoDBSchemaChanges value and the ViewAndOptimizeSchema privilege to decide whether to display that option.

Further examination of the ViewAndOptimizeSchema privilege showed that this had a privilege level of 2 for the role that was associated with the operator.
However, the current Production Level was set to 3. Hence disqualifying that landing page from being displayed.

Resolution



In order to overcome the problem the Production Level was temporarily changed to two and the system restarted.
After this the Optimize Schema landing page was available.

 

Published May 4, 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