【OB 4.5.0.0】新建 user 租户后系统视图 V$OB_SESS_TIME_MODEL 损坏,root inspection 持续报错(-4754 / references invalid)

AntTech_2GDURQ · 2026 年6 月 30 日 16:38

【使用环境】生产环境

【 OB or 其他组件】OceanBase（observer / RootService 巡检）

【使用版本】4.5.0.0_100000012025112711-0e8d5ad012baf0953b2032a35a88bdf8886e9a7a（Nov 27 2025 build）

【问题描述】

某 user 租户的系统视图 V$OB_SESS_TIME_MODEL / GV$OB_SESS_TIME_MODEL 无法查询,报 ERROR 1356: references invalid table(s);同时 RootService 巡检(root inspection)持续失败,observer 日志反复刷:

EDIAG [RS] check_sys_view_ (ob_root_inspection.cpp:1622) [errcode=-4029] check sys view: expand failed        tenant_id=1008, table_name=V$OB_SESS_TIME_MODELERROR [RS] check_sys_table_schemas (ob_root_inspection.cpp:1347) [errcode=-4754]        root inspection is not passed, msg="inner tables are unmatched", tenant_id=1008ERROR [RS] check_error_table_ids_ [RSInspectTask] table_ids=[21492]

sys 租户查同一视图完全正常,仅该 user 租户异常。 业务读写不受影响,但巡检不通过会持续告警。

【复现路径】

集群 3 节点(zone1/2/3),2026-05-08 部署,版本如上,部署后从未升级(3 节点 build_version 一致、observer 自部署起未重启)。
2026-05-11 18:33 create tenant marketing(MySQL 模式, USER 租户, id=1008),为集群唯一 user 租户。
建租户后该视图即损坏,疑似 建租户时 GV$OB_SESS_TIME_MODEL resolve 失败/不完整。

我方已完成的排查(排除法,供贵方跳过重复定位):

#	验证	结果	排除
1	报警租户类型	`marketing` = USER 租户(非 meta)	—
2	集群是否升级过	3 节点同 build、observer 未重启	升级残留
3	同视图在 sys 租户	正常返回	版本通病
4	视图定义 sys(1) vs marketing(1008)	`__all_virtual_table.view_definition` 逐字一致	定义建错
5	上游 `GV$SESSTAT`、`V$STATNAME` 在 marketing 单独查	均正常	上游对象缺失

→ 结论:仅 marketing 租户的 GV$OB_SESS_TIME_MODEL(table_id 21491) 视图解析态/依赖记录损坏,定义和上游都正常。

咨询点:

是否为 4.5.0.0 create tenant 初始化系统视图的已知问题?
如何重建该租户的系统视图(内部命令?重启租户能否触发重新 resolve?是否需补丁版本)?
是否影响后续在该集群新建 user 租户(会不会每个新租户都中招)?

【附件及日志】

obdiag 收集 RootService 巡检报错时段日志(按贵方需要,命令按 obdiag 实际版本调整):

