Call to dbms_index_manager.refresh fails after upgrading to version 1.3.0

Environment

• Version: OceanBase seekdb
• Revision: 100000062026050810-3d42dddc51f7aab2a9742414f59f380b0e805b53
• Build Branch: HEAD
• Build Time: May 8 2026 10:27:55
• Build Flags: RelWithDebInfo
• Is this an RD-provided temporary version? No

Description

After upgrading from seekdb version 1.2.0 to version 1.3.0, executing the stored procedure call dbms_index_manager.refresh; results in an error.

Steps to Reproduce

1. Using seekdb version 1.2.0, create a table and insert vector-related data.
2. Upgrade to seekdb version 1.3.0.
3. Execute call dbms_index_manager.refresh;.
4. The command fails with an error.

Error Message:
ERROR 1049 (42000): Unknown database 'dbms_index_manager'

Log Information

Logs were filtered using the trace ID YB427F000001-0006519AED2D4752-0-0.

$grep "YB427F000001-0006519AED2D4752-0-0" seekdb.log*
seekdb.log:[2026-05-12 16:50:39.428521] WDIAG [SQL.RESV] get_database_id (ob_schema_checker.cpp:449) [986360][T1_L0_G0][T1][YB427F000001-0006519AED2D4752-0-0] [lt=14][errcode=-4002] invalid arguments(tenant_id=1, database_name=, ret=-4002)
seekdb.log:[2026-05-12 16:50:39.428544] WDIAG [SQL.RESV] resolve_sp_access_name (ob_resolver_utils.cpp:1701) [986360][T1_L0_G0][T1][YB427F000001-0006519AED2D4752-0-0] [lt=22][errcode=-4002] fail to exec schema_checker.get_database_id(tenant_id, current_database, database_id)(ret=-4002)
seekdb.log:[2026-05-12 16:50:39.428553] INFO  [SHARE.SCHEMA] get_database_id (ob_schema_getter_guard.cpp:965) [986360][T1_L0_G0][T1][YB427F000001-0006519AED2D4752-0-0] [lt=6] database not exist(tenant_id=1, database_name=dbms_index_manager)
seekdb.log:[2026-05-12 16:50:39.428564] WDIAG [SQL.RESV] get_database_id (ob_schema_checker.cpp:470) [986360][T1_L0_G0][T1][YB427F000001-0006519AED2D4752-0-0] [lt=11][errcode=-5154] database is not exist(tenant_id=1, catalog_id=0, database_name=dbms_index_manager, ret=-5154)
seekdb.log:[2026-05-12 16:50:39.428572] WDIAG [SQL.RESV] get_package_id (ob_schema_checker.cpp:1250) [986360][T1_L0_G0][T1][YB427F000001-0006519AED2D4752-0-0] [lt=6][errcode=-5559] package is not exist(tenant_id=1, database_id=201001, package_name=dbms_index_manager, ret=-5559)
seekdb.log:[2026-05-12 16:50:39.428582] WDIAG [SQL.RESV] resolve_sp_access_name (ob_resolver_utils.cpp:1720) [986360][T1_L0_G0][T1][YB427F000001-0006519AED2D4752-0-0] [lt=9][errcode=-5154] get database id failed(package_or_db_name=dbms_index_manager, ret=-5154)
seekdb.log:[2026-05-12 16:50:39.428590] WDIAG resolve_sp_access_name (ob_resolver_utils.cpp:1721) [986360][T1_L0_G0][T1][YB427F000001-0006519AED2D4752-0-0] [lt=6][errcode=-5154] Unknown database 'dbms_index_manager'
... (additional log lines follow)

Additional Context

• Reproducibility: Consistently reproducible (必现).
• Test Changes: The issue appeared after replacing with the new version.
• Other Environment Anomalies: No.
• Log Directory: /var/lib/oceanbase/log
• Connection String: mysql -h -P2881 -uroot
• Environment Info: SSH access via work@

Start with the resolver paths named in the logs, especially resolve_sp_access_name in ob_resolver_utils.cpp and get_database_id/get_package_id in ob_schema_checker.cpp. Reproduce the 1.2.0-to-1.3.0 upgrade and run the failing CALL, then trace why dbms_index_manager is resolved as a database. Done means the procedure executes successfully after upgrade with a regression test covering this scenario.