Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Oracle Spatial indexes with LAYER_GTYPE on global storage (ASM,...)

LauryDec 18 2021

Hi,
I am working with Oracle Sptial on 19c RDBMS.
I understand that for beter performaance, it is beter to:
2) Spatial indexes should have a different tablespace than for regular indexes.

  1. Spatial indexes should have a tablespace for a specific layer, for instance point -> its own tablespace, line -> its own tablespace, etc...
    So, consequently we can create a Spatial index tablespace as:
    CREATE INDEX customers_sidx
    ON customers(location)
    INDEXTYPE IS MDSYS.SPATIAL_INDEX
    PARAMETERS ('LAYER_GTYPE=POINT TABLESPACE=CUSTOMER_POINT_D');
    In the past we used to have separate tablespaces according to the stored object usage (tables, indexes,...) and to allocate a given tablespace to a specific physical storage, and another one to another type of disk stotage.
    Nowdays, the storage is seen as "global", this mean that we have a physicalstorage for all tablespaces in once.
    So, even if we create tablespace A and tablespace B, they will be located on the same physical storage.
    What about Spatial tablespaces? If I define LAYER_GTYPE for each tablespace and for each layer but these tablespaces are still in the same "global" physical storage, what is then the benefit regading performance to define the tablespaces wirth the LAYER_GTYPE parameer?
    Having in mind that all the tablespaces are then on the same physical storage (ASM,...).
    Thanks by advance for sharing your experience.
    Kind Regards.

Comments

Post Details

Added on Dec 18 2021
0 comments
163 views