This topic describes some Oracle-compatible views in a MySQL tenant of OceanBase Database.
Storage location
Oracle-compatible views in MySQL tenants and the sys tenant are stored in the OceanBase database and can be accessed only from MySQL tenants and the sys tenant.
Characteristics
Oracle-compatible views in MySQL tenants have the following similarities with and differences from standard Oracle views.
Similarities:
- The view names are prefixed with
DBA_. - The column names and implementation are consistent with standard Oracle views prefixed with
DBA_.
- The view names are prefixed with
Differences:
The columns with the same name have different meanings. In a standard Oracle views, the
OWNERcolumn representsUSER, while theCON_IDcolumn representscontainer_id. However, in a MySQL tenant, they correspond toDatabaseandtenant_idrespectively.
View types
Oracle-compatible views in MySQL tenants include data dictionary views and dynamic performance views.
- Data dictionary views are prefixed with
oceanbase.DBA_and display information about some database objects in the current tenant. - Dynamic performance views are prefixed with
oceanbase.V$oroceanbase.GV$. Almost every view prefixed withoceanbase.V$has a corresponding view prefixed withoceanbase.GV$. In an OceanBase cluster, all views prefixed withoceanbase.GV$that meet the conditions are returned when you queryoceanbase.V$*views.