OceanBase logo

OceanBase

A unified distributed database ready for your transactional, analytical, and AI workloads.

Product Overview
DEPLOY YOUR WAY

OceanBase Cloud

The best way to deploy and scale OceanBase

OceanBase Enterprise

Run and manage OceanBase on your infra

TRY OPEN SOURCE

OceanBase Community Edition

The free, open-source distributed database

OceanBase seekdb

Open source AI native search database

Customer Stories

Real-world success stories from enterprises across diverse industries.

View All
BY USE CASES

Mission-Critical Transactions

Global & Multicloud Application

Elastic Scaling for Peak Traffic

Real-time Analytics

Active Geo-redundancy

Database Consolidation

Resources

Comprehensive knowledge hub for OceanBase.

Blog

Live Demos

Training & Certification

Documentation

Official technical guides, tutorials, API references, and manuals for all OceanBase products.

View All
PRODUCTS

OceanBase Cloud

OceanBase Database

Tools

Connectors and Middleware

QUICK START

OceanBase Cloud

OceanBase Database

BEST PRACTICES

Practical guides for utilizing OceanBase more effectively and conveniently

Company

Learn more about OceanBase – our company, partnerships, and trust and security initiatives.

About OceanBase

Partner

Trust Center

Contact Us

International - English
中国站 - 简体中文
日本 - 日本語
Sign In
Start on Cloud

OceanBase

A unified distributed database ready for your transactional, analytical, and AI workloads.

Product Overview
DEPLOY YOUR WAY

OceanBase Cloud

The best way to deploy and scale OceanBase

OceanBase Enterprise

Run and manage OceanBase on your infra

TRY OPEN SOURCE

OceanBase Community Edition

The free, open-source distributed database

OceanBase seekdb

Open source AI native search database

Customer Stories

Real-world success stories from enterprises across diverse industries.

View All
BY USE CASES

Mission-Critical Transactions

Global & Multicloud Application

Elastic Scaling for Peak Traffic

Real-time Analytics

Active Geo-redundancy

Database Consolidation

Comprehensive knowledge hub for OceanBase.

Blog

Live Demos

Training & Certification

Documentation

Official technical guides, tutorials, API references, and manuals for all OceanBase products.

View All
PRODUCTS
OceanBase CloudOceanBase Database
ToolsConnectors and Middleware
QUICK START
OceanBase CloudOceanBase Database
BEST PRACTICES

Practical guides for utilizing OceanBase more effectively and conveniently

Learn more about OceanBase – our company, partnerships, and trust and security initiatives.

About OceanBase

Partner

Trust Center

Contact Us

Start on Cloud
编组
All Products
    • Databases
    • iconOceanBase Database
    • iconOceanBase Cloud
    • iconOceanBase Tugraph
    • iconInteractive Tutorials
    • iconOceanBase Best Practices
    • Tools
    • iconOceanBase Cloud Platform
    • iconOceanBase Migration Service
    • iconOceanBase Developer Center
    • iconOceanBase Migration Assessment
    • iconOceanBase Admin Tool
    • iconOceanBase Loader and Dumper
    • iconOceanBase Deployer
    • iconKubernetes operator for OceanBase
    • iconOceanBase Diagnostic Tool
    • iconOceanBase Binlog Service
    • Connectors and Middleware
    • iconOceanBase Database Proxy
    • iconEmbedded SQL in C for OceanBase
    • iconOceanBase Call Interface
    • iconOceanBase Connector/C
    • iconOceanBase Connector/J
    • iconOceanBase Connector/ODBC
    • iconOceanBase Connector/NET
icon

OceanBase Database

