Help Center/ Database and Application Migration UGO/ FAQs/ Product Consulting/ Which Schemas in Source Databases Are Ignored for Migration?
Updated on 2024-11-07 GMT+08:00
View PDF
Share

Which Schemas in Source Databases Are Ignored for Migration?

Oracle as the Source

Schemas that are not collected:

APEX_050000, AUDSYS, ADAMS, ANONYMOUS,

AURORA$ORB$UNAUTHENTICATED, AWR_STAGE, APEX_030200, APEX_040200,

APEX_PUBLIC_USER, APPQOSSYS, BLAKE, CLARK, CSMIG,

CTXSYS, DBSNMP, DIP, DMSYS,

DSSYS, DEMO, DVSYS, DVF,

DBSFWUSER, EXFSYS, FLOWS_FILES,

GGSYS, GSMADMIN_INTERNAL, GSMCATUSER, GSMUSER

JONES, LBACSYS, MDDATA, MDSYS, MGMT_VIEW

OLAPSYS, ORACLE_OCM, ORDDATA, ORDPLUGINS

ORDSYS, OUTLN, OWBSYS, OWBSYS_AUDIT, OJVMSYS,

PERFSTAT, REMOTE_SCHEDULER_AGENT

SI_INFORMTN_SCHEMA, SPATIAL_CSW_ADMIN_USR,

SPATIAL_WFS_ADMIN_USR, SYS, SYSMAN, SPATIAL_CSW_ADMIN_USR, SYSBACKUP,

SYSKM, SYSDG, SYSRAC, SYS$UMF, SYSTEM,

TRACESVR, TSMSYS, WMSYS, XDB, XS$NULL, and GSMROOTUSER.

UGO does not collect the following tables:

  • System tables, for example, SYS_EXPORT_SCHEMA_ %
  • System objects starting with SYS_PLSQL are not collected.
  • Deleted objects starting with BIN$ are not collected.
  • Nested tables are not collected.

MySQL as the Source

INFORMATION_SCHEMA, MYSQL, PERFORMANCE_SCHEMA, and SYS

PostgreSQL as the Source Database

information_schema and a system schema prefixed with pg_, for example, pg_catalog, pg_toast, or pg_temp_1

Microsoft SQL Server as the Source Database

GUEST, INFORMATION_SCHEMA, SYS, DB_OWNER, DB_ACCESSADMIN, DB_SECURITYADMIN, DB_DDLADMIN, DB_BACKUPOPERATOR, DB_DATAREADER, DB_DATAWRITER, DB_DENYDATAREADER, and DB_DENYDATAWRITER

Parent topic: Product Consulting