Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
1.0.0, 1.2
-
None
-
2021-1, 2021-2, 2021-3, 2021-4, 2021-5, 2021-6, 2021-7, 2021-8, 2021-9
Description
An extent is marked as invalid if DELETE, INSERT, UPDATE touches this extent. The extent has to be reread by SELECT to become valid again. If one bulk inserts in the invalid extent then min/max values aren't updated in the EM.
One should read the data out after DML operations and before you bulk inserting data to make extents touched by DML valid again. To reduce number of extents to read one could set an impossible filter to eliminate all valid extents.
Attachments
Issue Links
- causes
-
MCOL-4766 UPDATE/INSERT in a transaction does not revert back extent ranges on a rollback
-
- Closed
-
-
MCOL-4779 Invalid extent ranges for short character columns
-
- Closed
-
- includes
-
MCOL-4722 Add extent range keeping for single-value insert operation
-
- Open
-
- is part of
-
MCOL-4343 umbrella for tech debt issues
-
- Open
-
- relates to
-
MCOL-4673 Regression: calShowPartition returns N/A
-
- Closed
-