Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

SQL exception occurs while running the Upgrade installer

SA-8287

Summary



The following error is generated while running the Pega 7.1.7 Upgrade installer upgrading from 6.1 SP2

Error Messages


         [java] WARNING: Statement: cre
     [java] ate table dbo.pr_index_circumstance_def
     [java] (
     [java]     pxCommitDateTime DATETIME NULL,
     [java]     pxCreateDateTime DATETIME NULL,
     [java]     pxCreateOperator VARCHAR(128) NULL,
     [java]     pxCreateOpName VARCHAR(128) NULL,
     [java]     pxCreateSystemID VARCHAR(32) NULL,
     [java]     pxIndexCount INT NULL,
     [java]     pxIndexPurpose VARCHAR(32) NULL,
     [java]     pxIndexedClass VARCHAR(96) NULL,
     [java]     pxInsIndexedClass VARCHAR(96) NULL,
     [java]     pxInsIndexedKey VARCHAR(255) NULL,
     [java]     pxInsName VARCHAR(385) NULL,
     [java]     pxObjClass VARCHAR(96) NULL,
     [java]     pxUpdateDateTime DATETIME NULL,
     [java]     pxUpdateOperator VARCHAR(128) NULL,
     [java]     pxUpdateOpName VARCHAR(128) NULL,
     [java]     pxUpdateSystemID VARCHAR(32) NULL,
     [java]     pyCountry VARCHAR(64) NULL,
     [java]     pyCity VARCHAR(64) NULL,
     [java]     pyDefinitionName VARCHAR(128) NULL,
     [java]     pyTemplateName VARCHAR(128) NULL,
     [java]     pyLabel VARCHAR(64) NULL,
     [java]     pyRegion VARCHAR(64) NULL,
     [java]     pyState VARCHAR(64) NULL,
     [java]     pyChannel VARCHAR(32) NULL,
     [java]     pyLevel VARCHAR(64) NULL,
     [java]     pyCompany VARCHAR(64) NULL,
     [java]     pyOrg VARCHAR(64) NULL,
     [java]     pyDept VARCHAR(64) NULL,
     [java]     pyPostalCode VARCHAR(32) NULL,
     [java]     pzInsKey VARCHAR(512) NOT NULL
     [java] )
     [java] com.microsoft.sqlserver.jdbc.SQLServerException: There is already an object named 'pr_index_circumstance_def' in the database.
     [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:298)
     [java] Mar 18, 2015 11:12:44 AM com.pega.pegarules.install.SQLLoader writeMessage


Steps to Reproduce



Run an upgrade from 6.1 SP2 to Pega 7.1.7

Root Cause



The root cause of this problem is a defect in Pegasystems’ code/rules.
Due to customizations on the table, it is not recognized as being present in the schema that is being upgraded.
Subsequently an attempt is made to create the table which already exists.


Resolution



This issue is resolved through the following local-change: 
Prior to executing the final step in the Upgrade assistant wizard, the generated SQL file is editted to remove the table causing the problem.
In this case no further alter or column population is required.

 
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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

Pega Community 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
Contact us