My Oracle Support Banner

Avoiding ORA-01114 When Altering Target Tablespace READ WRITE with Transportable Tablespaces (Doc ID 69373.1)

Last updated on MARCH 10, 2020

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 8.0.3 to 11.2]
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Generic UNIX


When using the Transportable Tablespace (TTS) feature, if the file
permissions are not set correctly, then it is possible to encounter ORA-1114,
ORA-1110, ORA-27091 when attempting to set the tablespace to READ WRITE.

For example, the source site has Unix user "oracle" belonging to the "dba" group.
Target site has Unix users "oracle" and "oracle2" as members of the
"dba" group.  However, "oracle2" owns the ORACLE_HOME and the oracle

You have done the following steps:
  1. Logged on to Unix as an user belonging to the dba group (say oracle).
  2. Created a tablespace TEST.
  3. Alter tablespace TEST read only.
  4. Exported the metadata pertaining to the tablespace.
  5. Physically copied the datafile across to the target location using ftp as user "oracle".
  6. Imported the metadata into the target location.
In the target location when you try to change the tablespace status, you
get errors similar to the following :


The note is intended for DBAs moving tablespaces from  a source to target database using TTS.


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.