Currently, REORG is not supported for PBG Tablespaces if Insync is enabled for those tablespaces. Replication status is changed to ERROR and data has to be reloaded.
|Who would benefit from this IDEA?||DBAs, Line of Business.|
How should it work?
All customers do REORG with LOG NO for PBGs. If customer is enabled that tablespace for Insync, table has to be reloaded to IDAA and this creates a major outage. It is better to support REORG operation in Db2Z when Insync is enabled with no business outage
|Priority Justification||All customers do REORG for PBG for various reasons. In Db2z it does not cause any outage but IDAA.|
|Customer Name||RBC, Canada|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "firstname.lastname@example.org" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions