What system databases are blocked by DMS by default - Data Management

By default, if you set the control mode of a database instance to Security Collaboration in Data Management, the system databases of the instance are blocked when metadata is collected from the instance. This topic describes the system databases that are blocked by default for different instance types.

Background information

After you register a database instance in DMS, DMS automatically collects metadata (data dictionary) from the databases in the instance. To protect the system databases and reduce the interference of the system databases in user business, if the control mode of the instance is set to Security Collaboration, DMS automatically blocks the system databases when metadata is collected from the instance. For more information about metadata, see Metadata.

Note

If an instance is managed in Flexible Management or Stable Change mode, DMS does not block the system databases of the instance when metadata is collected from the instance.

Limits

Regular users cannot query the blocked system databases of the instance, or apply for permissions to query system databases.

Note

Only the DMS administrator or database administrator (DBA) has permissions to query the system databases of the instance. For more information about how to change your role, see Manage users.

The following table describes the system databases blocked by DMS by default for various types of instances. You can also customize the system databases to be blocked for an instance type. For more information, see Block system databases in DMS.

Instance type	System database to be blocked
MySQL: ApsaraDB RDS for MySQL, PolarDB for MySQL, MyBase for MySQL, and MySQL databases from other sources MariaDB: ApsaraDB for MariaDB and MariaDB databases from other sources	mysql, tmp, sys, __recycle_bin__, and innodb test and sbtest information_schema and performance_schema
PolarDB for Xscale	mysql and test information_schema and performance_schema
SQL Server: ApsaraDB RDS for SQL Server, MyBase for SQL Server, and SQL Server databases from other sources	master, model, msdb, tempdb, and rdscore
PostgreSQL: ApsaraDB RDS for PostgreSQL, PolarDB for PostgreSQL, MyBase for PostgreSQL, AnalyticDB for PostgreSQL, and PostgreSQL databases from other sources	sys, dbo, and information_schema pg_catalog and pgagent
PolarDB for PostgreSQL(Compatible with Oracle)	Schemas: sys, dbo, information_schema, and msg_prop_t pg_catalog and pgagent aq$_agent, aq$_descriptor, and 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, and dbms_utility utl_encode, utl_file, utl_http, utl_mail, utl_raw, utl_smtp, utl_tcp, and utl_url Database: polardb_admin
ApsaraDB for OceanBase in MySQL mode	mysql, test, oceanbase, and information_schema
ApsaraDB for OceanBase in 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, and MYTEST OPS$ADMIN, B2BDBA, OPERATOR, IDBUSER, IDBADMIN, and DEVDBA RND and ERND SYS, SYSTEM, and SYSMAN APPQOSSYS, TSMSYS, EXFSYS, WMSYS, DMSYS, CTXSYS, MDSYS, ORDSYS, OWBSYS, and OLAPSYS OPSDBA, OPS$ORACLE, OPS$NAGIOS, and OPS$OPSDBA
DM	CTISYS, SYS, SYSAUDITOR, and SYSSSO
Db2	N/A
ApsaraDB for Redis	N/A
ApsaraDB for MongoDB	admin and local
Lindorm-CQL	system, system_auth, and system_schema
Lindorm-SQL	N/A
ApsaraDB for Cassandra	system, system_auth, system_cloud, system_distributed, system_schema, and system_traces
GDB	N/A
AnalyticDB for MySQL V2.0	N/A
AnalyticDB for MySQL V3.0	mysql, tmp, and sys test and sbtest information_schema and performance_schema innodb and analyticdb
DLA	N/A
ApsaraDB for ClickHouse	system
MaxCompute	information_schema
Hologres	sys, dbo, information_schema, pg_catalo, and hawq_toolki