Skip to main content
Contact a Moderator

Discussion

3
Replies
111
Views
 Mahesan Panavoor Mana Vasudevan (MahesanVasudevan) PEGA Lead System Architect - Pega Consulting
Pegasystems Inc.
GB
MahesanVasudevan Member since 2014 4 posts
PEGA
Posted: August 26, 2015
Last activity: August 27, 2015
Posted: 26 Aug 2015 8:11 EDT
Last activity: 27 Aug 2015 6:19 EDT
Closed

Error While Upgrading Rules Schema to Pega 7.1.8

Hi,

 

I have an environment with following configuration.

App Server - Tomact 7.0.41

DB - MS SQL 2008 R2

PegaRUELS - 6.3 SP1

 

I am trying an out-of-place manual upgrade with both source and target schema in the same db. I could successfully migrate rules to the target schema but when I run upgrade on the migrated rules I get the error "com.microsoft.sqlserver.jdbc.SQLServerException: Transaction (Process ID 62) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction."

What could be the reason for this?

 

Thanks,

Mahesan

 

System Administration Installation and Deployment
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Discussion, please write a new Discussion.
Posted: 6 years ago
Posted: 26 Aug 2015 8:30 EDT
Karuppan Chetty Atheppan (Karuppan) PEGA Lead Service Assurance Advisor
Pegasystems Inc.
IN

Helo Mahesan,

 

This seems like a general DEADLOCK issue with SQL Server.

 

Can you please make sure no other process is accessing this migrated DB when you are doing the upgrade.  Also make sure you are using the migrated DB credentials and not the original for when you are doing upgrade.

 

The below link may give some insight about the deadlock issue and how to fix that.

http://blog.sqlauthority.com/2007/05/16/sql-server-fix-error-1205-transaction-process-id-was-deadlocked-on-resources-with-another-process-and-has-been-chosen-as-the-deadlock-victim-rerun-the-transaction/

 
Posted: 6 years ago
Posted: 27 Aug 2015 6:19 EDT
Mahesan Panavoor Mana Vasudevan (MahesanVasudevan) PEGA Lead System Architect - Pega Consulting
Pegasystems Inc.
GB

I shutdown the app and tried resume.bat. It worked. I was using the same credentail used by application for running upgrade. I guess this could have caused the issue.

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