expdp full export not exporting all schemas

On Oracle 12c, fairly new database with APEX installed. I do a

expdp \"/ as sysdba\"  directory=dp_dir full=y dumpfile=full.dmp logfile=full.log

And I am getting just a few tables from SYS and SYSTEM exported:

```
. . exported "SYS"."KU$_USER_MAPPING_VIEW" 5.882 KB 24 rows
. . exported "SYS"."AUD$" 0 KB 0 rows
. . exported "SYS"."DAM_CLEANUP_EVENTS$" 0 KB 0 rows
. . exported "SYS"."DAM_CLEANUP_JOBS$" 0 KB 0 rows
. . exported "SYS"."DAM_CONFIG_PARAM$" 6.523 KB 14 rows
. . exported "SYS"."TSDP_ASSOCIATION$" 0 KB 0 rows
. . exported "SYS"."TSDP_CONDITION$" 0 KB 0 rows
. . exported "SYS"."TSDP_FEATURE_POLICY$" 0 KB 0 rows
. . exported "SYS"."TSDP_PARAMETER$" 5.945 KB 1 rows
. . exported "SYS"."TSDP_POLICY$" 5.914 KB 1 rows
. . exported "SYS"."TSDP_PROTECTION$" 0 KB 0 rows
. . exported "SYS"."TSDP_SENSITIVE_DATA$" 0 KB 0 rows
. . exported "SYS"."TSDP_SENSITIVE_TYPE$" 0 KB 0 rows
. . exported "SYS"."TSDP_SOURCE$" 0 KB 0 rows
. . exported "SYS"."TSDP_SUBPOL$" 6.320 KB 1 rows
. . exported "SYSTEM"."REDO_DB" 25.58 KB 1 rows
. . exported "SYSTEM"."REDO_LOG" 0 KB 0 rows
. . exported "SYS"."FGA_LOG$FOR_EXPORT" 0 KB 0 rows
. . exported "SYSTEM"."SCHEDULER_JOB_ARGS" 8.671 KB 4 rows
. . exported "SYSTEM"."SCHEDULER_PROGRAM_ARGS" 10.21 KB 22 rows
. . exported "SYS"."AUDTAB$TBS$FOR_EXPORT" 5.953 KB 2 rows
. . exported "SYS"."DBA_SENSITIVE_DATA" 0 KB 0 rows
. . exported "SYS"."DBA_TSDP_POLICY_

This is expected behaviour.

FULL


A full export does not, by default, export system schemas that contain
Oracle-managed data and metadata. Examples of system schemas that are
not exported by default include SYS, ORDSYS, and MDSYS.

12.1.0.1 EXPDP Does Not Export APEX Schema (Doc ID 1912162.1)


This is the expected behavior in 12.1.0.X version,


This was added, in part, to avoid problem with common objects in a
multi-tenant DB, but certainly has been very helpful in eliminating
errors report - particularly in full import. The bit is called
'ORACLE_MAINTAINED' in [user,all,dba]_objects dictionary views. Seems
pretty reasonable that Oracle maintained objects are not be moved
around by datapump.

StackExchange Database Administrators Q#139767, answer score: 3