My Oracle Support Banner

Tablespace With STORE IN Clause Would Not Change During Import Using REMAP_TABLESPACE With Interval Partitioning (Doc ID 958496.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Server - Enterprise Edition - Version: 11.1.0.7 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms

If a tablespace is getting remapped using datapump on a partitioned table, it is not getting remapped during import datapump.

Steps to Reproduce the issue.
---------------------------------------

++ Create a Partitioned table with 'STORE IN' Clause(Only with Interval Partitioning 11g introduced in 11g)
++ Export the table using datapump.
++ Import the table using REMAP_TABLESPACE option. It would get imported successfully.
++ However, when you query DBMS_METADATA.GET_DDL, the tablespace mentioned within STORE IN clause would not have changed.

Changes

This issue can only be reproduced in 11g with interval partitioning. This is introduced in 11g, it was not there in 10g or prior release.

Cause

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
  Symptoms
  Changes
  Cause
  Solution
  References

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