[2026-06-30 15:07:32.553534] INFO  [RS] check_sys_table_schema_ (ob_root_inspection.cpp:1227) [14197][RSInspectTask][T0][Y0-0000000000000000-0-0] [lt=22] async check sys table schema for tenant(ret=0, ret="OB_SUCCESS", tenant_leader="10.104.16.190:2882", arg={tenant_id:1008, data_current_version:{version_str:"4.5.0.0", version_val:17180196864}, rs_addr:"10.104.16.190:2882", rs_epoch_id:2})
[2026-06-30 15:07:33.053253] WDIAG [RS] check_sys_view_ (ob_root_inspection.cpp:1616) [3205094][T1008_L0_G0][T1008][YB420A6810BE-000651D9FAEFE934-0-0] [lt=12][errcode=-5231] execute sql failed(ret=-5231, ret="OB_ERR_VIEW_INVALID", tenant_id=1008, table_name=V$OB_SESS_TIME_MODEL, sql=SELECT FIELD FROM `oceanbase`.`__tenant_virtual_table_column` WHERE TABLE_ID = 21492)
[2026-06-30 15:07:33.053263] EDIAG [RS] check_sys_view_ (ob_root_inspection.cpp:1622) [3205094][T1008_L0_G0][T1008][YB420A6810BE-000651D9FAEFE934-0-0] [lt=18][errcode=-4029] check sys view: expand failed(ret=-4029, ret="OB_SCHEMA_ERROR", tenant_id=1008, table_name=V$OB_SESS_TIME_MODEL) BACKTRACE:0xaeb6c22 0xae6d30d 0xaeb7923 0xaeb72f7 0xaeb7251 0xaeb715d 0x10f676a6 0x10f61c43 0x10f5d27a 0x10f5f45c 0x13798cac 0xb2a86f4 0xa8cb9a8 0xa8b873a 0x13e8a542 0x285d39f9 0x7f98bfc8a0ea 0x7f98bfd0f150
[2026-06-30 15:07:33.227999] EDIAG [RS] check_sys_table_schemas (ob_root_inspection.cpp:1346) [3205094][T1008_L0_G0][T1008][YB420A6810BE-000651D9FAEFE934-0-0] [lt=0][errcode=0] check sys table schema failed(ret=0, ret="OB_SUCCESS", tenant_id=1008, error_table_ids=[21492]) BACKTRACE:0xaeb6c22 0xae6d30d 0xaeb7923 0xaeb72f7 0xaeb7251 0xaeb715d 0x10f60ba8 0x10f5d57b 0x10f5f45c 0x13798cac 0xb2a86f4 0xa8cb9a8 0xa8b873a 0x13e8a542 0x285d39f9 0x7f98bfc8a0ea 0x7f98bfd0f150
[2026-06-30 15:07:33.519102] EDIAG [RS] check_error_table_ids_ (ob_root_inspection.cpp:1104) [14197][RSInspectTask][T0][Y0-0000000000000000-0-0] [lt=20][errcode=-4029] check sys table schema failed(ret=-4029, ret="OB_SCHEMA_ERROR", tenant_id=1008, table_ids=[21492]) BACKTRACE:0xaeb6c22 0xae6d30d 0xaeb7923 0xaeb72f7 0xaeb7251 0xaeb715d 0x10f5c314 0x10f5bd95 0x10f5af0a 0x10f4adeb 0x10f4e6fe 0x10f47bb5 0x285be24f 0x285cb5f2 0x285bdf27 0x285bd8e1 0x285d3b0d 0x7f98bfc8a0ea 0x7f98bfd0f150
[2026-06-30 15:07:33.519146] WDIAG [RS] check_sys_table_schemas_ (ob_root_inspection.cpp:1078) [14197][RSInspectTask][T0][Y0-0000000000000000-0-0] [lt=1][errcode=-4029] failed to check sys table schemas(ret=-4029, ret="OB_SCHEMA_ERROR", tenant_ids=[1, 1007, 1008])
[2026-06-30 15:07:33.529032] INFO  [RS] process (ob_root_inspection.cpp:382) [14197][RSInspectTask][T0][Y0-0000000000000000-0-0] [lt=0] inspection task succ(i=2, task="tenant_checker")

关键诊断 SQL 输出(已附):

