Full Table Scans During DBMS_WM.LOCKROWS When Using A Topology

(Doc ID 1514980.1)

Last updated on DECEMBER 20, 2012

Applies to:

Workspace Manager - Version 11.2.0.3 and later
Information in this document applies to any platform.

Symptoms

When using the dbms_wm.LockRows procedure with a topology by specifying the Xmin, Xmax, Ymin, Ymax parameters, the optimizer is performing full table scans on a number of tables(NODE$, EDGE$, FACE$, etc) instead of using the domain index on the geometry column.  This is leading to degraded performance of the procedure.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms