My Oracle Support Banner

TSPITR Expdp Phase Limits The Number of Exported Tablespaces, e.g. to 137 (Doc ID 1967439.1)

Last updated on MARCH 27, 2019

Applies to:

Oracle Database - Enterprise Edition - Version and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.


Performing TSPITR using RMAN. The recover tablespace command includes more than 137 tablespaces. In this case there were 240 tablespaces.

The recovery set of tablespaces is self contained and all works fine but the expdp phase only exports 137 tablespaces from the 240 as mentioned in the recover tablespace command.

Trying several times, the expdp phase always exports 137 tablespaces as maximum. There is no error and expdp completes successfully but simply skips the rest of the tablespaces after 137.


None, simply trying to perform TSPITR with more than 137 tablespaces.

The number of tabelspaces may differ, e.g. in another situation with a TSPITR of 231 tablespaces, the expdp exported the first 227 tablespaces.


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

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

In this Document

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