SQL - V4.4.2

    Download PDF

    OceanBase logo

    The Unified Distributed Database for the AI Era.

    Follow Us
    Products
    OceanBase CloudOceanBase EnterpriseOceanBase Community EditionOceanBase seekdb
    Resources
    DocsBlogLive DemosTraining & CertificationTicket
    Company
    About OceanBaseTrust CenterLegalPartnerContact Us
    Follow Us

    © OceanBase 2026. All rights reserved

    Cloud Service AgreementPrivacy PolicySecurity
    Contact Us
    Document Feedback
    1. Documentation Center
    2. OceanBase Database
    3. SQL
    4. V4.4.2
    iconOceanBase Database
    SQL - V 4.4.2
    SQL
    KV
    • V 4.6.0
    • V 4.4.2
    • V 4.3.5
    • V 4.3.3
    • V 4.3.1
    • V 4.3.0
    • V 4.2.5
    • V 4.2.2
    • V 4.2.1
    • V 4.2.0
    • V 4.1.0
    • V 4.0.0
    • V 3.1.4 and earlier

    GATHER_INDEX_STATS

    Last Updated:2026-04-14 12:43:57  Updated
    share
    What is on this page
    Syntax
    Parameters
    Exceptions
    Considerations
    Examples

    folded

    share

    The GATHER_INDEX_STATS procedure collects index statistics.

    Syntax

    DBMS_STATS.GATHER_INDEX_STATS (
      ownname            VARCHAR2,
      indname            VARCHAR2,
      partname           VARCHAR2 DEFAULT NULL,
      estimate_percent   NUMBER DEFAULT AUTO_SAMPLE_SIZE,
      stattab            VARCHAR2 DEFAULT NULL,
      statown            VARCHAR2 DEFAULT NULL,
      degree             NUMBER DEFAULT NULL,
      granularity        VARCHAR2 DEFAULT DEFAULT_GRANULARITY,
      no_invalidate      BOOLEAN DEFAULT FALSE,
      force              BOOLEAN DEFAULT FALSE,
      tabname            VARCHAR2 DEFAULT NULL
    );
    

    Parameters

    Parameter
    Description
    ownname The schema to which the table belongs.
    indname The name of the index.
    partname The name of the partition.
    estimate_percent The percentage of rows to be estimated. Value range: [0.000001,100].
    stattab The name of the user statistics table for storing statistics.
    statown The username of the user statistics table for storing statistics.
    degree The degree of parallelism (DOP). Default value: NULL. NULL indicates that the default table DOP specified in the DEGREE clause of the CREATE TABLE or ALTER TABLE statement is used. When DEGREE=>NULL or DEGREE=>n is specified, DBMS_STATS may adopt serial execution if parallel execution cannot be guaranteed due to the object size.
    granularity The granularity of index statistics to be collected. This parameter is applicable only when the table is partitioned.
    • ALL: collects all index statistics, including subpartition-level, partition-level, and global statistics.
    • APPROX_GLOBAL AND PARTITION: This option is similar to GLOBAL AND PARTITION. However, when this option is specified, collected global index statistics are a summary of partition-level statistics. This option summarizes all index statistics other than the number of distinct values and the number of distinct keys of indexes. However, it summarizes only the partitions with statistics. It collects global index statistics if partname is NULL or summary fails, for example, index statistics on a partition are missing.
    • AUTO: determines the granularity based on the partition type. This is the default value.
    • DEFAULT: collects global and partition-level index statistics. This option is deprecated. We recommend that you use GLOBAL AND PARTITION.
    • GLOBAL: collects global index statistics.
    • GLOBAL AND PARTITION: collects global and partition-level index statistics. Index statistics at the subpartition level will not be collected even for composite partitioned objects.
    • PARTITION: collects partition-level index statistics.
    • SUBPARTITION: collects subpartition-level index statistics.
    no_invalidate Specifies whether to refresh the plan cache during statistics collection. If you set the value to TRUE, the plan cache will not be refreshed during statistics collection.
    force Specifies whether to perform forced collection and ignore the lock status. Default value: FALSE. If you set the value to TRUE, index statistics will be collected even if statistics are locked.
    tabname The name of the table.

    Exceptions

    Error code
    Description
    HY000
    • The index does not exist, or you do not have the required privileges.
    • The input value is incorrect.

    Considerations

    To call this procedure, you must be the owner of the table. If the object is in the sys tenant, you must be the owner of the table or have the SYSDBA privilege.

    Examples

    Collect the statistics on the idx index in the tbl1 table of the testUser01 user.

    obclient> CALL DBMS_STATS.GATHER_INDEX_STATS('testUser01', 'idx1', degree=>4, tabname=>'tbl1');
    Query OK, 0 rows affected
    

    Note

    In Oracle-compatible mode, you do not need to specify the tabname parameter because the index is unique under the current user. In MySQL-compatible mode, you must explicitly specify the table name because indexes are not unique under the current user.

    Previous topic

    FLUSH_DATABASE_MONITORING_INFO
    Last

    Next topic

    GATHER_TABLE_STATS
    Next
    What is on this page
    Syntax
    Parameters
    Exceptions
    Considerations
    Examples