Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Discussion

 Nandhini Nataraj (natan)
PEGA
Principal Software Engineer - Customer Success
Pegasystems Inc.
natan Member since 2012 32 posts
PEGA
Posted: Dec 3, 2015
Last activity: Apr 6, 2018
Posted: 3 Dec 2015 6:22 EST
Last activity: 6 Apr 2018 19:26 EDT
Closed

Rule Migration Failure - incompatible data type

Rules migration failed as ‘pr_index_circumstance_def’ table has columns of bit data type. This column is exposed using the Optimize Wizard of PRPC, which was creating with the datatype as bit.



**Moderation Team has archived post**


This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

To see attachments, please log in.
Updates

Posted: 8 years ago
Posted: 3 Dec 2015 6:22 EST
Nandhini Nataraj (natan)
PEGA
Principal Software Engineer - Customer Success
Pegasystems Inc.

The column datatype has to be modified to int and then the migration \ upgrade can be triggered to proceed further.

To see attachments, please log in.

Related content:

We'd prefer it if you saw us at our best.

Pega Collaboration Center 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