Unable to log in, blank screens and hangs
Issue logging in to Pega. While trying to log in, a blank screen displays, or the screen successfully loads but only after a long delay (more than 1 minute).
PegaRULES log displays the below error message.
The current transaction has been rolled back because of a deadlock or timeout. Reason code "2".. SQLCODE=-911, SQLSTATE=40001, DRIVER=3.64.133
SQL: delete from pr_index_operators where pxInsIndexedKey = ? and pxIndexPurpose = ?
Caused by SQL Problems.
Problem #1, SQLState 40001, Error code -911: com.ibm.db2.jcc.am.SqlTransactionRollbackException: The current transaction has been rolled back because of a deadlock or timeout. Reason code "2".. SQLCODE=-911, SQLSTATE=40001, DRIVER=3.64.133
Steps to Reproduce
There is no specific use case to replicate this behavior.
A configuration issue in the operating environment is responsible for this issue. The database backup configuration was changed, causing the overnight database backup operation to not be completed by the time peak usage hours began.
Stop the backup operation.
Revert the database configuration to its previously known working form before the next backup is taken, to address the issue in the long term.
Published January 31, 2016 - Updated October 8, 2020
0% found this useful
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.