My Oracle Support Banner

The Character Set Check Performed When Plugging In a Transportable Tablespace (Doc ID 297396.1)

Last updated on MAY 13, 2024

Applies to:

Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.


The purpose of this document is to explain the character set
compatibility check that is performed by the Oracle Database server
when plugging in (importing) a transportable tablespace set.


The character set compatibility check applies to any transportable
tablespace set being plugged into an Oracle database.

The exact compatibility rules used depend on the database server
version of both the source and the target databases.

The most significant change to the compatibility rules has been
introduced in Oracle10g Release 1 Patch Set 1 (
Unfortunately, there is a bug in this implementation that
causes incompatible transportable tablespaces to be accepted
for import when they should not be. See section 2 below.
The bug was fixed in version 10.2 and sections 3 and 4
describe this new feature.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.