V10 MASS DELETES and SYSCOPY
Michael_D. 1100004WAH Visits (1159)
PM52724:MASS DELETES ENDS UP WITH LOCK ESCALATION ON SYSCOPY IN V10.
As a mass delete is the execution of a DELETE statement without a where clause! All rows in the table are deleted. With the exception of segmented or universal (UTS) table space, all rows are also logged and SYSCOPY entries are created for RECOVER BACKOUT process. Exceptions for segmented or UTS are, if the table is a parent of a referential constraint or is defined with DATA CAPTURE(CHANGE) or a delete trigger is involved. Mass deletes ends up with lock escalation on SYSCOPY in V10 if only PM30991 is installed. The APAR PM52724 maintenance level is over a year old, but might be of interrest for customers that are behind maintenance. With the base code of PM30991 Mass deletes without a where clause will insert a 'L' record into SYSCOPY. This has been corrected and a temporal work around is to add a where clause (e.g. WHERE 1=1')avoiding the insert of the syscopy records, because DB2 will no longer treat the SQL statement as a mass delete.