OATM Utility Fails To Move Table FPA.AW$FPAPJP with ORA-14257 cannot move partition other than a Range or Hash partition
(Doc ID 463456.1)
Last updated on AUGUST 02, 2013
Applies to:Oracle OLAP - Version 10.2.0.4 to 10.2.0.5 [Release 10.2]
Information in this document applies to any platform.
***Checked for relevance on 27-Jun-2012***
OATM Oracle Applications Tablespace Migration Utility failed to move table FPA.AW$FPAPJP.
Command generated by OATM Utility was:
ALTER TABLE "FPA"."AW$FPAPJP" MOVE PARTITION PTN1 TABLESPACE
APPS_TS_TX_DATA LOB (AWLOB) STORE
AS (TABLESPACE APPS_TS_TX_DATA) NOPARALLEL
And it generates the following error:
ORA-14257: cannot move partition other than a Range or Hash partition
Therefore OATM Utility left objects in FPAD tablespace.
How to move this object FPA.AW$FPAPJP to the proper tablespace?
What is the proper tablespace?
How to rebuild and partition this table in the proper tablespace?
Release 11i.10 introduces the new Oracle Applications Tablespace Model (OATM), with fewer, consolidated tablespaces (twelve, including three system tablespaces: temporary, system and undo segments) and support for locally managed tablespaces. In prior 11i releases of the E-Business Suite, each product was allocated two tablespaces, one for data and one for indexes. Customers with previous releases of the E-Business Suite (11i/10.7) may adopt OATM using the Oracle Applications Tablespace Migration Utility, which is available in 11i.10 as well as in standalone mode. The Migration Utility is a menu-based PERL program and a series of sizing estimate reports that enables conversion of E-Business Suite applications schemas either in a single comprehensive migration or a phased, schema-by-schema migration. In general Oracle recommends performing a single comprehensive migration, however this requires a sufficient amount of down time and disk space. Oracle does not support partial migration of tablespaces. You must still migrate all schemas when performing a phased schema-by-schema
With OATM, each database object is mapped to a tablespace based on its Input/Output characteristics, which include object size, life span, access methods and locking granularity. This model allows for easier maintenance, and reduced space usage for the E-Business Suite.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|