Share this:

Like this:

Related

You could do it with two BOWIE tables in different schemas. One, in the schema ODDITY, with the indexes and the other in DUKE without. You log on to DUKE, do the move and the indexes in DBA_INDEXES are still valid (because they are on the other BOWIE table).

I think you’ve got something smarter though.

PS. How about copying Tim Hall and doing some quizzes at PL/SQL Challenge ?

I am guessing IOT too.
This is because IOT´s have the primary key and a “best guess adress” as their “rowid” on their secondary indexes and this remains valid even if the IOT is moved (only the guess is probably bad).
The first index, the primary key, is moved to a consistent state by the move table command which is better described as a move index command in this case.

Julian Dyke has published a presentation on IOT internals that describes secondary Indexes on IOT and best guess address stored in them.
That explains why move table on IOT won’t impact secondary indexes on IOT.
Link to the ppt: http://www.juliandyke.com/Presentations/IOTInternals.ppt

Gotta be an IOT. The secondary index is not an issue.
From the “manuel”:
“Use of primary-key based logical rowids, as opposed to physical rowids, in secondary indexes on index-organized tables allows high availability. This is because, due to the logical nature of the rowids, secondary indexes do not become unusable even after a table reorganization operation that causes movement of the base table rows.”
In IOTs, rows are stored in pk order and rowids use logical rowid rather than physical. The logical rowid doesn’t change with table location.