May I know that how does CHECK_TABLE_CONSISTENCY behave in terms of MVCC and garbage collection?
Kindly share your valuable views here and assist us.
Thanks in advance.
The following rules apply to MVCC in the context of CHECK_TABLE_CONSISTENCY:
Garbage collection is only blocked for the time of the analysis of an individual table. As soon as the analysis of a table is finished and the next table is checked, garbage collection can resume.
Up to SPS 08 garbage collection is blocked globally and not only for the analyzed table. Starting with SPS 09 improvements are implemented and so often the garbage collection is only blocked for the currently analyzed table.
This means that the garbage collection is never blocked longer than the analysis of a single table takes - even if the overall runtime of CHECK_TABLE_CONSISTENCY is much longer.
Sign up for STechies
All the site contents are Copyright © www.stechies.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies. The site www.stechies.com is in no way affiliated with SAP AG.
Every effort is made to ensure the content integrity. Information used on this site is at your own risk.
The content on this site may not be reproduced or redistributed without the express written permission of
www.stechies.com or the content authors.