-- 租户：marketing = USER, 2026-05-11 建DBA_OB_TENANTS: 1008 | marketing | USER | NORMAL | MYSQL | 2026-05-11 18:33:34
-- 版本（3 节点一致，未升级）__all_server: 4.5.0.0_100000012025112711 (Nov 27 2025) ×3, start_service_time≈2026-05-08
-- 现象对照[sys 租户]      SELECT * FROM oceanbase.GV$OB_SESS_TIME_MODEL LIMIT 1;  -- ✅ 正常返回[marketing 租户] SELECT * FROM oceanbase.GV$OB_SESS_TIME_MODEL LIMIT 1;  -- ❌ ERROR 1356 references invalid
-- 定义一致（排除定义错）__all_virtual_table WHERE table_id IN(21491,21492) AND tenant_id IN(1,1008): 两租户 view_definition 逐字相同
-- 上游正常（排除上游缺失，均在 marketing 租户执行）SELECT * FROM oceanbase.GV$SESSTAT LIMIT 1;  -- ✅SELECT * FROM oceanbase.V$STATNAME LIMIT 1;  -- ✅

淇铭 · 2026 年6 月 30 日 16:54

你之前做过升级么？如果升级过从什么版本升级上来的

– RS 升级任务
SELECT job_id, job_type, job_status, result_code, tenant_id,
gmt_create, gmt_modified, extra_info
FROM oceanbase.DBA_OB_ROOTSERVICE_JOB
WHERE job_type LIKE ‘%UPGRADE%’
ORDER BY gmt_create DESC LIMIT 20;

– 巡检状态
SELECT * FROM oceanbase.GV$OB_ROOTSERVICE_EVENT_HISTORY
WHERE event_name LIKE ‘%inspection%’ OR event_name LIKE ‘%upgrade%’
ORDER BY gmt_create DESC LIMIT 20;

AntTech_2GDURQ · 2026 年6 月 30 日 17:02

@淇铭

SELECT * FROM oceanbase.__all_rootservice_job
→ WHERE job_type LIKE ‘%UPGRADE%’
→ ORDER BY gmt_create DESC LIMIT 20;
Empty set (0.004 sec)

SELECT TIMESTAMP, MODULE, EVENT, NAME1, VALUE1, NAME2, VALUE2
→ FROM oceanbase.DBA_OB_ROOTSERVICE_EVENT_HISTORY
→ WHERE MODULE LIKE ‘%upgrade%’ OR EVENT LIKE ‘%upgrade%’
→ ORDER BY TIMESTAMP DESC LIMIT 30;
Empty set (0.004 sec)

淇铭 · 2026 年6 月 30 日 17:07

没有做过升级么？

AntTech_2GDURQ · 2026 年6 月 30 日 17:10

@淇铭没有升级，一开始就是这个版本

淇铭 · 2026 年6 月 30 日 17:17

查一下信息看看
– 集群版本

SELECT * FROM oceanbase.DBA_OB_CLUSTER_VERSION;

– 租户 1008 信息

SELECT TENANT_ID, TENANT_NAME, TENANT_TYPE, STATUS, LOCKED, TENANT_ROLE

FROM oceanbase.DBA_OB_TENANTS

WHERE TENANT_ID = 1008;

– 逐层探测（哪条先报 1356，问题就在该层或其依赖）
SELECT COUNT(*) FROM oceanbase.V$STATNAME
WHERE STAT_ID IN (200001,200002,200010,200011,200005,200006);

SELECT COUNT(*) FROM oceanbase.GV$SESSTAT LIMIT 1;

SELECT COUNT(*) FROM oceanbase.GV$OB_SESS_TIME_MODEL LIMIT 1;

SELECT COUNT(*) FROM oceanbase.V$OB_SESS_TIME_MODEL LIMIT 1;

SELECT table_id, table_name, table_type, schema_version
FROM oceanbase.CDB_TABLES
WHERE tenant_id = 1008
AND table_id IN (21491, 21492, 21004, 21006);

– 查看实际存储的 view definition
SELECT tenant_id, table_id, view_definition
FROM oceanbase.__all_virtual_table
WHERE tenant_id = 1008
AND table_id IN (21491, 21492);

– 等价于 RS 巡检中的 expand 逻辑
SELECT FIELD
FROM oceanbase.__tenant_virtual_table_column
WHERE TABLE_ID = 21492;

AntTech_2GDURQ · 2026 年6 月 30 日 17:29

