System databases that are blocked by DMS by default - Data Management

If an instance in Data Management (DMS) is in Security Collaboration mode, its system databases are blocked by default during metadata collection. This topic lists the system databases that are blocked by default for different database types.

Background information

After you add an instance to Data Management (DMS), DMS automatically collects metadata from the databases in the instance. If the instance is in Security Collaboration mode, DMS blocks the system databases during metadata collection to protect them and prevent user interference. For more information about metadata, see Metadata.

Note

If an instance is in Flexible Management or Stable Change mode, DMS does not block its system databases during metadata collection.

Limits

Users with the regular user role cannot query the default blocked system databases or request permissions to query them.

Note

Only users with the administrator or DBA role have permissions to query the system databases of an instance. For more information about how to manage user roles, see User management.

The following table lists the system databases that DMS blocks by default. You can also customize which system databases to block. For more information, see Customize system databases to block in DMS.

Database type	Default blocked system databases
MySQL: RDS for MySQL, PolarDB for MySQL, MyBase for MySQL, and other source MySQL databases MariaDB: RDS for MariaDB and other source MariaDB databases	mysql, tmp, sys, __recycle_bin__, innodb test, sbtest information_schema, performance_schema
PolarDB Distributed Edition	mysql, test information_schema, performance_schema
SQL Server: RDS for SQL Server, MyBase for SQL Server, and other source SQL Server databases	master, model, msdb, tempdb, rdscore
PostgreSQL: RDS for PostgreSQL, PolarDB for PostgreSQL, MyBase for PostgreSQL, AnalyticDB for PostgreSQL, and other source PostgreSQL databases	sys, dbo, information_schema pg_catalog, pgagent
PolarDB for PostgreSQL (Compatible with Oracle)	Schemas: sys, dbo, information_schema, msg_prop_t pg_catalog, pgagent aq$_agent, aq$_descriptor, aq$_reg_info dbms_alert, dbms_aq, dbms_aqadm, dbms_crypto, dbms_job, dbms_lob, dbms_lock, dbms_mview, dbms_output, dbms_pipe, dbms_profiler, dbms_random, dbms_redact, dbms_rls, dbms_scheduler, dbms_session, dbms_sql, dbms_utility utl_encode, utl_file, utl_http, utl_mail, utl_raw, utl_smtp, utl_tcp, utl_url Database: polardb_admin
OceanBase Database (MySQL Mode)	mysql, test, oceanbase, information_schema
OceanBase Database (Oracle Mode) and Oracle	Schemas: STDBYPERF, READONLY, ANYSQL, DBFLASH, TBSEARCH, MONITOR, MANAGER, ANONYMOUS, SCOTT, IDB_RND, DIP, ORACLE_OCM, OUTLN, DBSNMP, PERFSTAT, SEARCH, TOOLS, TBDUMP, XDB, XS$NULL, SH, PARACHK, ALIHA, MYTEST OPS$ADMIN, B2BDBA, OPERATOR, IDBUSER, IDBADMIN, DEVDBA RND, ERND SYS, SYSTEM, SYSMAN APPQOSSYS, TSMSYS, EXFSYS, WMSYS, DMSYS, CTXSYS, MDSYS, ORDSYS, OWBSYS, OLAPSYS OPSDBA, OPS$ORACLE, OPS$NAGIOS, OPS$OPSDBA
DM Database	CTISYS, SYS, SYSAUDITOR, SYSSSO
Db2	None
Redis	None
MongoDB	admin, local
Lindorm-CQL	system, system_auth, system_schema
Lindorm-SQL	None
Cassandra	system, system_auth, system_cloud, system_distributed, system_schema, system_traces
GDB	None
AnalyticDB for MySQL 2.0	None
AnalyticDB for MySQL 3.0	mysql, tmp, sys test, sbtest information_schema, performance_schema innodb, analyticdb
DLA	None
ClickHouse	system
MaxCompute	information_schema
Hologres	hologres, hologres_sample, hologres_statistic, hologres_streaming_mv, information_schema, pg_catalog Note By default, schemas are blocked.