About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
We also have the need to be able to drop a partition from a range-partitioned tablespace. When we try to rotate partitions of an archive-enabled PBR tablespace Db2 requires us to disable archiving before the rotate then re-enable archiving after the rotate. However, when we re-enable archiving we cause a deadlock with CICS and the online transaction fails. In order to prevent the deadlock we have stopped rotating partitions and are just adding a new partition at the end of each month and emptying out the oldest one. Since we cannot drop the old partition we will end up with many empty datasets from the partitions that we should have been able to rotate out.
To have that option (to delete limits of partitions in PBR tables) available, is very important to us.
Presently, customer we support have 300+ PBR tables, the partition key is the MVS ID, and from time to time (1 to 2 years) customer delete LPARs, coalesce others, and divide some of them in two.
For the new LPARs we are able to add the partition limits, but what about the deleted ones?
We are in a situation where more partitions exists on the tables, than LPARs exists
Until now we faced no problems with that, but in the future? Who knows...