-- 集群版本（⚠️ DBA_OB_CLUSTER_VERSION 在 4.5 不存在！用这个）
Query OK, 0 rows affected (0.000 sec)

SELECT DISTINCT value FROM oceanbase.GV$OB_PARAMETERS WHERE name='min_observer_version';
+---------+
| value   |
+---------+
| 4.5.0.0 |
+---------+
1 row in set (0.010 sec)


 -- 租户 1008 信息
Query OK, 0 rows affected (0.000 sec)

 SELECT TENANT_ID, TENANT_NAME, TENANT_TYPE, STATUS, LOCKED, TENANT_ROLE
    -> FROM oceanbase.DBA_OB_TENANTS WHERE TENANT_ID = 1008;
+-----------+-------------+-------------+--------+--------+-------------+
| TENANT_ID | TENANT_NAME | TENANT_TYPE | STATUS | LOCKED | TENANT_ROLE |
+-----------+-------------+-------------+--------+--------+-------------+
|      1008 | marketing   | USER        | NORMAL | NO     | PRIMARY     |
+-----------+-------------+-------------+--------+--------+-------------+
1 row in set (0.012 sec)


 -- 4 个视图的 schema 版本（⚠️ CDB_TABLES 是 Oracle 风格、无 table_id/schema_version 列，换 __all_virtual_table）
Query OK, 0 rows affected (0.000 sec)

SELECT tenant_id, table_id, table_name, table_type, schema_version
    -> FROM oceanbase.__all_virtual_table
    -> WHERE tenant_id = 1008 AND table_id IN (21491, 21492, 21004, 21006);
+-----------+----------+-----------------------+------------+------------------+
| tenant_id | table_id | table_name            | table_type | schema_version   |
+-----------+----------+-----------------------+------------+------------------+
|      1008 |    21004 | GV$SESSTAT            |          1 | 1778496755857112 |
|      1008 |    21006 | V$STATNAME            |          1 | 1778496756024352 |
|      1008 |    21491 | GV$OB_SESS_TIME_MODEL |          1 | 1778501252995856 |
|      1008 |    21492 | V$OB_SESS_TIME_MODEL  |          1 | 1778501253087960 |
+-----------+----------+-----------------------+------------+------------------+
4 rows in set (0.006 sec)


 -- 实际存储的 view definition
Query OK, 0 rows affected (0.000 sec)

 SELECT tenant_id, table_id, view_definition
    -> FROM oceanbase.__all_virtual_table
    -> WHERE tenant_id = 1008 AND table_id IN (21491, 21492);
+-----------+----------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| tenant_id | table_id | view_definition                                                                                                                                                                                                                                                                                                                                                                     |
+-----------+----------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|      1008 |    21491 |    SELECT     SID AS SID,     gv$sesstat.CON_ID AS TENANT_ID,     SVR_IP AS SVR_IP,     SVR_PORT AS SVR_PORT,     STAT_ID AS STAT_ID,     NAME AS STAT_NAME,     VALUE AS VALUE   FROM     oceanbase.GV$SESSTAT   left join     oceanbase.v$statname   on gv$sesstat.`statistic#`=v$statname.`statistic#`   WHERE     STAT_ID in (200001, 200002, 200010, 200011, 200005, 200006);  |
|      1008 |    21492 |    SELECT SID,     TENANT_ID,     SVR_IP,     SVR_PORT,     STAT_ID,     STAT_NAME,     VALUE   FROM     oceanbase.GV$OB_SESS_TIME_MODEL   WHERE SVR_IP = HOST_IP() AND SVR_PORT = RPC_PORT()                                                                                                                                                                                       |
+-----------+----------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
2 rows in set (0.005 sec)

 -- Bye


SELECT effective_tenant_id();   -- 先确认！必须显示 1008，不是 1
+-----------------------+
| effective_tenant_id() |
+-----------------------+
|                  1008 |
+-----------------------+
1 row in set (0.001 sec)


 -- 逐层探测：哪条先报 ERROR 1356，坏点就在该层
