Bad Performance and Excessive Redolog Generation For DML on Spatial Tables/Indexes
Last updated on DECEMBER 24, 2013
Applies to:Oracle Spatial and Graph - Version 10.1.0.2 to 22.214.171.124 [Release 10.1 to 11.1]
Information in this document applies to any platform.
Checked for relevance on 24-Dec-2013
Bad performance and excessive redo generation is seen on performing DML on Spatial tables.
Frequent inserts/updates on Spatial tables are being done and a large amount of redo generation is seen for each update of the spatial index (updates in several MDRT_xxxx$ tables and index metadata).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms