You are on page 1of 2

Doc ID 2402965.

User_OMPNN Posts: 2 Red Ribbon


Mar 20, 2019 4:09AM edited Apr 2, 2019 2:03AM 2 commentsAnswered

A spatial index's underlying MDRT table is corrupted.

What exactly leads to the corrupted state, how often it can occur, why not self-repair,
etc. -- all behind the scenes

any ideas ?

Platform

Linux- 64bit

Version

Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production


FlagQuoteOff TopicLike

Answers


SureshMuddaveerappa Posts: 8,478 Blue Diamond
Mar 20, 2019 6:47AM edited Mar 20, 2019 6:47AM

Hello,

You have posted under the RAC forum. There is a separate forum for Spatial which
may provide better feedback.

Always post your full version number and platform details which could assist in case of
bugs/issues.

In the case of spatial indexes (unlike traditional indexes) the associated information
gets stored in 'MDRT_<>$ tables'. The 'MDRT_<>' tables in turn makes use of the
associated 'MDRS_<>$' sequence. Internally these are based on 'rowid' as well. One
scenario a corruption could occur is when the object tablespaces gets moved to a
different tablespace. The other possibility when one tries to explicitly export the
'MDRT_<>' tables. Then of course there could also be bugs in the spatial component.

Cheers

Suresh
FlagQuoteOff TopicLike


User_OMPNN Posts: 2 Red Ribbon
Apr 1, 2019 5:30AM edited Apr 1, 2019 5:30AM

thanks for your answer

question moved to spatial section

You might also like