Query OK, 0 rows affected (0.000 sec)

SELECT COUNT(*) FROM oceanbase.V$STATNAME
    ->   WHERE STAT_ID IN (200001,200002,200010,200011,200005,200006);  -- 字典表，预期 OK
+----------+
| COUNT(*) |
+----------+
|        6 |
+----------+
1 row in set (0.002 sec)

SELECT COUNT(*) FROM oceanbase.GV$SESSTAT;                       -- 会话统计，预期 OK
+----------+
| COUNT(*) |
+----------+
|   269541 |
+----------+
1 row in set (0.070 sec)

SELECT COUNT(*) FROM oceanbase.GV$OB_SESS_TIME_MODEL;            -- 预期这里开始报 1356
ERROR 1356 (42S22): View 'oceanbase.GV$OB_SESS_TIME_MODEL' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them
SELECT COUNT(*) FROM oceanbase.V$OB_SESS_TIME_MODEL;             -- 预期报 1356
ERROR 1356 (42S22): View 'oceanbase.GV$OB_SESS_TIME_MODEL' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them

 -- RS 巡检的等价 expand 逻辑（预期复现 -5231 / 报错）
Query OK, 0 rows affected (0.000 sec)

 SELECT FIELD FROM oceanbase.__tenant_virtual_table_column WHERE TABLE_ID = 21492;
ERROR 1356 (42S22): View 'oceanbase.V$OB_SESS_TIME_MODEL' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them
--- Bye

淇铭 · 2026 年6 月 30 日 17:35

SELECT s.SID, s.CON_ID AS TENANT_ID, s.SVR_IP, s.SVR_PORT,
n.STAT_ID, n.NAME AS STAT_NAME, s.VALUE
FROM oceanbase.GV$SESSTAT s
LEFT JOIN oceanbase.V$STATNAME n
ON s.STATISTIC# = n.STATISTIC#
WHERE n.STAT_ID IN (200001, 200002, 200010, 200011, 200005, 200006)
LIMIT 5; -查一下这个信息

sys租户下执行一下这个
ALTER SYSTEM UPGRADE VIRTUAL SCHEMA;

执行完以后在查一下结果count(1)
SELECT COUNT(1) FROM oceanbase.GV$OB_SESS_TIME_MODEL;
SELECT COUNT(1) FROM oceanbase.V$OB_SESS_TIME_MODEL;

SELECT view_definition
FROM oceanbase.__all_virtual_table
WHERE tenant_id = 1008 AND table_id = 21491;

AntTech_2GDURQ · 2026 年6 月 30 日 17:46

ALTER SYSTEM UPGRADE VIRTUAL SCHEMA 已在 sys 租户执行成功(Query OK, 0.217s),但 marketing(1008)的 GV$OB_SESS_TIME_MODEL 仍报 ERROR 1356,view_definition 无变化。

分析:UPGRADE VIRTUAL SCHEMA 按 schema 定义比对决定是否升级(batch_upgrade_ 中仅 check_table_schema 返回 OB_SCHEMA_ERROR 的表才升级),而该视图定义与 hard-code 完全一致 → 被判定无需升级、跳过。坏的是视图运行态/依赖解析(expand 报 -5231 OB_ERR_VIEW_INVALID),非定义文本,该命令未触及。

请问下一步:① 重启 marketing 租户能否触发系统视图重新 resolve?② 是否有强制重建指定视图依赖的内部命令(而非按定义比对)?③ 还是需要补丁版本?

@淇铭

淇铭 · 2026 年6 月 30 日 18:34

