Schema changes fail during Jar file import
When importing a jar file with schema changes, Pega does not automatically apply the schema changes to the database even though the database account that Pega is using has the necessary privileges and the dynamic system setting "database/AutoDBSchemaChanges" is set to true. A warning screen is displayed stating that Pega cannot automatically apply schema changes. The role is SysAdmin4.
Steps to Reproduce
1. Select Application > Distribution > Import
2. Select a jar with schema change to import
3. Select “Automatic: PRPC applies the database schema changes using the database user defined in the database configuration”
4. Warning screen is displayed stating that auto schema changes cannot be applied even though you use SysAdmin4 role, and the dynamic system setting “database/AutoDBSchemaChanges” is set to true.
The production level of the target system is 3 but the SysAdmin4 role only allows import schema changes for production level of 2 or less.
This issue is resolved by making the following change to the operating environment:
The below article provides details on the privileges needed to automatically perform schema changes within Pega.
By default, the Access of Role of Object rule for the SysAdmin4 role sets the privileges for ImportSchema to production level of 2 or less. To allow schema changes you would either need to change the production level to be 2 or less or you must change the level of the corresponding privileges in the Access of Role to Object rule for SysAdmin4 (or your own version of that rule).
If you opt to change the production level to import, then clear the conclusion cache In Memory and In Database and then restart the JVM. The other option is to not change the settings and manually create the tables in the database.
0% found this useful