Referring to the Global Index changes in Space Manager 6.8 document on the Space Manager Management Community website, "UPDATE GLOBAL INDEXES" will be used when the partition contains less than 5% of the total rows in the table.
But based on the following test conducted, this does not hold true:
1. Create table with 2 partitions (P1,P2) (id less than maxvalue 50000)
2. Create 1 local index (for 2 partitions)
3. Create 1 global index (across all partitions)
4. Insert 100000 rows (from number 1 to 100000)
5. Delete 49000 rows (from number 1 to 49000 number, ie. rows are deleted from P1 only)
##Now partition P1 should have less than 5% of the total rows in the table##
6. Generate Reorg script
7. In the script it is "REBUILD OPTIONS" (instead of UPDATE GLOBAL INDEXES)
So what exactly is the criteria to have "UPDATE GLOBAL INDEXES" syntax in the Reorg script?
WORKAROUND
None.
STATUS
To decide between update global indexes vs. rebuild index, Space Manager looks at the allocated size of the partition, not the number of rows in the partition. To have "UPDATE GLOBAL INDEXES" syntax in the script, one partition size has to be less than 5% of total size.
Waiting for a fix in a future release of Space Manager with LiveReorg.
ST62848 - Update global indexes should happen based on rowcount if rowcount is available
The Global Index changes in Space Manager 6.8 document is available here
http://spacemanagementoracle.inside.quest.com/entry.jspa?categoryID=94&externalID=2753
Due to issues with Rebuild Global Indexes, we have refined the handling of reorgs of partitioned tables with global indexes;
1. The default is now to reorganize the entire table which avoids the need to rebuild global indexes
2. We now use the UPDATE GLOBAL INDEXES syntax when appropriate.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center