SELECT s.SID, s.CON_ID AS TENANT_ID, s.SVR_IP, s.SVR_PORT,
n.STAT_ID, n.NAME AS STAT_NAME, s.VALUE
FROM oceanbase.GV$SESSTAT s
LEFT JOIN oceanbase.V$STATNAME n
ON s.STATISTIC# = n.STATISTIC#
WHERE n.STAT_ID IN (200001, 200002, 200010, 200011, 200005, 200006)
LIMIT 5; 这个信息查一下

完整的报错observer.log日志提供一下 rootservice.log日志也提供一下

AntTech_2GDURQ · 2026 年6 月 30 日 19:23

SELECT s.SID, s.CON_ID AS TENANT_ID, s.SVR_IP, s.SVR_PORT,
→ n.STAT_ID, n.NAME AS STAT_NAME, s.VALUE
→ FROM oceanbase.GV$SESSTAT s
→ LEFT JOIN oceanbase.V$STATNAME n
→ ON s.STATISTIC# = n.STATISTIC#
→ WHERE n.STAT_ID IN (200001, 200002, 200010, 200011, 200005, 200006)
→ LIMIT 5;
ERROR 1054 (42S22): Unknown column ‘s.STATISTIC’ in ‘on clause’

@淇铭

AntTech_2GDURQ · 2026 年6 月 30 日 19:37

