You are about to plug a multi-terabyte non-CDB into an existing multitenant container database (CDB) as a pluggable database (PDB). The characteristics of the non-CDB are as follows…

Transportable database (full transportable export/import) requires character set compatibility between source and target; because WE8ISO8859P15 and AL32UTF8 are incompatible in the required direction, this technique cannot be used directly.

Transportable tablespace supports cross-character-set migration by using RMAN to convert datafiles during transport, avoiding a full logical export of terabytes of data. It minimizes downtime because datafiles are moved directly rather than being unloaded and reloaded row-by-row, while still handling the WE8ISO8859P15-to-AL32UTF8 character conversion.

Data Pump full export/import performs a logical row-by-row migration, which is prohibitively slow for a multi-terabyte database and results in far more downtime than a transportable approach.

The DBMS_PDB package requires that the non-CDB's character set be binary-compatible with or a strict subset of the CDB's character set; WE8ISO8859P15 does not satisfy this requirement relative to AL32UTF8, so the plug operation would fail.

RMAN alone cannot perform the logical character set data conversion required when migrating from WE8ISO8859P15 to AL32UTF8; RMAN handles physical datafile operations, not character encoding transformation of stored data.