Importing Customer Service framework (7.1.4 version) failed after PRPC 7.1.9 upgrade
Hi,
There is an application in PRPC v6.3 SP1 built on CPM 6.3 framework. After upgrading the application to PRPC v7.1.9, we tried to import Customer Service v7.1.4 framework. But import did not initialize with the below error being thrown:
2016-02-10 04:58:41,940 [ PegaRULES-Batch-2] [ STANDARD] [
] [ PegaRULES:07.10] ( internal.util.MoveLog) INFO Administrator@
pega.com - Error: Import failed due to an unallowed change (Column type)
2016-02-10 04:58:41,947 [ PegaRULES-Batch-2] [ STANDARD] [
] [ PegaRULES:07.10] (rnal.archive.ApplicationBundle) ERROR Administrator@
pega.com - The following SQL Statement contains a change to a column type. Type
Change Not allowed
2016-02-10 04:58:41,947 [ PegaRULES-Batch-2] [ STANDARD] [
] [ PegaRULES:07.10] (rnal.archive.ApplicationBundle) ERROR Administrator@
pega.com - ALTER TABLE RULES.pca_rule_dialog ALTER COLUMN pyAccessibilityLevel I
NT
When we logged into the database directly, using the admin ID, we were able to alter the column.
So we are unable to import the CS v7.1.4 framework due to the mentioned issue. If you could please assist.
**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.
Pegasystems Inc.
IN
We encountered similar issue, we have manually applied DDL.
We have performed below steps:
1. Taken the backup of table (pca_rule_dialog).
2. Truncated the data in the table.
3. Altered the table column appropriately
4. Restored the data back to the table.
Tata Consultancy Services
IN
If you do not have the permissions to execute the DDL yourse, then you need to share the scripts with your DBAs. Before sharing the DDLs, also share the scripts to take backup of the pca_rule_dialog table, truncate the pca_rule_dialog table, alter statement to update the column type and finally to restore the data back.
The DBAs should be able to get this done for you without any issues.
Cognizant
IN
create an Admin datasource called AdminPegaRULES with a JNDI name of jdbc/AdminPegaRULES. Point to the FUNCTIONAL ID that has CREATE TABLE and ALTER TABLE privileges.
Create JDBC Resources and update the prconfig.xml as below
<env name=”database/databases/PegaRULES/datasourceAdmin” value=”java:comp/env/jdbc/AdminPegaRULES”>
for more details about configuration please refer https://pdn.pega.com/how-provide-create-table-and-alter-table-database-privileges-admin-database-account
Regards,
Chandrasekhar Bhagath.