observer.log 2026-06-30 19:27:04 租户 1008 查询 GV$OB_SESS_TIME_MODEL 触发：
[SQL.RESV] resolve_table_column_ref (ob_select_resolver.cpp:5611) errcode=-5217
resolve table column expr failed (q_name={table_name:“gv$sesstat”, column:“statistic#”})
report_user_error_msg (ob_dml_resolver.cpp:3343) errcode=-5217
Unknown column ‘gv$sesstat.statistic#’ in ‘on clause’
[SQL.RESV] resolve_joined_table (ob_dml_resolver.cpp:6160) errcode=-5217 resolve and split sql expr failed
[SQL.RESV] resolve_table (ob_dml_resolver.cpp:5926) errcode=-5217 resolve joined table failed
do_expand_view (ob_dml_resolver.cpp:8276) errcode=-5231
View ‘oceanbase.GV$OB_SESS_TIME_MODEL’ references invalid table(s) or column(s) or function(s)…
[SQL.RESV] resolve_basic_table_without_cte (ob_dml_resolver.cpp:3796) errcode=-5231
expand view failed: table_name=“GV$OB_SESS_TIME_MODEL”, ref_id=21491,
ddl_schema_version=1778501252995856, is_view_table=true
[SQL] generate_stmt (ob_sql.cpp:3264) errcode=-5231 failed to resolve
[SERVER] send_error_packet ob_error=-5231, client error=1356

@淇铭

AntTech_MSPSKN · 2026 年7 月 1 日 08:09

学到了。

淇铭 · 2026 年7 月 1 日 10:16

SELECT s.SID, s.CON_ID AS TENANT_ID, s.SVR_IP, s.SVR_PORT,
n.STAT_ID, n.NAME AS STAT_NAME, s.VALUE
FROM oceanbase.GV$SESSTAT s
LEFT JOIN oceanbase.V$STATNAME n
ON s.STATISTIC# = n.STATISTIC#
WHERE n.STAT_ID IN (200001, 200002, 200010, 200011, 200005, 200006)
LIMIT 5;

字段STATISTIC#加上反引号在查一下

AntTech_2GDURQ · 2026 年7 月 1 日 10:20

SELECT s.SID, s.CON_ID AS TENANT_ID, s.SVR_IP, s.SVR_PORT,
    -> n.STAT_ID, n.NAME AS STAT_NAME, s.VALUE
    -> FROM oceanbase.GV$SESSTAT s
    -> LEFT JOIN oceanbase.V$STATNAME n
    -> ON s.`STATISTIC#` = n.`STATISTIC#`
    -> WHERE n.STAT_ID IN (200001, 200002, 200010, 200011, 200005, 200006)
    -> LIMIT 5;
+---------------------+-----------+---------------+----------+---------+--------------------+-------+
| SID                 | TENANT_ID | SVR_IP        | SVR_PORT | STAT_ID | STAT_NAME          | VALUE |
+---------------------+-----------+---------------+----------+---------+--------------------+-------+
|          3221517056 |      1008 | 10.104.16.190 |     2882 |  200010 | non idle wait time |     0 |
|          3221517056 |      1008 | 10.104.16.190 |     2882 |  200011 | idle wait time     |     0 |
|          3221650144 |      1008 | 10.104.16.190 |     2882 |  200010 | non idle wait time |     0 |
|          3221650144 |      1008 | 10.104.16.190 |     2882 |  200011 | idle wait time     |     0 |
| 1152921504648530320 |      1008 | 10.104.16.191 |     2882 |  200010 | non idle wait time |     0 |
+---------------------+-----------+---------------+----------+---------+--------------------+-------+
5 rows in set (0.033 sec)

@淇铭

AntTech_2GDURQ · 2026 年7 月 1 日 10:21

SELECT s.SID, s.CON_ID AS TENANT_ID, s.SVR_IP, s.SVR_PORT,
    -> n.STAT_ID, n.NAME AS STAT_NAME, s.VALUE
    -> FROM oceanbase.GV$SESSTAT s
    -> LEFT JOIN oceanbase.V$STATNAME n
    -> ON s.`STATISTIC#` = n.`STATISTIC#`
    -> WHERE n.STAT_ID IN (200001, 200002, 200010, 200011, 200005, 200006)
    -> LIMIT 5;
+------------+-----------+---------------+----------+---------+--------------------+---------+
| SID        | TENANT_ID | SVR_IP        | SVR_PORT | STAT_ID | STAT_NAME          | VALUE   |
+------------+-----------+---------------+----------+---------+--------------------+---------+
| 3221600632 |         1 | 10.104.16.190 |     2882 |  200010 | non idle wait time |       0 |
| 3221600632 |         1 | 10.104.16.190 |     2882 |  200011 | idle wait time     |       0 |
| 3221622008 |         1 | 10.104.16.190 |     2882 |  200010 | non idle wait time |       0 |
| 3221622008 |         1 | 10.104.16.190 |     2882 |  200011 | idle wait time     |       0 |
| 3221749992 |         1 | 10.104.16.191 |     2882 |  200010 | non idle wait time | 6303477 |
+------------+-----------+---------------+----------+---------+--------------------+---------+
5 rows in set (0.031 sec)

@淇铭上面是业务租户，这个是 sys 租户，结果好像都一样

淇铭 · 2026 年7 月 1 日 10:27

日志信息能提供多一点么？rootservice.log也查一下是否有

淇铭 · 2026 年7 月 1 日 10:36

SHOW VARIABLES like ‘%lower_case_table_names%’; 查一下这个变量

AntTech_2GDURQ · 2026 年7 月 1 日 10:49

 SHOW VARIABLES like '%lower_case_table_names%';
+------------------------+-------+
| Variable_name          | Value |
+------------------------+-------+
| lower_case_table_names | 2     |
+------------------------+-------+
1 row in set (0.005 sec)

淇铭 · 2026 年7 月 1 日 10:51

alter system set enable_rich_error_msg=true; --sys租户下执行
-业务租户下执行查询视图如：
obclient [test]> select count(*) from t2;
ERROR 1146 (42S02): Table ‘test.t2’ doesn’t exist
[xx.xx.xx.1:2882] [2024-04-13 20:10:20.292087] [YB420BA1CC68-000615A0A8EA5E38-0-0]

[root@x.x.x.1 ~]$ grep “YB420BA1CC68-000615A0A8EA5E38-0-0” rootservice.log
[root@x.x.x.1 ~]$ grep “YB420BA1CC68-000615A0A8EA5E38-0-0” observer.log

alter system set enable_rich_error_msg=false; --sys租户下执行