My Oracle Support Banner

EPY: DB2 deadlock when running concurrent calcs (Doc ID 648375.1)

Last updated on OCTOBER 10, 2018

Applies to:

PeopleSoft Enterprise HRMS ePay - Version: 8 - Release: 8
PeopleSoft Enterprise HRMS Payroll for North America - Version: 8 - Release: 8

Information in this document applies to any platform.

SPECIFIC TO:  Enterprise, 8.x , DB2.
 
ISSUE1:
Customer on DB2/UDB 8.1.3  32 bit.  OS AIX 5.1.  8.8 SP1 / 8.43.11 receiving Deadlocks on different SQL statements when running concurrent calcs.  Customer has the need for 6 concurrent runs due to the size of their business.

SOLUTION1:
Change DB2_RR_TO_RS = ON .  Change all Indices to TYPE 2.

ISSUE2:
 Deadlocking issue with our pay calc on the PSPSTRUN_D_TAX stored statement after 06C.

SOLUTION2:
We changed the commit level to row level locking from page level locking on the PAY_TAX tablespace.  

NOTE:
Here is some information that we recommend on locking:

Locking is specified at the tablespace level
We default all tablespaces to ANY level locking, which satisfies most concurrency requirements as long as Type 2 indexes are used.
The memory and resource requirements of some of the larger batch processes make row level locking an unsuitable choice for most customers. If you really need row level locking for concurrency, then be aware of the following

This document was previously published as Customer Connection Solution 201014586

Symptoms

DB2 deadlock when running concurrent calcs

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
  Symptoms
  Cause
  Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.