Activity

1. adela-bytebase commented on Sep 3, 2026

   

   adela-bytebase

   on Sep 3, 2026

   Contributor

   More actions

   Thanks for the detailed report! You're right — Bytebase doesn't currently discover OceanBase materialized views during schema sync, so they're missing from the schema browser, and queries against them then fail the resource lookup during masking checks.

   Could you run these on your OceanBase 4.3.5 instance and share the output (redact names as needed)? This will help us see exactly where the metadata is exposed.

   SELECT TABLE_NAME, TABLE_TYPE FROM information_schema.TABLES
   WHERE TABLE_SCHEMA = '<your_database>' AND TABLE_NAME = '<your_materialized_view>';
   
   SHOW TABLES FROM oceanbase LIKE '%MVIEW%';
   SHOW TABLES FROM information_schema LIKE '%MVIEW%';
   
2. Myifan610 commented on Sep 3, 2026

   

   Myifan610

   on Sep 3, 2026 – with ChatGPT Codex Connector

   Author

   More actions

   Thanks. I ran the queries on OceanBase 4.3.5.

   Only the following command returned rows:

   SHOW TABLES FROM oceanbase LIKE '%MVIEW%';

   Output:

   Tables_in_oceanbase (%MVIEW%)
   DBA_MVIEWS
   DBA_MVIEW_DEPS
   DBA_MVIEW_LOGS
   DBA_MVIEW_RUNNING_JOBS
   __all_mview
   __all_mview_dep
   __all_mview_refresh_change_stats
   __all_mview_refresh_run_stats
   __all_mview_refresh_stats
   __all_mview_refresh_stats_params
   __all_mview_refresh_stats_sys_defaults
   __all_mview_refresh_stmt_stats
   

   These two queries returned no rows:

   SELECT TABLE_NAME, TABLE_TYPE
   FROM information_schema.TABLES
   WHERE TABLE_SCHEMA = '<your_database>'
     AND TABLE_NAME = '<your_materialized_view>';
   
   SHOW TABLES FROM information_schema LIKE '%MVIEW%';

   However, querying DBA_MVIEWS directly returns the materialized-view names:

   SELECT MVIEW_NAME FROM DBA_MVIEWS;

   Output:

   MVIEW_NAME
   car_holiday_warn_summary
   mv_car_fuelling_info_summary
   mv_car_fuelling_info_summary
   mv_dwd_use_car_cost_wide
   mv_stat_by_use_dept
   car_holiday_warn_summary
   mv_test_mv
   mv_user_stat
   mv_stat_by_use_dept
   mv_dwd_use_car_cost_wide
   v_car_number_owner_dept_summary
   v_car_number_owner_dept_summary
   v_car_number_use_dept_summary
   v_car_number_use_dept_summary
   

   So on this OceanBase instance, the materialized-view metadata appears to be exposed through oceanbase.DBA_MVIEWS, but not through information_schema.TABLES.