Question
Anthem
US
Last activity: 10 Mar 2020 9:15 EDT
PEGA Upgrade (7.3.1 to 8.3.1) - SQL issues.
Hi Team,
While trying to upgrade from PRPC7.3.1 to PRPC8.3.1,we are running into the below mentioned issues because of which upgrade has been halted.
Application Specs : PRPC7.3.1,MSSQL and Tomcat 8.5.13.
How can I disable these kind of messages while running the upgrade related SQL scripts ?
Hi Team,
While trying to upgrade from PRPC7.3.1 to PRPC8.3.1,we are running into the below mentioned issues because of which upgrade has been halted.
Application Specs : PRPC7.3.1,MSSQL and Tomcat 8.5.13.
How can I disable these kind of messages while running the upgrade related SQL scripts ?
Msg 2714, Level 16, State 5, Line 94 There is already an object named 'pr_history_PK' in the database. Msg 1750, Level 16, State 0, Line 94 Could not create constraint. See previous errors. Msg 2705, Level 16, State 4, Line 522 Column names in each table must be unique. Column name 'pzInsKey' in table 'dbo.pr_data_offline_sync' is specified more than once. Msg 2705, Level 16, State 4, Line 526 Column names in each table must be unique. Column name 'pxInsName' in table 'dbo.pr_data_offline_sync' is specified more than once. Msg 2705, Level 16, State 4, Line 528 Column names in each table must be unique. Column name 'pxSaveDateTime' in table 'dbo.pr_data_offline_sync' is specified more than once. Msg 2705, Level 16, State 4, Line 530 Column names in each table must be unique. Column name 'pxCommitDateTime' in table 'dbo.pr_data_offline_sync' is specified more than once. Msg 2705, Level 16, State 4, Line 544 Column names in each table must be unique. Column name 'pzPVStream' in table 'dbo.pr_data_offline_sync' is specified more than once. Msg 2705, Level 16, State 4, Line 1370 Column names in each table must be unique. Column name 'pyKeyRotationInterval' in table 'dbo.pr_data_admin_sec_sde_cdk' is specified more than once.
Proximus
BE
Hello, Could you please clarify the way you selected to do the upgrade?
in-place / out-place? what's the user used for the upgrade? is it the typical recommended PEGA one with full access?
Was it a first upgrade execution?
Is your table pr_data_offline_sync properly defined?
Thanks
Anthony
Anthem
US
Inline comments below.
Hello, Could you please clarify the way you selected to do the upgrade?Out-Place (Proof Of Concept Purpose for now).
in-place / out-place? what's the user used for the upgrade? is it the typical recommended PEGA one with full access?DB owner (highest privilege access).
Was it a first upgrade execution? Yes,first from PRPC731 to PRPC831.
Is your table pr_data_offline_sync properly defined? Its OOTB,I guess,it should have been defined properly ?
I was running into the above mentioned SQL issues while trying to implement the upgrade sql script manually (by setting bypass.pega.schema to false).But while I was running the upgrade script by setting bypass.pega.schema to true,upgrade process exits with the below mentioned error messages.
"INFO - Started import of rule-service-rest.zip (3 of 189)
[java] Mar 10, 2020 5:38:38 AM com.pega.pegarules.internal.bootstrap.PRBootstrap
[java] SEVERE: Problem during method invocation (main)
[java] com.pega.pegarules.pub.PRException: PRException
[java] Mar 10, 2020 5:38:38 AM com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega
Inline comments below.
Hello, Could you please clarify the way you selected to do the upgrade?Out-Place (Proof Of Concept Purpose for now).
in-place / out-place? what's the user used for the upgrade? is it the typical recommended PEGA one with full access?DB owner (highest privilege access).
Was it a first upgrade execution? Yes,first from PRPC731 to PRPC831.
Is your table pr_data_offline_sync properly defined? Its OOTB,I guess,it should have been defined properly ?
I was running into the above mentioned SQL issues while trying to implement the upgrade sql script manually (by setting bypass.pega.schema to false).But while I was running the upgrade script by setting bypass.pega.schema to true,upgrade process exits with the below mentioned error messages.
"INFO - Started import of rule-service-rest.zip (3 of 189)
[java] Mar 10, 2020 5:38:38 AM com.pega.pegarules.internal.bootstrap.PRBootstrap
[java] SEVERE: Problem during method invocation (main)
[java] com.pega.pegarules.pub.PRException: PRException
[java] Mar 10, 2020 5:38:38 AM com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega
[java] SEVERE: Problem during method invocation (main)
[java] com.pega.pegarules.pub.PRException: PRException
[java] From: (unknown)
java] Caused by: com.pega.pegarules.pub.clipboard.PegaArchiveException: PegaArchiveException PRRuleMgmtUtils.createArchiveForRead(PRFile) PegaArchiveException PRRuleMgmtUtils.createArchiveForRead(PRFile) Corrupt archive or unsupported archive type."