Support Article
Facing issue while upgrading from PRPC 6.3 SP1 to Pega 7.1.9
SA-18087
Summary
Customer is facing an issue while performing split schema upgrade on Database. Migration of Rules schema went well. Upgrade of Rule schema is failing. Engine is generating schema scripts for upgrade and it is creating duplicate drop index script.
Because of that while executing the scripts it is unable to find the index in the second time.
Error Messages
[java] 26/10/2015 4:43:22 PM com.pega.pegarules.install.SQLLoader writeMessage
[java] INFO: File: mssql00720.sql
[java] 26/10/2015 4:43:22 PM com.pega.pegarules.install.SQLLoader writeMessage
[java] INFO: DROP INDEX RULES.PR4_RULE_VW.IX_PR4_RULE_VW_PYCLASS_PYCLASSNAME_PYRULESET
[java] 26/10/2015 4:43:22 PM com.pega.pegarules.install.SQLLoader writeMessage
[java] INFO: File: mssql00730.sql
[java] 26/10/2015 4:43:22 PM com.pega.pegarules.install.SQLLoader writeMessage
[java] INFO: DROP INDEX RULES.PR4_RULE_VW.IX_PR4_RULE_VW_PYCLASS_PYCLASSNAME_PYRULESET
[java] 26/10/2015 4:43:22 PM com.pega.pegarules.install.SQLLoader writeException
[java] WARNING: Failed to execute SQL in file mssql00730.sql
[java] com.microsoft.sqlserver.jdbc.SQLServerException: Cannot drop the index 'Rules.pr4_rule_vw.IX_pr4_rule_vw_pyClass_pyClassName_pyRuleSet', because it does not exist or you do not have permission.
[java] at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:197)
[java] at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1493)
[java] at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:775)
[java] at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:676)
[java] at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:4575)
[java] at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1400)
[java] at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:179)
[java] at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:154)
[java] at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(SQLServerStatement.java:649)
[java] at com.pega.pegarules.install.SQLLoader.main(SQLLoader.java:266)
[java] 26/10/2015 4:43:23 PM com.pega.pegarules.install.SQLLoader writeMessage
[java] WARNING: Statement: drop index Rules.pr4_rule_vw.IX_pr4_rule_vw_pyClass_pyClassName_pyRuleSet
[java] Exception in thread "main" com.pega.pegarules.install.SQLLoader$SQLLoaderException:
[java] ---
[java]
[java] Encountered a SQL Exception, clean schema before running again.
[java]
[java] ---
[java] at com.pega.pegarules.install.SQLLoader.fail(SQLLoader.java:359)
[java] at com.pega.pegarules.install.SQLLoader.main(SQLLoader.java:316)
BUILD FAILED
D:\softwares\114889_Pega719\scripts\setupDatabase.xml:330: The following error occurred while executing this line:
D:\softwares\114889_Pega719\scripts\setupDatabase.xml:1984: Java returned: 1
Total time: 5 minutes 58 seconds
Exiting with Error
Steps to Reproduce
1. Have an Instance with PRPC 6.3 SP1 with MSSQL server , JBOSS EAP server
2. Pega 7.1.9 Distribution file
3. Upgrade the System to Pega 7.1.9
4. Update the migration.properties and run migrate.bat file
5. update the setupDatabase.properties and run the upgrade.bat file
Root Cause
A defect in Pegasystems’ code. The query is fetching duplicate index names and column name causing the introspected xml to contain duplicate values. Query to get the covered index columns from the DB has to bechanged.
Resolution
Apply HFix-24699. The fix is not installable by Update Manager and needs to be installed as per instructions included in the Readme file.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.