Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Hi All,
Tech Specs: O/S Solaris 9 - IDS 7.31.FD7
I was playing around with fragmentation recently when I came across a
couple of interesting questions.
Question 1)
I came across a seemingly inconsistency when fragmenting a table that
contained
a Primary Key using a fragment by expression clause. Oncheck showed the
P.K. got fragmented across multiple dbspaces same as the table however
the underlying unique index that is system created upon
creation of the P.K. remained in the original dbspace and was not
fragmented.
This was not the case however for a P.K. that was build upon an existing
unique index that I had previously created.
In that scenario the unique index got fragmented along with the rest of
the table.
Question 2)
How could in the above case an unique index get fragmented upon
fragmentation of table if creating it with the
Same fragment by expression clause after the table gets fragmented
results in a 872 error.
finderr 872
-872 Invalid fragment strategy or expression for the unique index.
The round-robin method cannot fragment unique indexes. If the
expression method fragments the indexes, all the columns that are used
in the fragmentation expressions must also be part of the index key.
Any assistance is greatly appreciated.
TIA,
Zev Berezin
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.