Question

Pega Import Tool- Few schema changes aren't getting applied to higher env

Hi All,

We are trying to use Pega's automatic Schema changes push from one env to another using the Import Tool. The product file has the expected schema changes.
However, it is observed that some of the DB changes are not being applied to higher environment. Few of these are listed below. Is this a Pega limitation, how can we fix this?

1. Drop column script is not working when deployed to higher env.
2. 'Byte' is getting changed to 'Char' in higher env.
3. Change of column data types isn't being applied to DBs in higher env.

Also, if someone could list what all scenarios will not work with Pega AutoDBSchemaChanges.
We have verified creation of table, alter table with column addition, creation of index, constraints are working.

Thanks!
Bhagyashree

***Edited by Moderator Marissa to update platform capability tags****

Comments

Keep up to date on this post and subscribe to comments

September 20, 2019 - 1:19pm

Hi Bagyashree,
Check the value of the SchemaImport privledge in the Access of Role to Object in the context you are using. This may be set to something other than 5 in which case it will not import.

Also in what context is this import being done?

Regards,
Jim